fix switch term termination function #938
Merged
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.
I have noticed that when terminating switch terms with zero values to a network and they have different port impedances, I get a wrong answer. Ideally, when switch terms are zero, I should get the same values of the network back. However, S11 and S22 are impacted depending on the port impedances of the network and the switch terms.
The problem comes from the fact that the function is written in such way that it performs network cascading when computing S11 and S22, which obviously results in implicit impedance transformation when the network and switch terms have different impedances.
The fix is basically to explicitly write the equations for S11 and S22 without using network cascading.
Here is a test code:
Which results in below plots:
After the fix: