-
Notifications
You must be signed in to change notification settings - Fork 21
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
HKEM notebook run-time #196
Comments
The run time is mainly in the convolution between an image and the kernel (kernelise_image() function). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At present, the HKEM reconstructions take ~4 min each on the STFC cloud platform, even with the current
rebin
statement. It'd be nice to speed this up at some point (not now).Options:
Use smaller data. I guess theres no need to do this example of the fine-tuning with a full 127x344x344 image. I guess in-plane image cropping would already help a lot. Using a scanner with fewer rings could help as well as well.
@danieldeidda @ashgillman I guess most of the run-time sits in the kernel computations themselves? Do you know if these run-times are roughly expected? (we seem to have some slow-down with recent jupyter). I've had a quick look at stir::KOSMAPOSLReconstruction.cxx and see you've put openmp loops already. I even recall some profiling. Changing STIR would need a STIR issues of course.
The text was updated successfully, but these errors were encountered: