Skip to content
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

Closed
wants to merge 3 commits into from

Conversation

kecnry
Copy link
Member

@kecnry kecnry commented Oct 3, 2022

Description

This pull request adds support for model_type from the AutoTrace 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.

image

image

Change log entry

  • Is a change log needed? If yes, is it added to 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, maintainer
    should 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.

  • Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
  • Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
  • Do the proposed changes follow the STScI Style Guides?
  • Are tests added/updated as required? If so, do they follow the STScI Style Guides?
  • Are docs added/updated as required? If so, do they follow the STScI Style Guides?
  • Did the CI pass? If not, are the failures related?
  • Is a milestone set?
  • After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

@kecnry kecnry added this to the 2.11 milestone Oct 3, 2022
@kecnry kecnry force-pushed the spec-extract-polytrace branch 2 times, most recently from 69df308 to 4fae46c Compare October 6, 2022 14:35
@rosteen rosteen modified the milestones: 2.11, 3.1 Oct 10, 2022
@rosteen rosteen modified the milestones: 3.1, 3.2 Oct 26, 2022
@kecnry kecnry force-pushed the spec-extract-polytrace branch 2 times, most recently from e114465 to b41ee77 Compare November 8, 2022 17:45
Comment on lines -84 to +98
: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.'"
Copy link
Member Author

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)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. 👌🏻

Copy link
Contributor

@bmorris3 bmorris3 left a 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')
Copy link
Contributor

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! 😃

@kecnry kecnry mentioned this pull request Dec 2, 2022
13 tasks
@kecnry kecnry closed this Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants