Custom Query (210 matches)
Results (1 - 3 of 210)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#108 | fixed | Problem with mercator projection | adingwell | adingwell |
Description |
I've tried running FLEXPART-WRF with Mercator projection and got the error: need orientation longitude (stdlon) as: -180e <= lon1 <= 180w STOP map_init This error should not occur if Mercator projection is used. The problem is in the subroutine map_set. The variable 'proj_merc' is referenced before it is defined. I've marked the changes needed to fix the problem below: proj_code = proj_code_in !!! This is where map_init should be called to fix the problem call map_init ! first, check for validity of mandatory variables in proj if ( abs(lat1) .gt. 90.001 ) then print '(a)', 'latitude of origin corner required as follows:' print '(a)', ' -90n <= lat1 < = 90.n' stop 'map_init' endif if ( abs(lon1) .gt. 180.) then print '(a)', 'longitude of origin required as follows:' print '(a)', ' -180e <= lon1 <= 180w' stop 'map_init' endif if ((dx .le. 0.).and.(proj_code .ne. proj_latlon)) then print '(a)', 'require grid spacing (dx) in meters be positive!' stop 'map_init' endif if ((abs(stdlon) .gt. 180.).and.(proj_code .ne. proj_merc)) then print '(a,i3)', 'proj_code: ', proj_code print '(a,i3)', 'proj_merc: ', proj_merc print '(a)', 'need orientation longitude (stdlon) as: ' print '(a)', ' -180e <= lon1 <= 180w' stop 'map_init' endif if (abs(truelat1).gt.90.) then print '(a)', 'set true latitude 1 for all projections!' stop 'map_init' endif !!! This is where "map_init" is called in 3.2 BETA It's also rather confusing when the stop code is 'map_init' but the problem occurs in the subroutine 'map_set'. |
|||
#156 | fixed | Flexpart-WRF 3.3, new parameter in readinput.f90 | adingwell | mschoeppner |
Description |
There seems to be a new parameter listed in readinput.f90 of the newly released Flexpart-WRF3.3. In line 225 lu_option is listed between turb_option and cbl_scheme, but it is not listed in the flxp_input.txt examples. This makes the existing flxp_input format incompatible with the new Flexpart-WRF version. What is the purpose of lu_option? In order to make Flexpart-WRF 3.3 work with the existing flxp_input format, we had to remove line 225 from readinput.f90 and recompile. |
|||
#157 | fixed | Flexpart-WRF 3.3 forces verbose setting | adingwell | mschoeppner |
Description |
In lines 237-238 of readinput.f90 of Flexpart-WRF 3.3 the verbose variable is automatically set to 10, overwriting the input from flxp_input.txt. We have removed these lines to allow user input for verbose mode. |