branch: master 「№56468」
Commited by: Rebecca Alford
GitHub commit link: 「89bc66c4c530c410」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 21:38:01

Disabling SpanFileIO unit test suite for now which has an instability on the mac gcc platform

...


branch: master 「№56467」
Commited by: Andrew Leaver-Fay
GitHub commit link: 「90c5d22d3889bfde」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 20:02:56

Ooops! Disabling VectorizedEtable unit test suite which is not ready for prime time.

...


branch: master 「№56466」
Commited by: Roland Pache
GitHub commit link: 「4cd4eaed30085f05」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 19:05:16

Added pilot app for scoring protein-ligand interactions. Separately for each ligand in the pose, calculates the weighted two-body interaction energy between all residues and the given ligand. The output consists of a sorted list of ligand-residue pairs and their weighted two-body interaction energies (total, as well as per score-term), with the residues that contribute most to ligand-binding listed first. No test changes expected.

...


branch: master 「№56465」
Commited by: Andrew Leaver-Fay
GitHub commit link: 「326922343a9d28f0」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 17:27:10

Merging branches master and aleaverfay/vectorize_lj: 10% speed up for the etable evaluation. I'm changing the way the etable calculates the "cubic splines" that it uses to smoothly ramp the potential when it turns off. The new code evaluates the same spline polynomials, but doesn't use the cubic-spine formulation (which requires 8 additions, 13 multiplications and 1 division) but rather a cubic-polynomial formulation (which requires 3 additions and 3 multiplications). (The branch name is deceiving: the etable calculation is not being vectorized) Numeric changes result in 89 integration test trajectory changes. However, the score-function-fingerprint benchmarks do not change.

...


branch: master 「№56464」
Commited by: Brian Weitzner
GitHub commit link: 「e4d34f23d304dddc」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 16:37:23

Updating ASCII art in a doxygen tag. No changes.

...


branch: master 「№56463」
Commited by: Sergey Lyskov
GitHub commit link: 「187e989374ec5569」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 15:47:53

Increasing timeout for integration.debug to 60 minutes

...


branch: master 「№56462」
Commited by: phbradley
GitHub commit link: 「86ca7d429a16a731」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 09:42:19

Rework the loops in symmetric precomputed rotamer-rotamer energy calculation to handle unusual setups. This change improves handling of strange symmetries where the independent monomer is not first in sequence. It also looks to reduce the memory footprint a bit, and may speed up packing, since it short-circuits rotamer-rotamer calculations if the score_multiply factor for that residue pair is 0. It does not apply to use of the linmem interaction graph, only the (default) precomputed energies interaction graph. Two unit tests (zinc homodimer and beta strand homodimer) show logfile changes since the interaction graph is now smaller.

...


branch: master 「№56461」
Commited by: rhiju
GitHub commit link: 「8785d46f3e1fac9c」
Difference from previous tested commit:  code diff
Commit date: 2014-03-07 00:23:58

Big merge from rhiju/swm_rigid_body to master. Critical last step for stepwise monte carlo of RNA -- enables identification and sampling of docking of different chunks, a generalization of 'floating_base' move in original stepwise assembly code. Integration tests for SWA/SWM change. Numerous additional bug fixes, and clean-up of enums that were triggering warnings.

...


branch: master 「№56460」
Commited by: Frank DiMaio
GitHub commit link: 「14e9498048a7aff7」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 23:59:50

Remove warnings from phenix interface code. Remove temp ifdefs from EllipsoidalRandomizationMover.

...


branch: master 「№56459」
Commited by: Frank DiMaio
GitHub commit link: 「96f81079cff0a479」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 23:34:50

Accidentally missed a file in the previous commit

...


branch: master 「№56458」
Commited by: Frank DiMaio
GitHub commit link: 「268547744a985ab3」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 23:25:56

Updating boost version from 1.46 to 1.55. Removes boost 1.46 files, adds boost 1.55 files. Updates the import header script to reflect the parts of boost we are using. Two new flags are added to the default build, BOOST_ERROR_CODE_HEADER_ONLY and BOOST_SYSTEM_NO_DEPRECATED. Much thanks to Doug. With integration tests there are 8 changes. 6 are related to boost::unordered_map: - nonideal_rtmin, mr_protocols, hybridization --- via cart_bonded - rs_loophash, match --- via the 6D hasher - sequence_tolerance There are two other integration test changes: - sweep_respair_energies -- the binary .db3 files change; not replicated on other machines - noe_assign -- due to a small bugfix

...


branch: master 「№56457」
Commited by: Rocco Moretti
GitHub commit link: 「b1603f390f31c154」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 20:13:02

Revert "Fix issues with Gasteiger atom typing" Until I can understand the test server changes. This reverts commit cab6655af046ce82e656c1c35b9fda7c7cc9fa33, reversing changes made to b3b9b5d86a4cc4253f7e3ac9aa8e3d36429a4081.

...


branch: master 「№56456」
Commited by: jadolfbr
GitHub commit link: 「62b31f8ef84ffe90」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 19:02:43

make reduce radii default sasa radii for SasaCalc2/IAM + IAM bugfixes NEWS: ====Sasa==== * Make the reduce radii the default for SasaCalc, and subsequently IAM as discussed at MiniCon2014 * Add calculation of sidechain sasa within SasaCalc, make it accessable to SasaCalculator2 pose metric ====IAM Bugfixes==== * Implement packstat bug workaround to keep IAM from crashing on pymol selection printing of packstat residues. This bug in packstat makes the per-residue values returned not equal the total number of pose residues. You see the problem. I am not sure what causes this to happen, but it may be from the SimpPDB that is used in packstat. For now, we do not want IAM to crash on output of this selection. * Fix taskfactory bug that would cause a crash on poses with interface disulfides if -pack_separated option was used. This stemmed from pose separation repack needing a new packertask due to call to detect_disulfides. ===Tests ==== All integration tests that use IAM will change values slightly.

...


branch: master 「№56455」
Commited by: Labonte
GitHub commit link: 「d64e0b2d742472b7」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 18:16:17

Warnings Removal: hopefully fixing error with command-line options in GCC 4.7

...


branch: master 「№56454」
Commited by: Rebecca Alford
GitHub commit link: 「54229ff786a2434e」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 17:46:25

RosettaMembrane Framework Updates ========================================== - Updated MembraneConformation with total polymer residue and num polymer chains - Removed unfinished scoring code - Updated protocols library level for top level movers Updated 3/6/14

...


branch: master 「№56453」
Commited by: Labonte
GitHub commit link: 「a3a1b9b99b69c78e」
Difference from previous tested commit:  code diff
Commit date: 2014-03-06 16:49:06

ResidueType: improving error messages for debugging This makes it easier to know how things failed upon loading in a pose. Former output example: ERROR: unrecognized residue: Glc New output examples: ERROR: No match found for unrecognized residue at position 3 Looking for upper-terminal residue with 3-letter code: Glc or: ERROR: No match found for unrecognized residue at position 1 Looking for lower-terminal residue with 3-letter code: Glc etc.

...


< 1 .. 343 344 345 346 347 348 349 350 351 352 353 354 >

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