tasks.json
file as well.
Please see the following walkthrough for example structures, explanations, and other clarifications regarding export structures.
semantic_mask
or binary_mask
.
segmentMap
, which can be found in the tasks.json
file.
segmentMap
, which can be found in the tasks.json
file.
binary_mask
for Tasks that have overlapping segmentations. You can read more about the binary_mask parameter and how it affects exports here.semantic_mask
parameter of the Python SDK’s export_tasks()
function.
The Semantic Export enforces a direct mapping between an Object Label and the segmentMap
value. While this does not change the structure of the export subdirectory itself, Semantic Export does bring significant changes to the tasks.json
file generated upon export.
Please compare the two sample segmentMap
outputs below.
segmentMap
? segmentMap
integer incrementally based on the order the labeler created the annotations, the Semantic Export directly correlates this Category Number to your annotation within the NIfTI file, regardless of how the annotator did their work.
In other words (and using the example above), any Glioma annotation will always have a segmentMap
value of 3 upon semantic export, any Abscess will always have a value of 6, and so on.
segmentMap
for Semantic Export?tasks.json
file and the segmentations/
directory will have a unique structure.
Your export subdirectory will contain the annotation files for all users who generated and saved annotations on RedBrick AI. Each individual annotation file is marked with a numeric index (e.g. “_1” at the end of the file name, and you can map this file to the corresponding user by referencing your tasks.json
file.