-
Notifications
You must be signed in to change notification settings - Fork 134
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
Calls allocate_diag_field_output_buffers #1314
Conversation
…d setter functions)
…tions to get it to work
@@ -226,7 +226,7 @@ module fms_diag_yaml_mod | |||
character(len=:), allocatable, private :: diag_title !< Experiment name | |||
integer, private, dimension (basedate_size) :: diag_basedate !< basedate array | |||
type(diagYamlFiles_type), allocatable, public, dimension (:) :: diag_files!< History file info | |||
type(diagYamlFilesVar_type), allocatable, private, dimension (:) :: diag_fields !< Diag fields info | |||
type(diagYamlFilesVar_type), allocatable, public, dimension (:) :: diag_fields !< Diag fields info |
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.
We can do this for now, but we should really try to think of something better.
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.
:/ getter functions for both, but i am lazy
Also, the yaml object should be in diag_object like all the other objects
Description
diag_fields
public to be consistent withdiag_files
fms_diag_output_buffer_create_container
to a subroutine withintent(inout)
(other members of the buffer objects are set somewhere else and if it is a function they will get deleted)allocate_diag_field_output_buffers
allocate_diag_field_output_buffers
Fixes # (issue)
How Has This Been Tested?
CI
Checklist:
make distcheck
passes