Skip to content

Maintain residue numbers from a pre-build model & phosphoresidue modification #57

@TueRens

Description

@TueRens

First of all, thanks so much for building the software, it is truly excellent.

I have two problems I run into where I could use your help, if this is even possible:

  1. If you start from a pre-build PDB-file where only a couple of residues are missing, is it possible to maintain the residue numbering from the original PDB file?
  2. I have a complex with a protein (all normal AAs), a peptide (containing normal AAs and one phosphorylated residue) and a ligand (three-letter code XXX). For some reason, if I use the contents.json file below (I changed the protein sequences), it does build the first protein just normally. However, it doesn't recognize the second protein (which is the peptide) and builds all alanine residues for this stretch, labeling them as UNK. In the pre-build model, the phosphoresidue, along with some normal residues flanking it, is already build in. Strangely, when I use the FASTA approach, all is fine. However, I don't think there is a way to apply the modification in that case. I'm not even sure if the phosphorylation is possible using modelcraft. I prefer to use the json approach, since it gives more control. Any advise?

Here is the representative contents.json:

`{
    "copies": 1,
    "proteins": [
        {
            "sequence": "THISISARANDOMSEQUENCETHATIJUSTCAMEUPWITH",
            "stoichiometry": 1,
            "modifications": [],
        },
        {
            "sequence": "ANDSOHEREISANOTHERONE",
            "stoichiometry": 1,
            "modifications": ["4->SEP"],
        }
    ],
    "rnas": [],
    "dnas": [],
    "carbs": [],
    "ligands": [
        {
            "code": "XXX",
            "stoichiometry": 1
        }
    ],
    "buffers": [
        "NA",
        "MG",
        "CL"
    ],
    "smiles": {}
}`

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions