Skip to content
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

Force PNA to use expected format for SNP data #976

Merged
merged 1 commit into from
Nov 26, 2023

Conversation

mjpelmear
Copy link
Contributor

get_snp_network() in the PNA virtual instrument expects the data to be returned in Real/Imaginary format, but the instrument isn't necessarily configured to do so. This pull request alters the behavior to save the initial SNP format, change it to Real/Imaginary, then restore the original after pulling the SNP data.

You can verify that this matters by manually setting the SNP data type to one of the other values ("MA" or "DB") before calling get_snp_network() on the master branch. e.g., instr.write("MMEM:STOR:TRACE:FORM:SNP MA").

This was tested on a Keysight P9374A, but I use similar code on PNAs (where I can't test this change directly).

@cafeclimber
Copy link
Contributor

Solid fix! Thanks! (Also glad to hear the update is working for you!)

@jhillairet jhillairet merged commit a03e998 into scikit-rf:master Nov 26, 2023
12 checks passed
@jhillairet jhillairet mentioned this pull request Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants