Giddierone
Senior Member.
can you provide coordinates, or even better a kml, with those points in?
can you provide coordinates, or even better a kml, with those points in?
EDIT: to tidy up.A at 03;54;18 at 36°49'6.75"N, 38° 8'7.43"E
B at 03;55;18 at 36°50'40.81"N 38° 8'33.97"E
C at 04;07;20 at 36°55'2.21"N 38° 6'44.48"E
Label | Description | Frame No. | Time | Coordinates | Screen cap from video | Satellite image |
1 | white blob/hill | 6604 | 03:40 | 36°43'56.13"N 38° 7'11.19"E | ||
A | curved road | 7032 | 03:54 | 36°49'6.75"N, 38° 8'7.43"E | ||
B | dark field / diagonal line | 7062 | 03:55 | 36°50'40.81"N 38° 8'33.97"E | ||
C | converging roads | 7422 | 04:07 | 36°55'2.21"N 38° 6'44.48"E |
I don't understand how to read this graph. I think a lot of us could use some more detailed explanation of what you're doing.View attachment 80310
The target appears then movement starts around frame 2100, before that there's a slight CCW rotation.
Tracking lock is acquired around 6750, which is about the middle of the slope.
If we were circling something then the rate of change of the angle would be constant.
Here, the rate of change of angle looks like what you'd expect flying in a straight line, past something that's nearly stationary. It's not perfect symmetrical, which suggests a small wind component.
Ditto. Please explain in layman's terms.View attachment 80354
If we assume both the aircraft and the UAP are moving in straigth lines at constant speed, the theoretical heading of the camera tracking the UAP would be of the form :
with A,B,C and D constants.heading over time:\[ tan(\theta(t))=\frac{y_{UAP}(t)-y_{AIRCRAFT}(t)}{x_{UAP}(t)-x_{AIRCRAFT}(t)} \newline\newline\newline \theta(t)=atan(\frac{y_{0_{UAP}}-y_{0_{AIRCRAFT}}+(v_{y_{UAP}}-v_{y_{AIRCRAFT}})*t}{x_{0_{UAp}}-x_{0_{AIRCRAFT}}+(v_{x_{UAP}}-v_{x_{AIRCRAFT}})*t}) \newline\newline\newline \theta(t)=atan(\frac{A+B*t}{C+D*t}) \]
I used gradient descent to estimate A,B,C and D from Mick's measured headings (using data from frames between 2500 and 10000) :
A 19500 B -2.91 C 4000 D 0.21
This values multiplied by the same non zero factor would also work.
With A,B,C and D you can simulate the heading over time :
View attachment 80352
There is a good match between the measured and simulated data, the constant speed hypothesis seems to be close to the reality.
A,B,C and D can be used to reconstruct the trajectory of the UAP in the aircraft frame of reference.
UAP trajectory angle = atan(b/d) = 5 degrees
View attachment 80357
I animated the scene in blender. The camera rotation is from Mick's heading data, the UAP position is calculated from A,B,C and D.
(animation sped up x100)
Left side : View from the camera
Right side : Top view, the black triangle is the camera, the sphere is the UAP
View attachment 80358
I used gradient descent to estimate A,B,C and D from Mick's measured headings (using data from frames between 2500 and 10000) :
A 19500 B -2.91 C 4000 D 0.21
The graph shows the heading of the camera, it has been calculatedI don't understand how to read this graph. I think a lot of us could use some more detailed explanation of what you're doing.
It is not. So far I've just roughly eyeballed it. It's not at all quantified other than being roughly in the right direction and speed. The change of direction does not really match. We don't know what the velocity of the drone/camera is, so that's one of several variables, along with the turn rate.It seems you're comparing two types of motion in the analysis:
-The rotation (panning) of the camera, as indicated by the changing heading—i.e., the direction the camera is pointing, in relation to "N".
-The apparent motion of the background through the frame, caused by parallax as the camera pans to keep the object centered.
From this comparison, the actual heading of the drone itself—not just the camera—is being inferred through mathematical or geometrical analysis. I understand the basic principle behind this approach, but what I don't understand is how the background motion is being quantified. Is it measured in angular displacement across the frame? If so, how exactly is that angular movement calculated or referenced?
I don't. I rotated the heading until the lines of sight converged, showing there was a partial solution for a roughly non-moving object.Still not understanding how you infer the heading of the drone itself from this. Or is that what you're trying to do?
Mick calculated the camera heading from the position of the "N" in each frame of the video.Ditto. Please explain in layman's terms.
I would particularly appreciate an explanation about this...
What is this measuring?
if we assume both the aircraft and the UAP are moving in straigth lines at constant speed, the theoretical heading of the camera tracking the UAP would be of the form :
heading over time:\[ tan(\theta(t))=\frac{y_{UAP}(t)-y_{AIRCRAFT}(t)}{x_{UAP}(t)-x_{AIRCRAFT}(t)} \newline\newline\newline \theta(t)=atan(\frac{y_{0_{UAP}}-y_{0_{AIRCRAFT}}+(v_{y_{UAP}}-v_{y_{AIRCRAFT}})*t}{x_{0_{UAp}}-x_{0_{AIRCRAFT}}+(v_{x_{UAP}}-v_{x_{AIRCRAFT}})*t}) \newline\newline\newline \theta(t)=atan(\frac{A+B*t}{C+D*t}) \]
External Quote:we have two aircraft "UAP" and "AIRCRAFT", with their motion specified as x and y components for position and constant velocity. e.g. y_UAP = y0_UAP + vy_UAP*t
Use that notation to find a formula (using Atan2) for the angle between UAP and AIRCRAFT at time (t)
Simplify that to use relative positions and velocities. Use:
A = Relative Y position
B = Relative Y speed
C = Relative X position
D = Relative X speed
A = Relative Y position
B = Relative Y speed
C = Relative X position
D = Relative X speed
I agree with this. He's looking at the apparent direction of motion of the clouds/landscape through the frame. He has inserted some lines to show the angle. The camera is clearly looking to the right at the beginning of the video.We can also tell the camera is facing to the right of the aircraft's nose. If the camera were pointing in the direction the plane was traveling, everything would be moving to the bottom of the screen in a uniform motion. We don't see that. We can tell this because the foreground objects appear to move through at different angles, and based on limitations, it has to be looking to the right.
The Reaper could be flying in a straight line, or more likely, it could be flying in a right-hand bank, with the napkin math suggesting the Reaper is flying somewhere between a 260° and 200° heading.
I used the y axis as the craft heading to fix coordinate systems issues between your data, my math and blender. I used the craft heading estimation from :I'm not immediately clear why yours needs rotating about 62.
Okay, that makes sense.I used the y axis as the craft heading to fix coordinate systems issues between your data, my math and blender. I used the craft heading estimation from :