Closed taylorbell57 closed 10 months ago
I just remembered that the pmap differs between JWST and HST, and the current code also doesn't check if the user has set their pmap in their .bashrc
file, so I'll switch to using crds.get_context_name('jwst')
(and crds.get_context_name('hst')
if there are any reference files that are automatically downloaded for HST, which I don't think there are) instead of the crds.get_default_context()
I'm using right now
Hah, the automated testing also caught a bug in the cases where pmap is not explicitly set (File 'jwst_jwst_1148.pmap.pmap' is not known to CRDS.
)
What's the motivation behind muting the Eureka! version in the output? Are you worried about information overload on the screen or is there something else?
Yeah, I feel like that's not really something you want to know while running the code but rather is something you'd want to know a month or few later when you can't quite remember what you did
Attention: 333 lines
in your changes are missing coverage. Please review.
Comparison is base (
559f703
) 57.02% compared to head (f3e50e1
) 57.71%. Report is 148 commits behind head on main.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
To help strengthen reproducibility and to allow users to manually control the used pmap, we now (silently) log the Eureka! version for Stages 1-6 and the CRDS pmap from Stages 1-3 (4-6 aren't relevant). For all future analyses, warnings will be printed to the terminal if the Eureka! version or CRDS pmap changes (only in the relevant stages), but this will not apply to previous partial reductions of the data (e.g., running the new code on v0.10 Stage 1 files won't raise any pmap or Eureka! version warnings).