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
problem in LoadReads #1484
Comments
I can not reproduce this bug, anyhow I will try to contact Luis Enrique. |
@temehi Did you contact the person? |
@xenigmax yes, we had a couple of conversations on the mailing list. I asked Luis Enrique to send me his fastq files to locate the problem and I am still waiting. |
@temehi Thanks here are the files that were working with previous version of seqan |
@sccluisx Are you using the latest master of seqan? On which platform you are using SeqAn? windows? Because I have tested with your fastq files (OS X and linux), and LoadReads works just fine on both systems. @cpockrandt Can you please test this on windows using the following code fragment and the files above? Thanks!
|
@temehi Works on Windows with |
Is this correct? |
@xenigmax not really, but it still works with
on OS X and linux. @cpockrandt can you please check again? |
@temehi Still works! |
@xenigmax you may close this issue as we couldn't reproduce the error. |
Hi I am retaking this project, now I have isolated the problem and know what is what triggers the bug. #include int main(int argc, char * argv[]) { And it contains seqan1.3 and seqan from the master branch I compile by new SEQAN works fine if the input files have extension .fasta however if they have the extension is *.fastq_N it shows different behaviour as was in the old SEQAN In this example r1.fasta, r2.fasta and r1.fastq_N, r2.fast1_N are the same file respectively $ g++ -g3 -std=c++14 -Iseqan-old/ bug.cpp -o bug As you can see in seqan 1.3 the reads could be loaded even if they dont have extension fasta, but in latest seqan the reads are not loaded |
From the mailing list:
The text was updated successfully, but these errors were encountered: