@TimberWolfAu - wrote:
"Now, for me, I have some quick questions;
- Just looking through your Apollo 16 extract to start with, why are there frames missing? I've counted at least 9, might have been 12, fames that you don't have but I do, split in various locations across two to three seconds of footage.
- Where is your margin of error analysis? The footage is very pixelated when you try and nominate a point to measure from, either as a reference point or for determining the actual distance covered. Looking at frames I have pulled, this can be as much as ±3 pixels, and given (for me) the LM rises 55 to 56 pixels in 29 and 30 frames, this can be an error of almost 10% in the distance travelled. How have you accounted for this?
(For reference, I downloaded the Apollo 16 video you linked to and pulled 145 frames from about the 12s mark (just before we see evidence of the ignition being initiated ie the shift in the mylar of the descent stage)
"
===
I just re-reviewed my work, and get the same result on Frame Captures images. Here's the result:
1. My Google Drive was missing frames 013 and 017 (but I had these locally, and neither were part of the 10 FPS analysis, as they were intermediates).
FIXED -- I added them back.
2. After 1.3 seconds, I started grabbing only every 3rd frame (10 FPS equivalent) -- by this time, it was so blurry that the intermediates were of less Use.. I have them, just didn't name them with the "##" name or upload them. Do you think these are needed for a valid analysis, I'll copy 'em up if you think so.
====
TIMING -- if you look at the 30 FPS frames, you'll notice that 020.png is the FIRST frame where the YouTube timer turns to "14 seconds"... and then it changes to "15 seconds" EXACTLY on the frame named "120.png"... indicating a accurate 30 FPS frame rate, where each of these frames shows motion.
===
If you still notice some discrepancy, please name at least ONE specific frame that you think I'm missing (show the image)...
NEXT -- I'm going to redo the Image Motion Analysis, and show my reference points, side by side, with pixel measurements.
I'll upgrade my spreadsheet to show the impact of the tolerances defined.
For this exercise, I'm only going to examine the first 1 second of Apollo 16 launch. We can do more later.