-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix participants age for tokyoSkyra site #96
Conversation
you need to trace it back because we need to make sure:
so please, go back in time, look for emails, etc. document as much as possible. This is a very serious issue and we have a responsibility to not disseminate fake results. |
e.g.: the tokyoIngenia values are also suspicious:
|
I checked in all my emails. I could only find demographics for Juntendo. I think we received the data already converted to nifti. In the email conversation with @jcohenadad with the subject In the changes files, we don't have all the history of changes (the one from openeuro). I don't know who added the data to the dataset. |
This error seemed to be in the initial commit on openneuro https://github.com/OpenNeuroDatasets/ds002902 |
sorry for the oversight-- the answer is: no, we don't have the raw data
me neither |
OK, we know these are the same subjects. So the last sanity check is to verify that the sub01 on tokyoIngenia corresponds to sub01 on tokyoSkyra, etc. @alexfoias can you please do that (look at the T1w MRIs and you will easily find out if these are the same subjects) |
I did a visual checkout and the subjects seem to be correctly identified (similar anatomy for all 3 centers). |
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.
Because
we have a responsibility to not disseminate fake results.
this entire discussion needs to be summarized into the commit message before this is merged. Maybe even expanded, not summarized: include email addresses, institution names, URLs, dates, explanations, everything to explain where the error came from, how it was resolved.
That's the big benefit of using git diligently -- so that future us can trace back what happened to a dataset, and why.
Hey, I fixed CI, so now we can actually talk about reviewing this properly.
Also, this is probably worth a different issue, but:
|
yes ( i thought we already did it @alexfoias ?)
sorry i don't understand your suggestion-- what do you mean by "data from the same physical people"? |
🤦 you're right. Okay, punting: OpenNeuroOrg/openneuro#2484
By the way does anyone else have that credential? Does Julien? Should I? Better yet, can we make a Team on openneuro and all have our own credentials instead? Or are we giving up on OpenNeuro entirely? |
The older version is off OpenNeuro for good now: OpenNeuroOrg/openneuro#2484
-> #102
And all Still TODO: writing a good commit message.
@alexfoias could we see the email that inspired this PR? |
New CI bug? https://github.com/spine-generic/data-multi-subject/runs/4226501836?check_suite_focus=true#step:11:2598
Looks like maybe it's Amazon S3 having a minor outage?
The following run passed: https://github.com/spine-generic/data-multi-subject/runs/4226604983?check_suite_focus=true |
@kousu Here is the info from the email: Subject01 M 36 177cm 70kg |
@alexfoias can you please update this PR after #112 |
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.
The values are the ones transferred by the collaborator.
Updated the information based on the information from our collaborators.
I tried to trace back when did the issue appear, but it was impossible due to the various changes in infrastructure.