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

About the effective_pch_out_db of a ROADM #366

Open
Tobelightbeam opened this issue Oct 27, 2020 · 3 comments
Open

About the effective_pch_out_db of a ROADM #366

Tobelightbeam opened this issue Oct 27, 2020 · 3 comments

Comments

@Tobelightbeam
Copy link

Describe the bug
The propagate method of Class Roadm in gnpy.core.elements.py should be improved.

  1. target_pch_out_db is used to calculate carriers_att. However, effective_pch_out_db (rather than target_pch_out_db) is used to update p_spani. The meanning of effective_pch_out_db is not clear.
  2. As shown in the code, exceeding_att is introduced when carrier_power is lower than target_pch_out_db ( why not effective_pch_out_db?). In this case, it's reasonable to tunning the value of effective_pch_out_db accordingly. However, this step is missed.

p.s. The involved codes are between line 223 and line 243 in gnpy.core.elements.py

@EstherLerouzic
Copy link
Collaborator

I think this relates to another discussion we had on a proposed commit here: https://review.gerrithub.io/c/Telecominfraproject/oopt-gnpy/+/488967 (comments on sept. 04)
We have not finished on this discussion

@ojnas
Copy link

ojnas commented Oct 27, 2020

@Tobelightbeam, to clarify, the specific comment thread that @EstherLerouzic is referring to is this one:

https://review.gerrithub.io/c/Telecominfraproject/oopt-gnpy/+/488967/12/gnpy/core/elements.py#242

@Tobelightbeam
Copy link
Author

@EstherLerouzic , @ojnas ,
Thanks for your replies.

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

No branches or pull requests

3 participants