-
Notifications
You must be signed in to change notification settings - Fork 74
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
spectral extraction: update with new model types #1695
Conversation
69df308
to
4fae46c
Compare
e114465
to
b41ee77
Compare
:hint="trace_type_selected === 'Flat' ? 'Pixel row for flat trace.' : 'Pixel row initial guess for auto trace.'" | ||
:hint="trace_type_selected === 'Flat' ? 'Pixel row for flat trace.' : 'Pixel row initial guess for fitting the trace.'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bmorris3 - does this make sense to you given the conversation in #1827 (comment)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. 👌🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be great to have these features 👍🏻
elif isinstance(trace, tracing.KosmosTrace): | ||
self.trace_type_selected = 'Auto' | ||
elif isinstance(trace, tracing.FitTrace): | ||
self.trace_type_selected = trace.trace_model.__class__.__name__.strip('1D') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Today I learned that the str.strip
method takes arguments. Thanks for teaching me something! 😃
b41ee77
to
0f53528
Compare
0f53528
to
6079a9b
Compare
6079a9b
to
7d87f1c
Compare
Description
This pull request adds support for
model_type
from theAutoTrace
FitTrace
implementation in astropy/specreduce#128.This will require the specreduce PR to be reviewed, merged, released, and pinned here. Currently this draft PR exists to test that PR and imagine how it might look in jdaviz.
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.