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

Inconsistent output file interval settings #339

Closed
llpcarson opened this issue Dec 18, 2020 · 1 comment · Fixed by #691
Closed

Inconsistent output file interval settings #339

llpcarson opened this issue Dec 18, 2020 · 1 comment · Fixed by #691
Labels
bug Something isn't working

Comments

@llpcarson
Copy link
Collaborator

Description

A user reported an issue with the output files while using the UFS-MRWEATHER_APP which had inconsistent settings for the output file intervals in one case.

The issue occurs when the settings for output frequency in the input.nml atmos_model_ nml do not match those in the model_configure file, and the write-component is used. In this case, the write component was writing files more frequently than the atmos_model.F90 was updating the data structure (Diag DDT).

To Reproduce:

What compilers/machines are you seeing this with? compiler/machine independent
Give explicit steps to reproduce the behavior.

  1. Run the ufs-mrweather-app, selecting the GFSv16beta SDF
  2. look at the resulting output netcdf files (atm, sfc)
  3. the files at forecast hours 0,1,2 are identical. the files at forecast hours 3,4,5 are identical, etc.

Alternatively, set the following values in input.nml and model_configure:
input.nml:
fdiag=3
fhmax=240
fhmaxhf=0
fhout=3
fhouthf=1
model_configure:
nfhmax_hf: 12
nfhout_hf: 1
nfhout: 3

Additional context

  • ufs-mrweather-app needs to correct the default settings for this case:
  • recommend a check or warning on this in the ufs-weather-model, so that misleading output files are not created

Output

Screenshots
The file sizes are identical, and the contents as well.
-rw-r--r-- 1 carson ncar 16874881 Dec 18 11:44 sfcf000.nc
-rw-r--r-- 1 carson ncar 16874881 Dec 18 11:44 sfcf001.nc
-rw-r--r-- 1 carson ncar 16874881 Dec 18 11:44 sfcf002.nc
-rw-r--r-- 1 carson ncar 17932500 Dec 18 11:44 sfcf003.nc
-rw-r--r-- 1 carson ncar 17932500 Dec 18 11:44 sfcf004.nc
-rw-r--r-- 1 carson ncar 17932500 Dec 18 11:45 sfcf005.nc
-rw-r--r-- 1 carson ncar 18461607 Dec 18 11:45 sfcf006.nc

output logs
If applicable, include relevant output logs.
Either drag and drop the entire log file here (if a long log) or

paste the code here (if a short section of log)
@junwang-noaa
Copy link
Collaborator

This issue will be fixed in fv3atm issue #136

epic-cicd-jenkins pushed a commit that referenced this issue Apr 17, 2023
* updated container instructions

* GSI/RRFS formatting fix

* another GSI/RRFS formatting fix

* add info on binding file dirs

* minor edits

* update Container Run section

* fix headings

* fix typo

* minor updates

* change to release branch version

* update binding, sandbox

* add NOAACloud/miniconda3 instructions

* add table of .img locations

* update pre-installed container locations

* update .img locations & other minor changes

* add troubleshooting section, minor updates

* formatting, remove comments

* add JET info

* format JET info

* wording/minor edits

* update container name to develop

* switch to python workflow/yaml

* fix typos, ICS/LBCS file info

* minor fix

* add :orphan: tag to rst tables

* edit sandbox name

* wording

* typos

* add example stage-srw command

* remove regional_workflow reference, minor updates

* add orion/cron note

* fix orion/cron note

* fix orion/cron note

Co-authored-by: gspetro <gillian.s.petro@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants