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

tview / ttview equivalent for protein-peptides bam #188

Open
avilella opened this issue Sep 29, 2021 · 1 comment
Open

tview / ttview equivalent for protein-peptides bam #188

avilella opened this issue Sep 29, 2021 · 1 comment

Comments

@avilella
Copy link

Subject of the issue

I have some peptides from a proteomics experiment (~5000) and I have a list of protein references that they may align to, sometimes not perfectly. I've used ncbi-blast SAM output option and a bit of datamunging to create a SAM/BAM file output of this with the use of samtools. The contents of the BAM file look good, but when I display them in samtools tview, the aminoacids in each SAM record are converted into A,C,G,T, plus ambiguity codes.

I then remembered jvarkit had a bam ttview module that produced a similar, in some aspects more rich output, than samtools tview, with some more flexibility.

Expected behaviour

Should I expect this to work? E.g. same basic behaviour as with DNA alphabet reference and NGS input, but with a protein alphabet and peptide input.

If this is beyond what jvarkit would be interested in supporting, that's perfectly understandable. There may be a non-SAM based approach to do that which is a better alternative than shoehorning proteins into the SAM/BAM toolkits out there.

Thanks in advance,

@lindenb
Copy link
Owner

lindenb commented Sep 29, 2021

E.g. same basic behaviour as with DNA alphabet reference and NGS input, but with a protein alphabet and peptide input.

Hum I doubt it will work. jvarkit uses the htsjdk lib which is quite stringent with BAM format.

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

2 participants