Skip to content

[refactor] Allow full RunOptions to be specified in trainer configuration YAML #3815

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

Merged
merged 45 commits into from
Apr 30, 2020

Conversation

ervteng
Copy link
Contributor

@ervteng ervteng commented Apr 21, 2020

Proposed change(s)

Rather than have the YAML stored as part of RunOptions, make the YAML a representation of RunOptions, including engine options and other parameters. Anything not specified in the YAML config will be set to the default values; anything specified in the CLI will override values found in the YAML.

This removes the need for a separate run_experiment entry point.

Types of change(s)

  • Bug fix
  • New feature
  • Code refactor
  • Breaking change
  • Documentation update
  • Other (please describe)

Checklist

  • Added tests that prove my fix is effective or that my feature works
  • Updated the changelog (if applicable)
  • Updated the documentation (if applicable)
  • Updated the migration guide (if applicable)

Other comments

@ervteng ervteng requested a review from harperj April 21, 2020 00:45
@ervteng ervteng changed the base branch from develop-single-config to master April 29, 2020 23:27
@ervteng ervteng merged commit 383de98 into master Apr 30, 2020
@delete-merged-branch delete-merged-branch bot deleted the develop-default-overrides branch April 30, 2020 00:11
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants