Hello,
Thanks for your answer @couet. I hope @agheata will see this thread.
I thought that maybe, when clipping, the shape is good but my results are bad because i use the TGeoVolume.Capacity() to control my operation and this method could be not accurate.
ps : I re-uploaded the source file due to a mistake on the first one.
The capacity for composite shapes cannot be accurate, it is computed by sampling (i.e. sample N point in the bounding box, then capacity = bbox_capacity*Ninside/N). The number of sampling points is now hard-coded to 10000. This could be configurable, but it will never be an accurate number.
Thanks for the answer.
I have two others questions
Do you know how is described an arc once a tube is cut (is it polygonized or really described as an arc) ?
Actually, I’m making an intersection of my big geometry with a simple shape (extruded polygon). I intersect recursively all the nodes one by one.
Is there an easy way to cut a massive hierarchical geometry by a shape ?
No shape is “polygonized”, it is only the shape representation used for visualization that does. It would be interesting to know why you need to do such a complex operation - if it is just for visualization this is done in the GL viewer (you can not use arbitrary shape however.
I’m working on a tool for reactor core conception.
Today, the first version of this tool is using shapely to compute the geometries. All the circles, arcs are “polygonized”. Once the geometry is created, it is send to a mesh tool and then to a solver.
We are studying ROOT to replace shapely and the actual complex geometry management.
It is why I’m asking about the precision of the operations. I do not found this information in the doc for the moment.
The reactor core are very large geometry then we need to cut them by 1/4 or 1/8 for example. I didn’t find a easier way to cut it than to recursively intersect all the interesting nodes by a shape.
