-
Notifications
You must be signed in to change notification settings - Fork 12
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
Allow in memory manipulation of nalu yaml files #51
Conversation
1525238
to
f0cd11e
Compare
@psakievich Do we have the option to write the various nalu files for debugging purposes? Did I miss that somewhere in the PR? |
Yes it is in the regression test. |
@ashesh2512 I currently have it as But the more I think about it the more I want to make nalu just natively dump the input file into the logfile. Then you can see exactly what options were used for the run AND run the reproducer all by just having someone send you the log file. |
Allow users to overwrite entries in a single template nalu-wind yaml file for each yaml instance.
This PR allows you to specify parameters to change in all nalu-wind instance and each one individually. See the added test file for examples.
This PR only allows you to replace existing leaf nodes in the yaml graph so you can over write values, but you can not add totally new nodes to the graph i.e. add in a mesh motion if it doesn't exist in the template file.
It will change the naming convention for the log files to be
[input_file]_[index].log
when this is employed rather than[input_file].log
.I have unit-tests for this in a stand alone project. When we hook up googletest I can copy them over to the driver repo.