「view this page in B3 βῆτα server」

Revisions №60840

branch: master 「№60840」
Commited by: Rocco Moretti
GitHub commit link: 「9a323bc72ca18d3a」 「№4072」
Difference from previous tested commit:  code diff
Commit date: 2019-07-29 17:16:04
linux.clang linux.gcc linux.srlz mac.clang
linux.PyRosetta.unit linux.gcc.python37.PyRosetta4.unit mac.PyRosetta.unit build.clean.debug cppcheck mysql postgres linux.clang.python36.build.debug linux.zeromq.debug mpi mpi.serialization linux.icc.build.debug OpenCL mac.clang.python36.build.debug build.header build.levels ninja graphics static linux.ui mac.ui build.xcode beautification code_quality.clang_analysis serialization integration.mpi integration.release_debug integration.valgrind integration performance profile release.source scientific.rna_denovo_favorites linux.clang.score linux.gcc.score mac.clang.score linux.scripts.pyrosetta scripts.rosetta.parse scripts.rosetta.validate scripts.rosetta.verify linux.clang.unit.release linux.gcc.unit.release util.apps

Merge pull request #4072 from RosettaCommons/roccomoretti/component_loading_both Fix CCD component loading such that it is more complete. We're now providing the CCD for reading of arbitrary wwPDB recognized ligands, but we're doing it incompletely. Right now we have an odd system where we'll load a CCD version, but only if there isn't a Rosetta residue type which has the same three letter code. This is a bit silly, as there's a large number of Rosetta residue types with three letter codes which are not equivalent to the wwPDB residue with that three letter code, and these will obscure the CCD version. We already have a mechanism for removing CCD types that are equivalent to Rosetta types. This is the exclude_pdb_component_list.txt in the Rosetta database. (And associated facilities for -extra_res_fa etc.) If a three letter code is listed there, we don't load the CCD version. If the CCD version isn't excluded, and has the same three letter code as the (chemically non-equivalent) Rosetta version, we can load both and then let the atom name heuristic (or other such facility) pick the best residue type match. (The CCD types should come after the Rosetta types, so all else being equal, Rosetta should prefer the database version.) If, for some reason, this behavior doesn't work for you, you can always add -check_all_PDB_components false (now defaults true) to the command line, or call rtf.set_no_CCD_on_name3_match(true) in-code for your ResidueTypeFinder, and this should re-enable the old behavior. With this, I've dug through the centroid and fa_standard residue type sets, and updated their exclude_pdb_component_list.txt to be more complete.

Test: linux.gcc.integration.valgrind

Failed sub-tests (click for more details):
enzdes rna_design
Test: linux.clang.scientific.rna_denovo_favorites

 View log


 View log in dialog  View log in log in separate window