Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Robotic Camera Extension Takes Gigapixel Photos

Posted by timothy on Sat May 17, 2008 01:31 PM
from the ale-and-hugin-together-robotically dept.
schliz writes "Scientists at Carnegie Mellon University have developed a device that lets a standard digital camera take pictures with a resolution of 1-gigapixel (1,000-megapixels). The Gigapan is a robotic arm that takes multiple pictures of the same scene and blends them into a single image. The resulting picture can be expanded to show incredible detail."
+ -
story

Related Stories

[+] 26 Gigapixel Photo Sets New World Record 113 comments
FrenchSilk writes "The largest gigapixel photograph ever created with a DSLR camera was made by A.F.B. Media GmbH in Dresden, Germany. 1655 images, each 21.6 megapixels in size, were taken with a Canon 5D Mark II and a 400 mm lens over a period of 176 minutes. The images were stitched on a 16 processor system with 48GB of main memory, taking 94 hours to create the final result. The interactive view can be found here."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Not so novel (Score:5, Interesting)

    by Anonymous Coward on Saturday May 17 2008, @01:34PM (#23446944)
    Seth Teller at MIT EE was doing this 8 years ago. Check out his Cityproject.
    • Re: (Score:3, Insightful)

      How true. Another example of people in computer vision with no ideas who are stealing from people who don't sell themselves well enough. What a sad subject computer vision has become. See Adam Kropps paper with Seth Teller here on spherical mosaics. [mit.edu]
        • Re:Not so novel (Score:5, Insightful)

          by 2.7182 (819680) on Saturday May 17 2008, @02:18PM (#23447226)
          Well its a good idea to check before they submit for a patent, since there is prior art.

          Also, the MIT work is well known to anyone in this area. It's not that hard to google some of the keywords and get the MIT page. The CMU people either knew and ignored it, or they simply didn't do what most of the scientists at their institution usually do, which is read the standard conference papers in computer vision, and browse the web (just a little!!). It's not as if the MIT work was published in some obscure place.
        • by Clover_Kicker (20761) <clover_kicker@yahoo.com> on Saturday May 17 2008, @06:06PM (#23448636)
          You know what they say, a month in the lab can often save an afternoon in the library.
    • Re: (Score:3, Interesting)

      I believe that Steve Mann [wikipedia.org] of wearable computing fame was the first to create an algorithm for photo stitching [wearcam.org].
    • We Did It in 1990 (Score:5, Interesting)

      by Doc Ruby (173196) on Saturday May 17 2008, @02:44PM (#23447368) Homepage Journal
      I worked for a SF area startup in 1990 that produced and sold cameras for "digital prepress" [accessmylibrary.com] (later called "desktop publishing", and now just "publishing" ;) that had the highest resolution around, to compete with drum scanners [wikipedia.org] that were then the expensive industry standard equipment.

      We took a 512x512 Hitachi video sensor with a 2x2 C-M/Y-K mask repeated over it, for initial 1Kx1Kx40bit images that we derived from DSP on the intensity of the color-masked pixels. Then we physically stepped the sensor through 8x8 subpixel shifts, subsampling each pixel 64x. We ran the resulting 320MB raw composite files through a bank of multiple 25MFLOPS DSPs (interconnected and logic-accelerated by a fat FPGA) to produce 4Kx4Kx36bit 72MB files. In 1990 that was an awesome achievement.

      We poured dramatic engineering work into that platform, which replaced a $150K drum scanner with a $30K PC (on DOS or Win3.0, or plus optional $5K Mac with its GUI including Photoshop 1.0). We had to deal with DSP for micropositioning the video sensor quickly (using feedback data from a laser/interferometer), with new color spaces (I was part of the JPEG org that produced the image format), with custom interconnects at blazing bandwidth, with parallel multiprocessing at then-supercomputer speeds written in C on DOS, and even with the physics of the light variably distorted by turbulence in the air between the camera and scanned slides, heated by the hot lights necessary for exposures fast enough to allow 64 frames and rescan before the sensor wiggled.

      All for a 16Mpxl camera that's now beaten by big sensors on handheld consumer devices for under $2K (in 2008, not 1990, dollars). But I can proudly say that we beat them by almost 20 years.
        • Re: (Score:3, Interesting)

          Not really, though we did have a Lenna slide kicking around. We primarily used a Kodak test slide of color bars/wheels and greyscale gradients, and one image of a European/American looking blonde on Kodak slide and one image of a young Japanese looking woman on Fuji slide. We had different colorspaces for US/Europe and Japan, because Fuji film had a larger green dynamic range supposedly because Japanese people have more acute green-band vision (though I've never independently verified that).

          Once the camera
  • ALE (Score:5, Interesting)

    by pipatron (966506) <pipatron@gmail.com> on Saturday May 17 2008, @01:40PM (#23446988) Homepage
    Also check out Anti-Lameness Engine, http://auricle.dyndns.org/ALE/ [dyndns.org] which does exactly the same thing, but you have to provide your own arm.
  • by grimJester (890090) on Saturday May 17 2008, @01:47PM (#23447024)
    Is there any superresolution software good enough that I could, for example, take twenty blurry pics with my phone and merge them to a single sharp one?
  • After all, they do it all the time on CSI.
  • Wow (Score:2, Insightful)

    So, basically it can do the exact same thing as Photoshop, except with the added expense and complications of a robotic arm. Way to go, Carnegie Mellon.
    • So, basically it can do the exact same thing as Photoshop, except with the added expense and complications of a robotic arm. Way to go, Carnegie Mellon.

      Which is rather ironic since the Photomerge routine in Photoshop CS3 is quite adept at taking multiple hand shot images and stitching them together. Traditionally, photographers have used leveling tripods and paid careful attention to exposures. While this can lead to better results than a hand shot and stitch, the latter is awfully good. The intelligenc

  • by grimJester (890090) on Saturday May 17 2008, @01:53PM (#23447076)
    Here [cmu.edu]
  • by duguk (589689) <dug@f[ ].co.uk ['rag' in gap]> on Saturday May 17 2008, @01:54PM (#23447084) Homepage
    From TFS:

    take pictures with a resolution of 1-gigapixel (1,000-megapixels)

    Where's the other 24 megapixels? ;)

    caveat: yes, i know. don't start. it was a joke. don't link to wikipedia to explain, besides; xkcd explained it better. [xkcd.com]
  • Some Links (Score:4, Informative)

    This is a pretty cool project, and I actually saw it when I was at CMU a bit ago (and was wondering what the hell it was).

    There's a CMU press release [cmu.edu] about it.
    The site with all the pictures is http://www.gigapan.org/ [gigapan.org]
    You can see the hardware here [charmedlabs.com].

    The only problem with this, and any other multi-picture stitching, is that you get obvious stitching problems when there is any movement in the scene, like the trolley in the middle of this scene [gigapan.org].
  • by Manip (656104) on Saturday May 17 2008, @02:06PM (#23447168)
    I think this just proves that higher resolution doesn't result in a higher quality photo.

    If you look at the entire photo it doesn't look any better than a regular photo even if it contains much more information.

    For years now there has been a push to larger and larger resolution photos with people often mistaking this with "quality."

    All a higher resolution really allows you to do is zoom in more after a certain point. Which is awesome from a photo editing point of view, but for most people unimportant.

    What you really want to be focusing on is the lens quality, zoom quality (lol Digital Zoom), noise, and other characteristics of the camera (e.g. ISO rating).

    So it is great that they spent lot's of time doing this but it isn't all that interesting to average Joes or even serious photographers. We all really want better quality pictures, not bigger ones.
    • by RichardKaufmann (204326) on Saturday May 17 2008, @02:43PM (#23447362)
      You're confusing three different aspects of quality:

      1. Resolution (the number of pixels in am image, here increased by stitching overlapping images)
      2. Dynamic range, color fidelity, noise (the quality of a particular pixel). This can be somewhat ameliorated by HDR photography or just averaging identical shots (all with no moving subjects and a sturdy tripod). Google Photomatix for details.
      3. Whether the shot is interesting, well composed, in focus, without motion blur, etc. Panorama photography is most interesting for its artistic potential; more pixels is just a delightful side effect.

      #1 and #2 can be addressed by money and a willingness to prostrate yourself to the camera gods. #3 requires talent!

      And to put a final nail in the megapixel coffin: check out http://www.luminous-landscape.com/essays/Equivalent-Lenses.shtml [luminous-landscape.com] (particularly Nathan Nyhrvold's comments) for a discussion of how sensor size and f-stop place an upper bound on resolution irrespective of sensor density. Physics can be a pain sometimes!

    • Re: (Score:3, Insightful)

      When you get to the highest resolution the image is terrible. It looks like a muddy smoothing of a blocky jpeg. You can't say this is a gigapixel image much more than you can say a 640x480 tiff expanded to 400,000x250,000 pixels (in its blocky glory) is a gigapixel image.

      I was expecting to see good quality all the way down to the highest zoom. something like google-earth quality for the most part. They don't let you just keep zooming in past the point where the resolution has hit the wall like this does
  • by cinnamon colbert (732724) on Saturday May 17 2008, @02:15PM (#23447214) Journal
    to my understanding, resolution refers to a mapping of the object on to the image - resolution is a ration of 1 cm in object/x cm in image
    it has nothing to do with pixels per image, although you can have more of the object , at the same resolution, with more pixels
  • Big Deal! (Score:4, Funny)

    by Evildonald (983517) on Saturday May 17 2008, @02:31PM (#23447290)
    I've been doing this for years with a film camera and then sticky-taping all the photos together. Then when i want to "zoom in" I just move my head closer to the picture.
  • by AsmordeanX (615669) on Saturday May 17 2008, @02:38PM (#23447328)
    That's not really all that new. Motorized panorama heads have been around for a long time. People have even built them from Lego Technics.

    As an avid pano/gigapixel photographer myself I'm interested in any new entry into the excessively priced head market. I'm using a Kadian Quickpan Pro that cost me $400 a few years ago. An automated system would be very nice but the cost is usually horrific. I've even had a head custom built at one point.

    As for the use, I like to take big pictures. I have a 6ft x 3ft print hanging on my wall. The print is 400dpi taken from a 43000x22000 (just shy of 1GP). People see the picture and say it looks nice then walk a little closer, and closer, and closer. Pretty soon they are standing 4" away and excitedly reading the serial number on the front of a train car that is only 2" across on the print.
  • by SamP2 (1097897) on Saturday May 17 2008, @08:20PM (#23449520)
    True, you can put together a lot of composite pictures to achieve an arbitrary size and resolution. You can legitimately call the result a gigapixel picture (if it reaches the resolution requirement, of course). But that shouldn't be confused with a gigapixel camera, and in and by itself is not actually that impressive.

    For example, if you take the entire photoset of Google Earth, you'd probably get a few peta-pixels worth of data. Ultimately, it all boils down to how much of that data is needed at any given time. You might need a low-detail, large-area image (e.g. view of Earth as a whole), or a high-detail, small-area image of your backyard. In either case, you wouldn't need more than at most a few dozen megapixels at any given time. It's unlikely anyone ever needs more than that size, whether they are studying galaxies or atoms, because the more detail you need, the less physical area you need covered, and vice versa.