- User Since
- Aug 1 2016, 12:10 PM (159 w, 2 d)
Fri, Aug 2
Jun 26 2019
Apr 8 2019
Mar 18 2019
The derived segmentation can only be saved as DICOM if the original image is a DICOM.
Mar 4 2019
Mar 1 2019
Added a simple check for the dimension. I will have to take a closer look at the 4D (maybe 2D) support in the next weeks unless there are volunteers who can take more care of it.
The crash is caused by the duplicate creation of the layers:
Pushed new branch T25798-FixDICOMSegWriterConfidenceLevelCheck.
Feb 27 2019
JIP Dashboard for First Fersion including all named visualization.
- Renaming the visualization with ONE naming scheme
Feb 25 2019
Feb 20 2019
Jan 23 2019
Jan 7 2019
Dec 21 2018
If you load a DICOM image and create a segmentation based on that, you could write a DICOM Seg. For that case, the writer works for me.
Unfortunately not for 4d images and I will report a task for that. T25801
Pushed new branch T25798-DICOMSegWriterConfidenceLevelCheck.
Ok. Is this for the bugfix release? When is the 'deadline' for this?
Still I don't think that's the best way. Maybe we could rank the writer lower or something similar, so that people, who know when they can write DICOM SEGs, could use the writer. I will have a look at the GetWriterConfidenceLevel() checks asap.
Sorry, I missed this task. Maybe we should add a condition to the confidence level check and do not return unsupported in general. I think at the moment most checks are done IN the writer and not before. What was the actual problem?
Oct 23 2018
Oct 4 2018
Sep 7 2018
T25192 could be helpful.
Some hints for this use case:
NOT READY FOR MASTER!
Pushed new branch T25192-MultilabelNrrdToDICOMSeg.
See T25412 task for resolving the dependency problem after the changes.
Pushed new branch T25412-DICOMQIErrorSmallerFixes.
Sep 6 2018
Due to the missing dependency to the Multilabel modul, the DICOMSegmentationIO class moved back to an autoload module in the Multilabel context. Only the mimetypes class remains in the DICOMQI module. @kompan: This is important to your changes in the PM context.
Pushed new branch T25412-FixDependenciesErrorDICOMQIIO.
Sep 5 2018
Pushed new branch T25246-DICOMSegRefactoringIntegrationMaster.
Sep 3 2018
Aug 23 2018
Aug 9 2018
Pushed new branch T25246-DICOMSeg_Refactoring.
Aug 2 2018
Jul 19 2018
Mar 29 2018
Overview: Which compiler are recommended and supported?
Visual Studio 2013 drop: T23868
Visual Studio 2017 support T24391 ,T23882, T23034
Support MSVC 19.11 T23276
GCC 7.2 Compatibility T23614
Mac support: T23248 T23985
Mar 28 2018
The application should no longer crash when a surfaceSegmentationStorage class DICOM is loaded.
I also added a check for the SOPClassUID in the MimeType of the DICOMSegmentation. At the Moment we can only handle the SegmentationStorage objects. -.-