Skip to content

Adding mesh_repulsion_general.scn scene so the whole mesh_intersection_resolver pipeline works as intended - #5

Open
FadiWahbeh wants to merge 13 commits into
dev_IT3Dfrom
SOFA_CGAL_Scene_for_the_automated_pipeline
Open

Adding mesh_repulsion_general.scn scene so the whole mesh_intersection_resolver pipeline works as intended#5
FadiWahbeh wants to merge 13 commits into
dev_IT3Dfrom
SOFA_CGAL_Scene_for_the_automated_pipeline

Conversation

@FadiWahbeh

Copy link
Copy Markdown

Based on #4

Summary

This PR adds mesh_repulsion_general.scn, a reusable SOFA scene based on MeshRepulsionEngine.

The scene doesn't contain patient-specific mesh paths, positions, translations, scales, or dimensions. The required values are injected automatically by run_intersection_detection.py before each execution.

What was added

1.General SOFA scene

The following reusable scene was added:

scenes/mesh_repulsion_general.scn

Instead of containing fixed patient paths, the scene uses placeholders:

{{MASTER_MSH}}
{{SLAVE_MSH}}
{{SLAVE_OBJ}}
{{CSV_PATH}}
{{EXPORT_BASENAME}}

Before running SOFA, run_intersection_detection.py replaces these placeholders with the files and output paths corresponding to the current patient and slave.

Consequently, the scene itself does not need to be edited when switching patients.

2. Finding Patients Folder

master

The master object is found using filename = "{{MASTER_MSH}}"

Slave

The slave is found using filename = "{{SLAVE_MSH}}

Export

The export will be in .OBJ format and is going to to be places is choosen in run_intersection_detection.py. But right now it's placed inside the folder of SOFA inside of Patient_xx folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants