Is there a READY trajectory time limit?

[aschneid]

I'm trying to calculate 240-hour ensemble trajectories using the web interface, but the last reported trajectory age in the endpoints file is always 213 hours. Is this limit intended or is it a bug?

Original job numbers were 116212, 145083, 145609, and 167489.
A test from today, with a run time of 260 hours, also has 213 hours as the last entry in the endpoints file. Job number is 155435.

[glenn.rolph]

For this particular dataset we are limited by the number of meteorological datasets in the CONTROL file because this is a daily file dataset and HYSPLIT only allows up to 10 meteorological files in the CONTROL file. We always have one day back in the CONTROL file in case the user starts at the beginning of the dataset selected and then we add 9 additional days (forward in this case). So, in this case the answer is yes, you are limited to 213 hours, however of you run the GDAS 1 degree data set you should be able to run for 240 hours.

[aschneid]

Thanks for the quick response!