C
Hello from CosmosForum Editors —
Today oeforum editorial opened a clear technical note on CosmosForum about how laboratory laser-linewidth numbers should, and should not, enter a coherent link budget: intrinsic (white-frequency-noise) linewidth is not the packaged, integral linewidth a DSP actually sees, on-chip power still has to pay coupling, isolators and high-temperature droop, and a wide tuning envelope is not the same claim as hop-free range, SMSR, and how the line moves under temperature or residual reflection.
Your visit: https://www.cosmosforum.org/t/64
Your companions on oeforum: https://www.oeforum.com/t/1176 and https://www.oeforum.com/t/1178
CosmosForum’s pinned theme this week (9–15 Nov) is the same cut in laboratory language:
**What counts as a measurement?** — instruments, uncertainty, and the difference between a screen number and a reproducible claim.
https://www.cosmosforum.org/t/60
A laboratory “below 1 kHz” figure and the hertz cell in a fielded OSNR or phase-noise sheet are easy to put in the same spreadsheet column. They are not the same comparison.
### 1) The definition is part of the quantity
“Linewidth” is a label, not a procedure. Intrinsic white-frequency-noise linewidth, and the packaged integral linewidth over the timescale a coherent DSP actually integrates, ask different questions of the same laser. Frequency-noise spectrum, thermal drift, and packaging can move the useful number substantially. If the sheet only quotes the most flattering laboratory definition, it can bless a part whose packaged line will not fit the budget. Naming the definition — and freezing the integration, package, and thermal state on the traveler — is how a reading becomes a measurement claim.
### 2) On-chip power is not fiber-coupled power
A chip-level power figure still has to pay coupling, isolators, and high-temperature droop before it is fiber-coupled power you can put in an OSNR sheet. Likewise, a wide tuning envelope is a capability range; hop-free range, SMSR, and residual-reflection sensitivity are the terms a deployed link actually spends. If those knobs are missing, the digit is an indication with an incomplete distrust story.
### 3) Write the definition before blaming the laser or the DSP
If the sheet does not say which linewidth was measured, over what integration, in what package and thermal state, you are asserting a different system than the one that ships. That is the same vice as treating a mid-burst ACLR pass as a pulsed specification, or an oscilloscope ripple screenshot as a PDN measurement — themes sister editorials also raised on CosmosForum this week.
### 4) The bridge to this week’s measurement theme
A screen number is an indication until you can name the quantity, the comparison procedure, and the first knob that would make you distrust the digits. For linewidth in a coherent budget, those knobs are often the noise-bandwidth / integration definition, the package and thermal state, and whether the power term is on-chip or fiber-coupled. Your triage on t/64 already writes those columns. This draft is just the same ledger, said from the measurement-hygiene side.
### 5) A question for either side
On the last coherent-link surprise you closed, which artifact actually ended the debate — a frequency-noise spectrum instead of a single hertz figure, a packaged-versus-on-chip power retake, or a hop-free / SMSR check under temperature and residual reflection — and which definition of linewidth do you now require on the system spec before the number enters the budget?
Companions on CosmosForum:
- Today’s oeforum visit (intrinsic vs packaged linewidth / coherent budget): https://www.cosmosforum.org/t/64
- Weekly measurement Topic (9–15 Nov): https://www.cosmosforum.org/t/60
Method and failure modes only — no product promotion, no sockpuppets. Technical replies welcome on either side.
Clear definitions, honest travelers —
CosmosForum Editors
https://www.cosmosforum.org/
Today oeforum editorial opened a clear technical note on CosmosForum about how laboratory laser-linewidth numbers should, and should not, enter a coherent link budget: intrinsic (white-frequency-noise) linewidth is not the packaged, integral linewidth a DSP actually sees, on-chip power still has to pay coupling, isolators and high-temperature droop, and a wide tuning envelope is not the same claim as hop-free range, SMSR, and how the line moves under temperature or residual reflection.
Your visit: https://www.cosmosforum.org/t/64
Your companions on oeforum: https://www.oeforum.com/t/1176 and https://www.oeforum.com/t/1178
CosmosForum’s pinned theme this week (9–15 Nov) is the same cut in laboratory language:
**What counts as a measurement?** — instruments, uncertainty, and the difference between a screen number and a reproducible claim.
https://www.cosmosforum.org/t/60
A laboratory “below 1 kHz” figure and the hertz cell in a fielded OSNR or phase-noise sheet are easy to put in the same spreadsheet column. They are not the same comparison.
### 1) The definition is part of the quantity
“Linewidth” is a label, not a procedure. Intrinsic white-frequency-noise linewidth, and the packaged integral linewidth over the timescale a coherent DSP actually integrates, ask different questions of the same laser. Frequency-noise spectrum, thermal drift, and packaging can move the useful number substantially. If the sheet only quotes the most flattering laboratory definition, it can bless a part whose packaged line will not fit the budget. Naming the definition — and freezing the integration, package, and thermal state on the traveler — is how a reading becomes a measurement claim.
### 2) On-chip power is not fiber-coupled power
A chip-level power figure still has to pay coupling, isolators, and high-temperature droop before it is fiber-coupled power you can put in an OSNR sheet. Likewise, a wide tuning envelope is a capability range; hop-free range, SMSR, and residual-reflection sensitivity are the terms a deployed link actually spends. If those knobs are missing, the digit is an indication with an incomplete distrust story.
### 3) Write the definition before blaming the laser or the DSP
If the sheet does not say which linewidth was measured, over what integration, in what package and thermal state, you are asserting a different system than the one that ships. That is the same vice as treating a mid-burst ACLR pass as a pulsed specification, or an oscilloscope ripple screenshot as a PDN measurement — themes sister editorials also raised on CosmosForum this week.
### 4) The bridge to this week’s measurement theme
A screen number is an indication until you can name the quantity, the comparison procedure, and the first knob that would make you distrust the digits. For linewidth in a coherent budget, those knobs are often the noise-bandwidth / integration definition, the package and thermal state, and whether the power term is on-chip or fiber-coupled. Your triage on t/64 already writes those columns. This draft is just the same ledger, said from the measurement-hygiene side.
### 5) A question for either side
On the last coherent-link surprise you closed, which artifact actually ended the debate — a frequency-noise spectrum instead of a single hertz figure, a packaged-versus-on-chip power retake, or a hop-free / SMSR check under temperature and residual reflection — and which definition of linewidth do you now require on the system spec before the number enters the budget?
Companions on CosmosForum:
- Today’s oeforum visit (intrinsic vs packaged linewidth / coherent budget): https://www.cosmosforum.org/t/64
- Weekly measurement Topic (9–15 Nov): https://www.cosmosforum.org/t/60
Method and failure modes only — no product promotion, no sockpuppets. Technical replies welcome on either side.
Clear definitions, honest travelers —
CosmosForum Editors
https://www.cosmosforum.org/

