NCAR / NCAR/DART

bug: perfect_model_obs namelist options cause true_state.nc to be written when you don't want any state output.

Open
#907 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

🐛 🌵

Describe the bug
  1. Run perfect_model_obs
    with the following namelist options,
 write_output_state_to_file = .false.,
 single_file_out            = .true.
  1. You've set write_output_state_to_file = .false., because you don't want to write out state files because you're running perfect_model_obs to get obs_seq.out. So you think you don't have to worry what single_file_out is set to.

  2. What actually happened?

    • true_state.nc gets written - which performance wise you are not interested in writing out the state you just read in and did not change.
    • and in the case of MOM6 you get:

PE 0: p_m_o trace: Before setup for next group of observations
PE 0: p_m_o trace: Number of observations to be evaluated 49953
p_m_o trace: Time of first observation in window day=149748, sec=43275
p_m_o trace: Time of last observation in window day=149749, sec=43200
PE 0: p_m_o trace: After setup for next group of observations
PE 0: p_m_o trace: Before updating true state
PE 0: file_to_text input.nml file shape is 1133 by 243 truncating to 1133
by 129
ERROR FROM:
source : netcdf_utilities_mod.f90
routine: nc_append_time
message: put_var time: NetCDF: Not a valid data type or _FillValue type mismat
ch
message: ...

Which model(s) are you working with?

MOM6, but I think true_state.nc would get written for any model.

Version of DART

Which version of DART are you using?
v11.11.1-1-gca200df36

Have you modified the DART code?

Yes mom6-z branch because the restart files have lz (see #906)

Build information

Please describe:

  1. Derecho
  2. Intel

Also the namelist options 'single_file_out' for perfect_model_obs are confusing for users (and developers).

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.

Research direction

Start by reproducing perfect_model_obs with write_output_state_to_file = .false. and single_file_out = .true., then trace the namelist handling and output setup. The fix is done when no true_state.nc is written while obs_seq.out is still produced, including for the reported MOM6 case.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.