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
As discussed with @NathanMolinier and @jcohenadad on Slack, dataset names should mainly reflect the site, the FOV and possibly the pathology. In this sense, we could rename the marseille-rootlets dataset to cervical-marseille. This would also better match with the recently added lumbar-marseille (#325).
The text was updated successfully, but these errors were encountered:
Most of our dataset covers the cervical cord, so it's a bit weird to start the name with 'cervical'. According to this logic we should rename 90% of dataset with 'cervical-xxx'.
Is there anything more specific about this dataset? Eg contrast, pathology, etc.
if healthy control, we could consider naming it hc-marseille as we started doing (eg for #323)
Most of our dataset covers the cervical cord, so it's a bit weird to start the name with 'cervical'. According to this logic we should rename 90% of dataset with 'cervical-xxx'.
Fair point. Agree.
Is there anything more specific about this dataset? Eg contrast, pathology, etc.
if healthy control, we could consider naming it hc-marseille as we started doing (eg for #323)
The dataset contains HC only. The images are 3T T2w covering the C spine.
I did a quick search on our git-annex server and found that we also have marseille-3t-mp2rage. So maybe we could use hc-marseille-t2w? Or hc-marseille-3t-t2w (to make explicit that the data is 3T)?
As discussed with @NathanMolinier and @jcohenadad on Slack, dataset names should mainly reflect the site, the FOV and possibly the pathology. In this sense, we could rename the
marseille-rootlets
dataset tocervical-marseille
. This would also better match with the recently addedlumbar-marseille
(#325).The text was updated successfully, but these errors were encountered: