Shreyas Bethur

### Description of issue NI-FGEN devices are referred to as Signal Generators. The correct term is Waveform Generators. Usages: - https://github.com/ni/nimi-python/blob/02ebc9ed0bcc43f74d685b26f30a634c19a98e8c/src/nifgen/metadata/config.py#L58 NI-SCOPE devices are referred to as High Speed Digitizers....

### Description of issue Due to a bug in NI-DCPower driver runtime 2022 Q3 (Internal error [AB#1973297](https://dev.azure.com/ni/DevCentral/_workitems/edit/1973297)), doing self_cal on a simulated session with a resource name that doesn't match...

### Description of issue On a multi-instrument session in `niscope`, any method that returns `MeasurementStats` or ` WaveformInfo` object (fetch(), read(), and friends) returns wrong data when the channel repeatability...

Documentation for public custom types is sourced in metadata of properties/methods that use them

1

### Description of issue There are custom types that are accepted/returned by public methods: - `WaveformInfo` by `fetch`, `fetch_into`, and `read` methods in `niscope` - `MeasurementStats` by `fetch_measurement_stats` method in...

Stop using DAQmx-based simulated device in nifgen system tests

5

- [x] This contribution adheres to [CONTRIBUTING.md](https://github.com/ni/nimi-python/blob/master/CONTRIBUTING.md). ~- [ ] I've updated [CHANGELOG.md](https://github.com/ni/nimi-python/blob/master/CHANGELOG.md) if applicable.~ ~- [ ] I've added tests applicable for this pull request~ ### What does this...

Add code coverage check to PR build

1

We currently use `coverage` tool to report the code coverage from unit and system tests. See e.g: https://github.com/ni/nimi-python/blob/266e87f372e27d4a05cbc637b0bbe8e5dc305726/generated/nidcpower/tox-system_tests.ini#L32 https://github.com/ni/nimi-python/blob/266e87f372e27d4a05cbc637b0bbe8e5dc305726/tox-travis.ini#L46 Logs: - https://app.travis-ci.com/github/ni/nimi-python/jobs/576582446#L2052 - https://github.com/ni/nimi-python/runs/7326743697?check_suite_focus=true#step:3:1027 We should looking into setting a...

niScope_GetChannelName() and niScope_GetChannelNameFromString() missing from niscope Python bindings

1

### Description of issue `niScope_GetChannelName()` and `niScope_GetChannelNameFromString()` are present in NI-SCOPE C API, but missing in `niscope` Python bindings. `get_channel_names(indices)` should be added to `niscope` Python bindings to cover for...

Returned parameter which is marked as unused in Python API still gets codegen-ed into the documentation

1

There is an existing bug with the codegen logic where return parameter which is marked as unused in Python API (i.e. by specifying 'use_in_python_api': False in python/functions/functions.hapigen) still gets codegen-ed...

nifgen API reference does not mention which properties and methods can be called on a repeated capabilities container

3

### Description of issue According to the documentation, [these ](https://nimi-python.readthedocs.io/en/1.3.3/nifgen/rep_caps.html#)repeated capabilities are supported in nifgen. But the API reference for properties and methods doesn't mention which of them can be...

For properties and method parameters that accept multiple types, documentation should promote the recommended type

1

### Description of issue The main idea being documentation should guide the users to use the most-pythonic type for any property or method parameter. e.g.: https://github.com/ni/nimi-python/blob/8540e86f00dc4b7aa9dbf5d905275db7255d9c7b/generated/nidigital/nidigital/session.py#L607 documentation says: ``` offsets...