-
Notifications
You must be signed in to change notification settings - Fork 14
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
ZLP alignment very slow #83
Comments
I'm going to assume that it tries to plot during fitting of the ZLP. Try suppressing plotting calls from events temporarily during plotting, to see if that has an effect. |
Whatever you've done over the past month has improved the situation, but it is still about 30 times faster in hs than in the UI. An oddity is that the three-stage zlp alignment with subpixel correction takes 5 sec, 13 sec and 5 sec for each stage in hyperspy, but 1.5min, 0.5min and 7.5 min in the UI. Looks like there's something happening with the first and last process that takes a long time in the UI whilst the middle process has fewer things slowing it down in the UI. |
There is not really anything that the UI should do to slow this down. Are you using the qt4 backend in normal hyperspy? That should be the same speed as int the UI. |
I think it might be related to the progress bar code. I'll I've at least been able to reproduce it locally, and will have a look. |
Nice and fast now. |
I haven't done anything, so why does it currently work? |
I thought this might be a hyperspy and matplotlib-backend related issue, but perhaps not.
Trying zlp alignment in HyperspyUI (using the console) is extremely slow - I think this is due to the matplotlib backend, although I'm not sure why. @Andyroo and I discovered that there was a big time delay on align1D depending if one was in inline or qt4.
The following 1.8 GB lowloss image takes 1.5 min to align in normal hyperspy (inline).
Hyperspyui estimates 91 hours. This is with the "view" of the SI off. Typing
%matplotlib inline
in the UI console makes the images dissappear, but the alignment takes the same amount of time.The text was updated successfully, but these errors were encountered: