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

Sometimes K band only gets 25 orders extracted #29

Open
ericasaw opened this issue Feb 9, 2024 · 1 comment
Open

Sometimes K band only gets 25 orders extracted #29

ericasaw opened this issue Feb 9, 2024 · 1 comment

Comments

@ericasaw
Copy link

ericasaw commented Feb 9, 2024

Noticed this bug or maybe feature in the pipeline from qlook branch onward that makes my life a little harder when comparing the old and new pipeline outputs. Sometimes the new pipeline will throw out the top order in K-band and the final pipeline products will only feature 25 orders instead of 26. I cant find any sort of consistency in how it occurs (ie. in the same night some K band spectra will have 25 orders and some will have 26).

I would prefer if there is a consistent number of orders for all the spectra in both bands (whether that be always chopping of the first order of K band or always keeping the first order).

Do you know where this stems from in the changes you made @leejjoon?

@leejjoon
Copy link
Contributor

I would say the proper way to workaround this would be to read the header and parse the WAT header to figure out which orders of spectra are extracted. The easier workaournd is to specify the range of orders to extract, and this is implemented in the PR #35. Please test the PR and send me any feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants