Skip to content
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

Merged
merged 5 commits into from
Aug 7, 2023

Conversation

uramirez8707
Copy link
Contributor

Description

  1. Makes diag_fields public to be consistent with diag_files
  2. Converts fms_diag_output_buffer_create_container to a subroutine with intent(inout) (other members of the buffer objects are set somewhere else and if it is a function they will get deleted)
  3. Fixes allocate_diag_field_output_buffers
  4. Adds the calls allocate_diag_field_output_buffers

Fixes # (issue)

How Has This Been Tested?
CI

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules
  • New check tests, if applicable, are included
  • make distcheck passes

@@ -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
Copy link
Member

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.

Copy link
Contributor Author

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

@rem1776 rem1776 merged commit 07ec8cf into NOAA-GFDL:dmUpdate Aug 7, 2023
27 checks passed
rem1776 pushed a commit to rem1776/FMS that referenced this pull request May 1, 2024
rem1776 pushed a commit to rem1776/FMS that referenced this pull request May 1, 2024
rem1776 pushed a commit to rem1776/FMS that referenced this pull request May 1, 2024
rem1776 pushed a commit to rem1776/FMS that referenced this pull request May 1, 2024
rem1776 pushed a commit to rem1776/FMS that referenced this pull request May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants