-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Solving crop_by_coord problem when data are rotated #113
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
909ce8c
Solving crop_by_coord problem when data are rotated
BaptistePellorceAstro 28aba8c
New error raising and dimension modified
BaptistePellorceAstro 952a712
Adding a new test for rotated data
BaptistePellorceAstro cefd9a7
PEP8 correction in test_ndcube.py
BaptistePellorceAstro 5a0f454
Solving test bug with old values on crop by coords
BaptistePellorceAstro b837d0e
Some error tests added
BaptistePellorceAstro 77b32f7
New API for crop by coords with units
BaptistePellorceAstro 16c08f0
Some Quantity types checks refactored
BaptistePellorceAstro 1adde1d
Fix a test error
BaptistePellorceAstro 76501e1
Improving units checks in crop by coords
BaptistePellorceAstro 7c56239
Improving corners calculation
BaptistePellorceAstro 4f729dd
Improving the data slicing
BaptistePellorceAstro b097241
Fix some error bugs
BaptistePellorceAstro d6cf940
Removing product importation
BaptistePellorceAstro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 it's better if you reverse the order of these
if
statements. That way you can issue the warning and constructupper_corner
frominterval_widths
without checking the number of elements is right. Then you can just check the length ofupper_corner
without requiring anif
statement since if it wasn't defined by the user, you will have defined in theif interval_widths:
if statement.Then when it comes time to stop supporting the
interval_widths
API, we just have to delete theif interval_widths:
statement.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.
If i delete the elements number checking between
lower_corner
,interval_widths
andn_dim
, an error will come by creating theupper_corner
values because one of these tuples will be out of range. Do you want I remove this error raising ?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.
Ah, you're absolutely right! Yes, leave in the length checking in both statements, but check
interval_widths
first. Then you can also add in a check thatinterval_widths
andupper_corner
were not both set: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.
Ok, I will input this line in my code, I already exchanged the if statements positions.