Page 1 of 1

Trajectory height does not ascend

Posted: May 9th, 2018, 3:28 am
by AraZeph
When I run HYSPLIT from the website it gives the trajectories but the vertical height is always flat. What am I doing wrong? I've tried from a few different starting locations and dates.

Image

Re: Trajectory height does not ascend

Posted: May 9th, 2018, 2:27 pm
by alicec
If you are doing multiple runs on READY and getting funny results, try using the "return to main menu and clear user inputs"
when it asks if you would like to return to the main menu to do another run. We have the option to remember
your inputs so that you don't have to re-input information if you are just doing something slightly different.
However, I think, in this case, it may be remembering inputs that you don't want it to.

Also, could you provide more information on what menu options you were using to do the run and what
you are trying to do?

I looked up your run and it has the following CONTROl and SETUP files


09 06 01 8 #STARTING TIME: YEAR MONTH DAY HOUR
9 #NUMBER OF STARTING LOCATIONS
-24.887800 113.670000 10 #STARTING 1: LATITUDE LONGITUDE HEIGHT (m-agl)
-24.887800 113.670000 100 #STARTING 1: LATITUDE LONGITUDE HEIGHT (m AGL)
-24.887800 113.670000 500 #STARTING 1: LATITUDE LONGITUDE HEIGHT (m AGL)
-114.698900 28.804700 10 #STARTING 2: LATITUDE LONGITUDE HEIGHT (m-agl)
-114.698900 28.804700 100 #STARTING 2: LATITUDE LONGITUDE HEIGHT (m-agl)
-114.698900 28.804700 500 #STARTING 2: LATITUDE LONGITUDE HEIGHT (m-agl)
-114.096700 22.240600 10 #STARTING 3: LATITUDE LONGITUDE HEIGHT (m-agl)
-114.096700 22.240600 100 #STARTING 3: LATITUDE LONGITUDE HEIGHT (m-agl)
-114.096700 22.240600 500 #STARTING 3: LATITUDE LONGITUDE HEIGHT (m-agl)
192 #TOTAL RUN TIME (hours)
0 #VERTICAL MOTION CALCULATION METHOD
15500 #TOP OF MODEL DOMAIN (m-AGL)
5 #NUMBER nextfile mfile OF INPUT DATA GRIDS
/pub/archives/gdas1/
gdas1.jun09.w1
/pub/archives/gdas1/
gdas1.may09.w5
/pub/archives/gdas1/
gdas1.jun09.w2
/pub/archives/gdas1/
gdas1.jun09.w3
/pub/archives/gdas1/
gdas1.jun09.w4
/pub/ready/hypub/
tdump.122735


&SETUP
KMSL=0,
khmax=24, Maximum duration of any trajectory
nstr=12, trajectory restart time.
mhrs=168,
/


In the SETUP.CFG file you have nstr=12, which means that HYSPLIT will automatically restart trajectories every 12 hours from
your first location in the CONTROL file. However, it ignores the other locations. So your plot is just showing 24 hour trajectories starting from
one location at 10m agl every 12 hours.

It would be helpful if you could tell me which options you were choosing from the menus on the web.
Also, please try clearing user inputs and trying the run again.

Let me know how it goes!
Alice

Re: Trajectory height does not ascend

Posted: May 16th, 2018, 1:01 am
by AraZeph
Hi
For this run I'm choosing the following, can't remember what I did on the last one but it's been doing this every time I run it no matter what I choose:

Hysplit archive trajectory
1 starting location
Normal
GDAS (jun09.w1)
-24.8878, 114.5198
120 hr, new traj every 12 hrs
0 m agl start

Image

The first one is running fine and the rest fail to ascend, this is with no previous user inputs

Re: Trajectory height does not ascend

Posted: May 16th, 2018, 3:34 am
by ariel.stein
The problem you are having is that your trajectories are hitting the ground.
Please take a look at the discussion about the that topic:
viewtopic.php?f=27&t=295&hilit=trajectory+hits+ground