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

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".

 
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".

 
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".

 
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".

 
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".

 
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".

 
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".

 
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".

 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
G

gchen@rsmas_miami_edu

New Member
Hi Jerry, thanks so much again pointing out to the right direction. I went through the codes and found out the U, V, etc, are diagnosed and outputted to the history files (.rh0.) by cam_run1 (in cam_comp.F90 using tphysbc in physpkg.F90) after a bunch of moist physical parameterization. Just right after the moist physical paramterizations are done, the diag_phys_writeout (in cam_diagnostic.F90) is called, and U, V, etc, are saved. I assume this is where they are dumped into .rh0. file. As oppose to the U, V, etc, in .r. file, which are dumped in cam_run4 (in cam_comp.F90) using write_restart_history (in cam_history.F90). So they are essentially different based on .rh0. is not yet updated in the dynamics and a bunch of parameterization whereas .r. is fully updated.Please correct me if I'm wrong, and thanks a bunch!--------------Gino
 
You must log in or register to reply here.
Top