cornerstonejs
[WIP]: Example/rtss
WIP - segmentToRTSS example has function for converting segmentation volume to ROIContour to be sent to dcmjs for export. Conversion to contour is performed via vtkImageMarchingSquares routine on each of the slices.
- Currently missing Referenced Image UIDs, should this be populated instead in dcmjs?
- Would the conversion function be best placed in a tool or as a general util?
Deploy Preview for cornerstone-3d-docs ready!
| Name | Link |
|---|---|
| Latest commit | a890377fed1a9d0f677812d2cdb5f923cef64871 |
| Latest deploy log | https://app.netlify.com/sites/cornerstone-3d-docs/deploys/6317f9b03d87c500090e72b3 |
| Deploy Preview | https://deploy-preview-202--cornerstone-3d-docs.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hey, glad to see that you have some progress on this. One small note, you need to add the name of the example folder here for it to show up in the demo page.
Looking forward to try it
Thanks for notice! I've updated with the changes.
The example at the moment only outputs the contour object in the console. The intention is for this object to be passed to dcmjs for export.
@dxlin Cornerstone3D does not have dependency on dcmjs (and we don't want to add that), hmmm, I'm wondering if then PR to Cornerstone is a bad idea. Let's try to implement the non-dcmjs part of the functionalities in the tools, and then the demo itself can have dependency on the dcmjs (right now some of them does).