Opened 4 weeks ago

Last modified 4 weeks ago

#242 accepted Defect

richardson not working -- bad h

Reported by: daliaga Owned by: pesei
Priority: major Milestone:
Component: FP coding/compilation Version: FLEXPART-WRF
Keywords: richardson bad h Cc:

Description (last modified by pesei)

I'm using FLEXPART-WRF_v3.3.2 with input data obtained from WRF-ARW.
I keep getting the following error:

richardson not working -- bad h = -2.87909937

where the negative h usually varies a bit. After this the programs aborts. I delved into the code and found out that this is due to FLEXPART getting a negative value for the Boundary layer height. How can Flexpart think that h is negative? what can be the source of this problem?

As a workaround, I chose
SFC_OPTION = 1

but then I got

#### FLEXPART MODEL ERROR! SFC_OPTION =           1

I went into the code again and find out that this option aborts the program since SFC_OPTION = 1 is no longer supported:

write(*,*) ' #### Reading from WRF no longer supported.'
write(*,*) ' #### ---------------------------------'

I modified the code so that it will not abort, but im wondering why this option is no longer supported

Attachments (2)

output43519254.txt (49.9 KB) - added by daliaga 4 weeks ago.
log file
flex_input.txt (8.1 KB) - added by daliaga 4 weeks ago.
input file

Download all attachments as: .zip

Change History (5)

comment:1 Changed 4 weeks ago by pesei

  • Component changed from FP other to FP coding/compilation
  • Description modified (diff)
  • Owner set to pesei
  • Status changed from new to accepted

Can you please give a few more details? How long into the integration happens this? Which part of the globe? Day or night? Which resolution / nest level? Maybe post your input file.

comment:2 Changed 4 weeks ago by pesei

See also #222 - might be related.

Changed 4 weeks ago by daliaga

log file

Changed 4 weeks ago by daliaga

input file

comment:3 Changed 4 weeks ago by daliaga

Thank you for the reply. Here I add more details:

  • How long into the integration happens this?

It has happened on multiple runs with the same domain but different times. It can happen at any point on the simulation

  • Which part of the globe?

South America with the center around lat: -17 and lon: -68.

  • Day or night?

I think that it happens mostly during the night but i would need to verify. In the example im uploading, it happened during the night.

  • Which resolution / nest level?

highest resolution is ~1km and lowest ~27km with 4 nested grids

  • Maybe post your input file.

I'm posting the input file along with the log file

Thanks for your time.

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