Thank you for the quick response!
barbara.stunder wrote:Are you saying that for each trajectory, 3 hours offset from each other, they are all the same trajectory? That is not right. The output file should have all the date/times and trajectory endpoints for the 56 trajectories.
No, the trajectories seem to be mostly correct. It's just that the time of the first point on each trajectory (chronologically the last point since these are backward trajectories) is the starting time of the entire run. All the other points on the trajectory seem to be fine. Since I know what this time should really be for each trajectory I can of course correct the time myself, but the bigger problem is that the met data is taken from the wrong time.
barbara.stunder wrote:Are you setting the NSTR variable in the SETUP.CFG file to 3? I suggest you do the equivalent run on our web page and compare the CONTROL and SETUP files to your run.
http://ready.arl.noaa.gov/HYSPLIT_traj.php
I played around on the web page and realized that this effect is not isolated to backward trajectories. Here is the output from a forward simulation of 4 trajectories with 1 hour offset in between them:
Code: Select all
2 1
GFSG 16 10 19 0 0
GFSG 16 10 20 0 0
4 FORWARD OMEGA
16 10 20 0 0.000 0.000 500.0
16 10 20 1 0.000 0.000 500.0
16 10 20 2 0.000 0.000 500.0
16 10 20 3 0.000 0.000 500.0
1 PRESSURE
1 1 16 10 20 0 0 0 0.0 0.000 0.000 500.0 956.7
2 1 16 10 20 0 0 0 0.0 0.000 0.000 500.0 956.7
3 1 16 10 20 0 0 0 0.0 0.000 0.000 500.0 956.7
4 1 16 10 20 0 0 0 0.0 0.000 0.000 500.0 956.7
1 1 16 10 20 1 0 1 1.0 0.147 0.024 536.1 951.6
1 1 16 10 20 2 0 2 2.0 0.284 0.051 553.9 948.0
2 1 16 10 20 2 0 2 2.0 0.147 0.022 530.9 950.3
1 1 16 10 20 3 0 3 3.0 0.417 0.081 564.7 946.5
2 1 16 10 20 3 0 3 3.0 0.286 0.047 549.2 947.8
3 1 16 10 20 3 0 3 3.0 0.148 0.020 526.7 949.9
1 1 16 10 20 4 0 2 4.0 0.544 0.113 578.1 945.8
2 1 16 10 20 4 0 2 4.0 0.419 0.074 566.6 946.9
3 1 16 10 20 4 0 2 4.0 0.287 0.042 548.1 948.7
4 1 16 10 20 4 0 2 4.0 0.146 0.017 526.4 950.7
1 1 16 10 20 5 0 1 5.0 0.663 0.144 594.0 944.3
2 1 16 10 20 5 0 1 5.0 0.542 0.101 589.2 944.8
3 1 16 10 20 5 0 1 5.0 0.415 0.065 573.6 946.4
4 1 16 10 20 5 0 1 5.0 0.280 0.035 552.8 948.5
1 1 16 10 20 6 0 0 6.0 0.773 0.174 607.3 943.5
2 1 16 10 20 6 0 0 6.0 0.654 0.127 614.2 942.5
3 1 16 10 20 6 0 0 6.0 0.532 0.087 607.4 943.2
4 1 16 10 20 6 0 0 6.0 0.403 0.053 586.3 945.4
2 1 16 10 20 7 0 1 7.0 0.753 0.153 634.3 940.4
3 1 16 10 20 7 0 1 7.0 0.633 0.109 642.5 939.1
4 1 16 10 20 7 0 1 7.0 0.510 0.072 628.7 941.0
3 1 16 10 20 8 0 2 8.0 0.716 0.130 669.4 936.5
4 1 16 10 20 8 0 2 8.0 0.596 0.089 670.7 936.1
4 1 16 10 20 9 0 3 9.0 0.661 0.106 706.1 932.5
You can see that the first four points are one point for each trajectory and they all have the same time and the same pressure. Above that you can see what the real trajectory starting times should be so I could just correct this info myself, but to get the pressure (or any other met data parameter) I would have to extract it separately from the met data files. If this was for the last point on each trajectory it wouldn't have been such a big problem, since I could just run it a little longer and throw away the last point, but the first point of the trajectory is really the one for which the met data is perhaps the most important.
barbara.stunder wrote:The extra line break when you output all the possible meteorology is probably a formatting issue that was overlooked when we added available fields to output. I’ll look at that for our next upgrade.
Ok, great!
barbara.stunder wrote:The terrain height should be the same at the same endpoint. Please send a tdump file showing this, and the corresponding CONTROL and SETUP.CFG.
I'll get back with this when I have more time. Where should I send the files?