"Crouching cars, hidden piano", or the theory of probability in action
I have long wanted to participate in some small, but entertaining web-experiment, tied to a full-screen interactive video broadcast, and now it happened: a client appeared, ready to sponsor it.
So we started doing http://carvspiano.ru - a project just a week long, but with a bold intention to test the Butterfly Effect in action.
')
Given:
- Beautiful black car - 1 pc.,
- No less beautiful black piano - 1 pc.,
- Video cameras - 3 pcs.,
- Projector - 1 pc.,
- Power Mac G5 to which it is connected - 1 pc.,
- Ropes with fasteners - 9 pcs.,
- Conditions under which the ropes break - 12 pairs,
- Platform with internet and relatively high ceiling - 1 pc.,
- “Probability theory and mathematical statistics” (Kremer’s textbook) - 1 pc.
Required:
- Find out how many conditions out of 12 will play,
- Understand whether the piano will fall on the car for the 6 days allotted to him (from Monday to Saturday).
All conditions are verifiable. We check them twice a day, at 11:00 and 17:00.
At the moment, the following has already happened:
1. Monday morning. If an eagle falls on a coin thrown in front of the camera, we cut the rope.
Result: tails fell, not cut.
2. Monday evening. If the number of likes to this video at the time of the check will be even, cut the rope.
Result: it was even cut.
3. Tuesday morning. If the traffic jams at the time of verification will be more than 6 points (according to Yandex.Probok), we cut the rope.
Result: traffic jams were 7 points, cut.
4. Tuesday evening. If the number of messages on Twitter with the word "piano" in the last hour at the time of the check will be even, we will cut the rope.
Result: there were 26 tweets, cut.
5. Wednesday morning. (This is what we all love very much) If Barcelona reaches the final, we will cut the rope.
Result: Chelsea exited, not cut.
At the moment, 3 ropes are shot, there are still 6.
We do not know how many of them should remain for the piano to fall. In addition, when shooting off each rope, additional stress is created - the lid can simply not withstand.
The next condition check is today at 17:00 Moscow time.
Since theoretically the piano can fall not only when we shoot the ropes, but generally at any time (the thing is, in general, not new and not very adapted for acrobatic tails), we write video from each of the three cameras around the clock.
Considering that 1 hour of video with a three megabyte bitrate weighs about 1.3 GB, by the end of the project we will have about 3 x 24 x 7 x 1.3 = 655.2 GB of video. Now it is written directly to the server (thanks to Scalaxy for this!)
Maybe after the fact we will mount a small video from it with the most important moments.
PS In many ways, this project is a first attempt at testing and checking how realistic it is to make an uncomplicated but technologically advanced website in a short time and with a limited budget.
Comments, questions and constructive criticism are welcome!
upd .: Many thanks to Habrayuser for load testing. Programmers swore, but the blow was more or less restrained. At the peak moment, there were 1,700 video connections, but the servers survived.
So we started doing http://carvspiano.ru - a project just a week long, but with a bold intention to test the Butterfly Effect in action.
')
Given:
- Beautiful black car - 1 pc.,
- No less beautiful black piano - 1 pc.,
- Video cameras - 3 pcs.,
- Projector - 1 pc.,
- Power Mac G5 to which it is connected - 1 pc.,
- Ropes with fasteners - 9 pcs.,
- Conditions under which the ropes break - 12 pairs,
- Platform with internet and relatively high ceiling - 1 pc.,
- “Probability theory and mathematical statistics” (Kremer’s textbook) - 1 pc.
Required:
- Find out how many conditions out of 12 will play,
- Understand whether the piano will fall on the car for the 6 days allotted to him (from Monday to Saturday).
All conditions are verifiable. We check them twice a day, at 11:00 and 17:00.
At the moment, the following has already happened:
1. Monday morning. If an eagle falls on a coin thrown in front of the camera, we cut the rope.
Result: tails fell, not cut.
2. Monday evening. If the number of likes to this video at the time of the check will be even, cut the rope.
Result: it was even cut.
3. Tuesday morning. If the traffic jams at the time of verification will be more than 6 points (according to Yandex.Probok), we cut the rope.
Result: traffic jams were 7 points, cut.
4. Tuesday evening. If the number of messages on Twitter with the word "piano" in the last hour at the time of the check will be even, we will cut the rope.
Result: there were 26 tweets, cut.
5. Wednesday morning. (This is what we all love very much) If Barcelona reaches the final, we will cut the rope.
Result: Chelsea exited, not cut.
At the moment, 3 ropes are shot, there are still 6.
We do not know how many of them should remain for the piano to fall. In addition, when shooting off each rope, additional stress is created - the lid can simply not withstand.
The next condition check is today at 17:00 Moscow time.
Since theoretically the piano can fall not only when we shoot the ropes, but generally at any time (the thing is, in general, not new and not very adapted for acrobatic tails), we write video from each of the three cameras around the clock.
Considering that 1 hour of video with a three megabyte bitrate weighs about 1.3 GB, by the end of the project we will have about 3 x 24 x 7 x 1.3 = 655.2 GB of video. Now it is written directly to the server (thanks to Scalaxy for this!)
Maybe after the fact we will mount a small video from it with the most important moments.
PS In many ways, this project is a first attempt at testing and checking how realistic it is to make an uncomplicated but technologically advanced website in a short time and with a limited budget.
Comments, questions and constructive criticism are welcome!
upd .: Many thanks to Habrayuser for load testing. Programmers swore, but the blow was more or less restrained. At the peak moment, there were 1,700 video connections, but the servers survived.
Source: https://habr.com/ru/post/142794/
All Articles