Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Timestamp in output files not consistent in CESM1.5.5 branch run

M

mnawang@ucdavis_edu

New Member
Hi, I try to add a another cam variable to the output, so I created a branch run from a previous run.The restart files are - VR14_H_HIST.cam.h1.1984-07-01-00000.ncVR14_H_HIST.cam.h2.1984-07-01-00000.ncVR14_H_HIST.cam.h3.1984-07-01-00000.ncVR14_H_HIST.cam.h4.1984-07-01-00000.ncVR14_H_HIST.cam.h5.1984-07-01-00000.ncHowever, after running for 1 day, the output files from the branch run has various time stamp (different second) - VR14_H_1985.cam.h1.1984-07-01-10800.nc (output every 3 hourly, 8 output per file)VR14_H_1985.cam.h2.1984-07-01-10800.nc (output every 3 hourly, 8 output per file)VR14_H_1985.cam.h3.1984-07-02-00000.nc (output every 24 hourly, 1 output per file) (this one is correct)VR14_H_1985.cam.h4.1984-07-01-21600.nc (output every 6 hourly, 4 output per file)VR14_H_1985.cam.h5.1984-07-01-10800.nc (output every 3 hourly, 8 output per file) Basically, taking the h1 output files as examplt, the output times should be (0, 0.125, 0,25, 0.375, 0.5, 0.625, 0.75, 0.875)However, now is (0.125, 0,25, 0.375, 0.5, 0.625, 0.75, 0.875, 1), where the last time should really be the first time in the next output file. The previous run has never had this issue, and I've made sure all the settings for the env_* and user_nl_* files are the same between the two(previous/branch), except the "branch" run options. Has any body ran into the same problem before? Any help is appreciated! P.S. my yellowstone run directory is /glade/scratch/mnawang/VR14_H_1985/run                   work directory is /glade/p/work/mnawang/VR14_H_1985 Thanks!Meina 
 
M

mnawang@ucdavis_edu

New Member
I just wanted to add to my post above-  For startup runs, when I do restart, with daily outputs per file, the timestamp are always at 00000 (which is expected). However, for branch run (branch from 00000 timestamp files), the daily outputs are shifted for 3 hour (for outputing every 3 hours, e.g. *h1* output files in my previous post). So I'm wondering if this is beacuse the branch run will start output begining from the next time from restart time, while for startup run, the restart will start exactly from the restart time. From what I've experiemented for now, this seems like the most likely reason to me. I'm wondering if any of you that have ran branch runs have ever noticed this issue? Thank you,Meina
 
M

mnawang@ucdavis_edu

New Member
Hi Jim, Thank you for your reply! If this is the case, then I'm wondering if there is any way I can make all my output file timestamp consistent (all at 00000 timestamp when outputing daily per file)? Thank you!Best,Meina 
 
You must log in or register to reply here.
Top