Post by xpoq47 on Dec 25, 2011 21:22:24 GMT -5
Yes, there are various skywatch efforts, as well as meteor-tracking networks, and even hobbyists who use software like UFOCapture with their own cameras and computers, etc. And there was Project Twinkle, which used the best equipment available in 1950 and was technically based on a good idea (since it could produce good motion pictures of those mysterious things in the sky and have valuable theodolite data printed on each frame) but never released the results to the public. And we wind up with zilch from Project Twinkle, zilch from the meteor-tracking networks (which could be producing solid evidence of UFO activity), and various pictures going out on the Web that even if legit are soiled by the thick smokescreen of hoaxes.
I would like to make a proposal that could avoid the high cost of theodolites yet produce zoomed, synchronized pictures in sets of three (for triangulation) all stamped with time, azimuth, and elevation data, where three backyard cameras at a time a few miles apart can be controlled by a single operator anywhere on-line, thus avoiding the chaos of having three people trying and probably failing to coordinate their efforts to get zoomed-in pictures of the same object at the same time. The main key here is that the software on the operatorfs computer displays the three views in low resolution of what is in frame of the three cameras, and then the operator can use the mouse to move the point where three on-screen lines intersect (which represents the position in the sky where the operator thinks the object is). The bottom point of each line represents the location of one camera. The shape of the pyramid figure formed by the three lines changes as the operator moves the apex, and the framing of the object in the three on-screen viewports changes accordingly.
Aligning the object in all three viewports is the goal of moving the apex of the pyramid, in response to which the control computer sends a few bytes of aiming data to the computer at each camera station (in someonefs back yard), which in turn sends signals to its camerafs motorized pan/tilt mount (much cheaper than a theodolite) then sends a low-resolution, monochromatic image back to the control computer. Once all three images are in frame to the operatorfs satisfaction, itfs time to zoom. The zoom command is sent to all three camera stations, and each starts recording, saving high-resolution images on its own local computer rather than wasting time transferring them over the Internet (or an intranet). Each image is saved locally with data stamps for time, azimuth, and elevation.
Recording of video continues as long as the object is in frame of all three cameras, accompanied by valuable data that can be used to determine the objectfs location, size, and altitude, in addition to shape and details that can be gleaned from the pictures themselves. And if the object is moving slowly out of frame, the operator can still attempt to pan the cameras to stay with it.
If the object makes a sudden jump of considerable distance, the operator (with a single keypress) can order all three cameras to zoom out as they continue data-stamped recording. If the object is still in frame, although speed of the jump is hard to determine, at least there will be hard data on how far the object traveled, and the system may be able to pick up other point-to-point jump data while still zoomed out, which would actually be superior movement data (unencumbered by zoom delay).
If the object jumps out of frame, the operator may try to catch it, by activating (with a single keypress) a feature that orders the three cameras to search in different directions until one picks it up, whereupon the other two cameras search along the line represented by the pan & tilt data from the first camera until the object is again in frame, whereupon the operator can return to pyramid-based control and try for further video capture.
After an event, team members can examine the high-resolution video and see if the object looks otherworldly. If it does, scientifically valid evidence has been gained.
Verification of the system and operator practice would be done by targeting ordinary airplanes or balloons at first. Once the system is operational, anything captured that looks like a secret military craft should not be reported, nor should a black helicopter hoisting a cow. The target is so-called flying saucers, daylight discs in particular.
A team for one location would consist of three people who live in the area (each of which would have to have his/her own camera and the specified camera mount plus an outdoor table for it that doesnft move, so that the camera can be kept indoors when not in operation because of bad weather, etc.) plus operators who can be located far away and are willing to devote one hour at a time in shifts to monitor the images (each of which would have to only have a computer with the operator software installed and some practice using it)
How to proceed
First, some UFO organization may consider the proposal then start by gathering information on those motorized pan/tilt camera mounts in order the select the best model for the job. One criterion would be open access to its control codes, which would be used by the software for the camera-station computers.
Next, the software has to be developed. In addition to the features already described, it should have a simulator mode to allow each operator before starting to pull shifts with the project to get some practice, where the software simulates a target and the operator can gain skill in trying to keep the target in range while the program also simulates delays caused by operation of the camera mounts and network transfer time.
The software would be, of course, free and open-source, developed by volunteers. Once it is developed, prospective team members would be able to download and try it out in Simulator mode to get a taste for the project before deciding whether or not to join. If the software works nicely, that can help promote participation.
Then, once a team is assembled, the member at each camera station would have to (unless someone has a better idea) set up a cheap wooden table outdoors and purchase and install the specified model of motorized pan/tilt mount on a piece of plywood with a wooden frame that can hug the tabletop, so that it can be set in place in exactly the same position each time it is taken outdoors for operation. The location of the camera on that table has to be determined with a map or GPS device. Its exact location and orientation of pan home (deviation from true north) have to be registered with the system.
The three camera stations should be a few miles apart, perhaps surrounding Los Alamos or Sandia (for the clear skies and possible interest to the targets). Once set up, the project could run for as long as it takes. Once a target has been captured and verified, weather data should be obtained and an FOIA request for radar data submitted immediately. Captured frames with acquired data could then be published, and the weather and radar data, as well as a description and even the source code for the software, could be made available for examination
Once the first location is set up and running, if others are interested in forming teams in other locations, having the software available and having determined the model of mount to use, plus experience gained at the first location, should make it easier. But capturing just one daylight disc from three angles with data stamps plus weather and radar data should be enough to make a solid case.
This rough sketch of the operator screen is in color, but monochrome would be better for fast data transfer.
i299.photobucket.com/albums/mm309/LCARS24/Twinkle2.png
I would like to make a proposal that could avoid the high cost of theodolites yet produce zoomed, synchronized pictures in sets of three (for triangulation) all stamped with time, azimuth, and elevation data, where three backyard cameras at a time a few miles apart can be controlled by a single operator anywhere on-line, thus avoiding the chaos of having three people trying and probably failing to coordinate their efforts to get zoomed-in pictures of the same object at the same time. The main key here is that the software on the operatorfs computer displays the three views in low resolution of what is in frame of the three cameras, and then the operator can use the mouse to move the point where three on-screen lines intersect (which represents the position in the sky where the operator thinks the object is). The bottom point of each line represents the location of one camera. The shape of the pyramid figure formed by the three lines changes as the operator moves the apex, and the framing of the object in the three on-screen viewports changes accordingly.
Aligning the object in all three viewports is the goal of moving the apex of the pyramid, in response to which the control computer sends a few bytes of aiming data to the computer at each camera station (in someonefs back yard), which in turn sends signals to its camerafs motorized pan/tilt mount (much cheaper than a theodolite) then sends a low-resolution, monochromatic image back to the control computer. Once all three images are in frame to the operatorfs satisfaction, itfs time to zoom. The zoom command is sent to all three camera stations, and each starts recording, saving high-resolution images on its own local computer rather than wasting time transferring them over the Internet (or an intranet). Each image is saved locally with data stamps for time, azimuth, and elevation.
Recording of video continues as long as the object is in frame of all three cameras, accompanied by valuable data that can be used to determine the objectfs location, size, and altitude, in addition to shape and details that can be gleaned from the pictures themselves. And if the object is moving slowly out of frame, the operator can still attempt to pan the cameras to stay with it.
If the object makes a sudden jump of considerable distance, the operator (with a single keypress) can order all three cameras to zoom out as they continue data-stamped recording. If the object is still in frame, although speed of the jump is hard to determine, at least there will be hard data on how far the object traveled, and the system may be able to pick up other point-to-point jump data while still zoomed out, which would actually be superior movement data (unencumbered by zoom delay).
If the object jumps out of frame, the operator may try to catch it, by activating (with a single keypress) a feature that orders the three cameras to search in different directions until one picks it up, whereupon the other two cameras search along the line represented by the pan & tilt data from the first camera until the object is again in frame, whereupon the operator can return to pyramid-based control and try for further video capture.
After an event, team members can examine the high-resolution video and see if the object looks otherworldly. If it does, scientifically valid evidence has been gained.
Verification of the system and operator practice would be done by targeting ordinary airplanes or balloons at first. Once the system is operational, anything captured that looks like a secret military craft should not be reported, nor should a black helicopter hoisting a cow. The target is so-called flying saucers, daylight discs in particular.
A team for one location would consist of three people who live in the area (each of which would have to have his/her own camera and the specified camera mount plus an outdoor table for it that doesnft move, so that the camera can be kept indoors when not in operation because of bad weather, etc.) plus operators who can be located far away and are willing to devote one hour at a time in shifts to monitor the images (each of which would have to only have a computer with the operator software installed and some practice using it)
How to proceed
First, some UFO organization may consider the proposal then start by gathering information on those motorized pan/tilt camera mounts in order the select the best model for the job. One criterion would be open access to its control codes, which would be used by the software for the camera-station computers.
Next, the software has to be developed. In addition to the features already described, it should have a simulator mode to allow each operator before starting to pull shifts with the project to get some practice, where the software simulates a target and the operator can gain skill in trying to keep the target in range while the program also simulates delays caused by operation of the camera mounts and network transfer time.
The software would be, of course, free and open-source, developed by volunteers. Once it is developed, prospective team members would be able to download and try it out in Simulator mode to get a taste for the project before deciding whether or not to join. If the software works nicely, that can help promote participation.
Then, once a team is assembled, the member at each camera station would have to (unless someone has a better idea) set up a cheap wooden table outdoors and purchase and install the specified model of motorized pan/tilt mount on a piece of plywood with a wooden frame that can hug the tabletop, so that it can be set in place in exactly the same position each time it is taken outdoors for operation. The location of the camera on that table has to be determined with a map or GPS device. Its exact location and orientation of pan home (deviation from true north) have to be registered with the system.
The three camera stations should be a few miles apart, perhaps surrounding Los Alamos or Sandia (for the clear skies and possible interest to the targets). Once set up, the project could run for as long as it takes. Once a target has been captured and verified, weather data should be obtained and an FOIA request for radar data submitted immediately. Captured frames with acquired data could then be published, and the weather and radar data, as well as a description and even the source code for the software, could be made available for examination
Once the first location is set up and running, if others are interested in forming teams in other locations, having the software available and having determined the model of mount to use, plus experience gained at the first location, should make it easier. But capturing just one daylight disc from three angles with data stamps plus weather and radar data should be enough to make a solid case.
This rough sketch of the operator screen is in color, but monochrome would be better for fast data transfer.
i299.photobucket.com/albums/mm309/LCARS24/Twinkle2.png