Kyle Champley

I actually got a cudaMalloc error when I tried this. Turns out this was caused by LEAP trying to allocate data with a negative number of elements. I fixed this...

Thanks @[ProjX0](https://github.com/ProjX0) and @[hws203](https://github.com/hws203) for this discussion. It has helped me find and fix several bugs in LEAP, making this toolbox better. If you find LEAP useful, please consider giving...

Are you using the latest code? I just fixed this bug about 48 hours ago. You can just pull from the main branch because I merged all changes to main....

Thanks for your patience. I found and fixed another bug that hopefully solves your issue. Apparently, I forgot to account for the extra memory used by texture memory and I...

I just cannot reproduce those blurry results that you guys are getting. I've tried both of your data sets on two different computers (Windows with 2 1080Ti GPUs and Linux...

I recommend starting with a cone-beam specification, converting it to modular-beam, and then tweaking the geometry specification to match your geometry. Like this: leapct.set_conebeam(...) leapct.convert_to_modularbeam() ... See [demo 25](https://github.com/LLNL/LEAP/blob/main/demo_leapctype/d25_detector_dithering.py) for...

Uh, ya, there are a few methods in LEAP you could try. I guess the main method you could try is iterative reconstruction. If you know the overall shape of...

I added a new sample script that demonstrates a cone-beam artifact method. Its currently on a development branch here: [d33_reducingConeBeamArtifacts.py](https://github.com/LLNL/LEAP/blob/champley_dev/demo_leapctype/d33_reducingConeBeamArtifacts.py) Here is an example of the results: 

@scf819 did you try the above demo? Did you have any other questions about reducing cone-beam artifacts?

Those iterative reconstruction steps are an overkill just to make the method super robust. You can get results that are almost as good by quantizing the FBP result and then...