sokrypton / sokrypton/ColabFold
Keeping included sequences constant in subsequent MSAs
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2.9k
- Forks
- 747
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Thanks for the really helpful software!
In my case, I have a fasta sequence containing personalized protein sequences derived from a biobank population. When I run colabfold_batch on this FASTA, it iteratively queries MMseqs2 server for each sequence separately. This means that the non-input sequences included in each resulting MSA are going to be a bit different, which complicates making direct comparisons with the AF2 outputs.
colabfold_batch --save-single-representations --save-pair-representations ENST00000357654.fasta af2
Is there a way I can create separate MSAs for each personalized input sequence, but still keep the non-input sequences the same?
Here is a cartoon example of what I'm trying to achieve:
Input FASTA
>ref_seq
XXXXXX
>personalized_seq1
XYXXXX
>personalized_seq2
XXX-XX
...
Output MSA for ref
>ref_seq
XXXXXX
>msa_seqA
XXXXZX
>msa_seqB
XXQXXX
...
Output MSA for personalized_seq1
>personalized_seq1
XYXXXX
>msa_seqA
XXXXZX
>msa_seqB
XXQXXX
...
Output MSA for personalized_seq2
>personalized_seq2
XXX-XX
>msa_seqA
XXXXZX
>msa_seqB
XXQXXX
...
I've tried manually editing the a3m files but can't quite figure out which sequence corresponds to my input query sequence, or whether simply replacing it with a different sequence would produce a valid new file (the new sequence can contain indels which could mess up the alignment).
Many thanks in advance!,
Brian M. Schilder, PhD
Postdoctoral Research Scientist
Simons Center for Quantitative Biology
CV | bschilder.github.io/CV/CV
LinkedIn | linkedin.com/in/brian-schilder
Lab | koo-lab.github.io
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the colabfold_batch workflow that queries the MMseqs2 server and produces the per-sequence a3m files. Inspect how FASTA queries are represented in those files; done means defining a supported workflow that preserves the same non-input sequences across outputs while handling indels correctly.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100