SpudFiles

Does anyone know what the inputs for this calculator mean?

http://www.ajdesigner.com/phpprojectile ... uation.php


Does anyone know how to calculate initial velocity and acceleration of gravity (9.82? earth gravity?).

I have got velocity from GGDT.

You can calculate range with GGDT also.

GGDT>Tools>External Ballistics Calculator.
You will need to know the drag coefficient of your projectile though, the Cd value. I usually use between .2 to .25 for a golfball to get the most accurate results (in my experience). I've never calculated the range for any other projectile so hopefully someone else can help you with more Cd values.

Matt_NZ wrote:Does anyone know what the inputs for this calculator mean?

Yes, but more important is what this means: "Note: Valid only for equal initial and final elevation."

And what that means is that it's next to useless for almost any real-world projectile, because it doesn't account for drag.
If you're trying to calculate the range of a fast moving projectile over a long distance, not including drag in the equation makes the result utterly useless.

I'm confused by your post, Ragnarok. You mention a quote regarding elevation change, then relate this to drag? A formula for calculating range over different elevations can be derived using basic projectile motion equations, and it is possible to account for drag if you know the numbers... personally I take some issue with online calculators, and would rather crunch what numbers I can by hand.

saefroch wrote:I'm confused by your post, Ragnarok. You mention a quote regarding elevation change, then relate this to drag? A formula for calculating range over different elevations can be derived using basic projectile motion equations, and it is possible to account for drag if you know the numbers... personally I take some issue with online calculators, and would rather crunch what numbers I can by hand.

what he means is according to this calculator a projectile landsat the same angle it leaves the launcher, but this is only true in an absolute vacuum, in real world examples the path is changed because of the drag and other variables. It takes a little more than basic knowledge once you bring drag and other variables into the equation, if you want it to be very accurate that is.
:tongue8:

saefroch wrote:You mention a quote regarding elevation change, then relate this to drag?

Depends on whether you take elevation to mean "angle of elevation" or "altitude" - both are reasonable interpretations of the word elevation.

And as far as angles, any projectile suffering drag will land at a greater angle than it was launched at*.

*Well, it's a little more complex than that. The earth's curvature means it's possible for a very fast and very low drag projectile to land at a lesser angle than it was launched at, but I don't believe there are many things capable of that task. Lift can also result in that, but again, rare that it will happen.

and it is possible to account for drag if you know the numbers

Sure. But possible does NOT mean simple or easy.

Even I'd head for a pre-written program if I wanted to calculate trajectories. Admittedly, I wrote said program, but I think that demonstrates the situation all the better - it's hugely less effort to write the program than it is to actually try and crunch the numbers yourself.

And there's no shame in that. Computers are designed to do mathematical calculations en masse.

Ah, I thought you were referring to altitude, not angle of launch and landing. Yup, numbers are for number crunching, so if you can produce a program in a reasonable amount of time that will be used often, all the better. I've personally never found it easier to write a program than crunch the numbers for that specific scenario, but that's awesome if you're that good at programming.

And so far as drag is concerned, you'd need a wind tunnel or some sort like that to actually find the number for a homemade projectile, so I'd just use a chrono at a safe shooting range and forget about this whole discussion about calculating muzzle velocity.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras nec placerat erat. Vivamus dapibus egestas nunc, at eleifend neque. Suspendisse potenti. Sed dictum lacus eu nisl pretium vehicula. Ut faucibus hendrerit nisi. Integer ultricies orci eu ultrices malesuada. Fusce id mauris risus. Suspendisse finibus ligula et nisl rutrum efficitur. Vestibulum posuere erat pellentesque ornare venenatis. Integer commodo fermentum tortor in pharetra. Proin scelerisque consectetur posuere. Vestibulum molestie augue ac nibh feugiat scelerisque. Sed aliquet a nunc in mattis.

Again, sorry for context issue. What I meant was: "I've personally never found it easier to write a program for ONE INSTANCE than crunch the numbers for that specific scenario." I do know that creating a program to solve a problem like that multiple times is much worth it.

saefroch wrote:What I meant was: "I've personally never found it easier to write a program for ONE INSTANCE than crunch the numbers for that specific scenario."

Hitting the "Calculate" button on my range calculator sets off a cycle of many tens of thousands of calculations.

If you think it'd be easier to do the number crunching manually, rather than writing a program that will do it for you, then be my guest. Personally, given that writing the program would be less work than the manual number crunching, even if I were only doing it once - and given that I plan on using the program thousands of times - I'm writing the program.