-
Notifications
You must be signed in to change notification settings - Fork 106
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
Spatial flexure options #1855
Open
rcooke-ast
wants to merge
74
commits into
develop
Choose a base branch
from
spatflex_options
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Spatial flexure options #1855
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # pypeit/spectrographs/gemini_gmos.py
# Conflicts: # doc/releases/1.16.1dev.rst # pypeit/flatfield.py
Co-authored-by: Debora Pelliccia <[email protected]>
Spatial flexure reorganisation
# Conflicts: # doc/releases/1.17.1dev.rst
# Conflicts: # doc/releases/1.17.1dev.rst # presentations/py/users.py # pypeit/wavetilts.py
# Conflicts: # doc/calibrations/flexure.rst # doc/releases/1.17.2dev.rst # pypeit/core/flexure.py # pypeit/images/rawimage.py # pypeit/par/pypeitpar.py
debora-pe
reviewed
Dec 20, 2024
pypeit/images/rawimage.py
Outdated
if self.par['spat_flexure_correct'] else None | ||
self.spat_flexure_shift = None | ||
if self.par['spat_flexure_method'] != "skip" or not np.ma.is_masked(manual_spat_flexure): | ||
self.spat_flexure_shift = self.spatial_flexure_shift(slits, method=self.par['spat_flexure_method'], |
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.
Hey @rcooke-ast . Just a little confusion here.
maxlag
is not a parameter ofself.spatial_flexure_shift()
anymore.self.par['spat_flexure_maxlag']
is passed directly toflexure.spat_flexure_shift()
- you can do the same with
method
. Since it is defined inself.par
, you can just pass it directly toflexure.spat_flexure_shift()
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.
Ah, yes, good call! I'll update it 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reworks a lot of the code that uses spatial flexure. The main change here is that instead of a single value, the spatial flexure is now stored for each slit edge. I haven't yet implemented the edge-by-edge spatial flexure adjustment. These updates are just to ensure that the code base is unaffected by the change from a single floating point value to a 2D array.
There is a matching PR in the dev-suite. I'm running tests now...