-
I just realized that for who knows how long, my input file stopped creating new ptrack files when I run it. I have just been viewing a single ptrack file that hasn't been overwritten for who knows how many modifications to my simulated geometry. Is there any list of issues that could just make a ptrack file not get created? Is there anywhere I could find a error saying that it wasn't created and why? Because I haven't gotten any errors saying it cant make one in the terminal output. Incase it matters, my geometry is mostly composed of ndgeometry cylinders, a cone stack, two boxes and a few union geometries. Is it some issue like you can only have one union geometry or you can't have unused geometries defined? I honestly have no clue how to troubleshoot this. ⬇️⬇️⬇️⬇️⬇️ |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It's a parallelization issue - you're not meant to have tracks being generated when you run in parallel since you can generate as large of a ptracks file as you could possibly want in a minute or less on a single core. My recommendation is just to turn off track generation when you parallelize. We should improve the messaging/documentation about this. |
Beta Was this translation helpful? Give feedback.
It's a parallelization issue - you're not meant to have tracks being generated when you run in parallel since you can generate as large of a ptracks file as you could possibly want in a minute or less on a single core. My recommendation is just to turn off track generation when you parallelize. We should improve the messaging/documentation about this.