-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RFSG attenuation example #888
Merged
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
Signed-off-by: Gerardo Orozco <gorozco@ni.com>
reckenro
reviewed
Mar 20, 2023
reckenro
reviewed
Mar 20, 2023
reckenro
reviewed
Mar 20, 2023
reckenro
reviewed
Mar 20, 2023
reckenro
reviewed
Mar 20, 2023
Co-authored-by: Ryan Eckenrode <77176215+reckenro@users.noreply.github.com>
…/ni/grpc-device into users/gorozco/attenuationexample
…/ni/grpc-device into users/gorozco/attenuationexample
astarche
changed the title
Users/gorozco/attenuationexample
Add RFSG attenuation example
Mar 22, 2023
astarche
approved these changes
Mar 22, 2023
reckenro
reviewed
Mar 22, 2023
Co-authored-by: astarche <56981669+astarche@users.noreply.github.com>
Co-authored-by: Ryan Eckenrode <77176215+reckenro@users.noreply.github.com>
reckenro
requested changes
Mar 28, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're in the process of making the 2.1 release and I don't want anything going into main until we've bumped the exports from main to be 2.2. I'll reset myself and approve after the export version is bumped (should be in a day or so).
reckenro
approved these changes
Mar 29, 2023
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.
What does this Pull Request accomplish?
New example that would help customers navigate how to convert attenuation tables to s-parameters and how they are used in RFSG
Why should this Pull Request be merged?
These concepts are tricky in RFSG and given this is a new no one to one map with C, is hard to get this right in the first attempt.
What testing has been done?
Based on the single tone example, and only adding these attenuation table definition.