You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with @fedorov, I think it would be beneficial to add a few lines in the itkimage2segimagedocumentation page to help users with the following use case:
generation of the JSON file when the input is a comma-separated list of N files, each storing the segmentation mask for a single structure.
The reason I'm opening this issue is that the JSON generated at http://qiicr.org/dcmqi/#/seg is not right in such case - as segmentAttributes will be a list of a list containing N different dictionaries (with labelID going from 1 to N):
# this works if a single input file stores N different structures
{
"ContentCreatorName": "DB",
...
"segmentAttributes": [
[
{
"labelID": 1,
# dict for structure 1
},
{
"labelID": 2,
# dict for structure 2
},
...
]
],
"ContentLabel": "SEGMENTATION",
...
}
instead of a list of N lists containing one dictionary each (per structure, with labelID: 1 in all the cases):
# this works if N input files store one structure each
{
"ContentCreatorName": "DB",
...
"segmentAttributes": [
[
{
"labelID": 1,
# dict for structure 1
}
],
[
{
"labelID": 1,
# dict for structure 2
}
],
...
"ContentLabel": "SEGMENTATION",
...
}
The text was updated successfully, but these errors were encountered:
Hey all,
Thanks for the work you guys put in dcmqi.
As discussed with @fedorov, I think it would be beneficial to add a few lines in the
itkimage2segimage
documentation page to help users with the following use case:The reason I'm opening this issue is that the JSON generated at http://qiicr.org/dcmqi/#/seg is not right in such case - as
segmentAttributes
will be a list of a list containing N different dictionaries (withlabelID
going from 1 to N):instead of a list of N lists containing one dictionary each (per structure, with
labelID: 1
in all the cases):The text was updated successfully, but these errors were encountered: