-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Introduce JWST Boxcar Development Notebook from Ivo Busko #79
Conversation
Co-authored-by: Ivo <busko@stsci.edu> Co-authored-by: ojustino <ojustino@users.noreply.github.com>
I can't request reviewers, but @tepickering should definitely review the algorithm we have here; also @ojustino should look at this just to rubber stamp the "final" version, since we dont' have @ibusko to confirm the small changes I made |
i think the |
Hi @duytnguyendtn, the notebook runs for me without issues. I agree with @tepickering that it would be good to switch the trace implentation from I have a couple of suggestions on the notebook itself:
|
Good catch @ojustino ! I've updated the notebook.
This was my intention with introducing this notebook as it is @tepickering. I imagine that substitution can happen as a follow up to this effort? |
that's what i was thinking. once i get the trace fitting implemented, i'll update this notebook as part of that effort. |
shall i go forth and merge this? |
@tepickering Yes please! I think we're good on our side to merge! |
Migrating @ibusko's notebook exploring implementing the JDAT notebook boxcar extraction algorithm into specreduce: https://github.com/ibusko/dat_pyinthesky/blob/spectral_extraction_tests/jdat_notebooks/spectral_extraction_tests/specreduce_extract_jwst.ipynb
This notebook also contains changes during my technical review
Co-authored-by: @ibusko
Co-authored-by: @ojustino