The need for the "battery" arose because I was essentially removing Ian's hard coded experiments from their base, the skeleton that is called the "battery."
Battery
What is a battery?
A battery is (still) a collection of experiments, but it really corresponds with a set of experiments and a desired deployment environment. As we have it now, we are hard coding common scripts and templates into expfactory-battery, holding an expectation about the experiment format, running, etc. This is a bad strategy, because it means that the experiments are dependent on the battery, can't be run without it, and you run into trouble with experiments having different dependencies (and needing to be served together). Thus, my proposal is that this battery component is entirely removed. The dependencies for each experiment must live with the experiment to make it reproducible. Any "plugging in" of something to a template should live with singularity-python. Thus my proposal is:
The need for the "battery" arose because I was essentially removing Ian's hard coded experiments from their base, the skeleton that is called the "battery."
Battery
What is a battery?
A battery is (still) a collection of experiments, but it really corresponds with a set of experiments and a desired deployment environment. As we have it now, we are hard coding common scripts and templates into
expfactory-battery, holding an expectation about the experiment format, running, etc. This is a bad strategy, because it means that the experiments are dependent on the battery, can't be run without it, and you run into trouble with experiments having different dependencies (and needing to be served together). Thus, my proposal is that this battery component is entirely removed. The dependencies for each experiment must live with the experiment to make it reproducible. Any "plugging in" of something to a template should live with singularity-python. Thus my proposal is: