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 unit conversion of limits from Fnu to Flam #2889

Merged
merged 4 commits into from
May 31, 2024

Conversation

astrofrog
Copy link
Collaborator

Description

I have expanded the test suite for to_unit and found that an error occurred when converting limits from Fnu to Flam. The issue in this specific case was that if '_pixel_scale_factor' in spec.meta: was True so the clause relating to len(values)==2 was never invoked, resulting in an issue with incompatible dimensions.

In addition to fixing this logic, I have made it so that we just use one wavelength/frequency in this case for the conversion, as it doesn't specifically make sense to use the first and last spectral axis value. When converting limits we are probably interested in the values being right at the start of the spectral axis.

This builds on top of #2888 and should be rebased once #2888 is merged.

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? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone. Bugfix milestone also needs an accompanying backport label.
  • After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

Copy link

codecov bot commented May 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.70%. Comparing base (b3c3ae9) to head (c26c5e1).
Report is 174 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2889   +/-   ##
=======================================
  Coverage   88.70%   88.70%           
=======================================
  Files         111      111           
  Lines       17132    17134    +2     
=======================================
+ Hits        15197    15199    +2     
  Misses       1935     1935           

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

jdaviz/app.py Show resolved Hide resolved
@pllim pllim added the bug Something isn't working label May 22, 2024
@pllim pllim added this to the 4.0 milestone May 22, 2024
@gibsongreen gibsongreen added the no-changelog-entry-needed changelog bot directive label May 30, 2024
Copy link
Contributor

@gibsongreen gibsongreen left a comment

Choose a reason for hiding this comment

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

Post-rebase of pixel scale factor updated PR: #2860:

  • New limits test passing
  • small medication to conditional to include update from this PR:
    elif len(values) == 2:
  • Profile-viewer behavior post display units/conversion changes functioning

@gibsongreen gibsongreen merged commit e9147aa into spacetelescope:main May 31, 2024
18 of 19 checks passed
@gibsongreen
Copy link
Contributor

Note:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working no-changelog-entry-needed changelog bot directive testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants