-
Notifications
You must be signed in to change notification settings - Fork 417
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
DragMap fails if --trim_fastq flag is enabled #1445
Comments
What version are you running? Can you send the error message? there are several issues with dragmap that were never resolved: Illumina/DRAGMAP#47 |
The error is: line 8: 115 Segmentation fault (core dumped) dragen-os -r dragmap --num-threads 12 -1 0002.11718FA_1.fastp.fastq.gz -2 0002.11718FA_2.fastp.fastq.gz --output-directory output --output-file-prefix 11718FA 2> 11718FA.dragmap.log and I am using dragmap version: pulled from |
Can you confirm it works without the |
Yes I tried multiple times, and when i added --trim_fastq it failed. Sarek by default put the arguments However, "--disable_adapter_trimming" to me is apparently in conflicts with "--detect_adapter_for_pe " which is written inside the module. |
This issue persists as of version 3.4.3. Related: Illumina/DRAGMAP#11 In my case, specifying any of Since dragmap does not seem to be actively maintained at the moment, but there is an issue in place to replace it with a better maintained fork #1358, I suggest putting a warning into the parameter docstrings of |
Description of the bug
Good evening,
I am experiencing problems with Sarek's pipeline. When I try to remove the adapters from my WES data, the dragmap tool runs into "Segmentation Fault".
Do you have any idea what the problem might be?
Command line:
nextflow run main.nf
--input sample_sheet_3.csv
--genome GATK.GRCh38
--aligner dragmap
--save_output_as_bam
--step mapping
--outdir './results'
--save_output_as_bam
--wes false
-resume
-profile aws
--trim_fastq
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: