-
Notifications
You must be signed in to change notification settings - Fork 19
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
Remove hardcoded parameters, minor improvements for parameters-as-functions #2087
Conversation
f9de597
to
a62e081
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks! In general, how do we determine if some parameters (e.g. sponge) should be in the top-level struct?
For now, we can just keep adding parameters to the top level because there aren't too many. If we keep adding parameters, we should probably find better ways to break them up. |
58d15ad
to
4f1ce64
Compare
bors r+ |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Content
entr_coeff
detr_coeff
andentr_tau
from the config, makes them parametersedmfx_bomex_box_v2.toml
to include thedetr_coeff
changeforcing_tendency
, update the parameter struct accordinglySpongeParameters
- I think we can keep these in the top-level struct@eval
Note: This does not get rid of all hardcoded parameters, only the high-priority ones.