-
Notifications
You must be signed in to change notification settings - Fork 10
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
Gb/no regrid #206
Gb/no regrid #206
Conversation
…e index was already sliced so this error is inaccurate
features=self.lr_dh.features, | ||
max_workers=self.lr_dh.norm_workers) | ||
|
||
if id(self.lr_dh.data) != id(self.lr_data.base): |
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.
what do you think about putting these id checks in a separate method? clean code has made me wary of using inline comments over good method names/doc strings.
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.
Just the checks? What about two new methods: _norm_lr()
and _norm_hr()
with each describing the id issues?
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.
Yeah "checks" in a royal sense lol. That sounds perfect!
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.
Makes sense to me! good suggestion.
No description provided.