JR
* Ace Member *
Coldness is a non issue.
How much is too much turn? I thought to use perfect frozen ropes without any turn and fade whatsoever. Not even a centimeter if I can pull it off.
30 meters wide view mandate higher resolution. We have filmed drives before during summer on a sunny day and unfortunately the camera does not have the ability to manually force short enough exposure times for unblurred images at that resolution. The camera is capable of better exposure performance in automatically controlled 250 FPS mode but I'm not sure if other parameters can be manually locked. We need to check that. We probably need to try a close up250 FPS and HD 50 FPS from farther away and if necessary 50 FPS from close up as well to determine angles. We need to come up with more sticks then but I was gonna stretch a 1 m measure vertically onto a stick in the center of image anyway for height determination help.
How many meters separation for the vertical sticks do you want? I think we need a flat area and that's gonna be a problem for close up shooting over wise unless we can find a suitable yard and use a house corner. Local DG courses with corners may not be flat enough. Meilahti may do but I'm not sure of flatness and the ground is asphalt so the disc may get lighter and panting stakes may be impossible on a shoestring budget. I'll ponder on a suitable place. For a few dozen pics at 50 FPS it's a minimum of half a second flight then and looking at your bag I also have an XD that is even slower but more nose angle insensitive so it may not be a typical disc but a flat landing is easiest to achieve with it. Half a second is easily a bunch of sticks with one meter interval. My Classic Roc is so new that it fades even on full power. Thinking of weight I need to clean up the disc after each throw to maintain a constant weight.
We really need to use a string with weight.
I looked at forecasts and no windless days are near but the figures are likely averages or top wind speeds so we may get windless periods. They usually occur in the evenings if there are calm periods in a day. If I got a portable weather station with real time and peak wind speed functions and log wind direction and speed would that be ok if we logged the results for each throw? I've been toying with the idea of getting one anyway. Seeing as finding time that suits us both and getting no wind and having light may prove to be a long time coming.
Do you need airbounces for AoA and cruise speed determinations? Those fade necessarily and so will many other nose angles. I'm not sure if I get a no fade throw uphill in steep angles but I'm also haywire when it comes to accuracy of dropping rates using sticks that are planted uphill. that's why I've been stuck on flat ground thinking.
I don't know about but mafa could about camera closeness perspective distortion. In the case he doesn't how do we eliminate that? How do we determine the minimum distortion free filming distance from the disc and the sticks?
I think the disc turning experiment may need another video session unless we manage to capture unintentional but useful to you turns.
How much is too much turn? I thought to use perfect frozen ropes without any turn and fade whatsoever. Not even a centimeter if I can pull it off.
30 meters wide view mandate higher resolution. We have filmed drives before during summer on a sunny day and unfortunately the camera does not have the ability to manually force short enough exposure times for unblurred images at that resolution. The camera is capable of better exposure performance in automatically controlled 250 FPS mode but I'm not sure if other parameters can be manually locked. We need to check that. We probably need to try a close up250 FPS and HD 50 FPS from farther away and if necessary 50 FPS from close up as well to determine angles. We need to come up with more sticks then but I was gonna stretch a 1 m measure vertically onto a stick in the center of image anyway for height determination help.
How many meters separation for the vertical sticks do you want? I think we need a flat area and that's gonna be a problem for close up shooting over wise unless we can find a suitable yard and use a house corner. Local DG courses with corners may not be flat enough. Meilahti may do but I'm not sure of flatness and the ground is asphalt so the disc may get lighter and panting stakes may be impossible on a shoestring budget. I'll ponder on a suitable place. For a few dozen pics at 50 FPS it's a minimum of half a second flight then and looking at your bag I also have an XD that is even slower but more nose angle insensitive so it may not be a typical disc but a flat landing is easiest to achieve with it. Half a second is easily a bunch of sticks with one meter interval. My Classic Roc is so new that it fades even on full power. Thinking of weight I need to clean up the disc after each throw to maintain a constant weight.
We really need to use a string with weight.
I looked at forecasts and no windless days are near but the figures are likely averages or top wind speeds so we may get windless periods. They usually occur in the evenings if there are calm periods in a day. If I got a portable weather station with real time and peak wind speed functions and log wind direction and speed would that be ok if we logged the results for each throw? I've been toying with the idea of getting one anyway. Seeing as finding time that suits us both and getting no wind and having light may prove to be a long time coming.
Do you need airbounces for AoA and cruise speed determinations? Those fade necessarily and so will many other nose angles. I'm not sure if I get a no fade throw uphill in steep angles but I'm also haywire when it comes to accuracy of dropping rates using sticks that are planted uphill. that's why I've been stuck on flat ground thinking.
I don't know about but mafa could about camera closeness perspective distortion. In the case he doesn't how do we eliminate that? How do we determine the minimum distortion free filming distance from the disc and the sticks?
I think the disc turning experiment may need another video session unless we manage to capture unintentional but useful to you turns.
JHern said:Regarding resolution vs. frame rate, maybe try out the various settings and see which gives the clearest image of the disc while capturing the flight. We will not need a huge number of data points (a few dozen is probably just fine), so frame rate may not need to be so high as you guys have in the drive videos. So this is more up to the film crew. If you want, you can also try another setting for comparison, but this is of course more work and it is cold out there! Resolution and exposure might be most important, since we would like to be able to measure the nose angle from the videos. So I would initially go for the highest res, fastest exposure, and slowest frame rate setting. But only doing it will give the experience to know for sure which is best. But right now I'm thinking that 50 fps is plenty fast enough.
You can film on a hillside, if you wish, but make sure you place the camera level so we know which way is "up" in the frames, or hang an object on a string from something in the background for orientation double-check.
Camera zoom should not add any error, so you could use it to film further from the side and hence get the camera away from danger. Aim to get some of the flight before the apex and after the apex. Of course, the more you can get, the better. The straighter the flight at apex, the better (i.e., zero hyzer at apex). You'll probably need to do a bunch of throws, and only keep the straight ones (you can delete the others where there is too much turn, they aren't useful right now).
At the apex of the flight, we're working with a relatively simple equation for apex speed. The square of the apex speed divided by the square of the cruise speed is equal to 1+(a_up/g), where a_up is the upward acceleration and g is the gravitational acceleration. So we need 2 things: the velocity at apex, and the change in upward velocity at apex. These can be obtained by getting a number of data points from the video, translating them to "x(t)" and "z(t)" (where x is the horizontal dimension along the flight path, and z is the altitude), and after fitting smooth functions to eliminate aliasing, we simply take the time derivative of x(t) at z_max to get apex speed and the second time derivative of z(t) at the apex to get the apex upward acceleration.
Recall that cruise speed is a function of nose angle. To better constrain this functional dependence (which in principle can tell us everything we need to know about the lift coefficients), we need to film throws with different nose angles (which will, in turn, give us different cruise speeds and drags).
From the x(t) data we can also take the second time derivative at the apex, which gives the lateral acceleration, a_lat (negative, since it should be slowing). At the apex, the equation is simple, m*a_lat=-F_D, where F_D is the drag force. We would have a_lat and m, allowing us to analyze drag. Again, F_D at the apex is a function of nose angle, so we need flights with a variety of nose angles.
If the throw is fairly straight, and a_up and a_lat are small, then: 1) we can almost ignore a_up in the correction for cruise speed, or at least its smallness from the fitting is not a big deal. 2) we will need a wider frame shot from the side to be sure we can resolve a_lat.
So, if you guys can turn out the following...
- Throw several flights in as straight a line as possible, and film from the side with the center of frame approximately at the apex. The more flights you get, and the more difference in nose angle on each flight, the better the data set.
- For each flight, obtain several dozen frames of the flight near apex, with a frame covering around 30 meters horizontally (this seems reasonable).
- The pixel positions on the video for the center of the disc need to be translated into lateral and upward distances (of course, I'm a fan of metric system). One can use horizontal markers placed at given increments of spacing on the ground along the flight track of the disc (try to throw over these as best you can) that can be seen from the camera angle.
- Try to do whatever adjustment you can so that we can directly measure the nose angle of the disc from the frames. I know the resolution is tough, but I think if you aren't too far away that you can't see the nose angle, but not so close that camera perspective distortion becomes an issue, then we will have a great data set.
Using this information, we should be able to distill quite a lot of essential flight data. We should be able to find (in order from expected easiest to constrain, to most difficult to constrain):
- Cruise Speed
- Lift Coefficient (derived from cruise speed, air density, mass, and diameter of disc)
- AoA for Zero Lift (from fitting the cruise speed function for various nose angles...more nose angle variety in data->better constraints on AoA for Zero Lift)
- Drag Coefficient (from lateral deceleration of the disc at apex, air density, mass, and diameter of disc)
- Change of Drag Coefficient with AoA (this requires big nose angle differences in different flights to resolve it well)
- AoA for Minimum Drag (this will be the toughest, since the system is expected to be quadratic...only a large number of flights and good variety of nose angles will allow for a robust constraint of this quantity)
The data should will also give us error estimates on our determinations.
This would be fantastic, and a great place to begin. The next step would be to examine the moments and begin analyzing the turn of the disc in flight, which will be another fun project...I need to do some more analysis of this part of the equations to find the key measurements to make.