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

Implement ConfigManager #21

Open
wessle opened this issue Nov 4, 2020 · 2 comments
Open

Implement ConfigManager #21

wessle opened this issue Nov 4, 2020 · 2 comments
Assignees

Comments

@wessle
Copy link
Owner

wessle commented Nov 4, 2020

It would be nice to have a working version of this to test with ExperimentRunner once the latter is almost done being debugged.

@DavidNKraemer DavidNKraemer reopened this Nov 5, 2020
@wessle wessle self-assigned this Nov 11, 2020
@wessle wessle changed the title Implement ConfigGenerator Implement ConfigManager Nov 16, 2020
@wessle
Copy link
Owner Author

wessle commented Nov 16, 2020

Now that we have standard YAML config file formats for specifying trials and experiments (see issue #29), we need to implement a ConfigManager that can automatically translate back and forth between the YAML config files and live ConfigTuples to be used at runtime. This is important not only so it's easier to specify experiments, but also because we need to save a copy of the corresponding trial config file alongside the results of each trial for ease of identification and replication.

@wessle
Copy link
Owner Author

wessle commented Nov 17, 2020

Progress

The experiment_runner_* scripts in the examples directory on experiments now save YAML config files alongside each trial's output.

TODO:

  • Create a ConfigManager that implements the config file parsing contained in experiment_runner_experiment_config.py
  • Use the above to hide all config file parsing from the user by putting ConfigManager inside ExperimentRunner
  • Update the ExperimentRunner drawio diagram to reflect these changes

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

2 participants