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

read in all possible constituents from file, not just build-time ones #301

Open
wants to merge 5 commits into
base: development
Choose a base branch
from

Conversation

peverwhee
Copy link
Collaborator

Tag name (required for release branches):
Originator(s): peverwhee

Summary (include the keyword ['closes', 'fixes', 'resolves'] and issue number):

  • Updates to enable reading in data for runtime constituents

Describe any changes made to build system:
M cime_config/cam_autogen.py
M cime_config/cam_build_cache.py
M cime_config/cam_config.py

  • keep track of registry constituents

Describe any changes made to the namelist: None

List any changes to the defaults for the input datasets (e.g. boundary datasets): None

List all files eliminated and why: None

List all files added and what they do: None

List all existing files that have been modified, and describe the changes:
(Helpful git command: git diff --name-status development...<your_branch_name>)
M src/data/generate_registry_data.py

  • create list of registry constituents to pass to write_init_files
    M src/data/write_init_files.py
  • handle constituents separately from other host variables; read/check ALL constituent variables, not just "required" ones
    M test/unit/test_*.py
  • update calling lists

If there are new failures (compare to the test/existing-test-failures.txt file),
have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?

derecho/intel/aux_sima:

derecho/gnu/aux_sima:

If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:

CAM-SIMA date used for the baseline comparison tests if different than latest:

Copy link
Collaborator

@nusbaume nusbaume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but did have a few questions!

@@ -550,6 +573,17 @@ def write_ic_arrays(outfile, ic_name_dict, ic_max_len,
#Write line to file:
outfile.write(log_arr_str, 2)
# end for
for var_num, var_name in enumerate(registry_constituents):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to reset arr_suffix to ", &" before this loop starts?

@@ -579,6 +612,16 @@ def write_ic_arrays(outfile, ic_name_dict, ic_max_len,
#Write line to file:
outfile.write(log_arr_str, 2)
# end for
for var_num, varname in enumerate(registry_constituents):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question here. Do we need to reset arr_suffix to ", &" before this loop starts?

outfile.write("write(iulog,*) 'Constituent ', trim(std_name), ' initialized to default value: ', constituent_default_value", 6)
outfile.write("end if", 5)
outfile.write("else", 4)
outfile.write("field_data_ptr(:,:,constituent_idx) = 0._kind_phys", 5)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we initialize to the constituent minimum value instead of zero?

outfile.write("var_found = .false.", 3)
outfile.comment("Check if constituent standard name in registered SIMA standard names list:", 3)
outfile.write("call const_props(constituent_idx)%standard_name(std_name)", 3)
outfile.write("if(any(phys_var_stdnames == trim(std_name))) then", 3)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there going to be any issues with the fact that the phys_var_stdnames entries aren't trimmed here? The same question holds for the other if(any(phys_var_stdnames check below as well.

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.

2 participants