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

Feature request - MAAPS (Mixed Amino Acid Position Screening) tool #22

Closed
InaMBerry opened this issue May 4, 2015 · 4 comments
Closed

Comments

@InaMBerry
Copy link

I will probably be starting on a new Dengue project this fall and I would need some help with a script for the sequence data I will be using. Basically, I need to screen many Miseq sequences for occurrence of mixed amino acid positions.

Current tools for sequence analyses allow for export of a consensus sequence with mixed nucleotide positions, that is, when both A and G are found in a certain position that position is designated as R. However, when the sequence is translated into amino acids, and A in this position encodes say Gly while G encodes Pro, the exported amino acid consensus sequence will just have a ? for this mixed amino acid position. I would need a script that:

  1. Goes through the sequence and designates the mixed amino acid positions as Gly/Pro instead (that is, informs of the exact amino acid composition of this position)
  2. Counts how many mixed amino acid positions that are found in a sequence
  3. Provides me with the exact position number of the mixed positions
  4. Preferably provides information on what gene these mixed positions are found in

For this I will be providing Dengue full genome miseq nucleotide consensus sequences (using standard IUPAC codes for mixed nucleotide positions). Start will be the first Met of the coding region. Since Denv1,2,3 and 4 genes differ slightly in their positions on the genome, this will need to be taken into account for 4.

Thanks!

@necrolyte2
Copy link
Member

@demis001 Please work with @InaMBerry on this portion of bio_pieces

It will be a great introduction on how to work with travis-ci.org, readthedocs.org, coveralls.io

@demis001
Copy link
Contributor

@InaMBerry

Can you share sample data inputs and a template output you expected (some sort of table with header)? It would be nice if the inputs are from the real data.

@averagehat
Copy link
Contributor

It occurred to me that while the only examples we discussed were codons with one ambiguous base, it is also possible (correct me if I'm wrong) for a codon to have 2 or 3 ambiguous bases, i.e. ARR or RRR

@InaMBerry
Copy link
Author

Classification: UNCLASSIFIED
Caveats: NONE

That is true and we need to account for that as well.

-----Original Message-----
From: averagehat [mailto:[email protected]]
Sent: Friday, May 22, 2015 3:19 PM
To: VDBWRAIR/bio_pieces
Cc: Maljkovic Berry, Irina CTR USARMY MEDCOM WRAIR (US)
Subject: Re: [bio_pieces] Feature request - MAAPS (Mixed Amino Acid Position Screening) tool (#22)

It occurred to me that while the only examples we discussed were codons with one ambiguous base, it is also possible (correct me if I'm wrong) for a codon to have 2 or 3 ambiguous bases, i.e. ARR or RRR


Reply to this email directly or view it on GitHub #22 (comment) . https://github.com/notifications/beacon/AKlTHHlghZRtYNUQ70m_GYWwFqWwc9Yzks5oL3i-gaJpZM4EPbyx.gif

Classification: UNCLASSIFIED
Caveats: NONE

demis001 added a commit to demis001/bio_pieces that referenced this issue May 27, 2015
demis001 added a commit to demis001/bio_pieces that referenced this issue May 27, 2015
demis001 added a commit to demis001/bio_pieces that referenced this issue Jun 10, 2015
demis001 added a commit to demis001/bio_pieces that referenced this issue Jun 10, 2015
demis001 added a commit to demis001/bio_pieces that referenced this issue Jun 10, 2015
demis001 added a commit to demis001/bio_pieces that referenced this issue Jun 17, 2015
This was referenced Aug 21, 2015
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

4 participants