Commontk - User contributions [en]

CTK-Hackfest-Dec-2012

2012-12-20T15:25:25Z

Yves.martelli: Added link to CLI testing code on github

== Event pictures ==
Images from the hackfest
<gallery widths=300 px heights=200px perrow=3>
image:Bologna-2012-12-12 16.55.22.jpg|<big>Bologna as seen from Asinelli tower</big>
image:CTK-Hackfest-2012-Bologna-Palazzo D Accursio.jpg|<big>Visiting Bologna</big>
image:Bologna-2012-12-12 17.23.11.jpg|<big>Julien taking the photo of everyone else</big>
image:DSC02729.JPG|<big>Presenting results</big>
image:DSC02730.JPG|<big>Exchanging ideas</big>
image:DSC02727.JPG|<big>Hacking</big>
image:DSC02726.JPG|<big>... and hacking</big>
</gallery>

== Introduction ==

'''Date:''' December 10-14, 2012

'''Location:''' [http://www.iporticihotel.com/en | Hotel i Portici] in Via Indipendenza , Bologna, Italy, Sala Montagnola (Room)

'''Goal:''' A follow on to the [[Commontk:Current_events#Past_events|wildly successful previous hackfests!]]

'''Requirements:''' Attendees must be willing to spend their time during the event writing ctk code that contributes to the main [[CTK-Roadmap | ctk roadmap]]. This means spending the week immersed in C++, Qt, DCMTK, CMake, and related technologies. People who do not feel qualified for this task 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]].

'''Site Hosts:''' Alessandro Chiarini, Daniele Giunchi

'''Organizing Committee:''' Ivo Wolf, Stephen Aylward, Steve Pieper

'''Future Events:''' 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. We welcome participation via the CTK email lists, the source code repository, and this website.

== Attendees ==
*So far we have received confirmation for the following people (in no particular order).

'''WE HAVE REACHED THE MAXIMUM NUMBER OF PARTECIPANT - REGISTRATION CLOSED - 16 PARTECIPANTS
'''

Please fill in your intentions in terms of common accommodation.

{|class="wikitable alternance" style="text-align:left; border:1px solid black;"
|+ '''''Participants'''''
|-
! scope=col style="background:#cde6f8;"| Name
! scope=col style="background:#cde6f8;"| Organization
|-
|Alessandro Chiarini
|SCS, Bologna IT
|-
|Daniele Giunchi
|SCS, Bologna IT
|-
|Alberto Losi
|SCS, Bologna IT
|-
|Steve Pieper
|Isomics, Inc., Cambridge, MA, USA
|-
| Ivo Wolf
| Mannheim University of Applied Sciences & DKFZ Heidelberg
|-
| Jean-Chistophe Fillion-Robin
| Kitware
|-
| Julien Finet
| Kitware
|-
| Andreas Fetzer
| DKFZ Heidelberg
|-
| Michael Bauer
| DKFZ Heidelberg
|-
| Marco Nolden
| DKFZ Heidelberg
|-
| Sascha Zelzer
| DKFZ Heidelberg
|-
| Florian Vichot
| INRIA
|-
| Yves Martelli
| UPF
|-
| Claire Mouton
| CREATIS
|-
| Miklos Espak
| University College London (UCL)
|-
| Luca Antiga
| Orobix
|-
|}



{{Note}}There were also other invitations sent to active people on the community, and people who recently showed interest. When their intent will be known they will be added to the list.

== Preparation ==

Developers should bring a laptop with the [http://github.com/commontk/CTK current CTK source code] downloaded and [[Build_Instructions|built]].

Use the [http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers CTK developers mailing list] to discuss build issues and topics for ongoing work.

Phone conferences have been scheduled in the weeks leading to the event:
* To be announced

== Topics and Projects ==



==== DICOM Application Hosting ====

* Refine, extend, [[DICOM_Application_Hosting_Testing | test]], and integrate with applications
* See also [[CTK-Hackfest-Nov-2011#DICOM_Application_Hosting | (some still open) tasks]] and [[Hackfest_Nice_AppHosting_Progress | progress]] from the last hackfest
* Goal: connect some real code via command line interface

==== DICOM Database and Networking ====

* Dig into ongoing developments. See [[CtkDICOM]] for discussion.
* See CTK DICOM support is used in Slicer 4.2
** [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.2/Modules/DICOM End-user documentation]
** [http://na-mic.org/Bug/search.php?project_id=3&category=Module+DICOM&sticky_issues=on&sortby=last_updated&dir=DESC&hide_status_id=90 Slicer4 DICOM Bugs and Feature Requests]
** SlicerRT Issues:
*** https://www.assembla.com/spaces/slicerrt/tickets/25 - display of ^ (carat character) in ctkDICOMModel
*** https://www.assembla.com/spaces/slicerrt/tickets/153 - extension import failure (slicer issue)
*** https://www.assembla.com/spaces/slicerrt/tickets/36 - non-uniform study information in RT files

==== QAT ====
Quality Assurance Toolkit -> how to integrate in CTK

==== Widgets ====

* Discuss and refine as needed.
* [https://www.assembla.com/spaces/slicerrt/wiki/20120125_Slicer_DICOM_browser_meeting SlicerRt example dicom interfaces discussion]

==== Tests Framework ====
Try QtTesting with CTK applications

==== Build Systems & Software process ====



* Update to [http://git.dcmtk.org/web?p=dcmtk.git;a=summary latest DCMTK]
** includes dcmrt
** need to pick a commit to standardize on
** investigate shared/static library building. (Static instances of classes getting destructed in wrong order)
** incorporate version checking
*** build ctk against head or snapshot version

* Prepare Debian packaging (Marco)
** Resolve outstanding issues
** Make CTK also build with latest stable DCMTK release (3.6.0)

* Evaluate Qt5 (Sascha)

* <del>Setup developer package</del>
** See [https://github.com/commontk/CTK/issues/10 #10] and [https://github.com/commontk/CTK/issues/65 #65]
** Work in progress - See topic [https://github.com/jcfr/CTK/compare/65-packaging-support 65-packaging-support]


** Release a version of CTK (Work on policy this week and maybe release this week).


** Work in progress - See [https://github.com/jcfr/CTK/compare/master...cmake-doxygen-filter-reuse cmake-doxygen-filter-reuse]

==== Command Line Modules ====
* Extract CLI interface
** Unify VPH and Slicer refactoring
* Qt SEM XML widget
* Follow on interoperability tests done in [[CLI_In_Context]]
* Refine CLI XML standard
** Text format for description/help/acknowledgement/resources: plain text ? html ? structured text ? github markup ?
** Multiple categories per module ?
** CLI XML versioning.

== Agenda ==

==== Monday ====


10:30am Welcome

10:45 - 12:00 Round table: everyone presents 10-15 minutes how CTK is used in their project. And what's new in CTK (what has been added since previous hackfest)

: CTK in use:
:* MSVTK: [http://www.msvtk.org/content/electro-physiological-dataset-application ECG], HAI, Buttons (DG/AL, JF) (10m)
:** Give your feedback: http://www.msvtk.org/content/evaluation
:* [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/DICOM DICOM in Slicer] (SP) (5m)
:* [http://www.commontk.org/index.php/Documentation/CLI_In_Context CLI in Gimias, MITK, NiftyView, Slicer] (SZ, YM, ME) (10m)
:* CTK in MITK (MN) (5m)
: What's new since last hackfest?
:* [http://www.commontk.org/index.php/Documentation/Command_Line_Interface CLI] in CTK (SZ, YM) (15m)
:* DICOM Tag caching (SP) (5m)
:* [http://www.commontk.org/index.php/Documentation/ImageGallery Widgets improvements] in CTK(JF, JCFR) (5m)
:** New: ctkExpandableWidget/ctkSizeGrip, ctkPathListWidget
:** Tweaks: ctkCoordinatesWidget (normalized), ctkPathLineEdit (sizeHint), ctkPanelSettings (user/revision settings),

1:00pm Lunch

: Discuss plans/priorities for hacking

3:30pm Coffee Break

hack, hack, hack...

5:00pm Close

==== Tuesday ====

9:30am Welcome
* Review of Topics and demos
11:00am Coffee Break
* Discussion of goals for the week and breakout into working groups

* Command Line Module Working Group Topics
** Using ctk CLI infrastructure in Slicer (Jc, Sascha, Julien)
** CLI Incremental Communication (Luca, Steve)
** MAF CLI Integration (Daniele, Alberto)
** PythonQt wrapping of ctkCLI
** DAH and CLI (Ivo)
** CLI Compatibility Testing (Yves)
** CLI In MedINRIA (Florian)
* CTK Qt Testing and Quality Assurance Toolkit (Claire, Andreas, Julien, Jc)
* Transfer function interaction (Julien, Florian)
** Publish previous CTK hackfest work into VTK
** Minor interaction tweaks

1:00pm Lunch

hack, hack, hack...

5:00pm Close

hack, hack, hack...

==== Wednesday ====

9:30am Welcome

hack, hack, hack...

11:00am Coffee Break

hack, hack, hack...

1:00pm Lunch

hack, hack, hack...

5:00pm Close

==== Thursday ====

9:30am Welcome

hack, hack, hack...

11:00am Coffee Break

hack, hack, hack...

1:00pm Lunch

hack, hack, hack...

5:00pm Close

==== Friday ====

9:30am Welcome

hack, hack, hack...

11:00am Coffee Break

Wrap up discussion and presentations:
* Alberto, Allesandro (for Daniele)
**MAF2,3 migration
*** Use CTK command line module explorer as MAF3 Plugin
*** Wrap MAF2 modules as CLIs
*** Solution to the WXWidgets (MAF2) to Qt (MAF3) migration with uniform solution
** QAT running on CTK source code, working to make it more widely available
** Migrating MAF plugins to CTK plugins
* Claire
** Fixing configuration issues, to be improved by JCFR : https://github.com/commontk/CTK/issues/258
** Fixing compilation issues, merged to CTK master branch : https://github.com/commontk/CTK/issues/268
** Fixed a bug in QtTesting, merged to CTK master branch : https://github.com/commontk/CTK/issues/269
** Working with Qt Testing and QAT for CREATIS (working to migrate to Qt)
** Will report back in Lyon
* Miklos
** XNAT Plugin replacing curl with Qt network and ssl
** Working with Jc on REST API implementation generalized across MIDAS and XNAT
** With Sascha and Jc: updates to the build system to support plugins - new superrepository that has git submodules for optional plugins
* Sascha
** Superrepository and build system (see issue [https://github.com/commontk/CTK/issues/266 #266] and its corresponding [https://github.com/commontk/CTK/tree/266-checkout-repositories-at-build-time branch])
** Looked into Qt5 (see issue [https://github.com/commontk/CTK/issues/277 #277] and the [https://github.com/commontk/CTK/tree/qt5 qt5 branch])
*** some ifdefs required for deprecated functions
* Andreas
** Putting Qt Testing into MITK
** Some issues being sorted out
* Marco
** Debian packaging
*** dcmtk 3.6.0 build compatibility (with remote help from Michael Onken)
*** Some debian specific patches in a separate branch
***vtk 5.8 compatibility
*** aim for named version release CTK within 6 months (for debian/ubuntu release)
* Michael
** Fixed selection of query results for retrieval
** Refactoring Query and Retrieve
*** New ctkDICOMOperation (superclass)
*** May rename some widgets for consistency
* Florian
** CLI modules now work in MedINRIA!
*** Interface is generated
*** command line executable can be run
*** Looking at specializations of GUI to support MedINRIA concepts
** Fixes to some Qt style / css compatibility issues
** Issue is reported to Qt, and now will be included in Qt 5.1
* Ivo
** DICOM Application Hosting
*** Updated dah branch to the latest master
*** Embedded dah into MITK
*** MITK as hosted application
*** ...and MIT as a host!
* Yves
** New tests for CLIs
*** CLI finishes with error
*** CLI checks that defaults are as expected
*** CLI checks that image data passed from host is the same as when read from disk
** Code could go into Slicer Execution Model repository, for now it is there: https://github.com/ivmartel/semit
* Julien
** Lookup table editor
*** layers of lookup tables
*** Combine and edit layers independently
*** Integrates Florian's work from Boston hackfest
** Issues of ordering of XML for XML Schema comptibility
* Jc
** Build system work
** Shared library backend for CLI framework
** Updated XSD / XSL to handle additional element
** Integrated CTK CLI module framework to Slicer
*** Still uses Slicer custom logic for execution
*** Delegates to custom widgets for specific data types (extra XSL definitions)
* Steve
** DICOM Bug fixes (with Marco)
*** Name displays
*** Encoding crashes
** Command Line Module Widget - stand alone widget configured with CLI XML
*** Test version with subclassed module reference: https://github.com/pieper/CTK/tree/cli-widget-reference-subclass
*** improved version using QtGui subclass: https://github.com/pieper/CTK/tree/cli-widget
*** [https://github.com/pieper/CTK/blob/8391b2f54e18e68e6672a4d3a54da38bc9c77b79/Libs/CommandLineModules/Widgets/Testing/Cpp/ctkCmdLineModuleWidgetTest1.cpp#L86 working test code for the module]
* Luca
** Work on refactoring GenerateCLP into a more dynamic structure to support incremental CLI
** https://github.com/lantiga/CLIInterface

1:00pm Lunch

hack, hack, hack...

* Reminder: Update project status on wiki
** Links to branches, repositories, bug reports
** Screen captures of progress to the Gallery below
** Action photos of hacking in progress...

== Gallery of Results ==

<gallery widths=300 px heights=200px perrow=3>
Image:Cli-widget-prototype-2012-12-14.png|[https://github.com/pieper/CTK/blob/8391b2f54e18e68e6672a4d3a54da38bc9c77b79/Libs/CommandLineModules/Widgets/Testing/Cpp/ctkCmdLineModuleWidgetTest1.cpp#L86 Example widget generated from XML description.]
Image:VtkCompositeControlPointsStack.png|Layers in VTK charts for transfer function edition.
Image:MedInria-cli.png|Command-line module integration in medInria
</gallery>

== Travel & Hotel ==

'''Local contact'''
If you have any troubles during your visit, call Alessandro: +39 342 1401554 or Daniele: +39 348 7260365

'''Airport'''
* [http://www.bologna-airport.it/uk/?LN=UK Bologna G.Marconi (BLQ)]

'''Transportation on Site'''

Airport Shuttle from airport to Railway Station (near to meeting location) 6 euro, link: http://www.atc.bo.it/orari/aerobus-airport-railway-station-link

Taxi from airport to Railway Station 15-20 euro



'''Lodging'''

There are a lot of hotel options in Bologna.

Millennium Hotel[http://www.millennhotelbologna.it/en/index.html]: close to the centre and to the central railways station.

Star Hotel [http://www.starhotels.com/hotels/excelsior/en/home.aspx]: close to the centre and in front of the central railways station.

Mercure Hotel [http://www.accorhotels.com/it/hotel-1310-mercure-bologna-centro/index.shtml] (Italian link, you need to find the page on your language from the Accor portal) In front of the central railways station.

Albergo Atlantic [http://www.albergoatlantic.net/ENGLISH/index.html] In the city centre, 10' walking time from the central railways station.

I Portici Hotel [http://www.iporticihotel.com/en/i-portici-hotel-bologna]10' walking time from the central railways station.

'''Meeting Location'''

TBA We are finding a meeting venue that could be in the city centre or in the central station area.

'''Catering'''

It will be provided by the meeting venue.

'''Weather'''

* Probably not sunny, colder than Italian average :-), even it is quite variable, temperatures can range from 0°C to 10°C (min) and from 5°C to 20°C.

Documentation/CLI In Context

2012-12-17T09:12:02Z

Yves.martelli: tests are not yet completely automatic...

This page lists some example and notes on different integration of CLI modules in different frameworks including CTK (see [[Documentation/Command_Line_Interface]]). The first interoperability testing was done during the [http://www.creatis.insa-lyon.fr/Interoperability_workshop third] VPH NoE Imaging workshop hold in Lyon, France on October 22-23, 2012. It will be continued in consecutive hackfests. The aim is to try to plug in CLI modules in CLI compatible frameworks and come up with possible improvement of the CLI standard, advice to CLI module and CLI framework developers.

== Events ==

* [[CTK-Hackfest-Nov-2011|CTK Hackfest]] in Sofia Antipolis, France in November 2012
** Preliminary work to integrate CLI into Gimias
* [[CTK-Hackfest-Jul-2012|CTK Hackfest]] in Boston, USA in July 2012
** Preliminary work to integrate CLI into MITK
* [http://www.creatis.insa-lyon.fr/Interoperability_workshop 3rd VPH NoE Imaging workshop] in Lyon, France on October 22-23, 2012
** First [[#Interoperability_tests|Interoperability tests]] with CTK, Gimias, NiftyView and Slicer
* [[CTK-Hackfest-Dec-2012|CTK Hackfest]] in Bologna, Italy on December, 2012
** Preliminary work to integrate CLI into medInria, MAF3
** Semi-Automatic framework CLI integration tests

== Interoperability tests ==

These first tests mainly concern the integration of niftyreg (registration algorithms from UCL). The different stages of integration are: load, execute and results. Meaning that the CLI module can be loaded. executed and provides the same results as if it was run only from the command line. The problems we encountered were:

* Gimias does not support to have a `default` element different that `None` for the output, not sure about the `advanced` option for the `parameters` element
* niftyreg was using `fileExtensions` with stars (`*.nii`) which is not supported by neither Gimias nor Slicer (the star is directly used in the file name)
* The default output folder should be set to the user folder and not the running one, otherwise the CLI module can crash because they were denied access to write in that folder (for example `Program Files` under Windows)
* What to do with CLI modules that have dependencies on shared libraries with the platform but of different versions? Platforms should have the option to only use the libraries shipped with the CLI module
* Platforms should align the way they treat data since if two load data differently, the same CLI module could give different results

It would be interesting to create test CLI modules for these integration tests. For example one that exposes all possible types of options, one running a simple algorithm without any dependencies (as niftyreg) and one with dependencies.

Some thoughts on the tested platforms:
* Niftyview has nice controls on the way CLI modules are found and loaded (control on the `XML` validation)
* Slicer has a nice display of the loaded and non loaded CLI modules (appear in red, there could be more explanation why the loading failed)

== Snapshots ==

Here are the snapshots of niftyreg on the different platforms:

* CTK command line module explorer

[[File:Niftyreg-ctk.png|400px]]

* Slicer

[[File:Niftyreg-slicer.png|400px]]

* NiftyView

[[File:Niftyreg-niftyview.png|400px]]

* GIMIAS

[[File:Niftyreg-gimias.png|400px]]

CTK-Hackfest-Dec-2012

2012-12-10T11:04:43Z

Yves.martelli: Added link to CLI_In_Context

== Event pictures ==
Images from the hackfest
{|
|}

== Introduction ==

'''Date:''' December 10-14, 2012

'''Location:''' [http://www.iporticihotel.com/en | Hotel i Portici] in Via Indipendenza , Bologna, Italy, Sala Montagnola (Room)

'''Goal:''' A follow on to the [[Commontk:Current_events#Past_events|wildly successful previous hackfests!]]

'''Requirements:''' Attendees must be willing to spend their time during the event writing ctk code that contributes to the main [[CTK-Roadmap | ctk roadmap]]. This means spending the week immersed in C++, Qt, DCMTK, CMake, and related technologies. People who do not feel qualified for this task 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]].

'''Site Hosts:''' Alessandro Chiarini, Daniele Giunchi

'''Organizing Committee:''' Ivo Wolf, Stephen Aylward, Steve Pieper

'''Future Events:''' 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. We welcome participation via the CTK email lists, the source code repository, and this website.

== Attendees ==
*So far we have received confirmation for the following people (in no particular order).

'''WE HAVE REACHED THE MAXIMUM NUMBER OF PARTECIPANT - REGISTRATION CLOSED - 16 PARTECIPANTS
'''

Please fill in your intentions in terms of common accommodation.

{|class="wikitable alternance" style="text-align:left; border:1px solid black;"
|+ '''''Participants'''''
|-
! scope=col style="background:#cde6f8;"| Name
! scope=col style="background:#cde6f8;"| Organization
|-
|Alessandro Chiarini
|SCS, Bologna IT
|-
|Daniele Giunchi
|SCS, Bologna IT
|-
|Alberto Losi
|SCS, Bologna IT
|-
|Steve Pieper
|Isomics, Inc., Cambridge, MA, USA
|-
| Ivo Wolf
| Mannheim University of Applied Sciences & DKFZ Heidelberg
|-
| Jean-Chistophe Fillion-Robin
| Kitware
|-
| Julien Finet
| Kitware
|-
| Andreas Fetzer
| DKFZ Heidelberg
|-
| Michael Bauer
| DKFZ Heidelberg
|-
| Marco Nolden
| DKFZ Heidelberg
|-
| Sascha Zelzer
| DKFZ Heidelberg
|-
| Florian Vichot
| INRIA
|-
| Yves Martelli
| UPF
|-
| Claire Mouton
| CREATIS
|-
|-
| Miklos Espak
| University College London (UCL)
|-
|}



{{Note}}There were also other invitations sent to active people on the community, and people who recently showed interest. When their intent will be known they will be added to the list.

== Preparation ==

Developers should bring a laptop with the [http://github.com/commontk/CTK current CTK source code] downloaded and [[Build_Instructions|built]].

Use the [http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers CTK developers mailing list] to discuss build issues and topics for ongoing work.

Phone conferences have been scheduled in the weeks leading to the event:
* To be announced

== Topics and Projects ==



==== DICOM Application Hosting ====

* Refine, extend, [[DICOM_Application_Hosting_Testing | test]], and integrate with applications
* See also [[CTK-Hackfest-Nov-2011#DICOM_Application_Hosting | (some still open) tasks]] and [[Hackfest_Nice_AppHosting_Progress | progress]] from the last hackfest
* Goal: connect some real code via command line interface

==== DICOM Database and Networking ====

* Dig into ongoing developments. See [[CtkDICOM]] for discussion.
* See CTK DICOM support is used in Slicer 4.2
** [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.2/Modules/DICOM End-user documentation]
** [http://na-mic.org/Bug/search.php?project_id=3&category=Module+DICOM&sticky_issues=on&sortby=last_updated&dir=DESC&hide_status_id=90 Slicer4 DICOM Bugs and Feature Requests]
** SlicerRT Issues:
*** https://www.assembla.com/spaces/slicerrt/tickets/25 - display of ^ (carat character) in ctkDICOMModel
*** https://www.assembla.com/spaces/slicerrt/tickets/153 - extension import failure (slicer issue)
*** https://www.assembla.com/spaces/slicerrt/tickets/36 - non-uniform study information in RT files

==== QAT ====
Quality Assurance Toolkit -> how to integrate in CTK

==== Widgets ====

* Discuss and refine as needed.
* [https://www.assembla.com/spaces/slicerrt/wiki/20120125_Slicer_DICOM_browser_meeting SlicerRt example dicom interfaces discussion]

==== Tests Framework ====
Try QtTesting with CTK applications

==== Build Systems & Software process ====



* Update to [http://git.dcmtk.org/web?p=dcmtk.git;a=summary latest DCMTK]
** includes dcmrt
** need to pick a commit to standardize on
** investigate shared/static library building. (Static instances of classes getting destructed in wrong order)
** incorporate version checking
*** build ctk against head or snapshot version

* Prepare Debian packaging (Marco)
** Resolve outstanding issues
** Make CTK also build with latest stable DCMTK release (3.6.0)

* Evaluate Qt5 (Sascha)

* <del>Setup developer package</del>
** See [https://github.com/commontk/CTK/issues/10 #10] and [https://github.com/commontk/CTK/issues/65 #65]
** Work in progress - See topic [https://github.com/jcfr/CTK/compare/65-packaging-support 65-packaging-support]


** Release a version of CTK (Work on policy this week and maybe release this week).


** Work in progress - See [https://github.com/jcfr/CTK/compare/master...cmake-doxygen-filter-reuse cmake-doxygen-filter-reuse]

==== Command Line Modules ====
* Extract CLI interface
** Unify VPH and Slicer refactoring
* Qt SEM XML widget
* Follow on interoperability tests done in [[CLI_In_Context]]

== Agenda ==

==== Monday ====


10:30am Welcome

10:45 - 12:00 Round table: everyone presents 10-15 minutes how CTK is used in their project. And what's new in CTK (what has been added since previous hackfest)

: CTK in use:
:* MSVTK (DG/AL, JF) (10m)
:* DICOM in Slicer (SP) (5m)
: What's new ?
:* New widgets in CTK(JF, JCFR) (e.g. ctkSizeGrip, ctkPathLineEdit, ctkPanelSettings...) (5m)

1:00pm Lunch

: Discuss plans/priorities for hacking

3:30pm Coffee Break

5:00pm Close

==== Tuesday ====

9:30am Welcome

11:00am Coffee Break

1:00pm Lunch

5:00pm Close

==== Wednesday ====

9:30am Welcome

11:00am Coffee Break

1:00pm Lunch

5:00pm Close

==== Thursday ====

9:30am Welcome

11:00am Coffee Break

1:00pm Lunch

5:00pm Close

==== Friday ====

9:30am Welcome

11:00am Coffee Break

1:00pm Lunch

2:00pm Wrap up discussion and Meeting Closes
* Update project status on wiki

== Travel & Hotel ==

'''Local contact'''
If you have any troubles during your visit, call Alessandro: +39 342 1401554 or Daniele: +39 348 7260365

'''Airport'''
* [http://www.bologna-airport.it/uk/?LN=UK Bologna G.Marconi (BLQ)]

'''Transportation on Site'''

Airport Shuttle from airport to Railway Station (near to meeting location) 6 euro, link: http://www.atc.bo.it/orari/aerobus-airport-railway-station-link

Taxi from airport to Railway Station 15-20 euro



'''Lodging'''

There are a lot of hotel options in Bologna.

Millennium Hotel[http://www.millennhotelbologna.it/en/index.html]: close to the centre and to the central railways station.

Star Hotel [http://www.starhotels.com/hotels/excelsior/en/home.aspx]: close to the centre and in front of the central railways station.

Mercure Hotel [http://www.accorhotels.com/it/hotel-1310-mercure-bologna-centro/index.shtml] (Italian link, you need to find the page on your language from the Accor portal) In front of the central railways station.

Albergo Atlantic [http://www.albergoatlantic.net/ENGLISH/index.html] In the city centre, 10' walking time from the central railways station.

I Portici Hotel [http://www.iporticihotel.com/en/i-portici-hotel-bologna]10' walking time from the central railways station.

'''Meeting Location'''

TBA We are finding a meeting venue that could be in the city centre or in the central station area.

'''Catering'''

It will be provided by the meeting venue.

'''Weather'''

* Probably not sunny, colder than Italian average :-), even it is quite variable, temperatures can range from 0°C to 10°C (min) and from 5°C to 20°C.

Documentation/CLI Support in CTK

2012-10-31T16:19:45Z

Yves.martelli: Added link to the Slicer execution model page.

Command Line Interface (CLI) support in CTK will primarly focus on providing an API for working with existing CLI modules. Providing utilities and tools for creating CLI modules from scratch is a desired addition but there are no concrete plans for this yet. See [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Slicer3:Execution Model Documentation] for the definition of the standard. For example integration in different frameworks, see [[Documentation/CLI_In_Context|CLI In Context]].

=== Getting the Code ===

The code is available in the CTK master:

https://github.com/commontk/CTK

Enable the following CMake options to be able to play with the code:

* '''BUILD_TESTING''' (for creating CLI test modules)
* '''CTK_APP_ctkCommandLineModuleExplorer''' (small program allowing you to test-drive CLI modules using the CTK CLI module API, enables all the options below)
* '''CTK_LIB_CommandLineModules/Core''' (the CTK library providing the core CLI module API)
* '''CTK_LIB_CommandLineModules/Frontend/QtGui''' (the CTK library providing GUI generation using the Qt widgets)
* '''CTK_LIB_CommandLineModules/Backend/LocalProcess''' (the CTK library for executing local executable files as command line modules)

=== API Design ===

This is a partially overview of the API design, showing the GUI generation process for the Qt front-end.

<graphviz>
digraph G {
graph [
rankdir = "TB"
];
node [
fontsize = "16"
shape = "ellipse"
];
edge [
];
subgraph cluster_0 {
label = "CTK";
color = lightGray;
"xmlFile" [
label = "{<f0> Command Line Module XML (.xml)| <f1>}"
shape = "record"
];
"gui" [
label = "{<f0> Qt GUI | <f1>}"
shape = "record"
];
"uiFile" [
label = "{<f0> CLI UI (.ui) | <f1>}"
shape = "record"
];
"ctkCLIModuleDescription" [
label = "{<f0> ctkCmdLineModuleDescription| <f1>}"
shape = "record"
];
}

subgraph cluster_1 {
label = "3D Slicer";
color = gray;
"vtkMRMLParametersNode" [
label = "{<f0> vtkMRMLParametersNode| <f1>}"
shape = "record"
];
}
"xmlFile":f0:e -> "xmlFile":f0:ne [label = "XSD file check" ];
"xmlFile":f1 -> "uiFile":f0 [label = "QtGui XSL file" ];
"xmlFile":f1 -> "uiFile":f0 [label = "" style=invis];
"xmlFile":f1 -> "ctkCLIModuleDescription":f0 [label=ctkCmdLineModuleXmlParser];
"ctkCLIModuleDescription":f1 -> "vtkMRMLParametersNode":f0 [label=create];
"uiFile":f1 -> "gui":f0 [label = QUiLoader];
"gui":f1:e -> "vtkMRMLParametersNode":f1:w [dir = both label=synchronize constraint=false];
}
</graphviz>

Overview of some central classes and their scope.

Please see the full [file:///opt/ctk-builds/CTK-debug-gcc/CTK-build/Documentation/html/group__CommandLineModulesCore__API.html Core API] for a list of available classes and their documentation.

==== ctkCmdLineModuleDescription ====

C++ API for accessing the command line arguments meta-data defined in the XML description.

This class is ''read-only''.

==== ctkCmdLineModuleReference ====

A handle to a command line module.

* Get ctkCmdLineModuleDescription class
* Convenient meta-data access (module location etc.)
* Used to crate actual ctkCmdLineModuleFrontend instances from specific ctkCmdLineModuleFrontendFactory implementations

==== ctkCmdLineModuleFrontend ====

Represents an invokable command line module and its current parameter values.

Multiple instances for the same ModuleReference may exist.

* Set/Get individual parameter values or all at once
* Reset to default parameters
* Get GUI representation (QObject*)
* Get parameter value change notifications

==== ctkCmdLineModuleFuture ====

Returned by the ctkCmdLineModuleManager run method and used to communicate with a running module.

* Run/Abort
* Status
* Progress reporting

==== ctkCmdLineModuleManager ====

Responsible for managing and running other ctkCmdLineModule* classes.

* Register specific back-ends for handling different types of modules
* Register/Unregister modules
* Get ctkCmdLineModuleReference objects
* Run ctkCmdLineModuleFrontend objects

=== Customizability ===

==== Qt Widget related ====

See also the [http://www.commontk.org/docs/html/classctkCmdLineModuleFrontendQtGui.html ctkCmdLineModuleFrontendQtGui] class for customization information.

* Use parameters for the default XSLT file to customize widget class names for argument types
* Use your own XSLT file for custom transformations of XML to UI
* Use your own QUiLoader to control instantiation of certain widget types

==== General ====

* Use a custom ''factory'' to create your own GUI based on a ctkCmdLineModuleDescription instance.

Documentation/CLI In Context

2012-10-31T16:17:15Z

Yves.martelli: Added links.

This page lists some example and notes on different integration of CLI modules in different frameworks including CTK (see [[Documentation/Command_Line_Interface]]). The first interoperability testing was done during the [http://www.creatis.insa-lyon.fr/Interoperability_workshop third] VPH NoE Imaging workshop hold in Lyon, France on October 22-23, 2012. It will be continued in consecutive hackfests. The aim is to try to plug in CLI modules in CLI compatible frameworks and come up with possible improvement of the CLI standard, advice to CLI module and CLI framework developers.

== Interoperability tests ==

These first tests mainly concern the integration of niftyreg (registration algorithms from UCL). The different stages of integration are: load, execute and results. Meaning that the CLI module can be loaded. executed and provides the same results as if it was run only from the command line. The problems we encountered were:

* Gimias does not support to have a `default` element different that `None` for the output, not sure about the `advanced` option for the `parameters` element
* niftyreg was using `fileExtensions` with stars (`*.nii`) which is not supported by neither Gimias nor Slicer (the star is directly used in the file name)
* The default output folder should be set to the user folder and not the running one, otherwise the CLI module can crash because they were denied access to write in that folder (for example `Program Files` under Windows)
* What to do with CLI modules that have dependencies on shared libraries with the platform but of different versions? Platforms should have the option to only use the libraries shipped with the CLI module
* Platforms should align the way they treat data since if two load data differently, the same CLI module could give different results

It would be interesting to create test CLI modules for these integration tests. For example one that exposes all possible types of options, one running a simple algorithm without any dependencies (as niftyreg) and one with dependencies.

Some thoughts on the tested platforms:
* Niftyview has nice controls on the way CLI modules are found and loaded (control on the `XML` validation)
* Slicer has a nice display of the loaded and non loaded CLI modules (appear in red, there could be more explanation why the loading failed)

== Snapshots ==

Here are the snapshots of niftyreg on the different platforms:

* CTK command line module explorer

[[File:Niftyreg-ctk.png|400px]]

* Slicer

[[File:Niftyreg-slicer.png|400px]]

* NiftyView

[[File:Niftyreg-niftyview.png|400px]]

* GIMIAS

[[File:Niftyreg-gimias.png|400px]]

Talk:CLI In Context

2012-10-30T14:46:33Z

Yves.martelli: Created page with "This page should be deleted (my mistake, I did not create it in the Documentation section). --~~~~"

This page should be deleted (my mistake, I did not create it in the Documentation section).
--[[User:Yves.martelli|Yves.martelli]] 10:46, 30 October 2012 (EDT)

Documentation/CLI Support in CTK

2012-10-30T14:44:32Z

Yves.martelli: Better link

Command Line Interface (CLI) support in CTK will primarly focus on providing an API for working with existing CLI modules. Providing utilities and tools for creating CLI modules from scratch is a desired addition but there are no concrete plans for this yet. For example integration in different frameworks, see [[Documentation/CLI_In_Context|CLI In Context]].

=== Getting the Code ===

The code is available in the CTK master:

https://github.com/commontk/CTK

Enable the following CMake options to be able to play with the code:

* '''BUILD_TESTING''' (for creating CLI test modules)
* '''CTK_APP_ctkCommandLineModuleExplorer''' (small program allowing you to test-drive CLI modules using the CTK CLI module API, enables all the options below)
* '''CTK_LIB_CommandLineModules/Core''' (the CTK library providing the core CLI module API)
* '''CTK_LIB_CommandLineModules/Frontend/QtGui''' (the CTK library providing GUI generation using the Qt widgets)
* '''CTK_LIB_CommandLineModules/Backend/LocalProcess''' (the CTK library for executing local executable files as command line modules)

=== API Design ===

This is a partially overview of the API design, showing the GUI generation process for the Qt front-end.

<graphviz>
digraph G {
graph [
rankdir = "TB"
];
node [
fontsize = "16"
shape = "ellipse"
];
edge [
];
subgraph cluster_0 {
label = "CTK";
color = lightGray;
"xmlFile" [
label = "{<f0> Command Line Module XML (.xml)| <f1>}"
shape = "record"
];
"gui" [
label = "{<f0> Qt GUI | <f1>}"
shape = "record"
];
"uiFile" [
label = "{<f0> CLI UI (.ui) | <f1>}"
shape = "record"
];
"ctkCLIModuleDescription" [
label = "{<f0> ctkCmdLineModuleDescription| <f1>}"
shape = "record"
];
}

subgraph cluster_1 {
label = "3D Slicer";
color = gray;
"vtkMRMLParametersNode" [
label = "{<f0> vtkMRMLParametersNode| <f1>}"
shape = "record"
];
}
"xmlFile":f0:e -> "xmlFile":f0:ne [label = "XSD file check" ];
"xmlFile":f1 -> "uiFile":f0 [label = "QtGui XSL file" ];
"xmlFile":f1 -> "uiFile":f0 [label = "" style=invis];
"xmlFile":f1 -> "ctkCLIModuleDescription":f0 [label=ctkCmdLineModuleXmlParser];
"ctkCLIModuleDescription":f1 -> "vtkMRMLParametersNode":f0 [label=create];
"uiFile":f1 -> "gui":f0 [label = QUiLoader];
"gui":f1:e -> "vtkMRMLParametersNode":f1:w [dir = both label=synchronize constraint=false];
}
</graphviz>

Overview of some central classes and their scope.

Please see the full [file:///opt/ctk-builds/CTK-debug-gcc/CTK-build/Documentation/html/group__CommandLineModulesCore__API.html Core API] for a list of available classes and their documentation.

==== ctkCmdLineModuleDescription ====

C++ API for accessing the command line arguments meta-data defined in the XML description.

This class is ''read-only''.

==== ctkCmdLineModuleReference ====

A handle to a command line module.

* Get ctkCmdLineModuleDescription class
* Convenient meta-data access (module location etc.)
* Used to crate actual ctkCmdLineModuleFrontend instances from specific ctkCmdLineModuleFrontendFactory implementations

==== ctkCmdLineModuleFrontend ====

Represents an invokable command line module and its current parameter values.

Multiple instances for the same ModuleReference may exist.

* Set/Get individual parameter values or all at once
* Reset to default parameters
* Get GUI representation (QObject*)
* Get parameter value change notifications

==== ctkCmdLineModuleFuture ====

Returned by the ctkCmdLineModuleManager run method and used to communicate with a running module.

* Run/Abort
* Status
* Progress reporting

==== ctkCmdLineModuleManager ====

Responsible for managing and running other ctkCmdLineModule* classes.

* Register specific back-ends for handling different types of modules
* Register/Unregister modules
* Get ctkCmdLineModuleReference objects
* Run ctkCmdLineModuleFrontend objects

=== Customizability ===

==== Qt Widget related ====

See also the [http://www.commontk.org/docs/html/classctkCmdLineModuleFrontendQtGui.html ctkCmdLineModuleFrontendQtGui] class for customization information.

* Use parameters for the default XSLT file to customize widget class names for argument types
* Use your own XSLT file for custom transformations of XML to UI
* Use your own QUiLoader to control instantiation of certain widget types

==== General ====

* Use a custom ''factory'' to create your own GUI based on a ctkCmdLineModuleDescription instance.

CLI In Context

2012-10-30T14:43:31Z

Yves.martelli: moved CLI In Context to Documentation/CLI In Context: Better location!

#REDIRECT [[Documentation/CLI In Context]]

Documentation/CLI In Context

2012-10-30T14:43:31Z

Yves.martelli: moved CLI In Context to Documentation/CLI In Context: Better location!

This page lists some example and notes on different integration of CLI modules in different frameworks. The first interoperability testing was done during the VPH NoE Imaging workshop hold in Lyon, France on October 22-23, 2012. It will be continued in consecutive hackfests. The aim is to try to plug in CLI modules in CLI compatible frameworks and come up with possible improvement of the CLI standard, advice to CLI module and CLI framework developers.

== Interoperability tests ==

These first tests mainly concern the integration of niftyreg (registration algorithms from UCL). The different stages of integration are: load, execute and results. Meaning that the CLI module can be loaded. executed and provides the same results as if it was run only from the command line. The problems we encountered were:

* Gimias does not support to have a `default` element different that `None` for the output, not sure about the `advanced` option for the `parameters` element
* niftyreg was using `fileExtensions` with stars (`*.nii`) which is not supported by neither Gimias nor Slicer (the star is directly used in the file name)
* The default output folder should be set to the user folder and not the running one, otherwise the CLI module can crash because they were denied access to write in that folder (for example `Program Files` under Windows)
* What to do with CLI modules that have dependencies on shared libraries with the platform but of different versions? Platforms should have the option to only use the libraries shipped with the CLI module
* Platforms should align the way they treat data since if two load data differently, the same CLI module could give different results

It would be interesting to create test CLI modules for these integration tests. For example one that exposes all possible types of options, one running a simple algorithm without any dependencies (as niftyreg) and one with dependencies.

Some thoughts on the tested platforms:
* Niftyview has nice controls on the way CLI modules are found and loaded (control on the `XML` validation)
* Slicer has a nice display of the loaded and non loaded CLI modules (appear in red, there could be more explanation why the loading failed)

== Snapshots ==

Here are the snapshots of niftyreg on the different platforms:

* CTK command line module explorer

[[File:Niftyreg-ctk.png|400px]]

* Slicer

[[File:Niftyreg-slicer.png|400px]]

* NiftyView

[[File:Niftyreg-niftyview.png|400px]]

* GIMIAS

[[File:Niftyreg-gimias.png|400px]]

Documentation/CLI In Context

2012-10-30T14:41:49Z

Yves.martelli: First version.

File:Niftyreg-slicer.png

2012-10-30T14:36:38Z

Yves.martelli: Niftyreg in Slicer.

Niftyreg in Slicer.

File:Niftyreg-niftyview.png

2012-10-30T14:36:05Z

Yves.martelli: Niftyreg in Niftyview.

Niftyreg in Niftyview.

File:Niftyreg-gimias.png

2012-10-30T14:35:24Z

Yves.martelli: Niftyreg in GIMIAS.

Niftyreg in GIMIAS.

File:Niftyreg-ctk.png

2012-10-30T14:34:22Z

Yves.martelli: Niftyreg in CTK module explorer.

Niftyreg in CTK module explorer.

Documentation/CLI Support in CTK

2012-10-30T14:20:21Z

Yves.martelli: Added a link to CLI_In_Context.

Command Line Interface (CLI) support in CTK will primarly focus on providing an API for working with existing CLI modules. Providing utilities and tools for creating CLI modules from scratch is a desired addition but there are no concrete plans for this yet. For example integration in different frameworks, see [[CLI In Context]].

=== Getting the Code ===

The code is available in the CTK master:

https://github.com/commontk/CTK

Enable the following CMake options to be able to play with the code:

* '''BUILD_TESTING''' (for creating CLI test modules)
* '''CTK_APP_ctkCommandLineModuleExplorer''' (small program allowing you to test-drive CLI modules using the CTK CLI module API, enables all the options below)
* '''CTK_LIB_CommandLineModules/Core''' (the CTK library providing the core CLI module API)
* '''CTK_LIB_CommandLineModules/Frontend/QtGui''' (the CTK library providing GUI generation using the Qt widgets)
* '''CTK_LIB_CommandLineModules/Backend/LocalProcess''' (the CTK library for executing local executable files as command line modules)

=== API Design ===

This is a partially overview of the API design, showing the GUI generation process for the Qt front-end.

<graphviz>
digraph G {
graph [
rankdir = "TB"
];
node [
fontsize = "16"
shape = "ellipse"
];
edge [
];
subgraph cluster_0 {
label = "CTK";
color = lightGray;
"xmlFile" [
label = "{<f0> Command Line Module XML (.xml)| <f1>}"
shape = "record"
];
"gui" [
label = "{<f0> Qt GUI | <f1>}"
shape = "record"
];
"uiFile" [
label = "{<f0> CLI UI (.ui) | <f1>}"
shape = "record"
];
"ctkCLIModuleDescription" [
label = "{<f0> ctkCmdLineModuleDescription| <f1>}"
shape = "record"
];
}

subgraph cluster_1 {
label = "3D Slicer";
color = gray;
"vtkMRMLParametersNode" [
label = "{<f0> vtkMRMLParametersNode| <f1>}"
shape = "record"
];
}
"xmlFile":f0:e -> "xmlFile":f0:ne [label = "XSD file check" ];
"xmlFile":f1 -> "uiFile":f0 [label = "QtGui XSL file" ];
"xmlFile":f1 -> "uiFile":f0 [label = "" style=invis];
"xmlFile":f1 -> "ctkCLIModuleDescription":f0 [label=ctkCmdLineModuleXmlParser];
"ctkCLIModuleDescription":f1 -> "vtkMRMLParametersNode":f0 [label=create];
"uiFile":f1 -> "gui":f0 [label = QUiLoader];
"gui":f1:e -> "vtkMRMLParametersNode":f1:w [dir = both label=synchronize constraint=false];
}
</graphviz>

Overview of some central classes and their scope.

Please see the full [file:///opt/ctk-builds/CTK-debug-gcc/CTK-build/Documentation/html/group__CommandLineModulesCore__API.html Core API] for a list of available classes and their documentation.

==== ctkCmdLineModuleDescription ====

C++ API for accessing the command line arguments meta-data defined in the XML description.

This class is ''read-only''.

==== ctkCmdLineModuleReference ====

A handle to a command line module.

* Get ctkCmdLineModuleDescription class
* Convenient meta-data access (module location etc.)
* Used to crate actual ctkCmdLineModuleFrontend instances from specific ctkCmdLineModuleFrontendFactory implementations

==== ctkCmdLineModuleFrontend ====

Represents an invokable command line module and its current parameter values.

Multiple instances for the same ModuleReference may exist.

* Set/Get individual parameter values or all at once
* Reset to default parameters
* Get GUI representation (QObject*)
* Get parameter value change notifications

==== ctkCmdLineModuleFuture ====

Returned by the ctkCmdLineModuleManager run method and used to communicate with a running module.

* Run/Abort
* Status
* Progress reporting

==== ctkCmdLineModuleManager ====

Responsible for managing and running other ctkCmdLineModule* classes.

* Register specific back-ends for handling different types of modules
* Register/Unregister modules
* Get ctkCmdLineModuleReference objects
* Run ctkCmdLineModuleFrontend objects

=== Customizability ===

==== Qt Widget related ====

See also the [http://www.commontk.org/docs/html/classctkCmdLineModuleFrontendQtGui.html ctkCmdLineModuleFrontendQtGui] class for customization information.

* Use parameters for the default XSLT file to customize widget class names for argument types
* Use your own XSLT file for custom transformations of XML to UI
* Use your own QUiLoader to control instantiation of certain widget types

==== General ====

* Use a custom ''factory'' to create your own GUI based on a ctkCmdLineModuleDescription instance.

Documentation

2012-10-30T14:08:14Z

Yves.martelli: /* CLI Modules */ changed to link to proper page.

=== Architectural Notes ===

These notes have been taken during various meetings in the past and summarize discussions about the architecture and requirements of CTK.

* [[Documentation/Whitepaper|Whitepaper]]
* [[CTK-Roadmap|Roadmap]]
* [[Documentation/Third_Party_Dependencies|Third party dependencies]]

Topics being discussed but with no concrete agreement or maintained coding efforts include the following:

* [[Documentation/ctkScene|ctkScene ideas]]
* [[Documentation/Interfacing_Via_OpenGL|Interfacing systems at the OpenGL level (i.e. VTK and OpenInventor)]]
* [[Documentation/Messaging | Messaging service for event management and system integration]]

=== Build System ===

* [[Documentation/BuildSystem_Description | Description]]
* [[Documentation/Build Options | Build Options]]
* [[Documentation/Create_SVN_Project_Mirror | Create SVN project mirror]]

=== DICOM ===

=== DICOM Application Hosting ===

Please visit the page documenting the [[Documentation/DicomApplicationHosting | DICOM Part 19]] implementation efforts.

=== [[Documentation/Widgets|Widgets]] ===

* [[Documentation/WidgetPlans|Plans for widgets]]
* [[Documentation/ImageGallery|Image Gallery]]
* [[Documentation/ctkTransferFunctionWidget|Transfer function widgets]]
* [[Documentation/ctkWorkflowWidget|Workflow widgets]]
* [http://www.kitware.com/blog/home/post/169 Popup widgets]

=== Plugin Framework ===

The CTK Plugin Framework has its own page [[Documentation/Plugin_Framework | here]].

=== CLI Modules ===

Big picture for [[Documentation/Command_Line_Interface|Command Line Interface]]

=== Testing ===

* [[Documentation/Widget_testing | Widget testing]]

=== Python scripting ===

* [[Documentation/PythonScripting_ConvertPyQt2PythonQt | From PyQt to PythonQt]]

Talk:Documentation/CLI Modules

2012-10-30T14:06:52Z

Yves.martelli: Created page with "This page looks like a duplicate of Documentation/Command_Line_Interface, shouldn't it be removed? --~~~~"

This page looks like a duplicate of [[Documentation/Command_Line_Interface]], shouldn't it be removed?
--[[User:Yves.martelli|Yves.martelli]] 10:06, 30 October 2012 (EDT)

Documentation/CLI Modules

2012-10-30T14:03:14Z

Yves.martelli: Added missing <graphviz> tag

<graphviz>
digraph g {
graph [
rankdir = "LR"
];
node [
fontsize = "16"
shape = "ellipse"
];
edge [
];
"xmlFile" [
label = "<f0> CLI XML (.xml)| <f1>"
shape = "record"
];
"uiFile" [
label = "<f0> CLI UI (.ui) | <f1>"
shape = "record"
];
"gui" [
label = "<f0> Qt GUI | <f1>"
shape = "record"
];
"ctkCLIModuleDescription" [
label = "<f0> ctkCLIModuleDescription| <f1>"
shape = "record"
];
"vtkMRMLParametersNode" [
label = "<f0> vtkMRMLParametersNode| <f1>"
shape = "record"
];
"xmlFile":f1 -> "uiFile":f0 [
id = 0
];
"xmlFile":f1 -> "ctkCLIModuleDescription":f0 [
id = 1
];
"xmlFile":f1 -> "vtkMRMLParametersNode":f0 [
id = 2
];
"uiFile":f1 -> "gui":f0 [
id = 3
];
"gui":f1 -> "ctkCLIModuleDescription":f1 [
id = 4
];
"ctkCLIModuleDescription":f1 -> "vtkMRMLParametersNode":f1 [
id = 5
];
}

CTK-Hackfest-Nov-2011

2011-10-18T13:36:46Z

Yves.martelli: Added martin and yves to list.

== Event pictures ==
{|
|[[File:Ctk-Feb-2011-hackfest-panorama.jpg|thumb|right|300px|<big>Previous Hackfest!</big>]]
|}

== Introduction ==

'''Note: this page is a work in progress -- some information subject to change'''

'''Date:''' November 14-18, 2011

'''Location:''' INRIA - Sophia Antipolis, France

'''Goal:''' A follow on to the [[Commontk:Current_events#Past_events|wildly successful previous hackfests!]]

'''Requirements:''' Attendees must be willing to spend their time during the event with writing ctk code that contributes to the main ctk roadmap. 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]].

'''Site Hosts:''' Benoît Bleuzé

'''Future Events:''' 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. We welcome participation via the CTK email lists, the source code repository, and this website.

== Attendees ==
*So far we have received confirmation for the following people (in no particular order). Please fill in your intentions in terms of common accommodation.

{| border="5" cellpadding="10"
! Name
! Organization
! Interested in grouped accommodation
|-
| Jean-Chistophe Fillion-Robin
| Kitware
| Yes
|-
| Julien Finet
| Kitware
| Yes
|-
| Steve Pieper
| Isomics
| yes
|-
| Ivo Wolf
| Hochschule Mannheim
| Yes
|-
| Marco Nolden
| DKFZ, Heidelberg
| Yes
|-
| Sascha Zelzer
| DKFZ, Heidelberg
| Yes
|-
| Benoît Bleuzé
| INRIA, Sophia-Antipolis
| No
|-
|-
| Matt Clarkson
| University College London
| Yes
|-
| Daniele Giunchi
| SCS, Bologna
| Yes
|-
| Paolo Quadrani
| SCS, Bologna
| Yes
|-
| Martin Steghöfer
| UPF, Barcelona
| Yes
|-
| Yves Martelli
| UPF, Barcelona
| Yes
|}

* People who manifested interest in joining the fest. Please move your names up to the confirmed table, with the details as soon as you can to facilitate discussions with potential hotels.
{| border="5" cellpadding="10"
! Name
! Organization
|}

There were also other invitations sent to active people on the community, and people who recently showed interest. When their intent will be known they will be added to the list.

== Preparation ==

Developers should bring a laptop with the [http://github.com/pieper/CTK current CTK source code] downloaded and [[Build_Instructions|built]].

Use the [http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers CTK developers mailing list] to discuss build issues and topics for ongoing work.

Phone conferences have been scheduled in the weeks leading to the event:
* Tuesday 25th October 2011 18:00 (CET) - 12:00 (EST)
* Tuesday 8th November 2011 18:00 (CET) - 12:00 (EST)

== Topics and Projects ==

==== Roadmap development ====
*Develop a [[CTK-Roadmap|roadmap for the CTK core]]. It is advised to begin pondering on this in the weeks leading to the hack-fest in order to dedicate as much time as possible to the real hacking during the week. The [[CTK-Roadmap|roadmap for the CTK core]] is a good place to start your thinking. It has been written by Ivo and Marco at the start of the CTK initiative.

Participants
*Steve
*Stephen
*Ivo
*Marco
*Ben

==== DICOM Application Hosting ====

Possible work items:

* Data Exchange Interface
* SOAP interoperability
* Conformance testing

Participants

* Benoit
* Michael
* Sascha
* Jc

==== DICOM Networking ====

Possible work items:

See [[CtkDICOM]] for possible goals.

* ?

Participants

* Michael
* Steve
* Marco

==== Widgets ====
==== Tests Framework ====
Working towards a unified testing method throughout the whole code base.
* Julien (also linked but not limited to App hosting testing)

==== Build Systems & Software process ====
* Jc

== Agenda ==

TBD

== Travel & Hotel ==

'''Local contact'''
* If you have any troubles during your visit, call Benoit : +33 4 92 38 71 55 (or if not available, +33 6 32 78 59 92, but it's my mobile)

'''Airport'''
* Nice Airport: http://en.nice.aeroport.fr/

'''Lodging'''
Prefer Antibes to any other locations, Sophia-Antipolis is very badly connected to places to sustain you at night, and the buses stop after 20:00/20:30

'''Meeting Location'''
* Inria Sophia Antipolis:
2004 route des Lucioles BP 93
06902 SOPHIA ANTIPOLIS Cedex - FRANCE

'''Weather'''
* Average min/max temperature in November in Sophia Antipolis:15-20 Celsius

== Related Events/Activities ==

INRIA Imaging Workshop November 21-23: http://www-sop.inria.fr/asclepios/events/VPHimaging11/