Ok, so I put JC where 9:00 slot is and BINGO, it shows the LL wait time. Thanks @len
Great, and now… how do I choose my next LL attraction? I want to get an LL for BTMRR at 9:05 as soon as I tap for JC. When I click on the LL button it adds an “obtain LL” entry at the bottom, but I can only edit it if the LL can be obtained before 8:30
Btw, TP automatically added an LL for Philharmagic, which I don’t want
Have you moved the “obtain LL for BTMR” step after JC?
That shouldn’t happen when only using evaluate right?
I’m only using evaluate.
But yeah, good point, it shouldn’t happen - it might have been from previous optimizations.
Oh, I didn’t realize the obtain step was a physical step that had to be in alignment with the other times. Ok - let me try that.
That would make more sense.
I put the obtain LL step right after JC, but it is giving me late morning return times - which is not what I expected based on thrill data for 1/16 (I will be there 2/5). At 9:15 the return time for POC is 9:20 not 11:30?
The return time for BTM was 1:30 and even on thrill data it was 10:30 - neither of those times will work for me. I’ll try to “rope drop” BTM
At least now I know what needs to be done, so that’s progress 
Oof. Yeah that return time is not realistic. Not even on CL10 days. Len, the predicted LL return times are still too far away than what the data says. This still needs more work yet:
Do you think the fact that Splash will be closed has anything to do with it…?
No.
I did put in a ticket with this question/issue with my plans as well. I noticed the same thing regarding the inaccurate return times. I did not use Thrill Data as the comparison - just Becky’s blog post, but still, my results did not seem accurate for planning.
I got this response:
“The Genie+ return time predictions that our Personalized Touring Plan software is using are date-specific and based on a statistical analysis performed last month. We regularly analyze new data and update our forecasts, so I do not expect them to be the same as whatever was used in an October blog post. It’s also not the case that we assume the same return time forecasts for every crowd level 6 day – dozens of factors are taken into account in the date- and attraction-specific forecasts. If you optimize this plan again in a few weeks, you might again see different results.”
Yeah this can be a small problem foe longer rides. Like if I have an 8:30 TOT I would book the next LL before going in the hotel. Which would produce different times than 15 mins later when I am off the ride.
Yeah that’s another big flaw that probably can’t be fixed.
Thanks for sharing, but tbh that’s not a sufficient answer from TP when you look into the data.
This is the past month of data. The very latest RT was 11:00 at 9:20 on a CL9 day:
So this 11:35 RT would be almost impossible:
Also, if the TP predicted RT’s are all off in the same direction (over estimating), that’s a red flag.
Yeah- I figure it is pretty impossible!
I agree with that. I emailed them initially because of this issue. On a CL 6 day, obtaining MFSR at 9:15am gives me a return time of 6pm. I’ve been watching HS all week and that is very off from what I’ve seen for actuals.
I haven’t figured out yet how to get value out of the LL forecasting capability in the TP tool.
This is great feedback. I’m going to bring Fred, our statistician, into the convo. Thank you.
Great, thank you. We understand how difficult it is to get the G+ predictions,etc. mastered, but also hate to see frustrated customers of yours potentially giving up on Touring Plans all together.
There’s no doubt that some of the forecasts for Return Time will prove to be inaccurate. Accuracy improves once we have at least one full year of “typical” data. Just to be clear, 2022 was not typical.
Looking at specific examples like this is very helpful. There may be attractions that could use adjustments to the forecasting models to make them more accurate in the short term.
