Julien Cohen-Adad

- Inconsistency in the code: https://github.com/neuropoly/template/issues/19 - if you are using system call (see previous bullet point), i suggest you install SCT from package (option 1) or dev (option 2)....

> We definitely will need to be careful with the info_label.txt if we decide to remove this file. (Do we leave a gap? Do we renumber the labels after, but...

additional note: for now, the "Linux" binaries to select are the centos7 build. Because this is supposedly the most polyvalent version, and this is also Python's strategy for distributing binaries...

the info is not in the paper, unfortunately-- we need to dig in: - our duke folders (student's folder, projects folder, etc.) - our many repos

i know that a large amount of dat afrom sct_testing_large (previously on duke, now on git-annex) was used fro sct_depesegsc

> I can create a list of each deep learning-based CLI script, along with their associated repos and papers, to see what information is missing for each script. i think...

> Wonderful news! ❤️ > > > SCT's team has now access to the code source, but the code needs to remain closed (ie: not shareable via Github). > >...

> the only written document with all the details is the signed agreement i’ll upload the signed agreement on the new private repos so it’s clear and transparent for everyone...

> Hello @jcohenadad, can I have acccess to the `isct_spine_detect` source code? see: https://forum.spinalcordmri.org/t/where-is-the-c-source-code-for-the-binaries/1122/16?u=jcohenadad

Maybe [torchreg](https://github.com/codingfisch/torchreg) could be useful? @rohanbanerjee can you try on fMRI time series?