CTK-Hackfest-May-2010

Introduction

Date: May 17-21

Location:

Georgetown University, ISIS Center

2115 Wisconsin Ave. NW. Ste 603, Washington, DC 20007 (Google map)

USA

Goal: A follow on to the wildly successful March 2010 pre-hackfest.

Requirements: attendees must be willing to spend their time with the details of dicom, git, cmake, c++, Qt, vtk, itk, openinventor, and related technologies. People who do not feel qualified for this are politely not invited :)

Group size: maximum 20 participants so we can have a manageable working meeting. The organizing committee will invite and select participants based on input from TheTeam.

Organizers: Ivo Wolf, Steve Pieper, Stephen Aylward

Site Hosts: Kevin Cleary and Patrick Cheng

Attendees: (due to limited space, please contact the organizers to attend)

1. Steve Pieper, Isomics, Inc., USA
2. Ivo Wolf, Hochschule Mannheim and DKFZ, Germany
3. Marco Nolden, DKFZ, Germany
4. Sascha Zelzer, DKFZ, Germany
5. Dan Blezek, Mayo Clinic, USA
6. Daniele Giunchi, Italy
7. Alessandro Chiarini, Italy
8. Pedro Omedas, Spain
9. Xavier Planes, Spain
10. Patrick Cheng, Georgetown
11. Ziv Yaniv, Georgetown
12. Micheal Onken, OFFIS, Germany
13. Will Schroeder, Kitware
14. Stephen Aylward, Kitware
15. Julien Jomier, Kitware
16. Julien Finet, Kitware
17. Jean-Christophe Fillion-Robin, Kitware
18. Oliver Kutter Siemens
19. Nicolas Rannou Harvard

Future Events: The organizing committee invited a group of developers to get the CTK project started and we've believe we've reached capacity for this event. Future hackfests will be announced in advance and we hope lots of people will be interested in participating. The venue and activities at future hackfests will be determined based on the number of active participants in the project.

Preparation

Developers should bring a laptop with the current CTK source code downloaded and built.

Use the CTK developers mailing list to discuss build issues and topics for ongoing work.

Topics and Projects

Pick up threads of discussion and activity from Pre-Hackfest

General set of topics (attendees, please flesh this out with your own ideas!)

DICOM

• Marco
• Cache/Database issues
• Application Hosting
• Unified CMake for DCMTK (Michael, JJ, Dan, Jc)

• Wednesday:
  • MITK superbuild, with CTK widgets
  • DCMTK CMakeFiles
  • Stalled on findscu - integrating dcmtk, fetchdicom, sumatra ideas into CTK implementation

• Friday:
  • Progress on ctkDICOM app (still much to do)
  • MITK now uses superbuild and ctkDICOMIndexer (to be committed in the next few weeks)
  • New demos of Service Class User (SCU) classes for DCMTK in CTK repository
  • Need more testing data and "dummy" server that can be run during tests
  • mingw build ctk for MAF to incorporate DCMTK in MAF (nightly build on mingw coming).

Integration

• Marco and Ivo
• Integrating CTK into MITK and Slicer
• Slicer's Execution Model into MITK

• Wednesday
  • Started the CTK App Launcher: http://github.com/jcfr/CTK-AppLauncher
  • Discussion of generalizing execution model independent of MRML, but may wait until next hackfest

Widgets

• Julien F.
• Review of CTKWidgets and wishlist
• PythonQt
• Wednesday
  • progress on transfer function editor

Events and Communications

• Patrick
• Inter- and Intra-process events
• Sascha
• EventBus as a Service
• Wednesday
  • patches for ZMQ and git repository

Plugins, Modules

• Sascha
• Plugin system: Design Document
  • Xavier: Writing a plugin for a vtk bulls eye plot as a service
  • Xavier: Writing an LDAP expression filter for use in the service framework
  • Sascha: Finishing the service registry for the plugin framework
  • Daniele: Integrating the MAF Event Bus as a plugin -> maybe discussion with Patrick needed

Interoperability

• Oliver
• Interfacing systems at the OpenGL level (i.e. VTK and OpenInventor)
• Wednesday
  • VTK/Inventor integration - basic demo working, but many integration issues being investigated

Organization and Workflow

• Steve and Jean-Christophe
• Conventions for using git. Ideas: gitwash example, dead simple example, vtk plans.
• Coding styles and conventions
• Dashboard issues (setting up nightly and continuous build machines)
  • Dash21 now has a nightly (documentation + coverage) and continuous dashboard
• Superbuild (Jc)
  • Solve problem related to MITK/CTK
  • Fix bug in FindDCMTK
• Wednesday
  • Work on git documentation
  • doxygen coming soon to doc.commontk.org
  • superbuild/CTK support for multiple applications MITK, MAF, gimias
  • Now 3 machines submitting to dashboard - JJ will do mac submission, SA and SP to do windows machines.

Agenda

Time	Monday, May 17	Tuesday, May 18	Wednesday, May 19	Thursday, May 20	Friday, May 21
07:30-08:00		Breakfast	Breakfast	Breakfast	Breakfast
08:00-10:00
10:00-10:30		Coffee	Coffee	Coffee	Project Review
10:30-12:30			Brief Status Update
12:30-13:30		Lunch	Lunch	Lunch	Adjourn
13:30-15:30
15:30-16:00	Opening	Coffee	Coffee	Coffee
16:00-18:00		Clinic Visit	Clinic Visit	Clinic Visit
Evening Event	TBA	TBA	TBA	TBA

Travel & Hotel

Travel:

1. For flights you can use Dulles Airport (code: IAD) (most international flights), National Airport (code: DCA) (closest), or Baltimore Airport (code: BWI) (alternative international airport but the furthest away)
   • DCA is about 7 miles away
     • Travel option 1: Taxi ($25)
     • Travel option 2: Metro blue line ($1.35 direction Largo Town, see map) to Rosslyn, and then take a taxi ($10)
   • IAD is about 23 miles away from the hotel
     • Travel option 1: Taxi/Super Shuttle ($50)
     • Travel option 2: Bus 5A ($3-$4) to Rosslyn, then take a Taxi ($10)

Hotel

1. We are reserving a room block at the Georgetown Holiday Inn: http://www.higeorgetown.com/
   • Room rate Monday to Friday May 17-21 will be 169 per night: single or double
     • We need to book 10 rooms to get this rate
     • Please sign up on the Wiki if you are attending and email me your hotel needs
   • Room rate the weekend before (May 14-16) will be 149 per night: single or double
   • Taxes are 14.5% additional
2. The meetings will be next door to the hotel at our research center

Connectivity

1. We will provide both wired and wireless connection