Ligand dock analysis

Member Site Forums Rosetta 3 Rosetta 3 – Applications Ligand dock analysis

  • This topic has 3 replies, 3 voices, and was last updated 12 years ago by Anonymous.
Viewing 3 reply threads
  • Author
    Posts
    • #1283
      Anonymous

        Hi all,

        I am running ligandDocking application thru rosetta_scripts app. On the documentation “Rosetta Ligand Docking with Flexible XML Protocols”, there is a paragraph addressing how to analyse the result.
        The example can be downloaded from “http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0020161” in the supplement info.
        I did exactly what it says on the example folder provided in the documentation but there is error relating to the residue type:

        ERROR: Attempting to add a residue type with name ‘CP1’ but this name is already taken.
        Please check your residue parameter files.

        ERROR:: Exit from: src/core/chemical/ResidueTypeSet.cc line: 389
        application called MPI_Abort(MPI_COMM_WORLD, 911) – process 0


        The command I gave was:

        rosetta_scripts.linuxgccrelease -database $ROSETTA_DATABASE @flags -parser:protocol extract.xml -in:file:atom_tree_diff atom_tree_diff -in:file:extra_res_fa inputs/7cpa.params

        Have I missed out anything?

        I could be simply outputting the results into score.sc and pdb files, but if I want to output like 10000 models that would be a pain. Please help~

      • #7131
        Anonymous

          The error indicates that CP1 is getting loaded twice. Is CP1.params (perhaps 7cpa.params, I don’t know) already in your @flags file? If it’s in both the flags file already and you added it on the command line, it will try to load twice and get this error. It might also be that it’s already in your database somewhere (it doesn’t appear to be in my copy of 3.4).

        • #7132
          Anonymous

            Ahhh!!! right~ it really solve the whole problem! Thanks!

          • #7133
            Anonymous

              Usually this occurs when (as mentioned above) you have the same params file specified in the flags file and on command line. If you are still struggling with this, you can attach your flags file, params file, and input PDB, and mention the version of Rosetta you are using and I can have a look at it.

          Viewing 3 reply threads
          • You must be logged in to reply to this topic.