-
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
Background window fixes and improvement #86
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #86 +/- ##
==========================================
+ Coverage 88.70% 88.82% +0.12%
==========================================
Files 77 77
Lines 7453 7475 +22
Branches 1200 1205 +5
==========================================
+ Hits 6611 6640 +29
+ Misses 572 567 -5
+ Partials 270 268 -2 ☔ View full report in Codecov by Sentry. |
@CSSFrancis, can you please have a look at this PR, it seems that the migration to new markers API didn't support navigation dimension >=2. |
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.
@ericpre This looks good to me although the scaling not being linear is a bit concerning and probably should be investigated...
# convert to ragged array to comply with requirement for | ||
# navigation position dependent markers | ||
# 2000 x 2000 navigation shape takes ~2s | ||
# 1000 x 1000 navigation shape takes ~0.5s | ||
# 500 x 500 navigation shape takes ~0.01s | ||
segments = np.empty(self.axes_manager.navigation_shape, dtype=object) |
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.
Is there a reason this doesnt scale linearly?
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.
Yes, maybe it would be good to check if using lazy markers help here, I would assume so but off the top of my head, I don't remember how they work!
Going to merge for now to fix this regression and in the interest of making a release. |
…ng background and integration windows line markers
4b844b0
to
88d752e
Compare
Yea we are struggling with this in pyxem as well 😅 something about creating a large ragged array is very slow in numpy. Hopefully that is something that the awkward package could fix or we could try using numba. |
Fix #79.
Progress of the PR
upcoming_changes
folder (seeupcoming_changes/README.rst
),docs/readthedocs.org:exspy
build of this PR (link in github checks)Minimal example of the bug fix or the new feature
Raise the following error: