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

NIRSpec Visibility Fix #619

Closed
wants to merge 1,044 commits into from
Closed

NIRSpec Visibility Fix #619

wants to merge 1,044 commits into from

Conversation

hover2pi
Copy link
Member

Fixes the NIRSpec Visibility calculation.

nespinoza and others added 30 commits May 12, 2022 16:33
Merging develop into master for v1.2.4 release
…the list of filters so the JWST ones default to the repo files
hover2pi and others added 26 commits July 2, 2024 16:05
Adds proper motion correction and galaxy support to Contamination tool
Visibility tool goes from Cycle 3 to 6 now
Removed MIRI text from contam tool page
@hover2pi hover2pi requested a review from mfixstsci September 16, 2024 15:37
@mfixstsci
Copy link
Contributor

Still confused about how we ended up with commits from two years ago in this merge. From my investigations I think this might be the result of releasing from a branch that was not main in the past v.1.2.3 which was 2 years ago.

I think if we want to bring main up-to-date with develop that's fine and if we want to continue adding code into main that's okay too but when we are ready for a release, maybe we make a branch off of main that is version we are tagging and releasing.

So in this case, we can merge this, make a branch off of main called v1.2.6 and use that as the target branch of the release.

@hover2pi hover2pi closed this Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants