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

Update vcf-expression-annotator documentation to clarify custom id-column parameter #67

Merged
merged 2 commits into from
Oct 16, 2023

Conversation

susannasiebert
Copy link
Collaborator

Closes #61

Copy link
Collaborator

@chrisamiller chrisamiller left a comment

Choose a reason for hiding this comment

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

+1 - just a minor grammar suggestion

@@ -22,16 +22,17 @@ file.

The VCF Expression Annotator also accepts a custom tab-delimited (TSV) file input for the
expression file. This TSV file will need to contain one column with gene or
transcripts identifiers and one column with the expression values. This file
transcripts Ensembl IDs and one column with the expression values. This file
Copy link
Collaborator

Choose a reason for hiding this comment

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

transcripts -> transcript

@susannasiebert susannasiebert merged commit ad6167c into master Oct 16, 2023
4 checks passed
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.

Support gene names as well as gene Ensembl IDs when using the custom option of the vcf-expression-annotator
2 participants