-
Notifications
You must be signed in to change notification settings - Fork 43
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
BulkRNASeq workflow should determine adaptor type automatically #20
Comments
Potential route using within trim_galore adaptor auto-detection: |
I'll try using auto-detect by omitting the flag, will of course validate if the auto detect is consistent with direct user supply of the parameter. |
Testing Results using GLDS-426_Truncated (Known to have Nextera adapters): CURRENT (With --illumina)
With --nextera instead of --illumina
With neither --nextera nor --illumina (i.e. autodetect mode)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently workflow user is expected to replace this value manually in workflow module file.
Instead, the adaptor should be automatically determine, perhaps from the raw fastQC reports/multiQC and supplied to the trimming processing.
DPPD Reference
GeneLab_Data_Processing/RNAseq/Pipeline_GL-DPPD-7101_Versions/GL-DPPD-7101-F.md
Line 207 in 0fe1dfd
Workflow Reference
GeneLab_Data_Processing/RNAseq/Workflow_Documentation/NF_RCP-F/workflow_code/modules/quality.nf
Lines 73 to 76 in 0fe1dfd
The text was updated successfully, but these errors were encountered: