Out of bounds error

[mitchekc]

When I run flexpart-wrf using the command ./flexwrf_intel_omp I get out of bounds errors when my WRF geographical grid is compared to the grid in flexwrf.input. Where does FLEXPART-WRF look to find the WRF geographical grid to compare to? I have tried multiple settings in flexwrf.input and I can't determine which specific fields in the flexwrf.input file are causing the issue.

[pesei]

Can you please post the error message, including backtrace with line numbers?

[mitchekc]

output information

[mitchekc]

Replying to pesei:

Can you please post the error message, including backtrace with line numbers?

I have attached the output file. My interpretation of the error message is that my WRF output file data and my FLEXPART-WRF geographical domain are different. The thing I can't figure out is: where is FLEXPART-WRF looking to compare with the WRF data? Am I missing a file? Should my namelist.wps or namelist.input files from WRF be placed in a certain folder?

I have also attached my flexpart.input file for reference.

[mitchekc]

flexwrf.input file

[pesei]

What's the time interval in your meteorological input?

And please recompile FLEXPART-WRF with -fbacktrace (or corresponding option in other compiler if not gfortran) so that we can see at which line the problems are encountered (repost the output).

[mitchekc]

error file following compile with backtrace

[mitchekc]

Hi there
I recompiled with backtrace. The issue seems to be that my FLEXPART domain is different from my WRF domain. I'm not sure how to fix the problem since I don't know the source of the issue. I have attached my namelist.wps and namelist.input files. These files are where the domain for WRF are defined.

[mitchekc]

Specific questions I have about the FLEXPART-WRF output file include:

1. INFORMATION: SUBGRIDSCALE TERRAIN EFFECT IS NOT PARAMETERIZED DURING THIS SIMULATION.

I get this notice in my file and I don't know what it means. It seems to say that only dispersion in the air is calculated. Is that correct?

2. # of vertical levels in WRF data

n_bottom_top & "true" nuvz: 34 34
nwz & "augmented" nuvz: 35 35

nwzmax, nuvzmax, nzmax : 61 61 61
nconvlevmax, nconvlev : 60 33
nx, ny, nxmax, nymax : 147 121 250 190

Where does FLEXPART-WRF get this information from? It seems like it comes from one of the WRF namelist files. Does FLEXPART-WRF need the namelist files to work correctly or does FLEXPART-WRF get this information from the netCDF input data files?

3. readoutgrid diagnostics

xtmp1, ytmp1 (in) -7.8316902161E+01 4.5500301361E+01
xtmp2, ytmp2 (in) 2.1383683594E+04 1.4807500000E+04

-78.5038452148 outgrid_swlon

45.6768264771 outgrid_swlat

-78.1782531738 outgrid_nelon

45.7616157532 outgrid_nelat

out_xm0, out_ym0 -7.8316902161E+01 4.5500301361E+01
dxout, dyout 1.4600000000E+02 1.2100000000E+02

#### FLEXPART MODEL ERROR! PART OF OUTPUT ####
#### GRID IS OUTSIDE MODEL DOMAIN. CHANGE ####
#### OUTGRID IN INPUT FILE ####

This error message makes it clear that I need to change the OUTGRID section of the input file. I don't know how to change it. WRF defines domain location using the latitude and longitude at the centre of the grid. FLEXPART-WRF is looking for the Lower Left point and grid distance or upper right point. I am trying to define a FLEXPART-WRF grid that starts at a lower left point of (-78.3169,45.5003), goes 147 km to the East and 121 km to the North. Is this what I have defined in the flexwrf.input file?

4. xmet0 (WRF), out_xm0 (FLX) : 0.0000000E+00 < -78.31690 ? ymet0 (WRF), out_ym0 (FLX) : 0.0000000E+00 < 45.50030 ? xr1 (WRF), xr (FLX) : 147000.0 > 21383.68 ? yr1 (WRF), yr (FLX) : 121000.0 > 14807.50 ?

What is this trying to communicate? It seems like it is trying to say that the specified grid size is greater than a grid size that FLEXPART-WRF has generated. What input data or files does FLEXPART-WRF use to determine xr (FLX) and yr (FLX)?

Thank you for your help

[mitchekc]

The target longitude/latitude I have given above should be in eastern Ontario, Canada.

[mitchekc]

I think the problem may be due to the variable xmet0 and ymet0 not being initialized. I can't find where these variables are assigned a value.

[pesei]

Replying to mitchekc:

I think the problem may be due to the variable xmet0 and ymet0 not being initialized. I can't find where these variables are assigned a value.

The makefile contains an FFLAG -finit-local-zero, and the gfortran manual says about it:
The -finit-local-zero option instructs the compiler to initialize local INTEGER, REAL, and COMPLEX variables to zero, LOGICAL variables to false, and CHARACTER variables to a string of null bytes.

Did you remove this flag?

[pesei]

As there is no answer since 17 months, I assume that the problem is solved.