Julien Cohen-Adad

> @jcohenadad -- Would it be a desirable feature to allow users to input a centerline for angle correction (e.g. summed GM+WM), thus allowing for consistent CSA angle correction on...

> you would rather recommend to input a centerline for angle correction rather than no angle correction at all? It depends what you want to do with the analysis, what...

> Basically, our thoughts are that by multiplying the area of one slice by its thickness (need to figure out if we should use the theoretical thickness or the one...

right, if you select the same number of slices across mice, then the volume will simply be the average CSA multiplied by a scalar (so there is no _gained_ information...

> If that's the case, then I can prioritize implementing this in sct_process_segmentation (while ensuring that CSA for GM + WM = SC when angle correction is applied). i think...

Ah! Thank you for reporting this Mathieu. I did run into the exact same strange behaviour 2 days ago, and concluded that I was the strange one, because if we...

> If we choose to remove the SourceForge project, we would need the credentials for the adminstrator's account, which I currently lack. @joshuacwnewton i'll send it to you in our...

Since we're at it, we should also consider adding the name of the person doing the QC (similarly to what we do for the manual correction). Tagging @valosekj @sandrinebedard

> To reduce the amount of typing, we could consider a drop-down menu with a list of common options (oversegmention, undersegmentation, motion artifact, ...) with the possibility to add new...

About https://github.com/spinalcordtoolbox/spinalcordtoolbox/issues/4310#issuecomment-1828670693, can't we do it as we do our `exclude.yml` file ([example](https://github.com/spine-generic/data-multi-subject/blob/master/exclude.yml)): ```yaml FILES_SEG: - sub-05_acq-MTon_MTS.nii.gz # oversegmentation ```