from #545
Observed:
gnpy-path-request evaluates performance under a full-load spectrum derived from transceiver type/mode/spacing but does not accept a non-uniform --spectrum file (i.e., custom per-channel frequency/width lists). It is possible to work around this by using the Python API, but the CLI does not accept non-uniform spectrum files directly.
Expected:
gnpy-path-request should accept a --spectrum file with arbitrary/non-uniform channel definitions, or provide a documented flag for custom spectra.
Suggested change:
Allow the CLI to import and honor non-uniform spectrum files (same format accepted by the Python API), or provide a clear CLI documented workaround.
from #545
Observed:
gnpy-path-request evaluates performance under a full-load spectrum derived from transceiver type/mode/spacing but does not accept a non-uniform --spectrum file (i.e., custom per-channel frequency/width lists). It is possible to work around this by using the Python API, but the CLI does not accept non-uniform spectrum files directly.
Expected:
gnpy-path-request should accept a --spectrum file with arbitrary/non-uniform channel definitions, or provide a documented flag for custom spectra.
Suggested change:
Allow the CLI to import and honor non-uniform spectrum files (same format accepted by the Python API), or provide a clear CLI documented workaround.