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

CAM 5.0 restart files .r. and .rh0. generate different zonal wind field in a one time-step output

G

gchen@rsmas_miami_edu

New Member
I know that .rh0. file accumulates/adds the fields in time for one month and takes a monthly average in the end of each month. But, if I simply generate a one time-step (1800 sec) zonal wind (U) output field in .r. and .rh0. files, the difference between the two files is on the order of 10%. Could anyone explain why the two files give different U fields in a single timestep output?  In fact, not only the U fields are different, the other fields saved in both files are also different. Why?
 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
O

olson

Member
    Not having looked at these files in detail, there are at
  least 3 reasons I can think of for the behavior you
  are seeing, the one for sure being that the restart
  state (".r") and accumulated history file state (".rh0")
  are output at 2 different points in the timestep cycle.

 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, Thanks for pointing out the timestep cycle possibility. The timestep cycle you mentioned, are the two files just outputing at different physics or dynamics update stages? Or do you mean like an intermediate timestep using numerical scheme such as Runge-Kutta method? Is it possible to point out the fortran module I could look into? I appreciate your help.Gino Chen
 
O

olson

Member


 Correct, the ouputting can take place at different physics or dynamics stages.  Furthermore,
 in the case of .rh0, the outputting takes place at a unique stage for each different history
 field.  The output for each field is via calls to "outfld", hundreds of which are
 sprinkled throughout the code (in dynamics as well as physics).  For example, T, U, V, Q,
 and PS are output via calls in the routine "diag_phys_writeout" of the module "cam_diagnostics.F90".

 
You must log in or register to reply here.
Top