1. William Lorensen GE Research Niskayuna, NY February 12, 2001 Insight Segmentation and Registration Toolkit

2. Agenda Introduction Chronology Recipe For Success Observations

3. What is it? A common Application Programmers Interface (API). – A framework for software development – A toolkit for registration and segmentation – An Open Source resource for future research A validation model for segmentation and registration. – A framework for validation development – Assistance for algorithm designers – A seed repository for validated segmentations

4. Chronology October 1999, Bethesda – Project kick-off January 2000, Niskayuna Requirements March 2000, Big Apple – Validation Strategies June 2000, Bethesda – Core classes February 2001, Salt Lake – Code reviews April 2001, Bethesda – Show and Tell July 2001, Seattle – Refactoring November 2001, Bethesda – Demos – Preparation for the beta February 2002, UNC Chapel Hill – Developer exchange

5. Recipe for Success Vision Strong Core Team Openness Core Architecture Light Weight Software Engineering Community Support Funding

6. The NLM Vision Create a dynamic, self-sustaining, public domain and extensible toolkit that will empower researchers throughout the world to develop new segmentation and registration algorithms and create new applications that leverage the NLM’s investment in the Visible Human Male and Female data sets

7. The Team GE CRD/Brigham and Womens – Architecture, algorithms, testing, validation Kitware Architecture, user community support Insightful/UPenn – Statistical segmentation, mutual information registration, deformable registration, level sets – Beta test management Utah – Level sets, low level image processing UNC/Pitt – Image processing, registration, high-dimensional segmentation UPenn/Columbia – Deformable surfaces, fuzzy connectedness, hybrid methods

8. Openness From the start, NLM recognized the value of Open Source software There are NO restrictions on the software The Team has embraced openness

9. Open Source Products

10. The Core - Requirements Shall handle large datasets – Visible Human data on a 512MB PC Shall run on multiple platforms – Sun, SGI, Linux, Windows Shall provide multiple language api’s Shall support parallel processing Shall have no visualization system dependencies Shall support multi-dimensional images Shall support n-component data

11. The Core - Architecture Established a core architecture and support classes in June, 2000 Team used the initial core to develop their algorithms Architecture team adapted and modified the core

12. Architecture: Data Flow A sequence of process objects that operate on data objects to generate additional data objects Data Filter Data Display/disk Data Filter Mapper Source

13. Architecture Segmentation – Fuzzy connectedness – Supervised/Unsupervised Classification – Level Set Shape Detection – N-D Morphological Watershed – Voronoi based – Gradient Magnitude – Balloon Force Filter – Region Growing – Watershed Dozens of basic filters

14. Registration Architecture Multi-Resolution Registration Framework PDE Deformable Registration Input Reference Target Reference Mapper Metric Transform Optimizer

15. Longitudinal MRI No Registration Checkerboard Source Original image Difference Target Original image

16. Longitudinal MRI Registration Checkerboard Source Original image Difference Target Original image

17. Lung CT No Registration Checkerboard Source Original Image Difference Target Original Image

18. Lung CT Registration Checkerboard Source Original Image Difference Target Original Image

19. microPet/Volume CT

21. Process: Extreme Programming

22. A Light Weight Software Engineering Process Based on the new Extreme Programming process – High intensity design, test, implement cycle – Supported with web-enabled tools – Automated testing integrated with the software development

23. Extreme Programming Compression of standard analyze, design, implement, test cycle into a continuous process

24. Insight Development Cycles Daily – dashboard Weekly – telephone conferences Bi-weekly – architecture reviews Quarterly – developer meetings Yearly – work assignments

25. Extreme Programming Daily Testing Is The Key Testing anchors the development process (Dart) Developers monitor the testing dashboard constantly Problems are identified and fixed immediately Developers receive e-mail if they “Break the Build”

29. Building a Community Initial community of consortium members Outreach to other groups – Siggraph – Digital Human – DOE Genomes to Life – IEEE Visualization – NSF Shape Modeling Workshop – Supercomputer Conference Public Beta, February 2002 Application development, both academic and commercial

30. Funding Seed funding by NLM and its co-sponsors – Establish an architecture – Implement a representative set of algorithms – Produce frameworks to accommodate new algorithms – Define a development process – Establish a community support mechanism Continued support will be needed – Outreach to other communities – Create applications – More algorithms to fill gaps – Infrastructure support

31. Observations Good mix of commercial and academic Importance of communication The daily rhythm of Extreme Programming The Whole >>> Sum of the parts This process can (and should) be repeated

32. Insight Segmentation and Registration Toolkit William Lorensen GE Research Niskayuna, NY February 12, 2001