219 s
searchs 219 asearchcsearch Mona osearchd View 3 Forum 4 Buy i Forum fMona2 Buy od Www 3 Mona 4. Cfm n 219 o9 Buy h Mangosteen F Mangosteen r
m Cfm ss Vie a Mona csearchisearche Mangosteen r1328275757968_Rh Mangosteen sa Forum chrsearchB Mangosteen y Cfm a View F1327998654226_Rrsearchm Mangosteen i
nsearch Forum a Buy c Mangosteen lsearchtsearch t Cfm e Mangosteen s Buy o
esearch R Mona s Mangosteen vsearchrsearchr Mangosteen n)
m = (y2 - y1) / (x2 - x1)
How the transcoding engine works:
Given the longitude x, we find 2 corners of the map where x lies between the longitude counterpart of its Geocode location. (If x does not lie between any 2 corners' longitude values, then the target location is outside of our map)
We then find where x lies in relevance to the longitude values of these 2 corners.
ratio = (corner1 - x) / (corner2 - corner1)
Using the slope north and south slope, we find the y-intercept of each of these longitude lines using the following equation in slope intercept form:
y = mx + b (x and y are onionmap coordinates)
Once we solve for b for each corner (corner1_b, corner2_b), we apply the ratio to our y-intercepts and solve for target_b.
ratio = (corner1_b - target_b) / (corner2_b - corner1_b)
Once we have solved for target_b we plug target_b and the north and south slope m into our equation:
y = mx + b
and we have obtained the equation for our first line longitude_line.
Next we repeat this same process to find our latitude_line by using our east and west slope, and the latitude counterparts of our geocode data.
Once we have solved for latitude_line and longitude_line, we find the intersection of these 2 lines by solving for y and x.
First we solve for x:
(m1 * x) + b1 = (m1 * x) + b2
Then we solve for y:
y = m1 * x + b1 OR
y = m2 * x + b2
We now have our (x,y) pair.
Increase accuracy: so far we take 4 points, corner points, for the translation. If we take 4 more additional points, we can increase accuracy.
The translation for OSAT code to Geocode is a reverse process of the above process.
How the transcoding engine works:
Given the longitude x, we find 2 corners of the map where x lies between the longitude counterpart of its Geocode location. (If x does not lie between any 2 corners' longitude values, then the target location is outside of our map)
We then find where x lies in relevance to the longitude values of these 2 corners.
ratio = (corner1 - x) / (corner2 - corner1)
Using the slope north and south slope, we find the y-intercept of each of these longitude lines using the following equation in slope intercept form:
y = mx + b (x and y are onionmap coordinates)
Once we solve for b for each corner (corner1_b, corner2_b), we apply the ratio to our y-intercepts and solve for target_b.
ratio = (corner1_b - target_b) / (corner2_b - corner1_b)
Once we have solved for target_b we plug target_b and the north and south slope m into our equation:
y = mx + b
and we have obtained the equation for our first line longitude_line.
Next we repeat this same process to find our latitude_line by using our east and west slope, and the latitude counterparts of our geocode data.
Once we have solved for latitude_line and longitude_line, we find the intersection of these 2 lines by solving for y and x.
First we solve for x:
(m1 * x) + b1 = (m1 * x) + b2
Then we solve for y:
y = m1 * x + b1 OR
y = m2 * x + b2
We now have our (x,y) pair.
Increase accuracy: so far we take 4 points, corner points, for the translation. If we take 4 more additional points, we can increase accuracy.
The translation for OSAT code to Geocode is a reverse process of the above process.
Technology Product:
The following are the initial ‘working’ product in the form of computer software code. Just like every other software, this product will evolve with the time.
Excerpt of Geocode.php (class)
<?php
/*
Geocode class
Usage:
if(!is_object($Geocode)) $geocode = new Geocode($CITY);
*/
//Requirements:
class Geocode {}
}
public function geocode2omcode($latitude,$longitude){}
elseif($latitude < $this->om_ul_lat){}
else{}
// Convert longitude to om code
if($longitude < $this->om_ll_long){}
elseif($longitude < $this->om_ur_long){}
else{}
// Find intersection of the 2 lines
$x = ($b_long - $b_lat) / ($this->slope_lat - $this->slope_long); // (this->slope_long * x) + $b_long = ($this->slope_lat * x) + $b_lat
$y = (-1)*(($this->slope_lat * $x) + $b_lat);
if($this->debug) echo "<br>".$x.",".$y;
$omcode[0] = $x;
$omcode[1] = $y;
return $omcode;
}
else{}
}
?>
Click HERE for Cranky’s 3D-izer!
If you’re curious as to how I made it and how it works, read on.
Get your red and cyan 3D glasses out. I was at Ed Park’s place and he had a pair of red / cyan 3D glasses along with a 3D drawing notepad.Cool. In theory, I understood how 3D glasses work… but I wanted to experiment with it more. So Ed kindly let me borrow the notepad and the glasses.
So, when you look at a 3D image, there are 2 images… one blue (or cyan), one red. The glasses cancel one of them out on each eye, tricking your brain’s depth perception.I decided to write software that can 1) take one photo and make it 3D glasses compatible and 2) take two photos that were taken side by side and combine them as one 3D glasses compatible photo.
Sounds do-able… Why not? I first took a photo of my parents’ dog Einstein
I love PHP-GD. You can do wonders with it. So I used a GD image filter with the IMG_FILTER_COLORIZE option and I was able to apply the appropriate filters needed to make this work.
Now, going back to Ed’s notepad…. there’s a scribble on it. When I look at it right-side up, the scribble looks like it’s floating on top of a grid of lines. When I flip the notepad upside down, the scribble looks like it’s underneath the grid. Interesting. The red filter is on my left eye, so if the red image is shifted to the right of the cyan image, it pops in. If the red image is shifted to the left of the cyan image, it pops out!
This image pops in and
this image pops out.
To be honest, this is kind of boring because the “anchor” is the dust on my laptop screen…. and the 2nd image, in order for it to look popped out, you need to stand back from your screen.
Now, what if I took 2 photos (the way 3d movies are filmed with 2 lenses) and I applied a red filter on one and a cyan filter on the other? Wouldn’t that be much better?Taking these photos, I tried it out.
Now you need to step back from your computer screen with your 3d glasses in order for it to look good. I made the mistake of taking a photo of an object much too close.
If you see doubles, step back. Way back. Why do you see doubles? Well, focus on your computer screen and put your finger close to your eyes. You see double right? Apparently it’s not possible to make the image pop out SO close to your face that it can kiss you…. That is, without you seeing double. Now, if I shift the photos so the red and blue image overlap at the bottle, that becomes the focal point. Everything in front of it pops out and everything behind it pops in.
I made the focal point the plant on my desk. Pretty cool. Go ahead and use the 3d-izer to 3d-ize your photos. Just remember to take photos of objects that are somewhat distant. It also looks better on a bigger screen.
Cranky’s 3d-izerEnjoy. Here’s the source code:
if(is_uploaded_file($_FILES['leftphoto']['tmp_name'])){} else{} $glasses = $_POST['glasses']; $poptype = $_POST['poptype']; if($leftphototype === "image/jpeg" || $leftphototype === "image/pjpeg"){} elseif($leftphototype === "image/png" || $leftphototype === "image/x-png"){} elseif($leftphototype === "image/gif"){} unlink($leftphoto); if($type==="double") unlink($rightphoto); if($glasses === "redblue") $gvalue=0; elseif($glasses === "redcyan") $gvalue=255; imagefilter($bim, IMG_FILTER_COLORIZE, 0, $gvalue, 255); imagefilter($rim, IMG_FILTER_COLORIZE, 255, 0, 0); if($type==="double") $offset = 0; elseif($poptype==="in") $offset = -50; else $offset = 50; imagecopymerge($rim,$bim,$offset,0,0,0,imagesx($bim),imagesy($bim),50); header('Content-Type: image/jpeg'); imagejpeg($rim); imagedestroy($rim); imagedestroy($bim); }I’m working on building my first robot, but I’m still trying to decide all of its functions. What I do know is this:
1) It will be pretty primitive.
2) It will have wheels or treads instead of feet.
3) I’m going to try to make it look cuteSo I’m testing out its eyes right now. They look like eyes, but technically it’s a ear and a mouth. My robot will use echolocation (like bats) to be aware of its surroundings and avoid obstacles.
One side transmits a high frequency wave and the other waits for it to return. The timing allows us to determine the distance from a solid object.
This module was so cheap on ebay, I was a bit skeptical as to how well it would work. It works great. It’s surprisingly accurate. I tested it with this short snippet of code:
#include <Ultrasonic.h> Ultrasonic ultrasonic( 12, 13 ); void setup() {} void loop() {}Automatic Toilet Flusher?
If I wanted to, I could add something like this in the code:
distance = ultrasonic.Ranging(INC); if(distance<DISTANCE_TO_WALL){} else{} counter=0; }… and hook up a servo to the arduino and it would be an automatic toilet flusher that flushes the toilet after you step away from the toilet. The commercial sensors you see on toilets nowadays use IR sensors rather than ultrasonic sensors like this one… but this ultrasonic sensor, using my code, would eliminate the annoying random premature flushes (while placing your toilet seat cover on the toilet seat, or while you’re sitting on your toilet). But to be honest, I don’t want my robot’s eyes to sit atop a toilet all day. No. I wouldn’t do that to him/her.
In April 2011, my buddy Eugene launched a website called aWww Buy Mona Vie Mangosteen Juice Mangosteen Cs Forum View Cfm 219 Buy Mona Vie Mangosteen Juice cranklin.comh d Health i Buy Mona Vie Mangosteen Juice Vie Buy Mona Vie Mangosteen Juice nWww Buy Mona Vie Mangosteen Juice Mangosteen Cs Forum View Cfm 219 Buy Mona Vie Mangosteen Juice cranklin.comy Buy Mona Vie Mangosteen Juice Buy Mona Vie Mangosteen Juice Acai Buy Mona Vie Mangosteen Juice