You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to move all possible values and especially to put default values in a separate YAML file rather than specifying them manually in nengo_bones.config.fill_defaults. Such a YAML file would be a convenient place to document all of the possible things you can do in a .nengobones.yml without needing to write lots of prose, as we're currently doing in the configuration.ipynb notebook.
A few difficulties for this:
Some of the defaults are generated in Python code and thus can't be easily included in a .yml file (e.g., copyright_start is datetime.now().year).
Some things can be repeated, and have defaults within those repeated sections (e.g., each job in travis_yml can have some defaults set).
Some keys are required but do not have defaults (e.g., project_name)
These difficulties mean that the defaults.yml file might have to have some special values that we will later interpret in code, which partly defeats the purpose, but would at least be an explicit way of saying "this value has a special default" or "this value can be repeated" or "this value is required but has no default".
Alternatively, it may the case that the YAML file listing all possible keys is separate from the YAML file listing defaults. Thinking about that is giving me some XSLT vibes... and doing a bit of googling, it looks like we could perhaps replace a lot of our custom logic with jsonnet, though that would be a very big change.
The text was updated successfully, but these errors were encountered:
It would be nice to move all possible values and especially to put default values in a separate YAML file rather than specifying them manually in
nengo_bones.config.fill_defaults
. Such a YAML file would be a convenient place to document all of the possible things you can do in a.nengobones.yml
without needing to write lots of prose, as we're currently doing in theconfiguration.ipynb
notebook.A few difficulties for this:
.yml
file (e.g.,copyright_start
isdatetime.now().year
).travis_yml
can have some defaults set).project_name
)These difficulties mean that the
defaults.yml
file might have to have some special values that we will later interpret in code, which partly defeats the purpose, but would at least be an explicit way of saying "this value has a special default" or "this value can be repeated" or "this value is required but has no default".Alternatively, it may the case that the YAML file listing all possible keys is separate from the YAML file listing defaults. Thinking about that is giving me some XSLT vibes... and doing a bit of googling, it looks like we could perhaps replace a lot of our custom logic with jsonnet, though that would be a very big change.
The text was updated successfully, but these errors were encountered: