branch: master 「№57044」
Commited by: sarel
GitHub commit link: 「0b5140cf34509b14」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 15:47:09

Merge remote branch 'origin/master'

...


branch: master 「№57043」
Commited by: Rhiju Das
GitHub commit link: 「fcaae8c0c2a82202」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 15:06:18

further fix of bug in jump sampling for RNA denovo. output of rna_denovo filters when they are note passed. Added -extra_minimize_chi_res option to allow flexibility of ligand in RNA puzzle.

...


branch: master 「№57042」
Commited by: Kyle Barlow
GitHub commit link: 「3a708c33ddf23ab6」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 14:18:58

Added cmake Werror check to integration test

...


branch: master 「№57041」
Commited by: Rhiju Das
GitHub commit link: 「6b1556ca17c0df19」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 13:21:24

fixing bug in rna_denovo where chain_connections jumps were not sampled if connected residues were in rigid segments. big problem in rnapuzzle12 modeling!

...


branch: master 「№57040」
Commited by: Brian Weitzner
GitHub commit link: 「89295229bb75c443」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 13:07:37

Fixing a bug that can cause full atom only Docking to ignore constraints. Two integration tests change as a result of caching the constraints to the pose before converting it to the full atom representation. These tests are: 1) docking_distance_constraints 2) docking_site_constraints The scores and final coordinates of the decoys that are produced by these tests remain unchanged. I observed changes in two matcher tests that resulted from swapping HIS with HIS_D. This is a weird things that seems to occur sporadically (at least on my system), and it is unlikely that these tests will change on the test server. I wonder if there is anything we can do about that because it's not great to ignore changing integration tests. Big thanks to BK for discovering and reporting this bug.

...


branch: master 「№57039」
Commited by: gideonla
GitHub commit link: 「db014dca4f2bef34」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 08:32:19

Limited the number of allowed rotamers to pack in Splice in

...


branch: master 「№57038」
Commited by: gideonla
GitHub commit link: 「c95e5fb5458865f8」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 06:00:57

Merge branch 'master' of github.com:RosettaCommons/main

...


branch: master 「№57037」
Commited by: Kyle Barlow
GitHub commit link: 「fc50e38880f011d4」
Difference from previous tested commit:  code diff
Commit date: 2014-07-10 01:27:32

Created TrajectoryReportToDB to enable use of the features reporter system for trajectory output TrajectoryReportToDB is a child Mover of ReportToDB, meaning most of its functionality is the same as ReportToDB (e.g. any existing features reporter can be used with it). The new behavior is that the class counts how many times each pose (identified by JD2 output tag) has been "applied" in the features reporter system. A new table, "trajectory_structures_steps", keeps track of which step iteration a particular struct_id represents. Struct_ids can be grouped from the same output by using the existing tag field. The mover has also a stride option to control how often features are reported. The mover works in Rosetta Scripts, and could be particular useful as part of a parsed protocol that is called multiple times, as in the generic monte carlo mover. In the process of creating this class, I refactored some of the other database and features code, but behavior should be unchanged. I also removed SZ_MAX from core/types.hh, as it was causing an unused variable warning/error on my system, preventing compilation. This commit merges branch kylebarlow/general_dev into master Expected test changes: features: test now uses new reporter features_database_schema: new mapping table ligand_dock_script: numerical instability

...


branch: master 「№57036」
Commited by: Rhiju Das
GitHub commit link: 「073316304ccec5ad」
Difference from previous tested commit:  code diff
Commit date: 2014-07-09 21:11:53

decided to not have rna_chem_map_lores term on during fragment assembly by default, based on benchmark runs.

...


branch: master 「№57035」
Commited by: gideonla
GitHub commit link: 「e1acea1c459267ac」
Difference from previous tested commit:  code diff
Commit date: 2014-07-09 13:36:05

Added tarcer messages to Splice.cc

...


branch: master 「№57034」
Commited by: Rocco Moretti
GitHub commit link: 「d1c09aebaf1b5721」
Difference from previous tested commit:  code diff
Commit date: 2014-07-09 11:35:44

Fix signed compare errors that were breaking the build.

...


branch: master 「№57033」
Commited by: Kevin Houlihan
GitHub commit link: 「c959a80a7aa8e884」
Difference from previous tested commit:  code diff
Commit date: 2014-07-09 04:33:16

...


branch: master 「№57032」
Commited by: Rocco Moretti
GitHub commit link: 「53df8519dbc8cd35」
Difference from previous tested commit:  code diff
Commit date: 2014-07-08 20:45:34

Fix performance benchmark (ContextDependentGeometricSolEnergy) ContextDependentGeometricSolEnergy was using the HBondSet but not generating it. This results in issues when run in a Scorefunction with only those energy terms and no HBonding terms. Add cautious generation of the HBondSet in the setup function (along the lines of the HBond terms). No test changes expected.

...


branch: master 「№57031」
Commited by: Rhiju Das
GitHub commit link: 「e9323c627d01e4c6」
Difference from previous tested commit:  code diff
Commit date: 2014-07-08 18:42:08

another merge from my branch rhiju/dms_score, which introduces rna_chem_map_lores score term. This allows chemical mapping data to guide fragment assembly, and is being tested in the RNA puzzles blind trials. Integration tests show changes in KIC_refine, SnugDock, antibody_H3, and a few other tests that look like floating point deviations. This has happened to me before when I update ScoreType.hh -- I will pay attention to whether there is an effect on the test server...

...


branch: master 「№57030」
Commited by: Rocco Moretti
GitHub commit link: 「15059e4a16593b3d」
Difference from previous tested commit:  code diff
Commit date: 2014-07-08 16:44:02

Fix uninitialized variable in DdgFilter This was was giving us the intermitant DdgFilter unit test failures. No other test changes expected.

...


branch: master 「№57029」
Commited by: Andrew Leaver-Fay
GitHub commit link: 「390557fd7fa1b318」
Difference from previous tested commit:  code diff
Commit date: 2014-07-08 16:39:01

Renaming core::scoring::getScoreFunction to core::scoring::get_score_function This function violates our naming conventions, so I'm fixing it along with getScoreFunctionLegacy. Also fixing a bug in core/membrane/io/SpanFileIO.cc which was producing unit test failures.

...


< 1 .. 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 .. 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