Engineering:TCON 01 19 2006

Agenda:

Every Week: Review the NA-MIC To Do List

• What are the next steps to include Teem and Deft software tools from Gordon officially into the NA-MIC Kit? So far, the following has been done:
  • License for Teem has been changed from LGPL to LGPL + static linking exceptions (same as FLTK)
  • Teem now building with CMake, and has a dashboard (thanks Andy!)
  • Slicer now uses Teem, currently for 3x3 eigensolve, but also experimenting with its fiber tracking, and tensor estimation from DWI
  • NRRD DWI format tutorials have been presented at NA-MIC meetings
  • wiki pages for tutorial are also present
  • several NA-MIC people are using the tools (BWH, UNC, UUtah)
  • In his talk at the programming half week, Andy used Teem and Deft as examples of how easy it can be to apply CMake/CTest/Dart/CPack to software previously not using it

• Any questions from programming half week?

• Jan 31st is the date to complete the summary slides for the half week activities. Should we invite participants for a review on Thursday, Feb 2nd?

• July dates being considered for MIT programming week.

---

TCon

Questions:

• Steps to include teem in the namic kit.
  • Problem with LGPL and static lib, move to a license to allow static.
  • Complexity of the license (half a page) vs 20 pages. Follow FLTK path.
  • Slicer now ships with teem (binary format)
  • Teem has now a dashboard, 12 active developers.
  • Teem-nrrd has a different license for ITK (with name mangling).

• Since Slicer ships ITK/VTK, do we do training for ITK ? VTK Tutorials ? This is Kitware business. Teem is different on that subject (no gordon company).

• Need a review process for Slicer ala ITK (Insight Journal). No policy so far (ISC). Question I have a new algorithm : put it in ITK or teem (low level)? Where do we direct those users ? Somewhat similar to ITK-vnl.
• Can NAMIC help the use of a particular tool. For instance the dashboard help found bug in teem (win compiler).
• Teem need more tests, and a wiki (building...)
• How to add the tool (deft) to slicer ? Problem of glyph in VTK which is much slower. But deft is only info and not a bench. NAMIC kit any publication should be reproducible using the NAMIC tool (problem with matlab since we are not distributing). This is not a software engineering tool, more software tool, data inspection, develp tool. Falls in the same cat as imagemagick...

• ITK using teem should not go into ITK, but remain in NAMIC.

---

NAMIC TODO List: Validation. Make it easier for user. DBP framework ? Need regression testing for the VTK class in slicer. Problem of infrastructure : new scanner change the reprodicibilty.