Opened 7 days ago

Last modified 7 days ago

#222 accepted Defect

Richardson Failure - Flexpart WRF 3.3

Reported by: lchong Owned by: pesei
Priority: major Milestone: FLEXPART_WRF_3.4_FPbase_9
Component: FP input data Version: FLEXPART-WRF
Keywords: Cc:

Description

Dear all,
I'm trying to run flexpart-wrf-3.3 on LINUX (INTEL) but sometime I try running it, it crashes with "richardson failure".

There is a crash in richardson.f90 due to calcpar - richardson failure - ix,jy= 82 148. #171 shows this is caused by using time-integrated output in WRF and starting the FLEXPART simulation so that the first WRF output is ingested. Obviously, time-integrated winds can't be defined in this first output.

Here are some options:

20140727 050000 YYYYMMDD HHMISS beginning date of simulation
20140731 050000 YYYYMMDD HHMISS ending date of simulation

3600 SSSSS (int) output every SSSSS seconds
3600 SSSSS (int) time average of output (in SSSSS seconds)
180 SSSSS (int) sampling rate of output (in SSSSS seconds)
999999999 SSSSS (int) time constant for particle splitting (in seconds)
180 SSSSS (int) synchronisation interval of flexpart (in seconds)
10 CTL (real) factor by which time step must be smaller than tl
10 IFINE (int) decrease of time step for vertical motion by factor ifine
5 IOUT 1 concentration, 2 mixing ratio, 3 both, 4 plume traject, 5=1+4
1 IPOUT particle dump: 0 no, 1 every output interval, 2 only at end
0 LSUBGRID subgrid terrain effect parameterization: 1 yes, 0 no
0 LCONVECTION convection: 3 yes, 0 no
3600 DT_CONV (real) time interval to call convection, seconds
0 LAGESPECTRA age spectra: 1 yes, 0 no
0 IPIN continue simulation with dumped particle data: 1 yes, 0 no
1 IFLUX calculate fluxes: 1 yes, 0 no
1 IOUTPUTFOREACHREL CREATE AN OUPUT FILE FOR EACH RELEASE LOCATION: 1 YES, 0 NO
0 MDOMAINFILL domain-filling trajectory option: 1 yes, 0 no, 2 strat. o3 tracer
1 IND_SOURCE 1=mass unit , 2=mass mixing ratio unit
2 IND_RECEPTOR 1=mass unit , 2=mass mixing ratio unit
0 NESTED_OUTPUT shall nested output be used? 1 yes, 0 no
0 LINIT_COND INITIAL COND. FOR BW RUNS: 0=NO,1=MASS UNIT,2=MASS MIXING RATIO UNIT
1 TURB_OPTION 0=no turbulence; 1=diagnosed as in flexpart_ecmwf; 2 and 3=from tke.
1 LU_OPTION 0=old landuse (IGBP.dat); 1=landuse from WRF
1 CBL SCHEME 0=no, 1=yes. works if TURB_OPTION=1
0 SFC_OPTION 0=default computation of u*, hflux, pblh, 1=from wrf
0 WIND_OPTION 0=snapshot winds, 1=mean winds,2=snapshot eta-dot,-1=w based on divergence
0 TIME_OPTION 1=correction of time validity for time-average wind, 0=no need
1 OUTGRID_COORD 0=wrf grid(meters), 1=regular lat/lon grid
1 RELEASE_COORD 0=wrf grid(meters), 1=regular lat/lon grid
2 IOUTTYPE 0=default binary, 1=ascii (for particle dump only),2=netcdf
1 NCTIMEREC (int) Time frames per output file, only used for netcdf
0 VERBOSE VERBOSE MODE,0=minimum, 100=maximum

Change History (2)

comment:1 in reply to: ↑ description ; follow-up: Changed 7 days ago by pesei

  • Owner set to pesei
  • Status changed from new to accepted

Replying to lchong:

There is a crash in richardson.f90 due to calcpar - richardson failure - ix,jy= 82 148. #171 shows this is caused by using time-integrated output in WRF and starting the FLEXPART simulation so that the first WRF output is ingested. Obviously, time-integrated winds can't be defined in this first output.


Yes. Therefore you cannot start the Flexpart simulation at that time. It is also not advisable as WRF requires several hours of spin-up.

Your namelist says 0 WIND_OPTION 0=snapshot winds, so it should not be this problem. However, it would be useful to know whether you are starting Flexpart with the first field from WRF or if not, how long into the simulation this happens.

comment:2 in reply to: ↑ 1 Changed 7 days ago by lchong

It is not the first field from WRF, the richardson failure can happen at 2nd hour or 2nd day. And many modeling work has this problem.


2013_06_17_05/flex_backward.log:calcpar - richardson failure - ix,jy= 64 184
2013_06_18_05/flex_backward.log:calcpar - richardson failure - ix,jy= 64 184
2013_06_19_05/flex_backward.log:calcpar - richardson failure - ix,jy= 64 184
2013_06_20_05/flex_backward.log:calcpar - richardson failure - ix,jy= 64 184
2013_07_31_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2013_08_01_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2013_08_02_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2013_08_03_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2014_06_06_05/flex_backward.log:calcpar - richardson failure - ix,jy= 495 281
2014_06_07_05/flex_backward.log:calcpar - richardson failure - ix,jy= 495 281
2014_06_14_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2014_06_15_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2014_06_16_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2017_06_18_05/flex_backward.log:calcpar - richardson failure - ix,jy= 102 173
2014_06_19_05/flex_backward.log:calcpar - richardson failure - ix,jy= 539 206
2017_06_19_05/flex_backward.log:calcpar - richardson failure - ix,jy= 102 173
2014_06_20_05/flex_backward.log:calcpar - richardson failure - ix,jy= 539 206
2017_06_20_05/flex_backward.log:calcpar - richardson failure - ix,jy= 102 173
2014_06_21_05/flex_backward.log:calcpar - richardson failure - ix,jy= 539 206
2017_06_21_05/flex_backward.log:calcpar - richardson failure - ix,jy= 102 173
2014_06_22_05/flex_backward.log:calcpar - richardson failure - ix,jy= 539 206
2016_06_23_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2016_06_24_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2016_06_25_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2016_06_26_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0
2016_07_07_05/flex_backward.log:calcpar - richardson failure - ix,jy= 308 0

Replying to pesei:

Replying to lchong:

There is a crash in richardson.f90 due to calcpar - richardson failure - ix,jy= 82 148. #171 shows this is caused by using time-integrated output in WRF and starting the FLEXPART simulation so that the first WRF output is ingested. Obviously, time-integrated winds can't be defined in this first output.


Yes. Therefore you cannot start the Flexpart simulation at that time. It is also not advisable as WRF requires several hours of spin-up.

Your namelist says 0 WIND_OPTION 0=snapshot winds, so it should not be this problem. However, it would be useful to know whether you are starting Flexpart with the first field from WRF or if not, how long into the simulation this happens.

Last edited 7 days ago by lchong (previous) (diff)
Note: See TracTickets for help on using tickets.
hosted by ZAMG