[SOFA] Creation of new componeent responsible on translating the skeleton txt file into a vtk one

[bouamarakamelia]

1. Description

Adds a new SkeletonReader component to MeshSkeletonizationPlugin.
It reads the polyline skeleton file produced by MeshSkeletonization and rebuilds it in memory as a proper node graph
(id, parents, children, mesh correspondence), rooted as a tree from a chosen entry point, and exportable as .vtk for visualization in ParaView.

2. New features according to the 3 main classes

SkeletonNode : skeleton point as a data class

Plain C++ class (no SOFA/CGAL dependency).
Stores id, 3D position, parentIds/childrenIds, and optional mesh-correspondence fields (meshVertexId, distanceToMesh).

SkeletonGraph : parsing + tree building

• loadFromFile(): parses the polyline text format, merges coincident points into one node.
• buildTree(): BFS from an entry point, fills parent/child ids, flags loop/anastomosis (when veins loop over each other) edges instead of dropping or duplicating them.
• computeMeshCorrespondence(): links each node to its closest mesh vertex.
• exportToVTK(): writes points, tree-edge lines, and type/depth/is_loop scalars.

SkeletonReader : SOFA DataEngine wrapper

Exposes the above as scene Data fields (filename, inputVertices, entryPoint in; outputVTK, nodeCount out).
Registered in init.cpp alongside MeshSkeletonization.
init() forces one update() pass so it also runs correctly in batch mode, not just when a GUI happens to read its outputs.

3. Results

A comparison window between the txt file output on SOFA and the vtk file output dependent from MeshSkeletonization plugin on the left opened in 3DSlicer.

[epernod]

Why do you remove the 3 skeletons in txt ?

a few small remarks in the code to be changed.

[epernod]

Those 3 methods need to be in public as they are overriding mother class

[epernod]

good practice is to add that before returning:
sofa::core::objectmodel::BaseObject::d_componentState.setValue(sofa::core::objectmodel::ComponentState::Invalid);

[epernod]

in future version of SOFA we plan to generalise the check of this componentState, if a component is invalid we don't call it later in the simulation, etc...

[bouamarakamelia]

I'll take it into consideration.

[epernod]

no sure those should be there otherwise we will never be able to add new files

[bouamarakamelia]

Since we're not supposed to put big files in, i put them in the gitignore so they wouldn't be pushed in.
I had a lot of data.