ACM2 scheme error

bbbbbdst

New member
I use pxlsm and can successfully run the ACM2 scheme with three levels of nesting (36.12.04km).
But when I run 12km and 04km separately, I got this error (The input and bdy from nesting) . 36km can run successfully.
Model crashed immediately

Code:
FATAL CALLED FROM FILE:  <stdin>  LINE:     415
  RIBX never exceeds RIC, RIB(i,kte) =   0.0000000E+00 THETAV(i,1) =    300.0000     MOL=  -2.537926     TCONV =    2.587728     WST =    1.032219     KMIX =           23 UST =   0.2067498     TST =   -1.058871     U,V =   0.0000000E+00  0.0000000E+00 I,J=           1           1

I modified the timestep, but it didn't work. I changed the land type (mentioned in other posts in the forum), but it didn't work. I only use wrfbdy and wrfinput as input files, I use WRF4.3 and WPS4.4. The 04km simulation domain is located in the river plain, and there should be no very steep terrain.All other scheme can run successfully, but I really need PX lsm. I am using FNL data. Is there a better compatible forcing data?

How can I fix this problem? Looking forward to your help! ! !

Code:
&time_control
 run_days                            = 28,
 run_hours                           = 0,
 run_minutes                         = 0,
 run_seconds                         = 0,
 start_year                          = 2020,
 start_month                         = 08,
 start_day                           = 05,
 start_hour                          = 00,
 end_year                            = 2020,
 end_month                           = 09, 
 end_day                             = 01, 
 end_hour                            = 00, 
 interval_seconds                    = 21600
 input_from_file                     = .true.,
 history_interval                    = 60,  60,   60,
 frames_per_outfile                  = 24,  24,   24,
 restart                             = .false.,
 restart_interval                    = 1440,
 io_form_history                     = 2
 io_form_restart                     = 2
 io_form_input                       = 2
 io_form_boundary                    = 2
 write_hist_at_0h_rst                = .true.
 /

 &domains
 time_step                           = 8,
 time_step_fract_num                 = 0,
 time_step_fract_den                 = 1,
 max_dom                             = 1,
 e_we                                = 205,
 e_sn                                = 229,
 e_vert                              = 24,
 eta_levels                          = 1.000,0.995,0.988,0.980,0.970,0.956,     ! full sigma, bottom-up,
                                       0.938,0.916,0.893,0.868,0.839,0.808,     ! start with 1.0, end
                                       0.777,0.744,0.702,0.648,0.582,0.500,     ! with 0.0
                                       0.400,0.300,0.200,0.120,0.052,0.000,
 p_top_requested                     = 10000,
 num_metgrid_levels                  = 34,
 num_metgrid_soil_levels             = 4,
 dx                                  = 4000,
 dy                                  = 4000,
 grid_id                             = 1,  
 parent_id                           = 0, 
 i_parent_start                      = 0,   
 j_parent_start                      = 0, 
 parent_grid_ratio                   = 1, 
 parent_time_step_ratio              = 1,  
 feedback                            = 1,
 smooth_option                       = 0
 /

 &physics
 mp_physics                          = 10,
 mp_zero_out                         = 2,
 mp_zero_out_thresh                  = 1.0e-8,
 ra_lw_physics                       = 4,
 ra_sw_physics                       = 4,
 radt                                = 4,
 co2tf                               = 1,
 sf_sfclay_physics                   = 7,
 num_soil_layers                     = 2,
 pxlsm_smois_init                    = 1,
 pxlsm_modis_veg                     = 1,
 sf_surface_physics                  = 7,
 sf_urban_physics                    = 0,
 bl_pbl_physics                      = 7,
 bldt                                = 0,
 cu_physics                          = 1,
 kfeta_trigger                       = 2
 cudt                                = 0,
 ishallow                            = 0,
 shcu_physics                        = 0,
 prec_acc_dt                         = 60,
 isfflx                              = 1,
 ifsnow                              = 1,
 icloud                              = 1,
 cu_rad_feedback                     = .true.,
 surface_input_source                = 1,
 num_land_cat                        = 20,
 num_soil_cat                        = 16,
 sst_update                          = 0,
 seaice_threshold                    = 100,
 slope_rad                           = 1,
 topo_shading                        = 1,
 shadlen                             = 25000.,
 do_radar_ref                        = 1,
 grav_settling                       = 0,
 /

 &fdda
 /

 &dynamics
 hybrid_opt                          = 2,
 w_damping                           = 1,
 diff_opt                            = 1,
 km_opt                              = 4,
 diff_6th_opt                        = 2,
 diff_6th_factor                     = 0.12,
 damp_opt                            = 3,
 base_temp                           = 290.
 zdamp                               = 5000.,
 dampcoef                            = 0.05,
 khdif                               = 0,
 kvdif                               = 0,
 non_hydrostatic                     = .true.,
 moist_adv_opt                       = 2,
 tke_adv_opt                         = 2,
 scalar_adv_opt                      = 2,
 use_theta_m                         = 1,
 /

 &bdy_control
 spec_bdy_width                      = 5,
 specified                           = .true.
 /

 &grib2
 /

 &namelist_quilt
 nio_tasks_per_group = 0,
 nio_groups = 1,
 /
 

Ming Chen

Moderator
Staff member
This error message indicates something wrong in the LSM physics. It could possibly be caused by inconsistency in the initial data, e.g., soil moisture, soil temperature, landuse type, etc.
For 12km and 4km cases, the resolution of FNL data is too coarse. Can you use the GFS quarter degree data as the forcing? The GFS data can be downloaded from CISL RDA: NCEP GFS 0.25 Degree Global Forecast Grids Historical Archive
Please repeat your failed case and let me know whether it works.
 

bbbbbdst

New member
This error message indicates something wrong in the LSM physics. It could possibly be caused by inconsistency in the initial data, e.g., soil moisture, soil temperature, landuse type, etc.
For 12km and 4km cases, the resolution of FNL data is too coarse. Can you use the GFS quarter degree data as the forcing? The GFS data can be downloaded from CISL RDA: NCEP GFS 0.25 Degree Global Forecast Grids Historical Archive
Please repeat your failed case and let me know whether it works.
Thanks , I will do it.
 
Last edited:

bbbbbdst

New member
H
This error message indicates something wrong in the LSM physics. It could possibly be caused by inconsistency in the initial data, e.g., soil moisture, soil temperature, landuse type, etc.
For 12km and 4km cases, the resolution of FNL data is too coarse. Can you use the GFS quarter degree data as the forcing? The GFS data can be downloaded from CISL RDA: NCEP GFS 0.25 Degree Global Forecast Grids Historical Archive
Please repeat your failed case and let me know whether it works.
Hi Ming Chen
I used gfs forcing data but got the same error .
Would you mind to guide me on what to do next?
I will really appreciate it ~~!!
 
Last edited:

bbbbbdst

New member
This error message indicates something wrong in the LSM physics. It could possibly be caused by inconsistency in the initial data, e.g., soil moisture, soil temperature, landuse type, etc.
For 12km and 4km cases, the resolution of FNL data is too coarse. Can you use the GFS quarter degree data as the forcing? The GFS data can be downloaded from CISL RDA: NCEP GFS 0.25 Degree Global Forecast Grids Historical Archive
Please repeat your failed case and let me know whether it works.
And I found that if I set smooth_option=1, and get wrfinput and wrfbdy, then when I run the 04km case alone, I can run a time step, get wrfout and then the mode crashes. If I set smooth_option=0, then even wrfout will not be generated. I only have wrfbdy_d01 for 36 12 and 04 case. no wrfbdy_d02 or 03.
 
Last edited:

Ming Chen

Moderator
Staff member
if you run the 36-12-4km nested case, it is right that you should only have wrfndy_d01 for the 36-km domain.
if you run single domain cases for dx=12km and dx=4km, you do need wrfbdy_d01 for each case.
Please read the document below to get a clear picture how the WRF model works: Chapter 5: WRF Model
 

bbbbbdst

New member
if you run the 36-12-4km nested case, it is right that you should only have wrfndy_d01 for the 36-km domain.
if you run single domain cases for dx=12km and dx=4km, you do need wrfbdy_d01 for each case.
Please read the document below to get a clear picture how the WRF model works: Chapter 5: WRF Model
It works! Thank you very much .
Only ACM2 pbl scheme will crashed when I only use wrfbdy_d01. It's sems like ACM2 scheme more easier crash.
 
Last edited:
Top