-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Reverse order of composite subset regions #2116
Reverse order of composite subset regions #2116
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2116 +/- ##
==========================================
+ Coverage 91.93% 91.95% +0.01%
==========================================
Files 143 143
Lines 15789 15780 -9
==========================================
- Hits 14516 14510 -6
+ Misses 1273 1270 -3
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
I cannot run this PR right now, so could you pls list out the order of a compound subset with |
@pllim
on main
|
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.
LGTM. Thanks!
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 agree that this makes more intuitive sense and the previous implementation hasn't been released yet, so let's get this in asap!
Thanks, all! |
Description
This pull request is to address the ordering of composite subset regions. These regions show what pixel region and subset mode operations (i.e. and, or, xor, andnot) went into creating a composite subset, and in what order. The order is now newest pixel region at the end of the list (what is returned when running
viz.app.get_subsets(subset_name='Subset 1')
and indexingregion
or by settingobject_only=True
when callingget_subsets()
).This PR continues work from #2087 .
Change log entry
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, maintainershould 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.
trivial
label.