Repository navigation
Option Voxec (Size, Thread, Chunk) #9
Description
Thank you for this work. however I have a question about the extent of extraction of surfaces because despite the reduction in size the slab and many other classes are not extracted (0.01). also for thread, I put 3 but the extraction takes an hour for a file of 10 MB. if you could recommend me tips for use it would be appreciated
Activity
aothms commentedon May 21, 2022
File size is not so relevant. It's really about the size in m3.
1cm is also already fairly detailed for the current code which isn't optimized a lot (e.g no GPU usage)
Depending on use case 5cm is either 55 or 55*5=125 times faster.
If you have an example file we can investigate issues with extraction. It's a bit arbitrary as how many voxels need to be collected for an element to be included. Maybe this results in false positives or false negatives in your case.
Takieddinex commentedon May 23, 2022
Hello, thank you for your reply. However, the problem that I encounter is that by modifying the different parameters, the result is not necessarily the most correct. I put you these two screenshots and I share with you an example model that I used .
Model init :
Model modify :
as you can see it always guards the stairs that are not supposed to be guarded
Here is an example
https://filesender.renater.fr/?s=download&token=bf19571c-40cd-4774-99bf-77c6962efb6a
I would also like if you could explain to me what's the logic for this code : does the bailiwick of voxel or does it proceed otherwise
Thank you