You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that there are changes from dev1 to dev2 when it comes to info file. Please confirm.
First in the older version, the reads that were untrimmed were not reported in the info file, but with the new version, the untrimmed reads are reported in the info file where the second column has a value of -1. That is not really an issue, but the issue is that now it it not reporting the reads that are cleaved by both long and short adapters clearly, for e.g.
I have to get some counts and it is very difficult to find which reads are cleaved by both and which ones are uniquely cleaved by one or the other adapter.
Thanks,
Komal
The text was updated successfully, but these errors were encountered:
komalsrathi
changed the title
Issue with cutadapt 1.9.dev2 when using multiple adapters
Issue in the Info file with cutadapt 1.9.dev2 when using multiple adapters
Jul 23, 2015
You are right. When I added the lines with the -1 to fix issue #95, I also changed the output inadvertently to the one you are seeing now, where you cannot get proper statistics from it. I have no time to fix this right now, but I have prepared a Git branch for you that includes the fix for the issue #137 that you reported, but not the changes to the info file. The branch is called 'nohang'. It seems you are familiar with Git, but just in case you don’t know how to get the branch: Just run git pull and then git checkout nohang in your current copy of the repository. I have changed the version number in that branch to 1.9.dev3.
No worries, I had a zip file for dev1 and I will just go back to the previous version as using compressed files in the output are anyway taking longer than using uncompressed files. Thanks!
Hi,
This is my command:
I noticed that there are changes from dev1 to dev2 when it comes to info file. Please confirm.
First in the older version, the reads that were untrimmed were not reported in the info file, but with the new version, the untrimmed reads are reported in the info file where the second column has a value of -1. That is not really an issue, but the issue is that now it it not reporting the reads that are cleaved by both long and short adapters clearly, for e.g.
In the fasta file:
So, the read has been cleaved like this:
But in the info file:
So as you can see, it should report both long_adpt and short_adpt in the info file, whereas it reports only one of the two adapters.
I also have an example where I used dev1 and dev2 and generated info files:
I have to get some counts and it is very difficult to find which reads are cleaved by both and which ones are uniquely cleaved by one or the other adapter.
Thanks,
Komal
The text was updated successfully, but these errors were encountered: