Connor McCoy

I've been running a similar workflow, but in the shell rather than via scons. Setting the following environment variables prior to invoking `srun` works for me: ``` bash export SLURM_NTASKS=1...

For me, this `SConstruct` creates a single file and prints a single hostname when run under `salloc -n 3`: ``` python import os from bioscons.slurm import SlurmEnvironment env = os.environ.copy()...

That looks right to me (if `env` is a `SlurmEnvironment`), but you need `SLURM_NPROCS` in addition to `SLURM_NTASKS` -- `salloc` sets both.

How about bundling the HTML docs with future releases, as well? Would also be easy.

FWIW, Bio++ has some bits to deal with the event listener approach: http://biopp.univ-montp2.fr/Documents/ClassDocumentation/bpp-core/html/classbpp_1_1Parameter.html#abfdb45447531f2ded0047e5526762eee It still suffers the graph traversal problem you mention... On Fri, Dec 14, 2012 at 6:01 AM,...

I'm not sure I totally follow - would `invalid_to_new_map` be from the previous value of a parameter to the new value? Which is then filled in with all of the...

> And 1000 maps isn't all that many. > > But worst case is 1000 maps _per generation_ since we store the > predecessors, no?

At one point you brought up BEAST-style adjustable parameter move, where the size of the move is modified to generate the desired acceptance rate. That might be good to revisit...