ITK/Release 4/DICOM/Tcon 2011 04 15: Difference between revisions

From KitwarePublic
< ITK‎ | Release 4‎ | DICOM
Jump to navigationJump to search
(Created page with "= Agenda =")
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
= Agenda =
= Agenda =
<h3> Transition and effort</h3>
<ul>
<li>Mark awarded by NIH, as expected, and is transitioning out (original contract from NIH supposed to be out in june)
<li>(alex and) drew take over DICOM
<li>drew fly over to singapore for a month to do full time gdcm with Alex (april 17 to may 15)
</ul>
<h3>Status</h3>
<ul>
<li>status of merging gdcm in ITK
<ul>
<li>GDCM21Merge on the CoSMo Github page
<li>Warnings for vs2010 all fixed
<li>No ITK tests failing
</ul>
<li>status of PACS support in gdcm (SCU)
<li>status of streaming in gdcm (reading works, writing is failing tests)
<li>status of RT-STRUCT support in gdcm / VTK / ITK (works in VTK, not in ITK yet)
</ul>
<h3>Roadmap</h3>
<li>address failing tests <i>determine relevance to ITK before addressing</i>
<li>address warnings <i>mainly the sizeof(4) to sizeof(8) transition in 32 to 64 bits)</i>
<li>what Is needed to use protocol in ITK? <i>gdcmCompositeNetworkFunctions (briefly)</i>
<li>what Is needed to use streaming in ITK? <i>gdcmStreamImageReader (briefly)</i>
<li>what Is needed to use RT-STRUCT in ITK <i>Some kind of mesh interaction, RTStructSet writer function</i>
<li>what are our main use cases (cannot address all dicom) <i>What functions must be present</i>
<li>what would be the higher level API that could encapsulate gdcm/dcmtk  <i>Mathieu's ITKDICOM, or something else</i>
</li>

Latest revision as of 16:00, 9 December 2011

Agenda

Transition and effort

  • Mark awarded by NIH, as expected, and is transitioning out (original contract from NIH supposed to be out in june)
  • (alex and) drew take over DICOM
  • drew fly over to singapore for a month to do full time gdcm with Alex (april 17 to may 15)

Status

  • status of merging gdcm in ITK
    • GDCM21Merge on the CoSMo Github page
    • Warnings for vs2010 all fixed
    • No ITK tests failing
  • status of PACS support in gdcm (SCU)
  • status of streaming in gdcm (reading works, writing is failing tests)
  • status of RT-STRUCT support in gdcm / VTK / ITK (works in VTK, not in ITK yet)

Roadmap

  • address failing tests determine relevance to ITK before addressing
  • address warnings mainly the sizeof(4) to sizeof(8) transition in 32 to 64 bits)
  • what Is needed to use protocol in ITK? gdcmCompositeNetworkFunctions (briefly)
  • what Is needed to use streaming in ITK? gdcmStreamImageReader (briefly)
  • what Is needed to use RT-STRUCT in ITK Some kind of mesh interaction, RTStructSet writer function
  • what are our main use cases (cannot address all dicom) What functions must be present
  • what would be the higher level API that could encapsulate gdcm/dcmtk Mathieu's ITKDICOM, or something else