Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tracked down an error in the flux calibration stage in some data I
have been working with. If there was a nod and shuffle source observed,
then the NEXP, SEXP, NSUBEXPS header fields will still contain this
information when other observing modes are used. When the pipeline uses
the ’ns’:True parameter, signifying that N&S has been used, the exptime
is incorrectly re-calculated using these N&S parameters for exposures
made with other modes - like ClassicEquall for the standard star. This
can obviously throw off the calibration as the observed flux is scaled
in by exptime.
The fix checks the observing mode of a frame. If it is not a N&S, then
falls back to the exptime in original header, which has not been edited.