-
Notifications
You must be signed in to change notification settings - Fork 1
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
0.7.290: missing SBCDEN_P value in combined FP_FP 24BQ11-Oct28/3DA7AA0F8Ba_pp.fits #791
Comments
Note also the kw is also missing in all subsequent reduced files 3DA7AA0F8Ba* |
Its not missing, by definition any key that changes moves to an extension For a few keys I define a "combing method" i.e. exptime etc where we take a mean or a sum or something. If you want they key to be combined I just need to know what you want for it (i.e. take the mean of all values) otherwise you can find it in the Also the COMBINE_TABLE isn't passed to products using that file so subsequent processed files wont have this extension or the header key. |
ok I understand. Maybe for the density value it's worth I chnage my code and look at the individual values if the recombined is missing. |
I'll look in the code to see whether if I make it give the "mean" value it will also stay in the combined table - if we could have both that seems to be the best solution. I guess it depends on what you are checking for with the density - if a sudden change needs to be flagged and this can happen between the combine frames you definitely want to be checking the COMBINE_TABLE. |
Hi @njcuk9999
The pp file combining the FP_FP of the last night of the October run has no kw SBCDEN_P (FP density value) although all individual raw files have a correct value (value is 1.19 or 1.20)
Only one night in 24BQ11 is affected, but It happened with several nights from the september run.
Individual files:
pre_processed combined file:
FILE DPRTYPE SBCDEN_P
/data/spirou4/apero-data/quicklook290/red/24BQ11-Oct28/3DA7AA0F8Ba_pp.fits FP_FP
I'm using the value of the FP density to monitor the instrument, I never had this issue with the 0.6.132
The text was updated successfully, but these errors were encountered: