ERROR: unrecognized atomtype property VIRTUAL

Member Site Forums Rosetta 3 Rosetta 3 – General ERROR: unrecognized atomtype property VIRTUAL

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

        Hello,
        I have built Rosetta3.3 using gcc-4.3 which went smoothly without errors. While running any rosetta script(xml file) using rosetta_scripts.linuxgccrelease, i am getting the error ‘unrecognized atomtype property VIRTUAL’. When the same script is run using rosetta_scripts.linuxgccdebug, the error doesn’t occur. Please suggest me the solution for this error. Following is the error i am getting.
        ##BEGIN ERROR MSG##

        protocols.jd2.PDBJobInputter: PDBJobInputter::pose_from_job

        ERROR: unrecognized atomtype property VIRTUAL
        ERROR:: Exit from: src/core/chemical/AtomType.cc line: 108

        ##END ERROR MSG##

        This is the command i used to run the script ala_scan.xml (given in the example in documentation).
        ##COMMAND BEGIN##

        rosetta_scripts.linuxgccrelease -s 11GS_input.pdb -use_input_sc -nstruct 20 -jd2:ntrials 2 -database $ROSETTADB -ex1 -ex2 -parser:protocol ala_scan.xml

        ##COMMAND END##

      • #6258
        Anonymous

          It strikes me as weird that it says “Exit from: src/core/chemical/AtomType.cc line: 108” – my copy of 3.3 has that exit command at line 133, not 108. Try clearing and recompiling your release mode and tell me if it sticks (and if that number stays the same). You can also do “grep -n VIRTUAL src/core/chemical/AtomType.cc”, which should return line 124:

          15:00:21 somarriba ~/LOCAL/rosetta-3.3/rosetta_source> grep -n VIRTUAL src/core/chemical/AtomType.cc
          124: } else if(property == “VIRTUAL”){ //is the atom type virtual? defined in atom_properties.txt

          I assume you haven’t modified either the code or the database any?

        • #6259
          Anonymous

            I’m thinking there some code/database version mismatch, or there was some error in compiling.

            I’d recommend getting a fresh copy of the code and database for Rosetta3.3, reinstall and recompile, and make sure your $ROSETTADB environment variable is pointing to the correct Rosetta3.3 database.

          • #6261
            Anonymous

              Thanks a lot! The version of the database i was uisng was different from the executables i had built. By mistake i was using rosetta 3.2 build with database version 3.3.

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