Currently the Thorium linelist is saved as a python save file and requires both a list of wavelengths, and a list of pixels where these wavelengths should show up in the spectrum. The latter relies on a baked-in wavelength solution, which may or may not be reasonable for a given master 'guess' solution on any given day.
I propose we only use the most recent 'guess' solution to estimate the approximate pixel locations for a list of wavelengths (e.g. actively find the nearest pixel for a given static line wavelength), rather than relying on a static baked-in solution that is less traceable. This also means that the calibration linelists would only be a static list of wavelengths.
awhoward
commented
8 months ago
Currently the Thorium linelist is saved as a python save file and requires both a list of wavelengths, and a list of pixels where these wavelengths should show up in the spectrum. The latter relies on a baked-in wavelength solution, which may or may not be reasonable for a given master 'guess' solution on any given day.
I propose we only use the most recent 'guess' solution to estimate the approximate pixel locations for a list of wavelengths (e.g. actively find the nearest pixel for a given static line wavelength), rather than relying on a static baked-in solution that is less traceable. This also means that the calibration linelists would only be a static list of wavelengths.