We are actually able to figure out the current throughput and average dispatch rate based on the rate that boarding groups are being called while the ride isn't broken down.
Assumptions:
-100 people per boarding group (0 no shows)
-While ride is running, Ops is keeping the line ~the same length
-End of day data is not accurate as they are building are building a 2ish hour long line
-All seats are filled
-Any errors between no shows and empty seats will hopefully balance out over the long term.
Using the data from yesterday from thrill-data:
From ~9:05 to ~12:45 pm there didn't seem to be any slow down in calling boarding groups. In those 3 hours and 40 minutes, Groups 24 to 75 were called. That gives us [74-25*100] 4,900 people over [3*60+40] 220 minutes. For a final people per hour through put of [4,900 people/220minutes *60 min/hr]=
1,336 pph.
Because the ride releases 16 people per cycle we have [1336pph/16people per cycle] 83.5 cycles per hour. Meaning the seconds between dispatches [1/83.5*3600]
43.1 seconds between cycles.
Just for fun we can compare this to
Disneyland RotR yesterday Using data from Thrill-data once again:
Kinda hard to tell when they started speeding up to build the hour long time for their 9pm closing and 8pm last call, but it seems the speed up happened around 6pm. Therefore we will take the range from 2:00pm to 6:00pm where they called groups 43 to 84. That gives us [84-43*100] = 4100 people over 4 hours (240 minutes). The final people per hour through put of [4,100/4]=
1,025 pph.
Looking at a dispatch time [1,025/16]=64.1 cycles per hour. Meaning there are [1/64.1*3600]
56.16 seconds between cycles.
www.youtube.com
