Skip to content
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

Example datasets for bep036 #465

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

Conversation

Arshitha
Copy link

@Arshitha Arshitha commented Aug 29, 2024

Added pheno001 and pheno002 example dataset inspired by ds004215 on OpenNeuro but significantly modified to keep it simple and easy to convey the various use cases proposed in BEP036.

Use cases covered (and to be added to this PR):

  • pheno001 - Single session with both phenotype and imaging data
  • pheno002 - Two sessions with one imaging data only session
  • pheno003 - Two sessions with one phenotype data only session
  • pheno004 - Two sets of sessions. One set of sessions (e.g. screening, baseline, followup, etc) for phenotype data and another set of sessions (e.g. 01, 02, etc) for imaging data.

Still in draft state but would appreciate any and all feedback.

Pinging co-contributors: @ericearl @SamGuay @surchs

@Arshitha Arshitha marked this pull request as draft August 29, 2024 21:20
Copy link

@ericearl ericearl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, thanks! I'm guessing you left it in draft state becausew of pheno001 and pheno002, right?

I think we should remove the age_at_visit column/field from all phenotype/ measurement tools and instead provide a root-level sessions file with that field. Should we maybe take that a step farther and RECOMMEND or say it's OPTIONAL to add age to the sessions file?

@Arshitha
Copy link
Author

I like that idea. It's redundant information that can be aggregated to sessions level, and can be a recommendation in the BEP.

@Arshitha
Copy link
Author

It's in Draft state because I haven't prepared pheno003 and pheno004 but yes, all four example datasets will violate the contribution guidelines.

"f": "Female"
}
},
"age_at_visit": {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"age_at_visit": {
"age": {

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case, age_at_visit would be the same as age and that's the reason I changed it to age_at_visit.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's still fine to keep as age, but I would let @SamGuay and/or @surchs be the tie-breakers.

@@ -0,0 +1,3 @@
participant_id sex age_at_visit MRI ace demographics

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
participant_id sex age_at_visit MRI ace demographics
participant_id sex age MRI ace demographics

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as previous comment

pheno002/sessions.json Outdated Show resolved Hide resolved
pheno002/sessions.tsv Outdated Show resolved Hide resolved
pheno003/sessions.json Outdated Show resolved Hide resolved
pheno003/sessions.tsv Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants