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
Lazy decomposition raises error on mask check #2605
Comments
@thomasaarholt
|
@thomasaarholt's link is pointing to the current |
@erh3cq any chance you didn't |
@thomasaarholt I think the git desktop automatically fetches before rebase to origin (not upstream). My repo is showing updates that are one day old. I will give it another whirl then report back. |
Is there a traceback or a minimum example to reproduce? |
@thomasaarholt I didn't reinstall with PIP but I did a forced reboot of my repo to upstream.
I checked and my erh3cq/RELEASE_next_minor (origin) matches the one in hyperspy/hyperspy (upstream) but not the one you mentioned above. It looks like that is from a different branch than RELEASE_next_minor. Are we supposed to be using a different base branch now? @ericpre I don't have a MWE but I pasted the Traceback in gitter last week. Recopied below:
Out:
|
In the mean time, you can work around this issue by using |
@ericpre That fixed the mask error but raised the following
|
"Unchunking" the spectral axis as suggested by @pquinn-dls solves the last error. |
Fixed in #2657 |
Noticed by @erh3cq
hyperspy/hyperspy/_signals/lazy.py
Line 883 in 7bdee7a
The above line should read
if navigation_mask.any() or signal_mask.any()
. There might be more places with a similar error as well. Not sure ifnavigation_mask is None
would raise the same error or not.Note that @erh3cq might have a more general error with lazy decomposition, worth taking a look at (see link above).
The text was updated successfully, but these errors were encountered: