-
Notifications
You must be signed in to change notification settings - Fork 2
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
adding testing data for distriploy release #1
Conversation
@@ -0,0 +1 @@ | |||
{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where is this data coming from? is it a public dataset? if not, why not simply using a subject from spine-generic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just the copy of the testing data that was already in ivadomed. I do need to add the new data that will be used in the new tests. There will still be a single subject. I don't think it is a public dataset (this PR ).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it is a public dataset
can we replace it with another subject then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also: if you don't rebase the unused binaries, please make sure to "squash and merge" for merging this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm looking into it with the test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe. I am trying with the available csf_seg given in the ivadomed/data_example_spinegeneric repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, i'm getting confused now, i thought you were looking for a file with suffix _lesion-manual
?
i would suggest you list, in the PR's body, all the files that are needed by your tests. Then, we can all think and find the best solution for the listed files (in terms of size, availability, need for manual intervention, etc.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh sorry I will list them.
I was using the csf segmentation as a dummy seg. (I renamed it T2w_lesion_manual).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I renamed it T2w_lesion_manual
that’s exactly the kind of stuff i’d like to avoid. it might bring confusion to a future student
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lrouhier: For the previous testing data: what I did was to create a "fake lesion", ie a blob, in the spinal cord (the subject has healthy).
participants.tsv
Outdated
@@ -0,0 +1,2 @@ | |||
participant_id sex age first_name last_name date_of_birth date_of_scan pathology data_id institution_id | |||
sub-test001 unknown - unknown unknown - unknwon unknwon unknown unknown |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be better to use a data from which we know the provenance (e.g. spine-generic)
ef4bc83
to
8b4fa52
Compare
Pull request autamoatically Closed by removing the previous commit to replace subject with one from spine-generic. This was done to avoid having a big repository for a single subject. PR #2 will provide similar changes. In summary, nothing was done. |
^ scrap that-- info about closing: #1 (comment) |
This PR aims at uploading the current testing data used in the ivadomed test to github in order to perform a distriploy release.
Needed images and files: