Merge pull request #1231 from RosettaCommons/vmullig/minimizer_uninit
Fixing major uninitialized variable issue unique to lbfgs minimization
This illustrates why, when we change a convention or a Rosetta default behaviour, we REALLY need to make sure that we test the effects of the change very carefully. The switch to lbfgs as default caused a whole host of new Valgrind errors which were previously not revealed because tests were previously not invoking the lbfgs code. This, at least, should fix those issues.
Very minor trajectory changes observed (and expected) in those integration tests that were throwing Valgrind errors. These are probably associated with the first line minimization during the lbfgs minimization trajectory.