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

correct test and example files with direct Trx reception #244

Conversation

EstherLerouzic
Copy link
Collaborator

adding -15 differential per target on receiver instead of 0
and adding attenuator in front of receivers in example networks
and test network, to keep same performances as before this change

Signed-off-by: EstherLerouzic esther.lerouzic@orange.com

@codecov

This comment has been minimized.

adding  -15 differential per target on receiver instead of 0
and adding attenuator in front of receivers in example networks
and test network, to keep same performances as before this change

Signed-off-by: EstherLerouzic <esther.lerouzic@orange.com>
@ojnas
Copy link
Contributor

ojnas commented May 27, 2019

Two questions:

  • Why do you say "instead of 0"? If I understand the current code correctly the differential power (dp) depends on the loss of the following element. For a Transceiver the loss is 0 so the target would already be a negative differential, right?

  • I don't think the current Transceiver code cares about the input power, i.e. it only calculates OSNR/SNR and does not check that input power is within some range, so why is this change necessary?

@jktjkt jktjkt added this to WIP in GNPy May 27, 2019
@EstherLerouzic
Copy link
Collaborator Author

@ojnas thank you for your comment:
on question 1 : the "instead of 0" referred to the roadm dp. Indeed the dp value depends on "node" loss and delta_power_range defined in eqpt_config.json, so it can be negative 0 or positive. In the case of a trx the loss is set to 0 (by the function span_loss).
on question 2 : it's correct, the current transceiver does not care about its input power, performance is only limited by SNR. The purpose of this change was to put the finger on this fact, have more realistic power level on receiver and prepare future possible work on power limitation (not for the short term !).
I would prefer to integrate the change, but let's discuss this tomorrow within our weekly call

@jktjkt jktjkt moved this from WIP to Needs review in GNPy May 28, 2019
@jktjkt
Copy link
Collaborator

jktjkt commented May 28, 2019

I re-checked Codecov report. It complains because the newly added code path which sets Transponder's RX power is actually not hit by any test case. So the complaint is reasonable because this pull requests adds code which is not tested.

I'll add a test case which exercises this path.

@jktjkt jktjkt self-assigned this May 28, 2019
@jktjkt jktjkt moved this from Needs Review to Needs Coding in GNPy May 31, 2019
@jktjkt jktjkt closed this Jun 18, 2020
GNPy automation moved this from Needs Coding to Done Jun 18, 2020
@jktjkt
Copy link
Collaborator

jktjkt commented Jun 18, 2020

We have decided to remove the develop branch, and as a result of doing that, this PR got auto-closed on GitHub. If you believe that this change is still relevant and that it was closed by accident, please submit your patch to our Gerrit, or just comment here and I'll help sort this out.

@EstherLerouzic EstherLerouzic deleted the max_power_on_transceiver branch October 18, 2021 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
GNPy
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants