Open lldelisle opened 1 month ago
Thank you for this report and for providing the files to reproduce this issue.
Looking at the two BAM files I see there, it seems only the small_BAM_SR
BAM file (data 2) is triggering this issue, but not the small_BAM_PE
file (data 7), correct?
[EDIT: fixed the data #s]
Note to self & @mpertea: it seems this is related to #238 and the last version of the #357 bug, and the new development branch might have the fix for all of them. I'll work on back-porting and testing that possible fix.
Thank you for this report and for providing the files to reproduce this issue.
Looking at the two BAM files I see there, it seems only the
small_BAM_SR
BAM file (data 2) is triggering this issue, but not thesmall_BAM_PE
file (data 7), correct?[EDIT: fixed the data #s]
On the minimum example yes because I put a single gene where the coverage is below 1 for the small_BAM_SR
and above 1 for the small_BAM_PE
. So, I suspect this comes from the level of expression.
For the PE without subsetting I get (left is 2.2.1, right is 2.2.2):
If you want, I can share with you the full BAM and gtf.
Dear stringtie developer, I noticed a strong change between version 2.2.1 and 2.2.2 when I run stringtie with the -e option. It seems that all lowly expressed genes went to 0. Here is an example of output with version 2.2.1 on a small dataset:![Screenshot from 2024-06-26 09-09-16](https://github.com/gpertea/stringtie/assets/30404086/5677797d-0a69-4844-9cd3-1a656f610214)
Here is the output with the same command line but version 2.2.2:![Screenshot from 2024-06-26 09-10-48](https://github.com/gpertea/stringtie/assets/30404086/ae1d51f0-200f-4a58-b6de-cce6d7f18e62)
If you need a small dataset, I put a small BAM with reads covering a single gene and the associated gtf in usegalaxy.org.