JimParker
Bronze Member
- Joined
- Jul 4, 2006
- Messages
- 98
- Tractor
- John Deere 3320 eHydro
jk96 said:Now, the original parameters state – “as the plane moves the conveyor moves but in the opposite direction.the conveyor has a system that tracks the speed of the plane and matches it exactly in the opposite direction”
I copied this just to frame the reference...
jk96 said:As thrust is applied by the engines, they begin to push the plane forward along the MCB.
The "no fly" crowd assumes that the "and matches it exactly in the opposite direction" statement means that the MCB can run at whatever speed it takes to counteract the thrust. From their viewpoint, the plane never moves, because the infinitely accelerating MCB can create enough drag (even with the low-friction bearings) to counteract the thrust generated by the engine/propeller or jet blast.
The "will fly" crowd assumes that the MCB instead can only turn at a speed (reactive to the plane's speed) that equals the plane's speed. In other words, if the plane is moving at 10 MPH, the MCB can only move at 10 MPH in the opposite direction. They view the problem from the opposite perspective - that the MCB can only respond after there is movement. Once movement occurs, the MCB accelerates to match that speed. However, the plane is already moving, and has more thrust than drag, and therefore will continue to accelerate. If it is moving, and accelerating, it will continue to accelerate to the point where it can fly.
I may be the only one in the entire world who can see this problem from both points of view. I don't know which is correct. If I look at the problem from each perspective, I can see clear evidence to support both theories (assuming the "magic" part to be true). Of course, in the real world, with real conveyor belts, the plane would unquestionably fly, because the large surplus of available thrust when compared to the drag produced by the wheels and bearings.
As a software engineer, if I were assigned to solve this problem, I would categorically state say that the problem definition is too ambiguous to allow for a definitive solution.
Kind of reminds me of an argument I witnessed in a calculus class in college: Professor challenged a brilliant student (not me!) to mathematically prove that parallel lines were possible. Student took the bait, and used the definition of parallel lines as his proof. From his perspective - case closed. The Professor, on the other hand, countered with calculus proof starting with two lines at 90 degree angle to each other. He measured off a point about 4 inches below from the intersection, and pivoted the vertical line clockwise around that new point. As he did so, he used calculus to measure the acceleration of the point of intersection as it moved to the right. He went on to show the detailed calculus proof that this point of intersection would accelerate to infinity, but that the lines would never uncross. As long as you measured from one point in time to the next point in time, there was an increment where the point continued to accelerate at even faster speeds... but you could never show a time interval where the lines magically uncrossed.
It was an exersize in exquisite mathmatics to the two of them, and an exercise in frustration for the rest of us, who just really wanted to know how to solve the nearly impossible homework problem that started the discussion! That was the day I decided I would never again take a class where the professor was a Jesuit monk...!