-
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
🔧 Fix FASTQ Bug #58
🔧 Fix FASTQ Bug #58
Conversation
🔨 added sam attrs input
📝 added guidance for mulitple RGs
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.
Mostly good, but I think we should do one more quick enhancement while we're looking at this.
docs/10X_STAR_Solo_alignment.md
Outdated
@@ -31,7 +31,8 @@ They can also be obtained from the following sources: | |||
- `r2_max_len`: Set read2 to a fixed length. Useful for single cell experiments in which the number of cycles was improperly configured during sequencing. Recommend `91` for 10X v3 chemistry | |||
|
|||
### STAR Solo | |||
- `outSAMattrRGline`: Set if outputting bam, with TABS SEPARATING THE TAGS, format is: ID:sample_name LB:aliquot_id PL:platform SM:BSID for example ID:7316-242 LB:750189 PL:ILLUMINA SM:BS_W72364MN | |||
- `outSAMattrRGline`: Set if outputting bam, with TABS SEPARATING THE TAGS, format is: ID:sample_name LB:aliquot_id PL:platform SM:BSID for example `ID:HFWFVDMXX.L001 LB:750189 PL:ILLUMINA SM:BS_W72364MN`. If more than one fastq pair in input, it is recommended to have one read group per pair, separated by space-comma-space (` , `) |
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.
I think we should make this a list input since BixOps seems to prefer that approach.
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.
Description
A recent update to add a scatter job of cutadapt to fix lengths of inputs introduced a bug in which if a user does not provide lengths to fix, the workflow does not pass the correct input to STAR causing failure. This replaces pickValue with a valueFrom to better asses a [null, null] evaluation. Als,o more for added functionality, is the read group name input in the rare event a user wants to keep the bam output
Fixes # https://d3b.atlassian.net/browse/BIXU-3795
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Configuration:
Checklist: