Issue Description:
The AREG module within the SlicerAutomatedDentalTools extension is currently experiencing issues with the latest versions of ITK and ITK-elastix libraries. It appears to rely on specific library versions, specifically ITK 5.3.0 and ITK-elastix 0.17.1 (with a test compatibility with SimpleITK version 2.2.1).
Context:
We need to ensure that specifying library versions doesn't lead to conflicts with other extensions. Therefore, I am seeking guidance on the best practices for specifying the required library versions for AREG to ensure smooth functionality without interfering with other extensions.
Request for Guidance:
Please suggest a recommended approach for specifying the required versions of ITK, ITK-elastix, and possibly SimpleITK within the context of a Slicer extension.
Given the holiday break, I understand that responses may be delayed. Any guidance or pointers on how to proceed in the New Year would be greatly appreciated. Thank you for your assistance in addressing this issue. It will help ensure the smooth operation of the AREG extension and its compatibility with the broader Slicer ecosystem.
@allemangD @jcfr @bpaniagua @lassoan @pieper @juanprietob
Issue Description: The AREG module within the SlicerAutomatedDentalTools extension is currently experiencing issues with the latest versions of ITK and ITK-elastix libraries. It appears to rely on specific library versions, specifically ITK 5.3.0 and ITK-elastix 0.17.1 (with a test compatibility with SimpleITK version 2.2.1).
Context: We need to ensure that specifying library versions doesn't lead to conflicts with other extensions. Therefore, I am seeking guidance on the best practices for specifying the required library versions for AREG to ensure smooth functionality without interfering with other extensions.
Request for Guidance: Please suggest a recommended approach for specifying the required versions of ITK, ITK-elastix, and possibly SimpleITK within the context of a Slicer extension.
Given the holiday break, I understand that responses may be delayed. Any guidance or pointers on how to proceed in the New Year would be greatly appreciated. Thank you for your assistance in addressing this issue. It will help ensure the smooth operation of the AREG extension and its compatibility with the broader Slicer ecosystem.