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

Fix FieldVaryingPSF #506

Merged
merged 3 commits into from
Nov 19, 2024
Merged

Fix FieldVaryingPSF #506

merged 3 commits into from
Nov 19, 2024

Conversation

hugobuddel
Copy link
Collaborator

FieldVaryingPSF did not do anything at all because it used FieldOfView.image, which is otherwise unused, see AstarVienna/irdb#161

@hugobuddel hugobuddel marked this pull request as draft November 18, 2024 20:04
Copy link

codecov bot commented Nov 18, 2024

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 77.16%. Comparing base (d6758f6) to head (09eebc0).
Report is 4 commits behind head on main.

Files with missing lines Patch % Lines
scopesim/effects/psfs/discrete.py 80.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #506      +/-   ##
==========================================
- Coverage   77.18%   77.16%   -0.02%     
==========================================
  Files          66       66              
  Lines        8205     8203       -2     
==========================================
- Hits         6333     6330       -3     
- Misses       1872     1873       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@hugobuddel hugobuddel marked this pull request as ready for review November 18, 2024 20:16
@hugobuddel
Copy link
Collaborator Author

@oczoske , I have commented out FieldOfView.spectrum (never used) and FieldOfView.image (only used by FieldVaryingPSF, which I fixed by making it use FieldOfView.hdu.data directly).

I've kept FieldOfView.cube for now. FieldOfView.cube seems to be only used by SpectralTraceList. All other Effects use fov.hdu.data directly, and it seems that this can also be done by SpectralTraceList. Is there a reason to keep FieldOfView.cube around, or can we remove it in favor of FieldOfView.hdu.data?

This prevents regressions to the broken state of before.
@hugobuddel hugobuddel mentioned this pull request Nov 18, 2024
Copy link
Contributor

@teutoburg teutoburg left a comment

Choose a reason for hiding this comment

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

Ditching those specific (but (almost) unused) attributes in favor of the more general .hdu.data seems useful in this case 👍

@teutoburg teutoburg added bug Something isn't working effects Related to a ScopeSim effect labels Nov 19, 2024
@hugobuddel
Copy link
Collaborator Author

Hmm do I dear to merge this without checking the IRDB notebooks? Yeah for sure!

@hugobuddel hugobuddel merged commit 59557a7 into main Nov 19, 2024
22 checks passed
@hugobuddel hugobuddel deleted the hb/fixfieldvaryingpsf2 branch November 19, 2024 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working effects Related to a ScopeSim effect
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants