Engineering:TCON 2008

Back to TCON:Main

Slicer 3 Dartboard

Link to the Slicer 3 Dartboard here

2008-02-14

• Attendees:

Other NA-MIC Projects

16 - CPack: Slicer3 compiles and packs using the new C-tools with some bug fixes. Using CMake to select desired modules, using something similar to cygwin. Official Slicer3 snapshot tagged. Different Tcl/Tk versions are currently used for different platform. This need to be addressed.

17 - Slicer GUI Style Guide and Cookbook: This will be a long term effort. During the programming week, the design and implementation details were discussed. The Cookbook will be launched from Slicer, act like KWWidget tour.

18 - Volume rendering: UI is fairly stable.

19 - Volume rendering using Cuda:

20 - 3D W Widgets and Picking: found a list of candidates of widgets for Slicer. A few bug fixes for VTK.

21 - XNAT Integration: Requirements were gathered for a XNAT application that organizes files and caches files from XNAT repositories. Some XML format issues have been addressed.

22 - KWWidgets Roadmap: Gathered requirements. Been working down the list of the feature requirements.

External Collaboration

1 - Astronomical coordinate system support [Harvard IIC]

2 - New Meshing Techniques into NA-MIC

3 - Meshing Workflow into Slicer

4 - Evaluating NA-MIC Tools for Small Animal Imaging Workflows

5 - IGSTK-Slicer [Georgetown]

6 - Japanese Intelligent Surgical Instrument Project

7 - GoFigure:High-Level Microscopy Image analysis Application and Algorithms

8 - Doing microscopy image analysis with Slicer3 [The Ohio State University]

9 - fMRI Analysis with Slicer 3 [The Ohio State University]

10 - Resampling DTIs with Slicer 3

11 - Analyzing fMRI and concurrent EEG with Slicer and SCIRun [BWH]

12 - Bayesian hierarchical models for fMRI variance components analysis

2008-02-07

• Attendees: Ron, Will, Steve, Wendy, Nicole, David G, Mark S., Casey, Sebastien, Curt, Luca

• Look at upcoming VTK 3D widgets
• Review of projects from SLC AHM 2008 http://wiki.na-mic.org/Wiki/index.php/2008_Winter_Project_Week

DBPs

1 - Stochastic Tractography in Schizophrenia (need to be invited to follow-up TCon)

2 - Cortical thickness analysis - testing EM segmenter to their data. They estimated parameters and tested during the week. The goal now is to compare ITK-MS and EM segment module to see how these two tools compare for cortical thickness. They are reviewing the tools using the same patient data.

3 - (Mark Scully) Legion segmentation using EM segmenter and other options - worked with Brad using 2 channels of data. Flare as 3rd channel caused problems. Desired to have T1/T2/Flair together as three channel dataset. Marcel is going to deliver his segmentation algorithm software to them to compare results.

4 - Robotic Prostate Interventions - (David Gobbi) Working on transrectal biopsy module for Slicer. They had a previous module for transcranial biopsies. One of the most exciting developments was a new prototol "open IGT-Link" which will replace navitrack inside Slicer. Image transfer is working over this protocol. A simulator is being developed for the robot. A few VTK bugs may have been discovered during this process, but it isn't on the top priority list right now.

5 - Prostate Cancer - Wrote new ITK filter that has been submitted to the Sandbox. They are looking at spherical wavelets for shape segmentation. The wiki page will be updated soon.

Other NA-MIC Projects

1 - Groupwise Registration - (Casey) New Bspline registration method is being developed here. It has been used for another project by Casey (#6). Page needs to be updated.

2 - (Need to be invited to follow-up TCon)

3 - (Need to be invited to follow-up TCon))

4 - (Need to be invited to follow-up TCon). Page needs to be updated

5 - Incorporating DTI tools into NAMIC toolkit - They are gathering a dataset that has both structural and DTI data in agreement. Previous dataset was missing part of cortex. UNCDB2 dataset has full coverage of the brain. Resolution is a bit lower, but full coverage is an advantage. Page is close to up to data. Just submitted a paper to ISBI 2008 and working on MICCAI paper, as well.

• NITRIC is g-forge and would be a good place for automated build process for Slicer modules. This could make it easier to configure Slicer in client labs without need to build from source. This is still being developed by the NA-MIC core team. There is an entry on the collaboration section of the NA-MIC website. Also www.slicer.org/Documentation link.

6 - (Casey) Worked with Serdar using groupwise registration tool. They are currently evaluating results of this study. More images will be added.

7 - (John Melanakos) Spent last week working with collaborators on the MICCAI paper. Project page is well filled.

8 - (Need to be invited to follow-up TCon)

9 - (Need to be invited to follow-up TCon)

10 - MRML scenes for execution model. Some of the issues Brad was having have been resolved. Alex is making adjustments to MRML library as needed for the EM segmentation model.

11 - (Curt) Unstructured Grids in Slicer - Finite Element modeling process was originally in a standalone VTK application. The first Slicer module integration did not use MRML based storage. We are now creating subclasses of Model and Unstructured grid data for storage and display in Slicer. Some minor issues need to be worked out, but the MRML extensions for UnstructuredGrid datatypes are working.

12 - Python (Luca) MatPlotLib plots are close to happening within Slicer. Steve believes it is 80% complete. Python command line modules are working now. Multiple arguments had to be worked by Luca. He has developed Python-based CLI modules. The event broker is discussed here because it affects the interaction with Python, because a Mutex lock has to be placed on the MRML scene. Dan has been helping with metamodules - a single Python module which calls other mothers (hierarchical execution, recipes, etc.).

• Ron asked about using this scripting technique for the ModelMaker. Some of the parameter setting, etc. could be set in the top module. Nicole will look at this. Kilian said that he wanted to call the "modelmaker" from another module.

• A need was identified for new wiki pages: (1) scripted modules, (2) metamodules, (2) python scripted modules

13 - (Luca) Transform hardening - Sometimes images are not XYZ alligned. How will command line modules treat an object if it is the child of a transform. The module needs to be able to apply xforms to data (after hierarchy is flattened) to get xformed data. Jim and Steve talked through this lately becomes of the transforms access two-directions (from parents / to parents, etc.) They are looking at how to change the model.

14 - (Steve) MRML support for out-of-core processing - Steve put a link to a new page. Dan, Jim, Wendy, Steve, etc. working through NAC renewal grant (5 years). Multiresolution and asynchronous data are likely targets for this effort, but it will be a long-term effort.

15 - Event Broker discussion - Steve has made process on this, but this wiki page is older. See the event broker page. (look at link under Objective). New term "observation" : completely introspectable. A full dependency between objects is implemented. When a subject issues a "modified" event, Delete events are maintained. Complete "relationship" management of the interaction between objects. This helps by allowing asynchronous event processing. MRML has been converted to use the event broker with asynchronous events managed by the Slicer GUI (async events invoked after GUI events are done). This hasn't broken anything so far, but should improve scalability. Dot logfile format can be generated for inter-object dependencies. This can be used to help provide "who called who" traces. Some special magic is done in MRML Display nodes. They set "observation nodes"

Next Week

Continue through project review. Request missing project members to attend. Review wiki pages.

2008-01-31

Attendees: Jim, Steve, Stephen, Wendy, Xiaodong, Nicole, Katie, Ron

• Project week follow-up
  • Half of tcon on Feb 7
  • Half of tcon on Feb 14
• Registration
  • Viola-Wells optimizations need to be enabled
  • Stephen needs to check-in and publish recent changes
  • Stephen needs to update the wiki
  • Luis continues to make optimizations (main focus is memory reduction)
• BatchMake
  • Grid Wizard - meeting on Monday
  • Integration with Slicer delivered via getbuildtest2
• New webpages
  • http://slicer.org
  • Uses wiki-to-web
  • Feel free to edit/improve
• Slicer-specific wiki
  • Migrating appropriate info from Na-mic to slicer
  • Hold off on adding to Slicer-wiki until notified
    • Continue using Na-mic wiki
• New Nitrc project
  • Jim Miller is leading
  • "Slicer3 plug-in examples" project
  • http://nitrc.org - search for slicer3
    • Includes demo/stub for ITK filtering data, etc.
  • Collection associated with an ITK course being taught
  • Requires CVS version of ITK
  • Works with Slicer build and Slicer install
  • Steve P is the liaison with NITRC
• Slicer tutorial at UNC, April 14th
  • Working with UNC's BRIC (http://www.bric.unc.edu)
  • Sonja, Randy, Martin, Stephen
• User-level Slicer training - Feb 20 at BWH
  • 1249 Boyleston
  • Release version of Slicer3

2008-01-24

Attendees: Jim, Steve, Wendy, Xiaodong, Nicole, Katie, Alex, Luis, Ron, Will

• Project week follow-up (Next week?)
  • Will will send email invitations for first half of projects for next week's tcon
• Loadable modules
  • Alex and Terry are rearranging Slicer3.cxx to support loadable modules
  • Separate branch for built-in module discovery process
  • Sebastien is working on build issues for modules whose code is outside Slicer3
• GenerateCLP - Thanks Hans for changes to support building modules
  • Hans is running a class this semester where the students will build Slicer CLI modules.
  • Jim is working on an ExampleModule for people to use as a template for building modules outside of Slicer3. Perhaps NITRC.
• XML library
  • What to do with libaries that are too big to include in the source directory?
• AHM 2009, Jan 5-9, 2009
• Summer Project Week, Jun 23-27, 2008
• New server architecture for wiki, svn, publication database

2008-01-17

Attendees: Jim, Katie, Sebastien, Stephen, Luis, Steve, Wendy, Will

• Luis and Bill Hoffman are making progress in making ITK installation relocatable. This is needed to finish the work on building plugins from an installation.
• What's in VTK 5.2?
  • Infovis - Tables, Graphs, Views, IO
  • Refinements to WWidgets. Client/Server connections within the widgets. Event translation. New widgets (text, caption, affine, checkerboard, rectilinear wipe, annotation, key frame, contour, measurement, point/placer, plot)
  • Build now? Or wait until 5.2 released?
  • Repository freeze in March
  • Release on April 1, 2008
• ITK release
  • Patches to ITK 3.4
    • Nine component/six component tensor conversion in IO has been patched to ITK 3.4
  • 1/19-2/1 moving contributions on Insight Journal for ITK 3.6
  • Move items from Review directory to main tree (QuadMesh, TransformIO) for ITK 3.6
  • Freeze repository 2/29 for ITK 3.6
  • Slicer3 will need to build against the Review directory.
• CMake release
  • Version 2.6 on the horizon - release candidate in 3 weeks.
• Tcl/Tk 8.5
  • Sebastien has a Windows build
  • Steve will try it out
  • Wait to switch to 8.5 until we have a good reason
• Loadable modules
  • Sebastien - working on CMake issues on building modules as loadable modules
  • Terry - working on loading modules and reworking Slicer3.cxx
• Event Broker
• DWI DICOM as part of the Load Volume. Xiaodong is working on it.
• ITKFactories directory in build and installs to hold ImageIO plugin libraries. Should increase the speed of executable plugins on the Mac.
• OpenIGTLink
  • Protocol on the wiki (message format)
  • Put code in Sandbox, SourceForge, NITRC, Google Code???
• Will schedule a time to go over the Project Week results

2008-01-10

No tcon due to AHM

2008-01-03

• Attendees: Jim, Steve, Will, Brad Davis
• Topics:
  • Jim and Will talked about leading the Monday and Friday sessions, and who would do what.
  • We are going to send out reminders to the project leads to ensure that their project descriptions are up to date
  • We discussed the software process project to make sure that we have a chance to address the Slicer build process, dashboards, etc.
  • We decided not to hold the project wrap-up presentation at AHM; we will do that later at subsequent TCons. (We decided that we needed the time to actually work. We are concerned that we are starting to see too many break-outs and not enough time to work.)
  • We keenly missed Tina and hope that she and her family are doing well.