Improve accuracy of 360 stitching memory estimation

[yousefmoazzam]

Fixes #354

The main changes to the memory estimation are:

• the data shape change is accounted for (in particular, the sino width changes)
• several copies of a subset of the input array are accounted for

Acceptance criteria checklist:

• [x] Newly introduced memory hook tests for sino_360_to_180 pass
• [x] The variable names in the memory estimation code + code comments when connecting to the method code are understandable to other devs

[dkazanc]

Thanks, all seem clear me. Pretty memory-hungry one actually.

[yousefmoazzam]

One pretty simple way to reduce the amount of memory used is to make the weights array be float32 rather than float64; doing that would halve the amount of memory used by those 4 copies mentioned in the code comments.

I'll make an issue in the httomolibgpu repo so then we can address that at some point :slightly_smiling_face:

[dkazanc]

One pretty simple way to reduce the amount of memory used is to make the weights array be float32 rather than float64; doing that would halve the amount of memory used by those 4 copies mentioned in the code comments.

I'll make an issue in the httomolibgpu repo so then we can address that at some point 🙂

Thanks, there is no reason to keep it 64bit.