From NAMIC Wiki
Jump to: navigation, search
Home < Events:CTK-Pre-Hackfest-2010

The Common Toolkit Hackfest at the DKFZ in Heidelberg, Germany hosted by the MBI.

This is a working meeting - the goal is to start writing code!
Source: Heidelberg_corr.jpg
Group picture at a local restaurant
CTK team hacking...


The CommonTk homepage with links to other events and organizational information:


(1) Memory Management

  • Large Image Handling
    • streaming
    • out of core data management (memory mapped files, etc)
    • level of detail
    • Google Earth 3D
    • caching
  • Decide on smartpointers e.g. C++0x/Boost
    • Afternoon: check Qt vs C++0x/Boost smartpointers
    • Rule: Use Smartpointers of the super-class; if there is no super-class, use the one decided upon in the afternoon...
  • For large images, wait to see what ITK version 4 is planning to do.

(2) Migrate some code to the repository (e.g. Qt widgets) and use it in our respective toolkits

Steve: goal to make some progress on consolidating some Qt widgets from our various projects into a repository that we can all contribute to. Slicer Qt Project

See also CTK Widget Wish List Make use of Qxt? Qwt?

Slicer Annotation and Markup project for reporting

(3) DICOM IO layer on top of DCMTK: interpretation of DICOM data

(4) Interoperability of plugins

Steve: Summarize what would it take to make a standard that could handle at least the three following systems:

If we can handle those, then that's probably broad enough to cover many common scenarios.

Jc: PythonQt and the Qt based plugin architecture used in SlicerQt

Sascha, Olivier: Generic service oriented approach to expose modules for multiple platforms.

(5) Generic event mechanism (e.g. event bus, translate events into signals)

  • Sascha

Proposed Agenda


  • 19:00 Welcome Dinner at Hotel Ritter

Monday - Thursday

  • 9:00 Transfer by bus from Ritter to DKFZ (Note: every day)

Monday at DKFZ

  • 9:30 Short presentation of agenda
  • 9:45 – 12:00 Presentation of topic leaders 20 min each including discussion: requirements, existing libraries, … Coffee breaks on demand
  • 12:00 – 13:00 Lunch
  • 13:00 – 13:30 General discussion Goal: select three topics to start with in smaller teams
  • 13:30 – 16:00 More detailed exploration of topics
  • 16:00 Presentation of first results, planning of further agenda




  • Effort to plug some XIP code into MITK
  • Drafting a first generic plugin framework (based on Qt)

  • CTK Repository Naming Conventions:
    • CTK
      • Libs
        • Core (depends on QtCore, filenames start with ctk)
          • ctkBundleActivator.h
          • ctkBundleContext.h
        • DICOM
        • Scripting
          • PythonQt
        • Visualization
          • VTK
          • OpenInventor
        • Widgets
      • Utilities
        • DCMTK
        • KWStyle
        • ZMQ
      • Testing
      • Examples
      • Documentation
  • CTK File Naming Conventions
    • Considerations:
      • allow KWStyle regular expressions to identify coding style (style is based on parent class - vtkObjects use vtk style, QObjects use Qt style).
      • name should indicate dependencies - using ctk prefix implies QtCore dependency


  • TODO items for the day and beyond updates in italics
    • Add xip as external project to CTK superbuild requires small change to handle svn repository with a password (Jc)
      • widget needs to be added to ctk git done (Ivo/Oliver) - widget is plugged into MITK - need to plan follow up meeting to work out use cases for NA-MIC integration of XIP - could be done in Boston or in Princeton (Steve and Oliver)
    • Setup PythonQt as external project and add related widgets to CTK repository requires small rework - Jc will do
    • Setup nightly builds for windows, mac, linux linux set up, more to follow
    • Messaging - ctk class event manager and dispatcher as a demo (e.g. send IGSTK messages to MITK) - zmq supports both in-process and cross-process messaging. Patrick hecked in example multi-process messaging app (client/server)
    • Slicer CLI in MITK delayed a bit - Jc is refactoring the slicerqt CLI code into more generic widget and xml parser)
    • OpenIGTLink as superbuild external project (done - Patrick)
    • Qt Mobility running in linux - example service for discovering CLI in-process (Sascha)
    • Launcher in Qt todo (Steve/JC/J2)
      • Fast splash screen
      • setting paths
      • launching debuggers with paths resolved
      • monitor main application behavior (auto bug report?)
    • DICOM
      • Indexer working with CTK-built DCMTK - CLI existing - done (Marco)
      • Example application to tie sql database to qt widgets - mockup query/retrieve front end (Steve), database tree display widget (Julien)
    • Transfer function widget (next week or two) todo (Marco to help AlexY port to CTK to support integration with slicer)


  • Steve Pieper, Boston
  • Oliver Kutter, Siemens (SCR)
  • Patrick Cheng, Georgetown University
  • Julien Finet, Kitware Inc.
  • Jean-Christophe Fillion-Robin, Kitware Inc.
  • Julien Jomier, Kitware Inc.
  • Marco Nolden, DKFZ
  • Ivo Wolf, DKFZ
  • Sascha Zelzer, DKFZ