-
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
Systematic review of binary ground truth quality #25
Comments
Adding the QC of all the datasets as a single QC report. These QCs contain the binary ground truth. (Didn't add the SHA of the dataset because we have decided to not upload the dataset to git-annex but to openneuro directly. A list of the datasets can be found at: https://docs.google.com/spreadsheets/d/1xZMuR5OLRRIRWyIJicIqr6znDAaaJUqaOhgLX8qWgJI/edit#gid=0) |
Thank you @rohanbanerjee , I will review ASAP and I think it would be good if @MerveKaptan also had a look, so we can then find a consensus |
I suggest we all generate a
Then, revisit cases with ❌ and fix the mask in the problematic slices. If the data is of insufficient quality in some slices, then do not segment those slices. |
Number of experts per subject:
|
Started doing the QC from see #25 (comment) for updated report |
Additional comments:
Here is my report on the full dataset: qc_JulienCohen-Adad_20231127_172353.zip |
There are two more datasets that need to be reviewed which were not included in the provided QC above. These two datasets are |
|
Closing this issue as all the ground truths have been reviewed. The predictions/manual correction for each active learning training iteration would be discussed in separate issues. |
Keeping track of all the artifacts subjects in the yml file below: Cross-ref the comments: |
This is not the right location for this. This issue is called "Systematic review of binary ground truth quality". This tracking needs to go in a specific issue, eg: "Tracking images with artifacts". Moreover, the |
Done in issue #46 |
Closing this issue as all the purpose of this issue is solved now. |
In anticipation of #24, I would like the team to review all GT segmentations for this project. To ease the review, I suggest we make a single QC report for the entire dataset and post it here so we can discuss. Make sure to add the SHA of the data used to create the report.
Related to: #22 #13
The text was updated successfully, but these errors were encountered: