Custom Query (210 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 33 of 210)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#203 fixed inconsistency / bug in verttransform_gfs.f90 pesei shachinger
Description

Dear all,

in FLEXPART 9.2 I stumbled upon what is most probably a bug, and it is still present in the FLEXPART git dev branch.

Comparing verttransform.f90 (now seems to be verttransform_ecmwf.f90) to verttransform_gfs.f90, around line 500, one notices pieces of code which probably should be identical, but they aren't:

for ECMWF it looks like:

     if (vv(nx/2-1,0,iz,n).lt.0.) then
        ddpol=atan(uu(nx/2-1,0,iz,n)/ &
             vv(nx/2-1,0,iz,n))+xlonr
      else if (vv(nx/2-1,0,iz,n).gt.0.) then
        ddpol=pi+atan(uu(nx/2-1,0,iz,n)/ &
             vv(nx/2-1,0,iz,n))+xlonr

(+ + xlonr)

whereas for GFS:

    if(vv(nx/2-1,0,iz,n).lt.0.) then
        ddpol=atan(uu(nx/2-1,0,iz,n)/vv(nx/2-1,0,iz,n))+xlonr
     elseif (vv(nx/2-1,0,iz,n).gt.0.) then
        ddpol=pi+atan(uu(nx/2-1,0,iz,n)/vv(nx/2-1,0,iz,n))-xlonr

(+ - xlonr)

I would thus propose changes as you can see in the attached picture (i.e. changing to "+ +" in the GFS version, and modifying the infinity case to be consistent with both approaches to the limit).

http://shaching.userweb.mwn.de/Screenshot_20180824_181601.png

Unfortunately, I am neither an atmospheric transport expert nor do I have an idea anymore why I fixed it this way (I looked into that like several months ago, and I think I did a comparison with corresponding code pieces in FLEXTRA).

However, I think I write this here now as "as is" and some more expert people maybe check and fix this. Thanks very much!

Stephan


contact: http://shaching.userweb.mwn.de

#249 worksforme related to making FLEXPART V 10.3 pesei sdwivedi
Description

Dear sir/madam

I am trying to make FLEXPART v10.3. I am getting the .exe file of FLEXPART. But, no message like successful completion.

It is giving some warning related to readpath. When I am running the excercise it is giving segmentation fault.. sometime.

-345600 SECONDS SIMULATED:    16864 PARTICLES:    Uncertainty:   0.000  0.000  0.000

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x7f2e3d573c2d in ???
#1  0x7f2e3d572e45 in ???
#2  0x7f2e3d25ef5f in ???
#3  0x5642d9636d4b in ???
#4  0x5642d965541d in ???
#5  0x5642d9625b6a in ???
#6  0x5642d960c852 in ???
#7  0x7f2e3d241b6a in ???
#8  0x5642d960c889 in ???
#9  0xffffffffffffffff in ???
Segmentation fault (core dumped)

Kindly help me to install FLEXPART V 10.3

Regards

Sanjeev Dwivedi

#223 fixed ASCII output type UNFORMATTED pesei scloux
Description

Hello, my name is Sara and I have a question about how to save data in ASCII format. I am running flexpart-wrf 3.3 and the first time I wanted to obtain ASCII outputs I found this error message:

At line 287 of file concoutput_irreg.f90 (unit = 97, file = '/home/usc/fp/scg/lustre/PROYECTOS/FLEXPART/TEST/test_damian/output_back_2/grid_time_19821014170000_001') Fortran runtime error: Format present for UNFORMATTED data transfer srun: error: c7026: task 0: Exited with exit code 2 srun: Terminating job step 2165917.0

I looked for that line in the code and, from my point of view, it was difficult the program save ASCII outputs providing that this format was declared as UNFORMATTED. There is a high probability I had been doing something wrong, but I try to solve this incident by changing the concoutput_irreg.f90 file. I would like to share this new file in case this problem persists.

In other terms, I am wondering if it is possible to obtain by any way the partposition file in latlon coordinates if we are working with a Lambert projection and there is not a regular grid for mother domain.

Thank you for your time. Regards, Sara

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Note: See TracQuery for help on using queries.
hosted by ZAMG