Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

WRF execution information

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

J

JCollins

New member
Hi.

I have compiled WRF with two different options (dmpar and dm+sm). I usually used dmpar, but for technical reasons, I am currently using dm+sm.

I usually run long-term cases, so for me, it is very convenient to be able to check how the output file is going to be written. For this, I always use
Code: 
tail -f rsl.out.0000

When using dmpar I obtained an exit with a lot of information, where I could see the time that was running, that is, I could know how much I could miss finishing the execution. It's something like this:
Code: 
d03 2019-06-17_00:03:57+29/** calling inc/HALO_EM_MOIST_OLD_E_7_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/PERIOD_BDY_EM_MOIST_OLD_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/HALO_EM_A_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/PERIOD_BDY_EM_A_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/HALO_EM_PHYS_A_inline.inc
d03 2019-06-17_00:03:57+29/** Top of Radiation Driver
d03 2019-06-17_00:03:57+29/** calling inc/HALO_PWP_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/HALO_CUP_G3_IN_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/HALO_EM_FDDA_SFC_inline.inc
d03 2019-06-17_00:03:57+29/** calling inc/HALO_EM_TKE_C_inline.inc

Since I use dm + sm the information that I can see is much more limited, and the date and time that it is executing is not shown.
Code: 
calling inc/HALO_EM_D2_5_inline.inc
calling inc/PERIOD_BDY_EM_D_inline.inc
calling inc/PERIOD_BDY_EM_MOIST2_inline.inc
calling inc/PERIOD_BDY_EM_CHEM2_inline.inc
calling inc/PERIOD_BDY_EM_TRACER2_inline.inc
calling inc/PERIOD_BDY_EM_SCALAR2_inline.inc
calling inc/PERIOD_BDY_EM_TKE_inline.inc
calling inc/HALO_EM_TKE_5_inline.inc
calling inc/HALO_EM_MOIST_E_5_inline.inc
calling inc/HALO_EM_A_inline.inc
calling inc/PERIOD_BDY_EM_A_inline.inc

Is there any way to expand the information?
 
Hello

I will not answer directly but what I do; I count number of wrfout files written to disk and divide elapsed time from model start with that number. That way I know how much time wrf takes to integrate one output step. Then I use target number of wrfout files - written number of wrfout files = the number of files to be written. That number, times time to integrate one output step is expected time to finish. I know I complicated the explanation and maybe wrote something wrong but you probably got an idea.

Ivan
 
Thank you very much for your answer. I understand what you mean, it is a possible solution to, in some way, see what day and time is the execution and be able to calculate how much time is left.

Anyway, I understand that if you are doing so, there is no way to get the information as to when you run with dmpar.
 
JCollins said:
Anyway, I understand that if you are doing so, there is no way to get the information as to when you run with dmpar.
Click to expand...

I don't know that part. Maybe folks from wrfhelp will have better answer.
 
You must log in or register to reply here.
Top