cuMemcpyHtoD failed! about deepdrr HOT 6 CLOSED

I have exactly the same issue.
cuda.memcpy_htod(
self.index_from_world_gpu, np.array(proj.index_from_world)
)
where self.index_from_world_gpu is allocated as 8 float32's and proj.index_from_world is a 4x3 float32. From an admittedly naive viewpoint, it looks correct this should result in a memory segmentation violation but obviously it works for most people - I am also eager to find a solution - the project seems awesome and can't wait to get it working!
I tried with Cuda 11.6 (Ubuntu 22.04( and 11.1 (22.04 and 20.04) - same result.
Soren

from deepdrr.

@benjamindkilleen do you have any pointers?

from deepdrr.

one thing I would mention is that scatter at the moment is not really supported as we have shifted our focus to other parts of the project. this is largely because scatter (the way we implemented here) did not considerably help our usecases. This is something that may change in the future, but currently we have no clear timeline.

from deepdrr.

I'm the short term, I recommend to disable scatter. (Set scatter_num=0) Long term, this is a feature we hope to make more robust, but it is not a high priority.

from deepdrr.

I'm the short term, I recommend to disable scatter. (Set scatter_num=0) Long term, this is a feature we hope to make more robust, but it is not a high priority.

Thank you so much for the help! Good to know that scatter functionality should be avoided for now and now I can run the examples!
Best,
Soren

from deepdrr.

I'm the short term, I recommend to disable scatter. (Set scatter_num=0) Long term, this is a feature we hope to make more robust, but it is not a high priority.

Thanks for your help! I do notice that once I canceled the scatter, it works well. I guess I'll just use it without scatter for a while. Hope your project getting better! : ）

from deepdrr.