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
Labels.csv file could be simplified by using shorter column names (those proposed in Slicer/Slicer#7593).
Also, we could add the segment colors there as well, which would allow us to automatically generate segmentation terminology .term.json file from labels.csv.
@diazandr3s what do you think about updating all our labels.csv files in the current models?
LabelValue - no change
Name - no change
Color.R - new field, set from the colors currently in term.json files, value is 0-255
I could do download all the zip files from the model github release, update the labels.json files, and upload the new zip files; and update the code to use the new format. Older version of the extension would not work with the new models, but users then can just update to the latest extension version (and it is still better to do this breaking change sooner than later).
The text was updated successfully, but these errors were encountered:
Labels.csv file could be simplified by using shorter column names (those proposed in Slicer/Slicer#7593).
Also, we could add the segment colors there as well, which would allow us to automatically generate segmentation terminology .term.json file from labels.csv.
@diazandr3s what do you think about updating all our labels.csv files in the current models?
I could do download all the zip files from the model github release, update the labels.json files, and upload the new zip files; and update the code to use the new format. Older version of the extension would not work with the new models, but users then can just update to the latest extension version (and it is still better to do this breaking change sooner than later).
The text was updated successfully, but these errors were encountered: