This PR changes the structure of the Modules/ by adding a "component" layer. For instance, Filtering module now contains an "Objectness" component (which stays for the legacy filters found in Filtering/) :
Each module corresponds to a major step in the AngioTk pipeline
[MR input] -> Filtering -> Segmentation -> Meshing -> CFD -> MRI -> [MR output]
Core module would contains scripts that will implement an AngioTk pipeline by selecting specific components for each major step.
AngioTk automatically browses the Modules/ folder and adds CMake option. For now, every module is build by default. In the future, it could be relevant to check dependencies in order to set default to OFF if needed (eg. BUILD_MODULE_CFD OFF if Feel++_NOT_FOUND
This PR changes the structure of the Modules/ by adding a "component" layer. For instance, Filtering module now contains an "Objectness" component (which stays for the legacy filters found in Filtering/) :
Modules/ |-- CFD |-- Core |
-- ChainScripts |
-- src |-- Filtering |-- Objectness | |-- include | |-- src |
-- test |-- Meshing |-- MRI`-- Segmentation
Each module corresponds to a major step in the AngioTk pipeline [MR input] -> Filtering -> Segmentation -> Meshing -> CFD -> MRI -> [MR output]
Core module would contains scripts that will implement an AngioTk pipeline by selecting specific components for each major step.
AngioTk automatically browses the Modules/ folder and adds CMake option. For now, every module is build by default. In the future, it could be relevant to check dependencies in order to set default to OFF if needed (eg. BUILD_MODULE_CFD OFF if Feel++_NOT_FOUND