ITK/Tcons/Agendas/2011 05 06: Difference between revisions

From KitwarePublic
< ITK‎ | Tcons‎ | Agendas
Jump to navigationJump to search
(Created page with "= How to Join the Tcon = == Number to Call == '''Please be patient, due to some unforeseen circumstances, the call may not start on time...''' * 1-800-728-9607 (in the US) or...")
 
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 34: Line 34:
** [[ITK_Release_4/Modularization/Code Reviews/Process|Process]]
** [[ITK_Release_4/Modularization/Code Reviews/Process|Process]]
* Target:  June Meeting
* Target:  June Meeting
* Review Directory: hackathon Tuesday at Clifton Park
* Review Directory: hackathon  
** Famous golfer will join us
** All files were classified
** https://spreadsheets.google.com/a/kitware.com/ccc?key=0ApfVzIsZe0VFdFUxdE95WE5kMVE4LTJ6b3ZYQnpRalE&hl=en&authkey=CMyS68EE#gid=0
** Missing Insight Journal references were added
** Now: Select the ones that must be moved into the toolkit
* Finally: We will move the remaining Review directory out of the toolkit and into an external module.


== ITK Modularization Residuals ==
== ITK Modularization Residuals ==
Line 70: Line 74:


* Related to the new itkTestDriver
* Related to the new itkTestDriver
== FastMarching Refactoring ==
* Backward Compatibility
** Should we move v3 classes into Deprecated?
** Should we fix everything that currently depends on FastMarching? (Although, we are in the process of refactoring the level sets)
* Preferred class name?
* http://review.source.kitware.com/#change,1328


== Refactoring Workflow ==
== Refactoring Workflow ==
Line 135: Line 131:


* NO TCONF TODAY
* NO TCONF TODAY
* Next week: Tcon at 11am EST, Friday (after the ITK tcon)
* Next week: May 13th,
Tcon at 11am EST, Friday (after the ITK tcon)


   Toll-Free #:      1-800-704-9804  
   Toll-Free #:      1-800-704-9804  
Line 141: Line 138:
   Participant Code: 61466276
   Participant Code: 61466276


* additional buildhost with merged gdcm and gdcm warning ON been added
* system_gdcm has been compiled under mac, patch submitted
* a gdcm fork has been made in github and will be tested against itk using systems_gdcm
** new libraries for jpeg2000 and others
** this will allow easier integration, memory of the changes, and to send back modification to gdcm proper.
** need to be added to project using gdcm.
* bill reported that patch is not working under windows.
* currently the windows build have some lib naming problem, perhaps caused by cmake ? that are in the way for testing.


== Gerrit Reviews ==
== Gerrit Reviews ==
Line 174: Line 173:


* scripts
* scripts
** scripts to add the module for each class in the doxygen documentation?
** scripts to add (automatically) links to wiki example in the doxygen documentation?
** scripts to add examples/tests to doxygen documentation (for each class, whenever it is relevant)?
** scripts to add examples/tests to doxygen documentation (for each class, whenever it is relevant)?

Latest revision as of 14:10, 6 May 2011

How to Join the Tcon

Number to Call

Please be patient, due to some unforeseen circumstances, the call may not start on time...

  • 1-800-728-9607 (in the US) or
  • +1 9139049873 (international)
  • access code 6815251

Webex

Project Management

June Meeting in Chapel Hill

  • Summer_ITKv4_2011_Meeting
  • Will take place on June 28-29
  • Chapel Hill, North Carolina.
  • The Meeting will take place at the Franklin Hotel
  • URGENT: ADDING ONE DAY MORE TO THE MEETING
    • June 27
    • To sprint with the A2D2 projects

Technical Topics

Review Tasks

ITK Modularization Residuals

  • Check the TODO list file

Dashboard

Monolithic Dashboard

Modular Dashboard

Comments from Lorensen: Unfortunately, I am on travel today and cannot attend the t-con. My initial impression of the itk modular dashboard is that is not in a form that is usable for ITK at this time. The navigation is cumbersome and it is difficult to use on a day-to-day basis. I hope we can have more discussion about this. My recommendation is try it out for a week, evaluate the usability and identify the missing features. Then, revert all submissions to the non-modular dashboard and wait for a new cdash release.

OPENJPEG Dashboard


Valgrind Errors

  • Related to the new itkTestDriver

Refactoring Workflow

  • Right now
    • code is developed on other remote
    • once the code is mature, we submit to gerrit
    • lost history
    • refactoring may appear as single commit from one person (not team spirit oriented)
  • Any other solution?


ImageRegionDuplicator


Schedule

ITKv4 A06

ITKv4 A07

  • Let's tag now
  • The changes after modularization are enormous and we don't have a tag that marks the repository past the events
  • Many other changes are getting into the repository, and the diff between A07 and A06 is not longer: just modularization.

Teaching ITK

  • ITK Boot Camp : Houston : September 2011
  • ITK in image processing course : Houston : Fall 2011
  • ITK in biomedical imaging course : Houston : Spring 2012

Open Science Training

  • Reproducible Research Training Camp : TBD
  • Open Sourcing your Lab Training Camp : TBD

Image Interpretation Layer

Database Interface

DICOM

  • NO TCONF TODAY
  • Next week: May 13th,

Tcon at 11am EST, Friday (after the ITK tcon)

 Toll-Free #:      1-800-704-9804 
 International #:  1-404-920-6604
 Participant Code: 61466276
  • system_gdcm has been compiled under mac, patch submitted
    • new libraries for jpeg2000 and others
    • need to be added to project using gdcm.
  • bill reported that patch is not working under windows.
  • currently the windows build have some lib naming problem, perhaps caused by cmake ? that are in the way for testing.

Gerrit Reviews

Orfeo Toolbox Integration

  • Had tcon with the OTB team
  • Discussed registration of ImageIO factories in OTB
  • Reviewed the patch for supporting images of std::complex
  • Need to schedule call with Microscopy, Video and Remote Sensing groups to design a common "image interpretation layer"

SimpleITK

ITK FEM

ITK FEM Modifications

Doxygen

  • scripts
    • scripts to add examples/tests to doxygen documentation (for each class, whenever it is relevant)?