TubeTK/Events/2010.11.02: Difference between revisions

From KitwarePublic
< TubeTK‎ | Events
Jump to navigationJump to search
No edit summary
 
(14 intermediate revisions by 4 users not shown)
Line 2: Line 2:


*  Implementation on the ComputeTortuosity module (only Distance Metric) ---->OK!!
*  Implementation on the ComputeTortuosity module (only Distance Metric) ---->OK!!
** With input data = Branch-truth.tre (from tubetk/Data)
*** With mask covering the whole tube (Branch.n010.mha):
**** Distance Metric Tortuosity for tube section 0 - 999 is 0.0524638
**** Distance Metric Tortuosity for tube section 0 - 499 is 0.0656099
*** With other mask (Branch.n010.sub.mha) not covering the whole scene
**** Distance Metric Tortuosity for tube section 0 - 399 is 0.0811677
*Future
** tortuosity: documentation, tests, checkin
** Grassroots data visualization
** Conference website
** CLANG errors in metaImage
*GRASSROOT
** https://www.kitware.com/KWWiki/index.php/Medical_Imaging/Grassroots
**clsm-automation
[[File:Tile_rgb_z1.png|500px|tile rgb z1]]
[[File:Tile_rgb_z11.png|500px|tile rgb z11]]
**re-sample
[[File:23805.jpg|500px|23805]]
[[File:24267.jpg|500px|24267]]
[[File:24189.jpg|500px|24189]]


** With input data = Branchtruth.tre (from tubetk/Data)
= Stephen =


*** With mask covering the whole tube (Branch.n010.mha):
* TubeSpatialObject
[[File:sub.png|500px]]
** Bug in ComputeTangentAndNormals
- Starting /home/romain/Projects/TubeTK/TubeTK-build/TubeTK-Build/lib/TubeTK/Plugins/ComputeTortuosity...
** Therefore, Tube/Base/Segmentation/VTree/tubeMath.h
<filter-start>
** Pursue refactoring of itk's SpatialObject classes
<filter-name>ComputeTortuosity</filter-name>
** Time?  Funding?
<filter-comment> "ComputeTortuosity" </filter-comment>
* RadiusEstimation
</filter-start>
** Refactoring complete, bugs remain, tests being added
<filter-progress>0.1</filter-progress>
* Slicer integration
Number of children = 1
** Next Priority
Number of tubes = 2
* USC
'''Distance Metric Tortuosity for tube section 0 - 999 is 0.0524638
** Funding becoming active
Distance Metric Tortuosity for tube section 0 - 499 is 0.0656099'''
** Urgent need for unsupervised method
/home/romain/Projects/TubeTK/TubeTK-build/TubeTK-Build/lib/TubeTK/Plugins/ComputeTortuosity exited with code 0
* Grassroots
** Received data
** Romain to view in Slicer and send visualization to Danielle and Stephen
** NDA signed
** Meeting next week
* UCLA/TBI
** Received data (can't find it)
** Visualizations needed (Danielle)
* BWH US Machine in Eternia


*** With other mask (Branch.n010.sub.mha) not covering the whole scene
= Danielle =
Starting /home/romain/Projects/TubeTK/TubeTK-build/TubeTK-Build/lib/TubeTK/Plugins/ComputeTortuosity...
* Successfully registered XCAT images:
<filter-start>
[[File:2010_11_02_xcatRegistration.png]]
<filter-name>ComputeTortuosity</filter-name>
* Anisotropic gives much better motion field
<filter-comment> "ComputeTortuosity" </filter-comment>
* Gaussian does a bit of a better job than anisotropic
</filter-start>
* Currently doing last validations = mutual overlap / Haussdorf distance between surfaces (with Valmet)
<filter-progress>0.1</filter-progress>
* Small questions:
Number of children = 1
** Max filename size in ITK?
Number of tubes = 2
** Valmet only in Windows...
'''Distance Metric Tortuosity for tube section 0 - 399 is 0.0811677
* Next priorities: TubeTK dashboard, some code cleanup, register CT data, then implement improvements from Marc's suggestions + discussion with Stephen on Friday (coarse to fine, normals as matrices to handle corners)
'''/home/romain/Projects/TubeTK/TubeTK-build/TubeTK-Build/lib/TubeTK/Plugins/ComputeTortuosity exited with code 0
* To think about: MICCAI 2011 (submission of full papers = March 11)


*Future
[[Category:TubeTK Events and Meetings|2010.11.02]]
** obtain dimension??? make it work for every dimension??
** #tube command ????
** Implementation of the other 2 methods : ICM SOAM ????

Latest revision as of 18:49, 26 July 2013

Romain

  • Implementation on the ComputeTortuosity module (only Distance Metric) ---->OK!!
    • With input data = Branch-truth.tre (from tubetk/Data)
      • With mask covering the whole tube (Branch.n010.mha):
        • Distance Metric Tortuosity for tube section 0 - 999 is 0.0524638
        • Distance Metric Tortuosity for tube section 0 - 499 is 0.0656099
      • With other mask (Branch.n010.sub.mha) not covering the whole scene
        • Distance Metric Tortuosity for tube section 0 - 399 is 0.0811677
  • Future
    • tortuosity: documentation, tests, checkin
    • Grassroots data visualization
    • Conference website
    • CLANG errors in metaImage

tile rgb z1 tile rgb z11

    • re-sample

23805 24267 24189

Stephen

  • TubeSpatialObject
    • Bug in ComputeTangentAndNormals
    • Therefore, Tube/Base/Segmentation/VTree/tubeMath.h
    • Pursue refactoring of itk's SpatialObject classes
    • Time? Funding?
  • RadiusEstimation
    • Refactoring complete, bugs remain, tests being added
  • Slicer integration
    • Next Priority
  • USC
    • Funding becoming active
    • Urgent need for unsupervised method
  • Grassroots
    • Received data
    • Romain to view in Slicer and send visualization to Danielle and Stephen
    • NDA signed
    • Meeting next week
  • UCLA/TBI
    • Received data (can't find it)
    • Visualizations needed (Danielle)
  • BWH US Machine in Eternia

Danielle

  • Successfully registered XCAT images:

2010 11 02 xcatRegistration.png

  • Anisotropic gives much better motion field
  • Gaussian does a bit of a better job than anisotropic
  • Currently doing last validations = mutual overlap / Haussdorf distance between surfaces (with Valmet)
  • Small questions:
    • Max filename size in ITK?
    • Valmet only in Windows...
  • Next priorities: TubeTK dashboard, some code cleanup, register CT data, then implement improvements from Marc's suggestions + discussion with Stephen on Friday (coarse to fine, normals as matrices to handle corners)
  • To think about: MICCAI 2011 (submission of full papers = March 11)