Voxel discretization

[patrickrentian-sudo]

I came across PicoGK while learning object-oriented programming and have since been using it for reactor design. I have a question regarding voxel resolution, because as far as I understand, PicoGK uses a single global voxel size for the entire model. This means that if I want high resolution in the reactor interior, all other regions are also voxelized at the same size, leading to unnecessarily large STL files. I imagine you/other customers may have encountered a similar challenge when as an example designing rocket engines with PicoGK. I could not find a solution online without modifying PicoGK’s underlying logic, so I thought I would reach out directly. Have you encountered this issue before, and if so, how did you address it?
I would greatly appreciate any insight you may be able to share and would be very happy to hear back from you.

[DavidDonelan]

Hi, the voxel size becomes an issue when converting to mesh, which is needed for the part to appear in the viewer. I would use a moderate size of voxel, say 0,5 mm when creating the logic, then for exporting STL files I would have individual Library.Go methods with different voxel sizes for different components.