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

Revisions №61097

branch: master 「№61097」
Commited by: Rocco Moretti
GitHub commit link: 「2572a9b7963894ba」 「№4372」
Difference from previous tested commit:  code diff
Commit date: 2020-01-10 18:32:32
linux.clang linux.gcc linux.srlz mac.clang
PyRosetta4.notebook gcc-9.gcc.python37.PyRosetta4.unit linux.clang.cxx11thread.serialization.python37.PyRosetta4.unit linux.gcc.python36.PyRosetta4.unit mac.PyRosetta.unit build.clean.debug cppcheck alpine.gcc.build.debug gcc-9.gcc.build.debug 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 build.ninja_debug graphics static linux.ui mac.ui build.xcode beautification code_quality.clang_analysis serialization code_quality.submodule_regression integration.mpi integration.release_debug integration.tensorflow integration.thread integration performance profile release.source scientific.ligand_docking.debug 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 gcc-9.gcc.unit util.apps

Merge pull request #4372 from RosettaCommons/roccomoretti/no_chain_back_and_forth Defer chain parsing to apply time in ligand docking movers. Some of the ligand docking movers were doing chain parsing in the parse_my_tag function, versus waiting until apply time. Not only does this cause issues if the structure of the pose changes between parse time and apply time, there was a fair bit of back-and-forth (e.g. chain letter->chain id->chain letter) that can be avoided.

Test: linux.clang.build.cppcheck

 View log


 View log in dialog  View log in log in separate window
Test: linux.clang.performance

Failed sub-tests (click for more details):