Difference between revisions of "2012 Winter Project Week DICOM RT Breakout"
From NAMIC Wiki
(Created page with '=Objective= *Identify and priorize tasks regarding the integration of DICOM RT related functions in Slicer4 *Make decisions upon major design questions *Plan further steps =Time…') |
m (→Plan) |
||
| (18 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[AHM_2012#Agenda|Back to AHM Schedule]] | ||
| + | |||
=Objective= | =Objective= | ||
*Identify and priorize tasks regarding the integration of DICOM RT related functions in Slicer4 | *Identify and priorize tasks regarding the integration of DICOM RT related functions in Slicer4 | ||
| Line 10: | Line 12: | ||
=Agenda= | =Agenda= | ||
*3:10-3:20, Welcome, Goal of the meeting, Agenda, Taking notes in wiki | *3:10-3:20, Welcome, Goal of the meeting, Agenda, Taking notes in wiki | ||
| − | *3:20-3:35, Introduction of SlicerRT project (under [http://www.assembla.com/spaces/sparkit SparKit]) goals, design options - Csaba Pinter | + | *3:20-3:35, Introduction of [https://www.assembla.com/spaces/sparkit/wiki/SlicerRt SlicerRT] project (under [http://www.assembla.com/spaces/sparkit SparKit]) goals, design options - Csaba Pinter ([[media:DICOMRTImportInSlicer4.pptx|slides]]) |
| − | *3:35- | + | *3:35-3:50, Overview of DICOM-RT - Greg Sharp ([[media:2012-01-09-sharp-dicomrt.pdf|slides]]) |
| + | *3:50-4:15, Slicer annotations for Quntitative Imaging Network (DICOM SR, AIM) - Andrey Fedorov ([[media:2012-01-09-fedorov-qin_slicer_annotation.pdf|slides]]) | ||
*?:??-?:??, Introduction of ... - Anyone who is interested | *?:??-?:??, Introduction of ... - Anyone who is interested | ||
| − | *?:??-4:40, Discussion about the common needs, | + | *?:??-4:40, Discussion about the common needs, priorities, the best approaches and design options |
*4:40-5:00, Decisions, Action plan | *4:40-5:00, Decisions, Action plan | ||
| + | |||
| + | == Organizational Topics== | ||
| + | * How can we organize ourselves to minimize duplicated effort | ||
| + | ** How to share code with Slicer and non-Slicer projects (plastimatch) | ||
| + | * Who is 'on the hook' to deliver functionality related to DICOM? | ||
| + | ** What is funding the effort? | ||
| + | ** What is the use case and deliverable? | ||
| + | ** What toolkit will be used? | ||
| + | ** What synergy is there with other efforts? | ||
| + | * Are there specific issues that we can work out this week as a team? | ||
| + | |||
| + | == Design questions== | ||
| + | * How to add handling of the new entities in CTK? | ||
| + | ** Notifyable loadable module? | ||
| + | * How to represent the data in Slicer? (which MRML nodes to use) | ||
| + | * Conversion issues between the representations | ||
| + | ** Contour → Volume/Surface | ||
| + | ** Manual or automatic | ||
| + | * Are RT specific modules expanded during import or just on load in the treeview? | ||
| + | |||
| + | == Plan == | ||
| + | * Telecons | ||
| + | ** Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group<br>Participants please sign up on the bottom of the page | ||
| + | ** DCMTK | ||
| + | *** What can go reasonably in DCMTK should go there as lowest level toolkit | ||
| + | *** Middle level addition for interpreting raw data | ||
| + | ** CTK | ||
| + | *** Get relevant tags from RT/SR and insert them in database | ||
| + | * Slicer extension | ||
| + | ** Hidden loadable module | ||
| + | ** Lower level register-observe method | ||
| + | ** Storage nodes, IO factory | ||
| + | ** Solve binding of the annotations to a volume | ||
| + | * Representation | ||
| + | ** Contours | ||
| + | *** Store contour series - vtkMRMLAnnotation...Node: PolyLine | ||
| + | *** Hierarchy: Structure Set -> Structure -> Contour | ||
| + | **** Hierarchy nodes that represent a relationship | ||
| + | **** Transform graph: tree, Grouping: tree/graph? | ||
| + | |||
| + | == TBD == | ||
| + | * Image representation, multiple structures for a voxel | ||
| + | * DICOM Metadata format in Slicer | ||
| + | ** Keep it in the file? | ||
| + | *** We have the UID and the database -> we can get the file | ||
| + | *** Caching may be implemented in CTK | ||
| + | *** The file can be kept in memory | ||
| + | *** Pointer in the vtkMRMLNode to a DCMTK object | ||
| + | |||
| + | == Follow-up meeting == | ||
| + | '''Sign up here to get invitation to the meeting with CTK and DCMTK developer groups''' | ||
| + | *Andras Lasso | ||
| + | *Csaba Pinter | ||
| + | *Kevin Wang | ||
| + | *Steve Pieper | ||
| + | *Greg Sharp | ||
Latest revision as of 23:31, 12 January 2012
Home < 2012 Winter Project Week DICOM RT BreakoutBack to AHM Schedule
Contents
Objective
- Identify and priorize tasks regarding the integration of DICOM RT related functions in Slicer4
- Make decisions upon major design questions
- Plan further steps
Time and Place
- 3PM-5PM, Tuesday, January 10, 2012
- Amethyst room, Marriott, Salt Lake City, UT
Agenda
- 3:10-3:20, Welcome, Goal of the meeting, Agenda, Taking notes in wiki
- 3:20-3:35, Introduction of SlicerRT project (under SparKit) goals, design options - Csaba Pinter (slides)
- 3:35-3:50, Overview of DICOM-RT - Greg Sharp (slides)
- 3:50-4:15, Slicer annotations for Quntitative Imaging Network (DICOM SR, AIM) - Andrey Fedorov (slides)
- ?:??-?:??, Introduction of ... - Anyone who is interested
- ?:??-4:40, Discussion about the common needs, priorities, the best approaches and design options
- 4:40-5:00, Decisions, Action plan
Organizational Topics
- How can we organize ourselves to minimize duplicated effort
- How to share code with Slicer and non-Slicer projects (plastimatch)
- Who is 'on the hook' to deliver functionality related to DICOM?
- What is funding the effort?
- What is the use case and deliverable?
- What toolkit will be used?
- What synergy is there with other efforts?
- Are there specific issues that we can work out this week as a team?
Design questions
- How to add handling of the new entities in CTK?
- Notifyable loadable module?
- How to represent the data in Slicer? (which MRML nodes to use)
- Conversion issues between the representations
- Contour → Volume/Surface
- Manual or automatic
- Are RT specific modules expanded during import or just on load in the treeview?
Plan
- Telecons
- Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group
Participants please sign up on the bottom of the page - DCMTK
- What can go reasonably in DCMTK should go there as lowest level toolkit
- Middle level addition for interpreting raw data
- CTK
- Get relevant tags from RT/SR and insert them in database
- Internal (just us), next week (Jan 16-20) - to be organized by the SparKit group
- Slicer extension
- Hidden loadable module
- Lower level register-observe method
- Storage nodes, IO factory
- Solve binding of the annotations to a volume
- Representation
- Contours
- Store contour series - vtkMRMLAnnotation...Node: PolyLine
- Hierarchy: Structure Set -> Structure -> Contour
- Hierarchy nodes that represent a relationship
- Transform graph: tree, Grouping: tree/graph?
- Contours
TBD
- Image representation, multiple structures for a voxel
- DICOM Metadata format in Slicer
- Keep it in the file?
- We have the UID and the database -> we can get the file
- Caching may be implemented in CTK
- The file can be kept in memory
- Pointer in the vtkMRMLNode to a DCMTK object
- Keep it in the file?
Follow-up meeting
Sign up here to get invitation to the meeting with CTK and DCMTK developer groups
- Andras Lasso
- Csaba Pinter
- Kevin Wang
- Steve Pieper
- Greg Sharp
