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
FLAIR does not read the bam, it reads the bed, which cannot contain information about supplementary alignments
We can always add extra columns to the BED. With bigBed, such
BEDs can even be view in the browser.
This is referring to flair align dofiltering(), which is filtering and
writing a new BAM. It would be nice to not create two BAMs. Junk such,
as internal primed reads could be tossed in the minimap2 -> samtools
pipeline without writing to disk. Supplemental reads, which are useful
for understanding the alignment can be kept without the need to create
another BAM.
FLAIR only looking at the BED is even better, it could either discard
the supplemental reads when creating the BED or flag them in the BED.
It would be nice to be able to run flair fusion without redoing
an alignment.
cafelton ***@***.***> writes:
cafelton left a comment (BrooksLabUCSC/flair#426)
FLAIR does not read the bam, it reads the bed, which cannot contain information about supplementary alignments
--
Reply to this email directly or view it on GitHub:
#426 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Supplementary alignments are very useful in understanding issues with the primary alignment while they can cause FLAIR to create spurious models.
It would be good to leave these in the filtered BAM, and have FLAIR discard the supplementary alignments when it is reading the BAM
The text was updated successfully, but these errors were encountered: