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 have recently started using LeafCutter for sQTL analysis. I have used regtools to generate the junction files with the following command regtools junctions extract -a 8 -m 50 -M 500000 -s 1 $bamfile -o $bamfile.junc. The list of these junction files are then being used to generate the clusters using the following code:
The cluster counts that I get look strange as for some clusters the values are continuously zero across all of the samples. Additionally, the cluster counts seem to be varying drastically across the samples.
I have no experience with Leafcutter, so just wondering If this is normal.
Also, I looked into the BAM files within IGV and some of the clusters, where the count is zero, I can still see junction reads in IGV. I am wondering, how is that possible. I will be grateful if you can kindly help me understand what's going on.
The text was updated successfully, but these errors were encountered:
I have recently started using LeafCutter for sQTL analysis. I have used
regtools
to generate the junction files with the following commandregtools junctions extract -a 8 -m 50 -M 500000 -s 1 $bamfile -o $bamfile.junc
. The list of these junction files are then being used to generate the clusters using the following code:The cluster counts that I get look strange as for some clusters the values are continuously zero across all of the samples. Additionally, the cluster counts seem to be varying drastically across the samples.
Here is a screenshot of some of the rows
I have no experience with Leafcutter, so just wondering If this is normal.
Also, I looked into the BAM files within IGV and some of the clusters, where the count is zero, I can still see junction reads in IGV. I am wondering, how is that possible. I will be grateful if you can kindly help me understand what's going on.
The text was updated successfully, but these errors were encountered: