-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error in rule merge_kmers for the test. #27
Comments
Hi @akcorut and happy new year! Here is my suggestion, could you add a function that export all the processes into a bash file? for example, if I used the same test,
it will generate a bash file and we could run this pipeline by single run as Moreover, could you combine all these required environments into a single conda yaml? Lan |
Hello @akcorut, Bumping this thread because I'm also experiencing the same issue with a test run on the ecoli dataset. I tried running it with Dry run performs correctly. @Orz-CQ, did you ever solve the issue, yourself? I'm also attaching the full log file Thanks in advance for your help!
|
Hello! I ran into the same issue and was wondering anyone solved this issue yet? |
The error comes from the kmer GWAS code found here https://github.com/voichek/kmersGWAS/blob/master/src/kmers_add_strand_information.cpp. In the kmer GWAS manual it clearly says to run the non-canonized with When I'm looking at the log files for the preceding steps it seems like in the cases where I'm getting these errors, not all reads have been processed for the non-canonical step. If I run To me this is worrying. Why is the non-canonical step marked as complete when not all reads are processed? Could this lead to hard-to-detect errors where enough - but not all - reads are processed? EDIT: I just went back to my log files and verified that I have cases where not all reads are processed in the canonical step, but the pipeline still runs. You probably want to take a look at this @akcorut. |
It turns out that KMC may not process all reads when the number of threads is limited. I've submitted an issue with KMC here refresh-bio/KMC#235. |
Hello there :) Thanks for using KMC, I responded in the created issue. In this specific case (I mean the issue posted on kmc repo) the cause is in ill-formed input fastq file (at least for one file its true, I have not checked remaining but I guess this is the same case). I would like to point that its not that KMC may not process all reads, its actually more like "undefined behaviour", so for example it is possible that not only reads are missing, but that some other parts of file are treaten as reads etc. Best |
Thanks a ton for looking closer at this, @marekkokot ! I should have looked at the test data before submitting an issue with KMC. I just ran the pipeline using the SRA data for the E. coli example, and did not encounter this issue. I had some issues getting the data to download correctly from SRA however, maybe that was the reason for @brunacama93 getting this error with the E. coli dataset? |
Hi @akcorut,
The errors occurred while I am testing this workflow by
kgwasflow test -t 5 --conda-frontend mamba
The error log from snakemake is
While I also tested the single code line
scripts/external/kmers_gwas/bin/kmers_add_strand_information -c results/kmers_count/individual_53/output_kmc_canon -n results/kmers_count/individual_53/output_kmc_all -k 25 -o results/kmers_count/individual_53/kmers_with_strand
it return
Could you give me some suggestions?
The text was updated successfully, but these errors were encountered: