Pushed Revisions

branch: master 「№58100」
Commited by: Hahnbeom Park
GitHub commit link: 「7f5e2abea1d129b9」「№759」
Difference from previous tested commit: code diff
Commit date: 2015-08-28 20:27:05

Merge pull request #759 from RosettaCommons/hpark/hahnbeom/beta Hpark/hahnbeom/beta

branch: master 「№58099」
Commited by: P. Douglas Renfrew
GitHub commit link: 「537d1e6d29a5f94e」「№722」
Difference from previous tested commit: code diff
Commit date: 2015-08-28 14:15:55

Merge pull request #722 from RosettaCommons/dougrenfrew/enable_all_ncaa_residue_types Enabling all L-NCAA residue types in residue_type.txt. This is something I have wanted to do forever and with the new on-the-fly ResidueTypeSet creation it is now possible.

branch: master 「№58098」
Commited by: Andrew Watkins
GitHub commit link: 「786d8487cc7c36dd」「№744」
Difference from previous tested commit: code diff
Commit date: 2015-08-28 10:53:18

Merge pull request #744 from RosettaCommons/everyday847/proper_protonation Our protonation states are sometimes wrong!

branch: master 「№58097」
Commited by: Vikram K. Mulligan
GitHub commit link: 「1d976f6fa9f4b69e」「№752」
Difference from previous tested commit: code diff
Commit date: 2015-08-28 01:32:26

Merge pull request #752 from RosettaCommons/vmullig/new_d_problem Trying to fix a bug in the Disulfidize mover resulting in infinite recursion when no solutions are found This seems to actually be a ParsedProtocol bug: the last_mover_ is being set, but not being reset from job to job. This results in the Disulfidize mover (derived from the MultiplePoseMover class) seeking solutions from itself in a nasty recursive way if nstruct > 1...

branch: master 「№58096」
Commited by: Tom Linsky
GitHub commit link: 「3890ab90cc5b7bf8」「№733」
Difference from previous tested commit: code diff
Commit date: 2015-08-27 21:55:22

Merge pull request #733 from RosettaCommons/tlinsky/cppcheck_fixes Fix string passed by const value identified by cppcheck

branch: master 「№58095」
Commited by: Tom Linsky
GitHub commit link: 「f4635e64d0301502」「№750」
Difference from previous tested commit: code diff
Commit date: 2015-08-27 21:54:41

Merge pull request #750 from RosettaCommons/tlinsky/duplicate_rcg_unit_test_files remove weirdly duplicated unit test files

branch: master 「№58094」
Commited by: Jeliazko Jeliazkov
GitHub commit link: 「82df5e45d8a3040e」
Difference from previous tested commit: code diff
Commit date: 2015-08-27 13:47:45

Update make_symmdef_file.pl Forgot to end the escape char before the endline char so the script was failing... not any more...

branch: master 「№58093」
Commited by: Jeliazko Jeliazkov
GitHub commit link: 「5b52c1ab7fbe675a」「№755」
Difference from previous tested commit: code diff
Commit date: 2015-08-27 13:42:14

Merge pull request #755 from RosettaCommons/lqtza/make_symmdef_file_script_read_gz Update make_symmdef_file.pl to open gzipped pdbs without error.

branch: master 「№58092」
Commited by: Vikram K. Mulligan
GitHub commit link: 「ce9f66fe1ec5438e」「№742」
Difference from previous tested commit: code diff
Commit date: 2015-08-26 16:11:57

Merge pull request #742 from RosettaCommons/vmullig/rename_triazole Renaming TRIAZOLEMER property to TRIAZOLE_LINKER. No test changes expected.

branch: master 「№58091」
Commited by: Rhiju Das
GitHub commit link: 「f26e6cb0d8ed7edf」「№737」
Difference from previous tested commit: code diff
Commit date: 2015-08-26 11:56:07

Merge pull request #737 from RosettaCommons/rhiju/fix_match_test_instability fixing Matcher test instability Sweet, now integration.release_debug (linux) and integration (mac) versions of match tests actually match, including order of output of HIS vs. HIS_D, etc. (except for a nan vs. -nan).

branch: master 「№58090」
Commited by: Andrew Watkins
GitHub commit link: 「2ad4daebf1ac800a」「№680」
Difference from previous tested commit: code diff
Commit date: 2015-08-25 18:00:03

Merge pull request #680 from RosettaCommons/everyday847/chiral_flip_patch Generate D-amino acids using patches

branch: master 「№58089」
Commited by: Caleb Geniesse
GitHub commit link: 「db49f814cfeb3b32」「№740」
Difference from previous tested commit: code diff
Commit date: 2015-08-25 14:33:28

Merge pull request #740 from RosettaCommons/calebgeniesse/cmake-dev Fix CMake Mac graphics build

branch: master 「№58088」
Commited by: Sergey Lyskov
GitHub commit link: 「8b31a732470048c2」
Difference from previous tested commit: code diff
Commit date: 2015-08-25 14:03:33

branch: master 「№58087」
Commited by: Vikram K. Mulligan
GitHub commit link: 「a19fa6a1a60627a9」「№739」
Difference from previous tested commit: code diff
Commit date: 2015-08-25 03:34:01

Merge pull request #739 from RosettaCommons/vmullig/fix_swm_tests Trying to fix failing stepwise Monte Carlo integration tests. I think I've tracked the problem down to a point at which remove_variant_type_from_residue was being passed a residue and a pose that didn't contain that residue. This was an existing issue in protocols/stepwise/modeler/util.cc that was only revealed by my recent changes. Fixed now.

branch: master 「№58086」
Commited by: Vikram K. Mulligan
GitHub commit link: 「f70cef625f09eaaf」「№738」
Difference from previous tested commit: code diff
Commit date: 2015-08-24 17:37:00

Merge pull request #738 from RosettaCommons/vmullig/require_semicolon Removing semi-colons from some macros to remedy beautifier issue Removing semi-colons from the runtime_assert, runtime_assert_msg, and runtime_assert_string_msg macros to force explicit semi-colons in the code (or compilation failure if they're missing). This is intended to help to remedy cases in which the beautifier fails due to missing semi-colons. For developers, this means that you need to have a semi-colon after a runtime_assert, runtime_assert_msg, or runtime_assert_string_msg, just as you would if you were making a function call.

branch: master 「№58085」
Commited by: Frank DiMaio
GitHub commit link: 「f386b3c664c2f04a」
Difference from previous tested commit: code diff
Commit date: 2015-08-24 14:24:56

Legend:

queued	Queued Test
queued for comparison	Test finished running but not yet compared
running	Test is Running right now
comparing	Test results is now comparing with previous results
finished	Test is finished without errors
failed	Test failed
build Failed	Test could not be run because build failed
script failed	Test results is unknow because test-script failed
canceled	Test was canceled