A feature from manual_correction script is to have the possibility of iterating through subjects easily. Record of annotators such as name, date and revision step are able to be saved in a concomitant .json file related to the segmentation mask. For example:
However, manual_correction is primarly designed for fsleyes, but from a user perspective of individuals intended to do manual segmentation and/or manual correction, fsleyes has multiple navigation issues. This limits the efficiency that can be achieved for completing manual segmentation, a highly laborious task.
In that context, 3DSlicer exploration (issue 90) has been proposed with promising exploratory results. If using 3DSlicer, the proposition of creating .json file consistent with the format used in manual_correction has been discussed.
Although this has not been done yet, this is possible.
Here is an overview of pseudocode that could implement it :
python script from the 3DSlicer module -- function to write a .json file -- save the .json file in the derivative folder when a segmentation mask is created.
TO DO :
[ ] Implement a python script function in the 3DSlicer module used for navigation that creates a .json file once a segmentation mask is created.
[ ] Discuss with neuropoly team how versioning would like to be managed. This is already great with using git. However, the 3DSlicer module intended to be used can managed and display multiple versions at the same time.
A feature from manual_correction script is to have the possibility of iterating through subjects easily. Record of annotators such as name, date and revision step are able to be saved in a concomitant .json file related to the segmentation mask. For example:
However, manual_correction is primarly designed for fsleyes, but from a user perspective of individuals intended to do manual segmentation and/or manual correction, fsleyes has multiple navigation issues. This limits the efficiency that can be achieved for completing manual segmentation, a highly laborious task.
In that context, 3DSlicer exploration (issue 90) has been proposed with promising exploratory results. If using 3DSlicer, the proposition of creating .json file consistent with the format used in manual_correction has been discussed.
Although this has not been done yet, this is possible. Here is an overview of pseudocode that could implement it : python script from the 3DSlicer module -- function to write a .json file -- save the .json file in the derivative folder when a segmentation mask is created.
TO DO :