Custom Query (210 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (55 - 57 of 210)

Ticket Resolution Summary Owner Reporter
#92 fixed Erase empty page TestFiles admin dearn
Description

Erase unused and empty

http://flexpart.eu/wiki/TestFiles

#93 fixed problem when running in OpenMP mode jbrioude bszintai
Description

Hello,

I am running Flexpart-WRF 3.1 for nested input and output domains with 10 million particles. I get significantly different tracer clouds when I run in serial (1 cpu) or in OpenMP mode (4 or 6 OpenMP threads). For the OpenMP run it seems as if the tracer cloud would have much less particles (resembles a run with 2-3 million particles) then in the serial run (see attached plots). There is no difference between the 4 and 6 thread OpenMP runs and I get the same problem with gnu and intel compilers.

When I do not use input and output nesting, then there seems to be no such problem (i.e. serial and OpenMP runs are rather similar).

Thanks a lot for your help in advance.

Balazs

#96 fixed FLEXWRF3.1 output in lat/lon grid jbrioude bzhang
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

Note: See TracQuery for help on using queries.
hosted by ZAMG