Closed da-i closed 2 years ago
Hi @yangao07 , I saw there was the release of 1.5.2. Is that related to this issue?
Yes. I fixed this bug in v1.5.2. It's weird that I remember that I have replied to you in this thread several days ago. Anyway, please try out the new version.
Yan
No problem at all, Ive tested v1.5.2. All looks good! thanks for fixing this issue. As a side node, are you planning on adding the quality to the table output at some point? The flexibility the table output provides is amazing!
That should be an easy update. Will do that later.
Just add the Tabular with quality score output format (-f4) in TideHunter v1.5.3.
Hi Xinglab and @yangao07
Thanks for making TideHunter, awesome idea!
I've ran into an issue with using the fastq output format of Tidehunter where there are probably whitespace characters in the output of the fastq.
ive created a docker file for reproducability:
within the docker:
the input for this first example that works well is:
the command
the output is:
All fine over here, as i said before.
but when using the below dataset:
we get:
Is this a bug?
I've also noticed that sometimes the length of the quality scores are not matching with the consensus sequence. But i think that is related to the aforementioned characters.