This is mainly for @brklinck and folks who follow the inner workings of the Optimizer software.
I made two changes to the optimizer over the weekend to better handle certain ‘evaluate only’ conditions.
- When a plan has more than one request for the same FASTPASS-enabled ride, and the user has a FASTPASS for that ride, the optimizer has to choose which ride request should use the FASTPASS. In some cases, this requires inserting “free time” into the plan.
Starting now, the optimizer will use the start time of any meals and breaks as a clue when picking which ride request gets the FASTPASS. If adding free time to one request causes the user to miss a scheduled meal or break, then that request will not get the FASTPASS.
I don’t know why I didn’t think of this before. I told the user that requested it that she was the first in almost 19 million plans to observe that that would make a nice rule.
- In the same multiple-rides-with-one-FASTPASS scenario, when one of the requests is Step 1 or Step 2 of the plan, the optimizer will NOT insert free time before those steps if the free time exceeds 15% of the user’s total time in the park.
This is a very specialized rule, primarily for Flight of Passage at Animal Kingdom.
Let me know if any questions on this.