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

Revisions №60715

branch: master 「№60715」
Commited by: Brahm Yachnin
GitHub commit link: 「39a6c320681c5347」 「№3925」
Difference from previous tested commit:  code diff
Commit date: 2019-04-23 11:12:16
linux.clang linux.gcc linux.srlz mac.clang
linux.PyRosetta.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 serialization integration.mpi integration.release_debug integration performance profile release.PyRosetta4.MinSizeRel release.PyRosetta4.Release release.source linux.clang.score linux.gcc.score mac.clang.score linux.scripts.pyrosetta scripts.rosetta.parse scripts.rosetta.validate scripts.rosetta.verify unit.addsan linux.clang.unit.release linux.gcc.unit.release unit.ubsan

Merge pull request #3925 from RosettaCommons/BYachnin/fix_buns_reporter_handling The documentation and code comments for the BuriedUnsatisfiedHBonds filter loudly state that if no reporter behaviours are selected, `report_all_heavy_atom_unsats` will be set to true by default. If we actually run it this way, though, it returns 911. I've changed the default behaviour in parse_my_tag, and also in the compute function, as a fallback for PyRosetta/C++, to act as though `report_all_heavy_atom_unsats` is set to true. The ppi_v3_suiteA tests will fail. These tests were using the BUnS filter using the default settings, and getting the "911" result for the error case of now reporters being set to true. This is now corrected, with a reasonable value being output as the BUnS result. Other test failures appear to be timeouts or unstable.