Opened 5 years ago

Closed 5 years ago

#96 closed Support (fixed)

FLEXWRF3.1 output in lat/lon grid

Reported by: bzhang Owned by: jbrioude
Priority: minor Milestone:
Component: FP input data Version: FLEXPART-WRF
Keywords: Cc:

Description

Hi FPers,

I would like to thank all the develops of FLEXWRFv3.1 for your hard work. I run it perfectly with OUTGRID_COORD set to 0, which means the output will adopt the grids in wrf fields. However, when I try to set OUTGRID_COORD to 1 and expect to get a lat/lon grid output, I was confused about settings in the OUTGRID part and couldn't run the package. Actually, the descriptions of several parameters in this section are confusing to me. I hope someone can share with me a working input file with OUTGRID_COORD set to 1
, and explain a little bit more about how to set the following parameters right.

OUTLONLEFT
OUTLATLOWER (these two were actually need to be set as meter coordinate when OUTGRID_COORD was set to 0 and wrf files in meter coordinate. The description says geographical lon/lat)
NUMXGRD
NUMYGRID (As I found out for my case, when OUTGRID_COORD was set to 0, these two were grids set within the wrf domain.)
OUTGRIDDEF
DXOUTLON
DYOUTLON (I think this is a typo, should be DYOUTLAT.)

I tried my old settings in 8.22, OUTLONLEFT as -179, OUTLATLOWER as 0 , NUMXGRID as 360 and NUMYGRID as 90 for a full North Hemisphere run. The settings do not work here. The nc output feature is very nice, but the description for these settings may need to be specified more according to the griding method. I am now testing by guessing how these parameters are taken and digging into the fortran codes. Hope someone can help me out.

Many thanks,
Bo Zhang
Michigan Technological University

Change History (3)

comment:1 Changed 5 years ago by jbrioude

  • Owner changed from somebody to jbrioude
  • Status changed from new to assigned

Hi Bo,

You can try this:

-179.00 OUTLONLEFT

0.5 OUTLATLOWER
359 NUMXGRID
89 NUMYGRID

with the outgriddef switch, you have 2 options
if outgriddef=0, then the following values can be used:

0 OUTGRIDDEF

  1. which is the grid spacing along the longitudes
  2. which is the grid spacing along the latitudes

otherwise, you can use

1 OUTGRIDDEF

  1. which is the longitude of the upper right corner
  2. which is the latitude of the upper right corner

So if you use outgriddef=1, you can use in flexwrf.input file:

=====================FORMER OUTGRID FILE=====================

-179.00 OUTLONLEFT geograhical longitude of lower left corner of output grid

0.5 OUTLATLOWER geographical latitude of lower left corner of output grid
359 NUMXGRID number of grid points in x direction (= # of cells )
89 NUMYGRID number of grid points in y direction (= # of cells )
1 OUTGRIDDEF outgrid defined 0=using grid distance, 1=upperright corner coordinate

  1. DXOUTLON grid distance in x direction or upper right corner of output grid
  2. DYOUTLON grid distance in y direction or upper right corner of output grid 3 NUMZGRID number of vertical levels 100.0 LEVEL height of level (upper boundary)

1000.0 LEVEL height of level (upper boundary)

20000.0 LEVEL height of level (upper boundary)

================OUTGRID_NEST==========================

Jerome

comment:2 Changed 5 years ago by bzhang

Hi Jerome,

Thanks a lot for helping me out. I had tried similar settings before but got endless warnings like the following:

* ll_to_xyindex_wrf error -- x_i, y_j out of bounds

So, the simulation ran before but I just couldnt wait until the last line of the warnings. I guess this was because the outgrid set was out of wrf domain. When I shrink down the outgrid nearly matching my wrf domian, I finally got the simulation running with only a few warnings.

Cheers,
Bo

comment:3 Changed 5 years ago by jbrioude

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.
hosted by ZAMG