-
Notifications
You must be signed in to change notification settings - Fork 28
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
Aperture updates related to JSOCOPS-24 (limited to Grism Time Series) #254
Aperture updates related to JSOCOPS-24 (limited to Grism Time Series) #254
Conversation
This PR is ready for review |
Deleted comments that were intended for #261 after copying them there. |
Complicated conflicts: remote: Enumerating objects: 31, done.
I'll start resolving things by deleting the previous output files. |
`<<<<<<< JWSTSIAF-186
|
yes, you can choose to have them both, or because you already produced the figures for 242, you can actually leave just those for 186 and post those to the JWSTSIAF-186 ticket. |
Right, I see what you're saying. It is just the loop that creates the figures. I merged them locally, and it worked with no problems, but I think it makes more sense to do the auxiliary files in their separate tickets. |
I actually could solve the conflict myself (I probably have write privileges because this is my PR). I chose to go with -186 only, becuase we already have the plots for 242 |
Sounds good. |
This approach is also more similar to the typical sequential flow we use for when we do updates one ticket at a time. I.e. we modify the siaf-upadtes version of generate_nircam to put the "new" plots in that statement that was giving conflict. We usually do not have conflicts because the feature branch is the one and only feature branch that is branched off siaf-updates, but in this case we had 2 branches branched off at the same point in time from siaf-updates and the merging of the jwstsiaf-242 PR into siaf-updates has caused this minor conflict that indeed was expected. |
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.
I think this is what we want. After merging I'll check everything in the new siaf-updates, generate the files, and open a new PR.
Uh-oh, we just did something bad. This last PR deleted all of the NIRSpec data: ======================================================= short test summary info ======================================================== |
I think I can just try a new branch and pull those in from master... |
Holy cow...that is my fault: I was just seeing all these "._" files in my branch and I |
Under this PR NIRCam will deliver the follwoing changes:
F444W field point (several GRISMTS apertures in SIAF): Shift X by -94 LW px (DMS oriented).
NRCA3 and NRCA1 GRISM128 aperture: Shift Y by -8 SW px (DMS orientation)
NRCA3 and NRCA1 GRISM64 aperture: Shift Y by -10 SW px (DMS orientation)
Adjust the NRCA5_TAGRISMTS32_F405N: