HYSPLIT Forum: hysplitbbs.arl.noaa.gov

This section of the tutorial shows how to get to this menu.
https://www.ready.noaa.gov/documents/Tu ... _volc.html

Please see this section of the user guide and let us know if this answers your question.

https://ready.arl.noaa.gov/hysplitusersguide/S314.htm

Could you please try running with a smaller number of particles to see if the problem persists. I reproduced your run with 288,000 particles and was unable to reproduce the problem. See below. Please let us know. Index Height %Mass 11 3360.0 0.23 10 2755.0 1.77 9 2210.0 10.20 8 1725.0 21.00 7 1300.0...

Can you please attach your CONTROL and SETUP.CFG file you used for the run so we can reproduce the problem.
Thanks.

Thanks for updating and sharing your scripts. A few thoughts. With the new cdsapi you do not need to have separate files for the analysis and forecast surface data. The new api allows you to retrieve both types of variables into the same file (The old api did not). The era52arl program can still ing...

I reproduced your problem by downloading files using the request code that you have posted.
It looks like your request results in a file with
gridType = sh
please modify your request so
gridType = regular_ll

See some examples of requests at
https://github.com/amcz/hysplit_metdata

Can you make sure that you are using the most up to date era52arl code? You can get it from github as well as the lastest HYSPLIT release. https://github.com/amcz/hysplit_metdata I have also added some sample code in the README. For the pressure level data I am using the 'reanalysis-era5-pressure-le...

We recommend using the era52arl program to convert ERA5 data.
It can be found in the data2arl folder.

There are several problems. The CONTROL file that you posted will not work with your EMISS1.txt file. The number of starting locations in the CONTROL file needs to match the number in EMISS1.txt. Also in EMISS1, you have 10 starting locations in your top line, but you only provide 5. Also please che...

HYSPLIT only applies the cyclic boundary conditions to global data. So in your first dataset it sees the 'edge' of the dataset at -180 and 180. In your second data set the edges are now at 0 and 360. You will still have truncations with the 0-360 data, just in a different place. Currently the only w...