- User Since
- Jan 9 2019, 9:45 PM (246 w, 5 d)
Thu, Sep 7
offer the feature to take an instance UID that is an int as the pixel value.
Jul 11 2023
Sounds good Ralf - happy to help!
" increase monotonically by 1" could be interpreted as "no holes allowed". We should clarify if this is the case.
Apr 11 2023
@floca I think the issue is that it will probably be better to separately communicate server endpoint and refer to the Study/Series items in the DICOM model hierarchy via UIDs. I think adding support for DICOM should be done as part of the initial design, rather than and afterthought and replacement of file paths by URIs. But that only makes sense if DICOM is important and primary for the use case driving the development. That is why I suggest you guys proceed with your original plan, and we will try to experiment with the DICOM-centric design. But of course I may be wrong. I just think it is more expedient to experiment rather than coordinate the design at the same time as the use cases and requirements are evolving.
Apr 10 2023
Apr 3 2023
Thanks. Here are some more comments to start the discussion:
- l think it will be important to make it possible to work with the inputs defined by DICOM UIDs and available through DICOM endpoints, instead of relying purely on file system. Would this be acceptable for your use cases?
- In addition to segmentations, it would be helpful to include an option to perform the review of existing segmentations (e.g., those generated by AI that need to be QA'd by an expert, and where some kind of segmentation may or may not be generated as part of the QA process)
- I think there is potentially common needs between this task and the "MetaDashboard" initiative in kaapana (see https://projectweek.na-mic.org/PW38_2023_GranCanaria/Projects/MetaDashboard/) - should these two efforts be coordinated? In that regard, the definition of the worklist does not need to be limited to support of the segmentation task (e.g., there are other tasks already considered in the context of the MetaDashboard, such as series type classification, presence of the artifacts.
Mar 30 2023
Did you consider using JSON Schema to formalize the definition? It is a bit hard to grasp it right now, but admittedly I probably didn't spend enough time looking over the various resources provided.
Jan 27 2022
Since in the input image a required tag is missing, MITK cannot provide a fix, allowing a success in dcmqi
Feb 3 2021
Here's the PR with CI testing results https://github.com/QIICR/dcmqi/pull/415. You can look at the CI results for earlier commits, if you would like to investigate.
Jan 19 2021
@floca thanks for the report! I added a comment to the dcmqi issue you created.
Feb 18 2019
Also note that the link to the manual from the ModelFit page (which I am assuming is http://mitk.org/wiki/MITK-ModelFit) is currently broken: http://mitk.org/index.php?title=MITK_ModelFit_Manual_2018-07-17.pdf&action=edit&redlink=1