-
Notifications
You must be signed in to change notification settings - Fork 136
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
Field manager namelist #1412
Field manager namelist #1412
Conversation
field_manager/field_manager.F90
Outdated
@@ -829,7 +850,7 @@ end subroutine new_name | |||
!! needed within various modules. The field manager does not | |||
!! initialize any of those schemes however. It simply holds the | |||
!! information and is queried by the appropriate module. | |||
subroutine field_manager_init(nfields, table_name) | |||
subroutine field_manager_init_legacy(nfields, table_name) |
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.
I would prefer field_manager_init_field_table_original
or something like that. Legacy is not descriptive enough.
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.
renamed to read_field_table_legacy
and read_field_table_yaml
Description
Adds a namelist to specify whether or not use the yaml tables (
use_field_table_yaml
)The code crashes if
use_field_table_yaml = . true.
and are not compiling with yaml.The code crashes if both versions of the tables are present
Adds units test to test all the options
Fixes #1313
How Has This Been Tested?
CI
Checklist:
make distcheck
passes