Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposed changes to battery #68

Open
1 task
vsoch opened this issue May 7, 2017 · 0 comments
Open
1 task

proposed changes to battery #68

vsoch opened this issue May 7, 2017 · 0 comments

Comments

@vsoch
Copy link
Member

vsoch commented May 7, 2017

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:

  • work toward removing expfactory-battery dependency entirely
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant