-
Notifications
You must be signed in to change notification settings - Fork 3
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
Overestimation of max slices for sino_360_to_180
#354
Comments
I found some info in an issue in httomolibgpu that could be helpful for addressing this problem (if the shape of the stitched sinogram is calculateable, then the number of bytes in a single sinogram can be calculated from the stitched sinogram shape + data type). Originally posted in DiamondLightSource/httomolibgpu#107 (comment)
|
One possible way to achieve the above would be:
For reference, the current methods database entry for httomo/httomo/methods_database/packages/external/httomolibgpu/httomolibgpu.yaml Lines 22 to 30 in 4429711
|
thx, looks like the dedicated memory estimator for that function is the way to go. |
Setup:
hopper
node/mnt/gpfs03/scratch/data/imaging/tomography/tmp/testdata/360/112482.nxs
The following pipeline:
produces a CUDA OOM error on the first block being processed by the
sino_360_to_180
method:As
sino_360_to_180
is the only method in its section, only its memory estimator is determining the max slices for its section, which implies that its memory estimation must be incorrect.The text was updated successfully, but these errors were encountered: