I’m trying to cluster back trajectories (120-h, 500 m agl, Traj skip=1) in Hysplit4 but the program assigns more than 90 % of the calculated BT to cluster #0 (WARNING:” traj not long enough; traj not clustered” in the CMESSAGE file). I have tried running the cluster analysis several times and I have tried using a few different sets of trajectory files
Thanks for the attention, hope someone helps me
Cluster Problem
-
- Posts: 451
- Joined: November 9th, 2012, 4:23 pm
- Registered HYSPLIT User: Yes
Re: Cluster Problem
Please check your trajectories to verify they are at least 120-h long.
Does it work with that same set of trajectories for a shorter duration such as 24-h?
Does it work with that same set of trajectories for a shorter duration such as 24-h?
Re: Cluster Problem
yes, trajectories are 120-h long.
It doesn't work also with shorter trajectories
It doesn't work also with shorter trajectories
-
- Posts: 451
- Joined: November 9th, 2012, 4:23 pm
- Registered HYSPLIT User: Yes
Re: Cluster Problem
Please send a subset of the trajectories with a case that fails so I can reproduce the issue.
Re: Cluster Problem
Attached a subset of the trajectories used
thanks
thanks
-
- Posts: 451
- Joined: November 9th, 2012, 4:23 pm
- Registered HYSPLIT User: Yes
Re: Cluster Problem
I don't see the attachment. Please try again.
Re: Cluster Problem
Please, see a new attached
thanks
thanks
- Attachments
-
- fdump_2.zip
- (722.15 KiB) Downloaded 11882 times
-
- Posts: 451
- Joined: November 9th, 2012, 4:23 pm
- Registered HYSPLIT User: Yes
Re: Cluster Problem
I just opened several files and none of them are for 120-hours. For example
.fdump14060612 - 8 hours
.fdump14060412 - 9 hours
.fdump14050100 - 0 hours
.fdump14060218 - 3 hours
Hence if you are clustering for 120 hours, none of these I looked at would be used.
.fdump14060612 - 8 hours
.fdump14060412 - 9 hours
.fdump14050100 - 0 hours
.fdump14060218 - 3 hours
Hence if you are clustering for 120 hours, none of these I looked at would be used.