Opened 3 weeks ago

Last modified 26 hours ago

#325 new Enhancement

Flexpart v10.4 test cases run

Reported by: myoshimura Owned by:
Priority: minor Milestone:
Component: FP input data Version: FLEXPART 10.4
Keywords: Cc:

Description

Hello, I have started FLEXPART recently on Ubuntu18.04LTS(WSL2).

First of all, I use flex_extract v7.1.2 to download the input data.
As a local public user, I could successfully get EA~ data. I made AVAILABLE file and didn't modify other files in the directory options.

Then I tried to run example files in the folder tests/examples (section 7 of Pisso et al. (2019)) and received an error message discussed in #279. I modified parameters in par_mod.f90 and recompile. However, I'm now receiving another error message as following together with many warning messages stated in #303(WARNING: undefined GRIB2 message found!).

 Mother domain:
  Longitude range:  -24.00000 to   60.37500   Grid distance:    0.28125
  Latitude range :    9.87500 to   74.00000   Grid distance:    0.28125

  -25.0000000       10.0000000
   60.3750000       74.0000000      -24.0000000       9.87500000       60.0000000       75.0000000       1.00000000       1.00000000
  #### FLEXPART MODEL ERROR! PART OF OUTPUT    ####
  #### GRID IS OUTSIDE MODEL DOMAIN. CHANGE    ####
  #### FILE OUTGRID IN DIRECTORY               ####
./options_1-1_1/

I would appreciate it if someone tells me how to resolve this issue.

I guess I have to modify OUTGRID and other parameters of par_mod.f90. I would also like to know how to find the correct values that match the resolution of wind fields.

Thanks.

Change History (3)

comment:1 follow-up: Changed 5 days ago by pesei

  • Priority changed from major to minor

Hello, the error message is telling you exactly what the problem is and how you can solve it:

The first three lines inform you about the input domain (and grid distance).

The two lines directly above the error message are produced by readoutgrid.f90 line 103 / 104:

    write(*,*) outlon0,outlat0
    write(*,*) xr1,yr1,xlon0,ylat0,xr,yr,dxout,dyout

The first line gives you the southwestern corner of your output domain. If you compare it you can see that your input domain starts at 24 W while your output domain starts at 25 W. That's a mistake, obviously.

The second of the two code lines is, admittedly, a bit weird and we should sanitize this output.

  1. The first pair is the NE corner of the output domain.
  2. The second pair is the SW corner of the input domain (same as in the "Mother domain:" output).
  3. The third pair is the NE corner of the output domain (so you are also going too far north by 1 deg in your output domain).
  4. The fourth pair is the output grid distance.

The correct values for the output domain have to make sure that the output domain does not include any area that is outside the input domain. As for the resolution, this is totally your choice and not linked to the input grid.

comment:2 Changed 5 days ago by pesei

  • Type changed from Support to Enhancement

I change this from Support to Enhancement because the error message should be improved (in readoutgrid.f90).

The heading of the grid information written by gridcheck might also be made more clear by saying Mother domain (meteo input)

comment:3 in reply to: ↑ 1 Changed 26 hours ago by myoshimura

Replying to pesei:

Hello, the error message is telling you exactly what the problem is and how you can solve it:

The first three lines inform you about the input domain (and grid distance).

The two lines directly above the error message are produced by readoutgrid.f90 line 103 / 104:

    write(*,*) outlon0,outlat0
    write(*,*) xr1,yr1,xlon0,ylat0,xr,yr,dxout,dyout

The first line gives you the southwestern corner of your output domain. If you compare it you can see that your input domain starts at 24 W while your output domain starts at 25 W. That's a mistake, obviously.

The second of the two code lines is, admittedly, a bit weird and we should sanitize this output.

  1. The first pair is the NE corner of the output domain.
  2. The second pair is the SW corner of the input domain (same as in the "Mother domain:" output).
  3. The third pair is the NE corner of the output domain (so you are also going too far north by 1 deg in your output domain).
  4. The fourth pair is the output grid distance.

The correct values for the output domain have to make sure that the output domain does not include any area that is outside the input domain. As for the resolution, this is totally your choice and not linked to the input grid.

Dear pesei
Thank you so much for your comment. It helps me and now the test cases work.

Note: See TracTickets for help on using tickets.
hosted by ZAMG