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

Time shown in history file names is incorrect for instantaneous data #1167

Open
phillips-ad opened this issue Oct 8, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working correctly CoupledEval3

Comments

@phillips-ad
Copy link

What happened?

The translated time present in instantaneous history files does not match that shown in the actual file name. If the time variable translates to February 1st year 10 at 00Z, the history file name should end in "0010-02.nc". Right now, the file name ends in "0010-01.nc".

What are the steps to reproduce the bug?

Doing a ncdump on a file shows the issue:
ncdump -t -v time /glade/derecho/scratch/hannay/archive/b.e30_beta02.BMT1850.ne30_t232.104/atm/hist/b.e30_beta02.BMT1850.ne30_t232.104.cam.h0i.0010-01.nc
output: time = "0010-02-01"

What CAM tag were you using?

cam6_4_014

What machine were you running CAM on?

CISL machine (e.g. cheyenne)

What compiler were you using?

Other (please specify below)

Path to a case directory, if applicable

/glade/campaign/cesm/cesmdata/cseg/runs/cesm2_0/b.e30_beta02.BMT1850.ne30_t232.104

Will you be addressing this bug yourself?

No

Extra info

No response

@phillips-ad phillips-ad added the bug Something isn't working correctly label Oct 8, 2024
@brian-eaton
Copy link
Collaborator

This is related to the comment in #1166 which explains why there is an instantaneous file associated with a monthly average file. Those two files have the same date in the filename. The fix here is that the instantaneous file should get a filename that uses the same template as the other non-monthly instantaneous output files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly CoupledEval3
Projects
Status: To Do
Development

No branches or pull requests

4 participants