Non-Standard Wavelength Support

[Nat1405]

NIFS has a tunable central wavelength (documented here). This means the wavelength calibration could fail for non-standard central wavelength configurations. So far, nifsSort catches these and rejects them. It's good to know how many are getting rejected though and what configurations are worth adding support for.

A query of the CADC gemini archive for science programs shows which proposals use which central wavelengths:

(Output is in Central Wavelength : count proposal id format).

Length proposal_ids: 345
K_Short:
None: 5
2.1: 3
2.18: 1
2.0927: 1

H:
None: 56
1.649: 65
1.6: 2

K:
None: 94
2.25: 3
2.2: 131
2.14: 1
2.27: 1
2.16: 1
2.1: 3
2.200002: 5
2.3: 1
2.18: 1

J:
None: 29
1.25: 47
1.28: 2

K221:
None: 1

Mirror:
None: 3

K_Long:
None: 9
2.3: 13

Z:
None: 12
1.05: 26
1.001: 1
1.06: 1

[Nat1405]

I looked into the "None" results, and it looks like it might be the Gemini JSON summaries not always catching the CRWAVE header value (I checked some frames and header values are defined for them even though it doesn't show up in the JSON summary).

So treat these numbers as a rough guide only, they could change.