Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Added an image interval option that is symmetric about a midpoint #18602

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added an image interval option that is symmetric about a midpoint #18602

wants to merge 1 commit into from

Conversation

ayshih
Copy link
Contributor

@ayshih ayshih commented Sep 8, 2025

Description

This pull request adds an image interval option (SymmetricInterval) that specifies a symmetric extent about a midpoint (defaults to zero). This is primarily useful when having the radius of the interval be automatically determined such that the interval contains both the image minimum and maximum.

Example:

>>> import numpy as np
>>> from astropy.visualization import SymmetricInterval

>>> data = np.linspace(-20, 60, 100)

# Manually defining the radius of the interval about the midpoint (defaults to zero)
>>> SymmetricInterval(radius=40).get_limits(data)
(-40, 40)

# Automatically determine the radius of the interval to contain both the image minimum (-20) and the image maximum (+60)
>>> SymmetricInterval().get_limits(data)
(-60.0, 60.0)
>>> SymmetricInterval(midpoint=50).get_limits(data)
(-20.0, 120.0)
  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 8, 2025

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 8, 2025

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

@pllim pllim added this to the v7.2.0 milestone Sep 8, 2025
@ayshih ayshih marked this pull request as ready for review September 8, 2025 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@astrofrog astrofrog Awaiting requested review from astrofrog astrofrog is a code owner

@larrybradley larrybradley Awaiting requested review from larrybradley larrybradley is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
visualization
Projects
None yet
Milestone
v7.2.0
Development

Successfully merging this pull request may close these issues.
2 participants
@ayshih @pllim