Ideal Ball Trajectory Spreadsheet

[Michael Hill]

Sorry for kinda spamming CD with this post, but I calculated the drag here: http://www.chiefdelphi.com/forums/sh...ad.php?t=99485

I've just been pointing everyone there who has a question about drag. It turns out, it's pretty non-negligible as well as fairly difficult to model with a program. Your best bet is going to be to use a look-up table.

[Basel A]

Of course, finding the drag and implementing it into trajectory calculations are entirely different beasts. I've been working on it on-and-off for a couple days, but really understanding it requires calculus I'm not learning until later this semester (Multivariable). I'm just trying to get as far as I can. If you're interested in pursuing it, there's academic papers that discuss this sort of problem, I'm sure.

[Polaris395]

Did I hear someone say something about this problem being at the University level?

I think 2D kinematics will be sufficient, but hey, maybe that's just trying to build for an ideal world. I'll post this link in the other thread to make sure that people see it.

[dsirovica]

Mathematacally this is hard to compute - but you don't need to.

For the purposes of this game the key issue is repeatability of the shot. So you can calibrate the system to hit the "kill zone" and as long as it is repeatable - who cares about the math (again for the purpose of this game).
However you wil need to place your robot at the same place and orientation every time. Or a set of predefined positions.

Repeatability is tricky though, because you need to place minimization of errors as a key design rule for all you do. We hear for example that the weight of the balls is within a 10% range. When faced with an item that has such an inbuilt error, one needs to design mechanisms that reduce the significance of that error on the outcome.That is indeed what design engeneers do all the time, and there are multiple ways of doing it.

Good discussion,
Dean