-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shifted GT spinal cord segmentations for PSIR and STIR contrasts #102
Comments
isn't there a more efficient way to do it? Eg: running sct_deepseg_sc if it works better. |
I tried |
If the shift is related to v2.4 (i.e., after adding PSIR and STIR contrasts), how would you explain that the shift is also presented for v2.3 predictions (i.e., before adding PSIR and STIR contrasts)? See v2.3 vs 2.4 comparison: valosekj/dcm-brno#19 (comment) |
I would like to understand the cause for this shift. Could it be as simple as an interpolation issue? |
IIUC this is not what Naga implied-- the GT were already existing before, and they were used to train the v2.4 model (TLDR: shift exists for 2.3 and, consequently, 2.4) |
Another example from valosekj/dcm-brno#19: sct_deepseg -i sub-1860B6472B_ses-1860B_acq-ZOOMit_dir-AP_dwi_crop_crop_moco_dwi_mean.nii.gz -task seg_sc_contrast_agnostic -qc qc -thr 0 Further investigation in sct-pipeline/contrast-agnostic-softseg-spinalcord#113 |
There is a slight shift in the GT segmentations of PSIR and STIR contrasts of the
canproco
dataset. We used these shifted segmentations in training the contrast-agnostic model v2.4. This is a problem as it risks making the model biased and keep outputting shifted predictions in the future versions of the model.example sub-edm010
Mitigation strategy 1 (short term):
Mitigation strategy 2 (long term):
The text was updated successfully, but these errors were encountered: