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
It looks like there's some adapters on these reads that would need to get trimmed off. I expect this could be impacting the fusion calling by STAR-Fusion.
Here's an example screenshot for the MN1 region from the STAR aligned bam file and you can see the mismatches at the very 5' end.
After doing some form of read trimming, you could give STAR-Fusion another try.
I did run these data through FusionInspector with just MN1--PATZ1 as the target, and it did find one nice read supporting this fusion. Usually we hope for more reads. It might be that both FusionInspector and STAR-Fusion will do better once the reads are cleaned up.
Thanks. I've been busy with other projects but will be addressing this shortly. It's going to be a bit of a reverse engineering job. I have the output files from the internal ArcherDx pipeline so I need to figure out how the adapters are processed.
I have some RNA Seq fusion panel data generated with ArcherDx
Description of feature
I provide some ArcherDx fusion pipeline data here:
https://drive.google.com/file/d/1Ly7WZEo732qBSobsLOVdBpzJVRRCotOn/view?usp=sharing
The specific sequencing panel is FusionPlex Pan Solid Tumor v2 18091 v1.1
Would it be possible to have some guidance on how to change the rnafusion parameters to work with this data?
It's expected for this sample to have an MN1 - PATZ1 fusion
The text was updated successfully, but these errors were encountered: