NA-MIC Project Weeks
Back to Projects List
Common spline surfaces infrastructure for surgical planning in Slicer-Heart and Slicer-Liver
Key Investigators
- Gabriella D'Albenzio (Oslo University Hospital, Norway)
- Rafael Palomar (Oslo University Hospital, Norway)
- Csaba Pinter (Ebatinca, Spain)
- Andras Lasso (Queen's University, Canada)
Project Description
The primary goal is to unify the spline surface infrastructures of Slicer-Liver and Slicer-Heart, focusing on the integration of Bezier tensor product surfaces and NURBS tensor product surfaces. This integration aims to create a versatile and robust tensor-product surface filter capable of generating a variety of surface families.
Objective
-
Development of a Generic Tensor-Product Surface Filter:
Explore the feasibility of creating a filter that can handle both Bezier and NURBS surfaces, along with other potential surface types. -
Establishment of a Class Hierarchy:
Discuss the design of a class hierarchy that effectively supports different spline surface families. This includes determining the commonalities and differences between the current implementations in Slicer-Heart and Slicer-Liver. -
Creation of a Common Extension Framework:
Aim to develop a common extension framework that can be readily adapted for future extensions, ensuring scalability and flexibility. -
Integration with vtkAddon/VTK:
Consider how this new infrastructure could potentially be incorporated into the vtkAddon or VTK libraries, enhancing the broader community’s access to these tools.
Approach and Plan
-
Research and Analysis:
Conduct an analysis of the existing spline surface implementations in Slicer-Heart and Slicer-Liver. Identify the key features, limitations, and potential areas of synergy. -
Design and Development:
Develop a detailed plan for the implementation, including the architecture of the generic tensor-product surface filter and an eventual class hierarchy. -
Plan for further development:
As a common spline infrastructure could be useful in contexts wider than IGT, plan for further integration of this infrastructure in vtkAddon / VTK.
Progress and Next Steps
TBD