HYSPLIT Forum: hysplitbbs.arl.noaa.gov

Thanks for the info.
J

Hi Ariel,

are you sure the latest version of HYSPLIT runs under 10.6.8?

Could the segmentation error I reported be due to the system I operate under?
Cheers
Jost

You are right. Any possibility for you to update your OS?

"To run it in batch mode for many trajectories I had written FORTRAN code that worked so far but not with the new version"
If you know the scripts are working, then changing to a new version of the trajectory code should make no difference.
Do you still have the old version, so you can run that and can make sure it works?

Your original question was for a trajectory that used to run 240 hours, but only ran 100 hours, with no apparent error message. You said you load all the met files to cover that time span. Good. Double check the CONTROL file to see if the run duration is set to 240. Look at the MESSAGE file - is there a relevant error/notice there?

Stepping up the OS is a big change for me because I'd have to change hardware, FORTRAN compiler and more.

Concerning the 240h issue: I checked and made sure I had the same range of met files that the online version of HYSPLIT uses, which calculates the full 240h whereas my batch version in a specific case only goes to 78 hours without showing any indication of errors anywhere. This is really frustrating because I do not see any system in the truncations. Often the full 240h are calculated (but often not). I could send you a long list of cases with <240h calculation.

If the trajectories are leaving the domain, the runs will last less than 240 hours.

Sure but with the same met fields web-HYSPLIT calculates the full -240h for a given example.
Bdw: How would I know if a trajectory leaves the domain without error message?

Here is the example I am referring to:
lat lon height start_year start_month start_day start_hour run_time
78.900 11.860 474 2014 8 11 10 -240

Please send me the CONTROL file you are using to generate that run.

Hi Ariel,
it finally dawned on me when thinking about your suggestion concerning model domain:
When a trajectory reaches the default model top height the model stops without error message.
Increasing the top height in the CONTROL file solves that problem (and maybe creates new ones?).
The same case in web-HYSPLIT does not reach the model top because I am using option (5) instead of (0) for vertical velocities.
Eventually, I will have to step up in hard and software but I am sure you have some understanding for my waiting with system changes as long as possible.

Have a relaxing weekend

Jost