NCAR / NCAR/DART

bug: inflation files when using 'no copy back' variables

Open
#276 24 comments 0 reactions 1 assignee View on GitHub

@jlaucar is already working on this.

Since Nov 7, 2024.

Bug IO pmp state_structure
Dominant language
Fortran
Stars
263
Forks
182
Avg merge
11d 12h
Merged PRs (30d)
7

Description

🐛 Your bug may already be reported!
Please search on the issue tracker before creating a new issue.

Describe the bug

This came up when reviewing the clm documentation. Here is the section of documentation:

The ‘NO_COPY_BACK’ designation has some side effects when it comes to state-space inflation (inf_flavor 2,4 or 5 - >‘VARYING_SS_INFLATION’,’RELAXATION_TO_PRIOR_SPREAD’, or ‘ENHANCED_SS_INFLATION’ - respectively). State-space >inflation requires an inflation value for everything in the DART state. If the variable has been designated as ‘NO_COPY_BACK’ >the DART write routine (when called from filter) simply skips the variable and nothing is written. This is a problem for >inflation files that need to adapt.

The solution is to run PROGRAM fill_inflation_restart to create an initial inflation file with inflation values of 1.0 (i.e. no >inflation). fill_inflation_restart has been specially designed to output inflation values for every variable in the DART state. The >idea is to copy the input inflation file to the output inflation file name before each assimilation cycle. No new values will be >written for the variables designated ‘NO_COPY_BACK’, the original values will persist.

Error Message

not sure, but I think incorrect sized inflation files

Which model(s) are you working with?

CLM, but this would affect any model that uses 'NO COPY BACK'

Version of DART

v9.11.8

Have you modified the DART code?

No

Build information

Independent of build

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.