HYSPLIT Forum: hysplitbbs.arl.noaa.gov

Found a third location where this is happening. In advsti.f, when gspdx = 0 at the poles, then the calculation of UU becomes ill defined.

Version: 5.4.2

This may be very specific to my setup, but I'm encountering some numerical issues when using a global grid where the +90/-90 latitudes are included. Specifically, I'm using ERA5 data that was converted using the default configuration of the "hysplit_metdata" utility.

For instance ...

Version: 5.4.2

In global domain, when particles are near the poles, sometimes particles can wrap around the longitude band more than once. There's already some code in adv2nt and adv3nt to handle wrapping a single time, but if the particle has wrapped more than once it fails, and the XF ...

We're running with the Linux executables.
I re-ran our tests against the latest version 5.3.4, and can confirm that this version does fix the global boundary issue for our experiments.
Many thanks for the quick solution to this problem!

Apologies for any confusion. For GDAS, I'm getting a different particle cut-off at the prime meridian instead of the dateline. Seems to be specific to the dataset being used. Could you confirm if your particles are getting across the 0 degree longitude in your GDAS test? Thanks!
We're using the full ...

Same issue happens with GDAS1 met data, so this seems to be a general problem with global met fields and HYSPLIT 5.3? Particles hit the "boundary" of the grid, and die.

Running HYSPLIT 5.3.0 back trajectories, with ERA5 global met data encoded with hysplit_metdata and era52arl tools and the default area of 90/-180/-90/180 and grid resolution 0.3. In HYSPLIT, when the particles hit the meteorology longitude bounds (-180), they disappear from the grid. One example of ...