Fix/float command resolution #503
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Each Command subclass for a SCPI instrument defines a "formatter" which translates an assigned value to a string that can get sent to the instrument hardware. In some cases, the default formatter is inadequate, and this fix lets the Command be instantiated with a formatter that overrides the generic one defined as a class variable for the Command class.
Example: FloatCommand defaults to the "{:E}" formatter, which produces a string with six digits of precision. This isn't sufficient to set frequency start, stop, and span for a VNA with better than 1 kHz resolution.
This fix updates the Agilent NetowrkAnalyzer to permit 1-Hz frequency resolution.