Currently, the OSNR contribution per (ROADM-to-ROADM) link is calculated in PceLink.java. But as far as I can see there is no summing up of link OSNR contributions in order to calculate the OSNR for an end-to-end path. Is this something that is planned for implementation? Calculating path OSNR and comparing with some threshold for path validation (similar to what is currently done for max latency) seems to me like the main point of having OSNR "awareness".

There is a confusingly named parameter, maxOSNR, in PceConstraints.java but this parameter does not seem to be used anywhere. It is a bit confusing that both the maxOSNR parameter and the linkOsnrLu parameter returned by retrieveOSNR() actually seem to be inverse OSNRs (especially confusing is the debug message, "In retrieveOSNR: link OSNR is {} dB", when what is reported is not the OSNR in dB but the inverse OSNR in linear units).