getting @calebgeniesse updates for swa/swm tools into master.
not too many conflicts, except with regards to rosetta_submit.py submission for clusters with SLURM (stampede, sherlock, comet). In those cases, I chose master over the branch, but left some of the swa_revival branch commands in as commented blocks.
@everyday847 @calebgeniesse let's stay in touch via pull requests about rosetta_submit.py, especially as @everyday847 babysits sherlock over the break and as we shift to sherlock2, stampede2 over 2017.
getting @calebgeniesse updates for swa/swm tools into master.
not too many conflicts, except with regards to
rosetta_submit.pysubmission for clusters with SLURM (stampede, sherlock, comet). In those cases, I chosemasterover the branch, but left some of theswa_revivalbranch commands in as commented blocks.@everyday847 @calebgeniesse let's stay in touch via pull requests about
rosetta_submit.py, especially as @everyday847 babysits sherlock over the break and as we shift to sherlock2, stampede2 over 2017.