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

Annotating controls #260

Closed
seanhatton opened this issue Jan 13, 2025 · 4 comments
Closed

Annotating controls #260

seanhatton opened this issue Jan 13, 2025 · 4 comments
Labels
flag:check Issue needs attention before further action

Comments

@seanhatton
Copy link

Description

I need guidance on coding diagnoses. In https://neurobagel.org/user_guide/annotation_tool/ "Sex and Diagnosis rows (categorical values)" I want to add a diagnosis column to the participant.tsv, just asking:

Do we code "controls" as "controls", "healthy" etc? Is there a list of diagnoses so I choose the right category (e.g. depression, MMD, bipolar II0)

Relevant documentation pages

No response

Additional details

No response

@alyssadai alyssadai added flag:schedule Flag issue that should go on the roadmap or backlog. flag:discuss Flag issue that needs to be discussed before it can be implemented. and removed flag:schedule Flag issue that should go on the roadmap or backlog. labels Jan 14, 2025
@alyssadai
Copy link
Contributor

Hi @seanhatton, thanks for the question!

The annotation tool is currently undergoing a major refactor, so the usage instructions and screenshots are a little out of date. We will add a note about this refactor to the docs and the README shortly.

That said, we currently expect labels for healthy controls and specific diagnoses to be in the same column(s) in an input phenotypic TSV. For an example, see the pheno_group column in example_synthetic.tsv and its corresponding annotation in example_synthetic.json from the neurobagel_examples repo.

In the annotation tool, after mapping a column to "Diagnosis", you can annotate individual values in the column as encoding healthy controls by selecting "Healthy Control" in the diagnosis dropdown or using the "Mark as healthy control" button.
Image

Hope this helps!

@alyssadai alyssadai removed the flag:discuss Flag issue that needs to be discussed before it can be implemented. label Jan 16, 2025
@alyssadai
Copy link
Contributor

Duplicate of #225

@alyssadai
Copy link
Contributor

@seanhatton, if I answered your questions, mind closing this issue?

@alyssadai alyssadai added the flag:check Issue needs attention before further action label Jan 17, 2025
@seanhatton
Copy link
Author

Thank you for the insight!

@github-project-automation github-project-automation bot moved this to Review - Done in Neurobagel Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag:check Issue needs attention before further action
Projects
Status: Review - Done
Development

No branches or pull requests

2 participants