posted on Sep, 3 2015 @ 02:13 PM
originally posted by: IsaacKoi
@WeAreOne : Could you briefly explain the "technique / program" you mention you developed. Apart from usefulness in relation to the remaining columns
(some of which are unlikely to be essential), I'd be interested to learn any faster techniques since they potentially could be applied to other
Sure! The technique / program is nothing too advanced, after all it really came down to manual entry and pressing buttons. The first thing I did was
create a program that would load the spreadsheet for editing, and load the frame images in the same application, and any time I clicked on a specific
row of that spreadsheet, or pressed the UP or DOWN keys on the keyboard, it would display the frame image corresponding to that row. On my quick
computer I could hold the DOWN arrow and flip through the frames and the spreadsheet simultaneously almost as fast as the video, probably around 30
frames per second, with no lag.
After setting up the ideal environment I created two different tools. Since the coordinates of the aircraft are sequential, the first tool I developed
simply stored the current value in a variable (in memory) and any time I pressed the NumPad5 button on my keyboard it would input that value into the
correct column on the spreadsheet, and move to the next row (and load the next image). Any time the value increased or decreased (which on average
was about every 10 frames) I would simply press either NumPad8, or NumPad2 to increase or decrease the value in memory, then again press NumPad5 to
enter the new value. Using this technique was quite fast...
But I developed a faster way. Instead of inputting the value every frame, frame by frame, I created a tool that would "fill in the blanks" so to
speak, and I would simply only input values when they visibly changed. So I would hold the down arrow key on my keyboard, and flip through the
frames, and when I noticed the value changed I would press NumPad5 button to enter the new value in that row, and a function would go back and fill in
the empty rows above with the previous value automatically , instantly. So for example, if I input the value 10 for frame 1, and by frame 25 the
value changed to 11, I would enter the 11 in frame 25, and it automatically input value 10 in frame 2 through 24.
So essentially I was only inputting values when I noticed or detected a change, and the app would do the rest. Which was a much faster technique.
I can't imagine how you guys were doing it.
edit on 3-9-2015 by WeAre0ne because: (no reason given)