https://public.kitware.com/Wiki/index.php?title=Agenda%26Status_083110&feed=atom&action=historyAgenda&Status 083110 - Revision history2024-03-28T23:58:46ZRevision history for this page on the wikiMediaWiki 1.38.6https://public.kitware.com/Wiki/index.php?title=Agenda%26Status_083110&diff=29654&oldid=prevIbanez: Created page with '= How to Join the Tcon = == Number to Call == * 1-800-728-9607 (in the US) or * +1 9139049873 (international) * access code 6815251 == Webex == * Meeting link * https://emeet…'2010-09-01T22:35:32Z<p>Created page with '= How to Join the Tcon = == Number to Call == * 1-800-728-9607 (in the US) or * +1 9139049873 (international) * access code 6815251 == Webex == * Meeting link * https://emeet…'</p>
<p><b>New page</b></p><div>= How to Join the Tcon =<br />
<br />
== Number to Call ==<br />
<br />
* 1-800-728-9607 (in the US) or<br />
* +1 9139049873 (international)<br />
* access code 6815251<br />
<br />
== Webex ==<br />
<br />
* Meeting link<br />
* https://emeetings.webex.com/emeetings/j.php?ED=138191182&UID=482060457&PW=NNzJiNDk1ZGU3<br />
<br />
= Project Management =<br />
<br />
* Date of next meeting? 4-6 october?<br />
* location of next meeting?<br />
* move the tconf to 11am?<br />
<br />
= Technical Topics =<br />
<br />
== ITKv4-A02 ==<br />
* Work left to be done?<br />
* Work left to clean up the dashboard?<br />
* Target Date?<br />
<br />
== ITKv4-A03 ==<br />
* Work to be done?<br />
* Target Date?<br />
<br />
== LEVEL SET ==<br />
<br />
Megason lab to schedule Tcon for next week<br />
<br />
Details:<br />
<br />
* [[Refactoring Level-Set framework - V4]]<br />
<br />
== DICOM ==<br />
<br />
Dan and Mathieu to report<br />
* [[ITKv4_DICOM_Communications_Discussion | Beginnings of a requirements document]]. Comments welcome.<br />
* Updating openjpeg : DONE !<br />
* Introducing JPEG2000 : DONE !<br />
* Updating to GDCM 2.0 : DONE !<br />
* Release date for ITKv4-A02 ?<br />
<br />
== Simple ITK ==<br />
<br />
* Design Discussions<br />
* Sandbox in Github<br />
* Aggregating an ARB (composed of potential future users)<br />
** Define requirements<br />
* [[ITK_Release_4/SimpleITK|Simple ITK Layer]]<br />
* Wrapping for C# <br />
* Adding more filters<br />
<br />
== Uncrustify Code Cleanup (Hans) ==<br />
<br />
Please review the branch: http://github.com/hjmjohnson/ITK/tree/uncrustify_cleanup. It contains the uncrustified version of the code.<br />
<br />
<br />
== itkStaticConstMacro (Hans) ==<br />
I'd like to discuss creating a new macro called "itkEnumerationMacro" that will remove nearly all instances of itkStaticConstMacro in the code.<br />
<br />
* Reference materials: http://public.kitware.com/Bug/view.php?id=11158<br />
* In version 3.20 and earlier, this always defaulted to the enumerated type version of the itkStaticConstMacro.<br />
* The enumeration option for "template defined integer values" makes coding a lot easier<br />
* The "static const unsigned int" option requires definitions of those variables "outside" the class definition if they are to be used across compliation units (i.e. with explicit instantiation).<br />
<br />
<br />
<br />
== Stable ITK 3.20 ==<br />
<br />
* How to get it.<br />
* Maintenance rules (gate keeper ?)<br />
<br />
== Gerrit is ON ==<br />
<br />
* Marcus Hanwell to summarize<br />
* Details in the [[ITK/Gerrit|ITK Gerrit Wiki page]]<br />
* URL: http://review.source.kitware.com/<br />
* All developers must create their accounts.<br />
** You only need an [http://openid.net/get-an-openid OpenID]<br />
* Define groups<br />
* Define users' roles<br />
** Reviewers must be required from each contractor ?<br />
* '''Define workflow'''<br />
<br />
[[image:ITKv4-TransitionPlanProposal.png|529px]]<br />
* [[ITK_Release_4/Migration Plan/Phases|Phases]]<br />
<br />
== Testing Data in MIDAS ==<br />
<br />
* [[ITK_Release_4/Testing Data|ITKv4 Testing Data]]<br />
<br />
=== Data on MIDAS ===<br />
<br />
At:<br />
<br />
* http://midas.kitware.com/community/view/5<br />
<br />
=== MIDASapp ===<br />
<br />
Allows to download data on-the-fly, at run-time while running the testing. Data is cached (only downloaded once or when updated).<br />
<br />
* http://www.kitware.com/midaswiki/index.php/MIDAScpp<br />
* svn co https://www.kitware.com/svn/KWPublic/trunk/MIDAS/MIDAScpp<br />
* Dashboard http://www.cdash.org/CDash/index.php?project=MIDAS<br />
<br />
== Sequestered Reference Applications ==<br />
<br />
We have already made significant changes, and they are not being recorded yet. It is time to setup these reference applications.<br />
* Slicer<br />
* OTB<br />
** Nightly build use the current ITKv4. <br />
** http://dash.orfeo-toolbox.org/buildSummary.php?buildid=29602<br />
* V3D Plugins<br />
* IGSTK<br />
* Optional<br />
** Insight Applications (ITKApps from v3.20)<br />
** ITK tests from v3.20<br />
<br />
<br />
== Wrapping ==<br />
<br />
* Plans for wrapping<br />
* Tools<br />
** Pros and Cons<br />
* [[ITK_Release_4/Wrapping|Wrapping]]<br />
* update from brad on wrapitk test (new swig usage that addresses existing concerns)?<br />
<br />
== Refactoring Optimization Framework ==<br />
<br />
* Is the [http://www.itk.org/Wiki/Proposals:Refactoring_of_optimization_framework | refactoring of the optimization framework] going to be considered for itkv4?<br />
** Brian Avants to lead discussion on registration refactoring.<br />
<br />
=== ITK Readers for Microscopy formats ===<br />
<br />
* There's a need for readers in the microscopy community in order to be able to use ITK<br />
** Zeiss (LSM and ZVI)<br />
** Leica (LIF)<br />
** Olympus (OIB)<br />
** Nikon ()<br />
* [http://www.loci.wisc.edu/software/bio-formats BioFormats] has readers and example files for these. It is Java with C++ bindings for ITK, BUT it's GPL.<br />
<br />
= Software Process =<br />
<br />
== Migration to Git ==<br />
<br />
* Migration Completed<br />
** Procedure for contributing Patches: http://www.itk.org/Wiki/ITK/Git#Contributing_Patches<br />
* Updating Dashboard Machines to Git<br />
* Contractors to send information to Kitware about the developers who should receive Git write access.<br />
** (include email and public SSH key)<br />
<br />
<br />
== Clean up Releases ==<br />
<br />
<br />
{| border="1"<br />
|- bgcolor="#abcdef"<br />
! Release Tag !! Date !! Major Changes<br />
|-<br />
| Alpha-01 || August 7 || VS6,BCC55, SunCC (5.7?), Metrowerks Removal (based on compiler features), Remove large Images<br />
|-<br />
| Alpha-02 || August 14 || CMake Variables configuration cleanup<br />
|-<br />
| Alpha-03 || August 21 || GDCM 2.0, OpenJpeg-v2, +JPEG2000 <br />
|-<br />
| Alpha-04 || August 28 || Third party libraries update: TIFF, JPEG, PNG<br />
|}<br />
<br />
[[image:ITKv4-TransitionPlanProposal.png|529px]]<br />
<br />
* [[ITK_Release_4/Migration Plan/Phases|Phases]]<br />
<br />
<br />
== Unit testing framework ==<br />
<br />
A [[ITK_Release_4/UnitTesting|tutorial has been drafted]] using the Google Testing framework.<br />
<br />
== Tools ==<br />
<br />
=== Coding Style ===<br />
<br />
[[ITKv4_StyleChangeProposal]]<br />
* Fixing KWStyle/CDash/CTest for Git : Brad Davis report<br />
<br />
* The [http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C+++ Style Guide] is a good example of a style guide. Although the specifics may differ, the format and coverage of this guide is very nice. We may consider producing a similar Guide for ITKv4.</div>Ibanez