discrepancy in voxel size/FOV #147
Comments
|
Are you saying that there is a discrepancy between LTT and LEAP? Is it that the default volume gives different number of voxels or is it that the FOV mask is different? The code that calculates the default volume is here: And the code that calculates the FOV is here: |
|
Hi Kyle, sorry, yes I should have been much clearer. In one method, I am using LTT's loadsct, followed by setLEAPfromLTT. In the second method, I am setting the values with leapct.set_modularbeam(). Then, leapct.print_print() prints out 1 pixel-width different FOVs from the two methods (outputs are below). The 1-pixel difference changes the projections. If define an object (f) with Leap primitives, and forward project it to projections (g). f is different relative to g in the two methods. That's the 6149 reason I stumbled onto this discrepancy. I will start looking into the links and let you know what I find. Thanks for the response and links! --Seemeen leapct2.print_parameters() ======== CT Modular-Beam Geometry ======== ======== CT Volume ======== ======== Processing Settings ======== True
======== CT Modular-Beam Geometry ======== ======== CT Volume ======== ======== Processing Settings ======== |
When I try to set leap image volume parameters using an initialState.sct file, or when I set the parameters using setDefaultVolume(), I get a slight difference. Consider an image that is S x S, and the pixelsize is P
When using initialState.sct, the FOV = S x P, but when I use setDefaultVolume(), the FOV =(S-1) x P.
The text was updated successfully, but these errors were encountered: