Difference between revisions of "2015 Summer Project Week:Dicom parsing with DCMJS"
From NAMIC Wiki
| Line 25: | Line 25: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * Evaluated speed of current solutions |
| + | ** dcmjs slower (150ms for dcmdump vs 30ms for other solutions) | ||
| + | * Limitations of current solutions | ||
| + | ** single frame dicom images | ||
| + | ** hard to re-use | ||
| + | ** hard to extend | ||
| + | * Proposed workflow | ||
| + | ** https://docs.google.com/drawings/d/1BX0NBIDPrrM-JGk9b1awL_w57f9rMvdTJSeVjT9bM5U | ||
| + | * Take dicom segmentations/models into account | ||
| + | * Testing database | ||
</div> | </div> | ||
</div> | </div> | ||
Revision as of 07:49, 24 June 2015
Home < 2015 Summer Project Week:Dicom parsing with DCMJS
Key Investigators
- Nicolas Rannou
- Michael Onken
- Steve Pieper
Project Description
Objective
- Define target DICOM types
- Define a good workflow to parse targets with DCMJS.
- Define required JS models to support the workflow.
- Evaluate DicomParser from cornerstone team.
Approach, Plan
- Talk with DICOM/DCMTK experts to get some feedback on best strategy.
- Write a demo to showcase js models and dicom parsing workflows.
Progress
- Evaluated speed of current solutions
- dcmjs slower (150ms for dcmdump vs 30ms for other solutions)
- Limitations of current solutions
- single frame dicom images
- hard to re-use
- hard to extend
- Proposed workflow
- Take dicom segmentations/models into account
- Testing database
