Wavelength calibration when using d-spacing from calibration table?

[SimonHeybrock]

Consider the workflow mode computing d-spacing from a diffraction calibration table. This directly takes TOF as input. However, monitor normalization still computes wavelength using the "regular" math from TOF. In a sense, this bypasses the calibration. If the monitor does have pronounced features (such as between the WFM frames?), this might lead to inaccuracies.

Does the wavelength need calibration, somehow?

[nvaytet]

I agree that monitor and detector need to use the same calibration table to be consistent.

[SimonHeybrock]

My point is: Neither monitor nor detector use a calibration table to compute wavelength, as far as I can tell.

[nvaytet]

They compute tof using a table, which should be equivalent? (maybe I am missing something?)

[SimonHeybrock]

The calibration table is used to convert TOF->dspacing. I am assuming this "includes" some sort of position calibration. This position calibration that is encoded in the calibration table in an unknown way would also affect wavelengths.

[jokasimr]

We could calculate backwards from dspacing->wavelength using a good guess for the position.
If the wavelength is only used for monitor normalization it is likely that they don't need to be perfectly calibrated.