Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CaSSIS band-bin information not correct for re-ingested moasiacs #4147

Closed
krlberry opened this issue Nov 25, 2020 · 0 comments · Fixed by #4219
Closed

CaSSIS band-bin information not correct for re-ingested moasiacs #4147

krlberry opened this issue Nov 25, 2020 · 0 comments · Fixed by #4219
Assignees
Labels
Missions Issues which are a priority for missions

Comments

@krlberry
Copy link
Contributor

krlberry commented Nov 25, 2020

ISIS version(s) affected: 4.2.0

Description
Reported via email.

Old wavelength values are being put into CaSSIS image headers:

Current values:

NIR 985.000000 nm 220.000000
RED 840.000000 nm 100.000000
PAN 675.000000 nm 250.000000
BLU 485.000000 nm 165.000000

Correct values:

PAN: wavelength - 677.4; bandwidth - 231.5
BLU: wavelength - 497.4; bandwidth - 134.3
RED: wavelength - 835.4; bandwidth - 98.0
NIR: wavelength - 940.2; bandwidth - 120.6

The one for the framelets (TgoCassisBandBin.trn) was updated for the correct wavelengths/bandwidths, but not the one for the mosaics (TgoCassisMosaicBandBin.trn).

How to reproduce

Possible Solution
Update TgoCassisMosaicBandBin.trn to match TgoCassisBandBin.trn.

Additional context

@krlberry krlberry self-assigned this Nov 25, 2020
@krlberry krlberry added the Missions Issues which are a priority for missions label Nov 25, 2020
@krlberry krlberry changed the title Update mosaics band-bin output file for CaSSIS CaSSIS band-bin information not correct for moasiacs Nov 25, 2020
@krlberry krlberry changed the title CaSSIS band-bin information not correct for moasiacs CaSSIS band-bin information not correct for re-ingested moasiacs Nov 25, 2020
@krlberry krlberry removed their assignment Nov 30, 2020
@kaitlyndlee kaitlyndlee self-assigned this Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Missions Issues which are a priority for missions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants