With Evaluate, how do you get it to forecast a bunch of LL ‘Obtains’?
2 Likes
I haven’t tried the new features yet, so if anything I would just do a break or snack if there’s a step I need to squeeze in.
You may want to post your question on one of those blogs…
We plan to do this with Evaluate. To your point, we first wanted to see how complicated the UI got with what we had. Let’s see how this goes and we’ll go from there.
5 Likes
Sharing updates and info here from Len…
8 Likes
That part isn’t the issue; the problem is that it uses a predicted standby wait time for an attraction I will be using LL for. Thus It will show 52 min wait when it should be 6 min. I haven’t been able to figure out how to make TP factor in the use of the LL.
3 Likes
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
2 Likes
Have you moved the “obtain LL for BTMR” step after JC?
That shouldn’t happen when only using evaluate right?
1 Like
I’m only using evaluate.
1 Like
But yeah, good point, it shouldn’t happen - it might have been from previous optimizations.
1 Like
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.
2 Likes
That would make more sense.
1 Like
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 
2 Likes
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:
3 Likes
Do you think the fact that Splash will be closed has anything to do with it…?
2 Likes
No.
2 Likes
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.”
5 Likes
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.
4 Likes
Yeah that’s another big flaw that probably can’t be fixed.
3 Likes