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

Revisions №61000

branch: master 「№61000」
Commited by: Rocco Moretti
GitHub commit link: 「56cd6b218e5564ec」 「№4308」
Difference from previous tested commit:  code diff
Commit date: 2019-10-22 11:34:59
linux.clang linux.gcc linux.srlz mac.clang
debug
release
unit
PyRosetta4.notebook linux.clang.cxx11thread.serialization.python37.PyRosetta4.unit linux.gcc.python36.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.tensorflow integration.thread integration performance profile release.PyRosetta4.Release release.source scientific.enzyme_design scientific.mp_relax.debug scientific.mp_relax 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 #4308 from RosettaCommons/roccomoretti/reorganize_rosettascript_handling Reorganize RosettaScriptsParser tag handling. RosettaScriptsParser::generate_mover_for_protocol() was a bit of a muddle. Break out the detailed handling into sub-functions. Also, iterate through the subtags once, in order, rather than in multiple stages. * This may cause issues for some existing RosettaScripts, which (incorrectly) rely on having sections like RESIDUE_SELECTORS or SCOREFUNCTIONS _after_ the mover/filter section which use them. These should be rare, and can be fixed by reordering the tags. (Remembering you can repeat sections.)

...
Test: linux.clang.zeromq.build.debug

 View log

Loading...

 View log in dialog  View log in log in separate window