Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parsing of the X CIGAR code in bam files #422

Open
sanyalab opened this issue Feb 7, 2024 · 3 comments
Open

Parsing of the X CIGAR code in bam files #422

sanyalab opened this issue Feb 7, 2024 · 3 comments

Comments

@sanyalab
Copy link

sanyalab commented Feb 7, 2024

Hello,

Can agat_convert_minimap2_bam2gff.pl be modified to process the X CIGAR code in some BAM files? I have aligned IsoSeq data to genome with minimap and I have a bam file with the =/X CIGAR code. After conversion to GFF I cannot see the percent identity and coverage of the IsoSeq mRNA on the genome, like I do for a GMAP output.

Can the code be modified to handle the X CIGAR class?

Thanks
Abhijit

@Juke34
Copy link
Collaborator

Juke34 commented Feb 9, 2024

Sure, but I would need a detailed example to be sure to implement it properly

@sanyalab
Copy link
Author

Hi Jacques,

Thank you for replying and agreeing to implement. I am working on a different project for now, so closing this request temporarily. Will re-open once I have data, examples and objectives to share. Thanks

-Abhijit

@jdmontenegro
Copy link

Hi @Juke34, I'd like to reopen this thread because I just ran into the same error.
Very quickly, I generated bam files of transcripts mapped to a reference genome with minimap2. However some of the CIGAR descriptions contain an "X". I found here: (https://www.drive5.com/usearch/manual/cigar.html) that it represents a mismatch between the query and the reference, but currently the script cannot parse it. Any suggestion on how to work around it, would be more than welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants