NCAR / NCAR/DART

domain mismatch error message for CLM-DART

Open
#560 0 comments 0 reactions 1 assignee View on GitHub

@braczka is already working on this.

Since Dec 7, 2023.

Minor
Dominant language
Fortran
Stars
263
Forks
182
Avg merge
11d 12h
Merged PRs (30d)
7

Description

Describe the bug
  1. List the steps someone needs to take to reproduce the bug.
    When executing filter_restart within an CLM-DART assimilation a user can get a start+count exceeds dimension bound error if the number of domains specified within the &model_nml: ( 3 possible: restart, history and vector) is different than what is defined within the &fill_inflation_restart_nml:
    ..
    ..
    input_state_files = 'clm_restart.nc','clm_history.nc','clm_vector_history.nc'

and/or the &filter_nml:
..
..
input_state_file_list = 'restart_files.txt',
'history_files.txt',
'vector_files.txt'
output_state_file_list = 'restart_files.txt',
'history_files.txt',
'vector_files.txt'

  1. What was the expected outcome?
    An error or warning is definitely needed here, but the current error message is not very intuitive. Needs
    something that directs the user to check for domain consistency.

  2. What actually happened?
    See error message example below:

Error Message

An example when only restart and history domain variables are needed in &model_nml, but user
does not update the &fill_inflation_restart_nml or the &filter_nml settings:

fill_inflation_restart: - Reading File : clm_restart.nc
fill_inflation_restart: - Reading File : clm_history.nc
ERROR FROM:
source : netcdf_utilities_mod.f90
routine: read_variables: nf90_get_var
message: TLAI: NetCDF: Start+count exceeds dimension bound
message: ...

Which model(s) are you working with?

CLM

Version of DART

Which version of DART are you using?
latest

Have you modified the DART code?

No

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.