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

multithreading smalt error #71

Closed
lmoncla opened this issue Feb 13, 2017 · 8 comments
Closed

multithreading smalt error #71

lmoncla opened this issue Feb 13, 2017 · 8 comments

Comments

@lmoncla
Copy link

lmoncla commented Feb 13, 2017

When running IVA on full genome influenza samples and enabling multiple threads, I get the following smalt error:

smalt.c:807 ERROR: The two FASTA/FASTQ input file have different numbers of reads
[W::sam_read1] parse error at line 812880
[main_samview] truncated file.

I do not get this error if I run the same sample with a single thread.

@martinghunt
Copy link
Contributor

Could you share the input reads with me please so I can try to debug? Thanks.

@lmoncla
Copy link
Author

lmoncla commented Feb 14, 2017 via email

@martinghunt
Copy link
Contributor

Thanks. What version of IVA did you use and what was the command to run it?

@lmoncla
Copy link
Author

lmoncla commented Feb 14, 2017 via email

@martinghunt
Copy link
Contributor

I don't yet know why you didn't get the error with a single thread, but the reason for the error is that there needs to be the same number of reads in the two files. And the N^th read in each file should be mate pairs.

$ wc -l *
  1989088 6390_S23_L001_R1_001.trimmed.fastq
  1657760 6390_S23_L001_R2_001.trimmed.fastq

If you trim with trimmomatic, then you'll need to only keep the paired reads. Throw away everything else, ie when one read of a pair is removed by trimmomatic.

@lmoncla
Copy link
Author

lmoncla commented Feb 14, 2017 via email

@martinghunt
Copy link
Contributor

No, sorry but the read pair information is essential to its algorithm.

@lmoncla
Copy link
Author

lmoncla commented Feb 14, 2017 via email

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

No branches or pull requests

2 participants