1. Skip to navigation
  2. Skip to content
  3. Skip to sidebar

Want to add this gigapan to your favorites? Log In or Sign Up now.

Log In now to add this Gigapan to a group gallery.

About This Gigapan

Taken by
The Gigapanographer Currently Known as "Kilgore661" The Gigapanographer Currently Known as "Kilgore661"
Explore score
0.17 Gigapixels
Date added
Jul 13, 2009
Date taken
May 31, 2009

Part of my FFT experiment (taken from www.gigapan.org/viewGigapan.php?id=24978). FFT is here: www.gigapan.org/viewGigapan.php?id=28005.
Original discussion is here: www.gigapan.org/viewGigapan.php?id=27984. My idea here was to be able to compare the gigapan and its FFT side-by-side, but that doesn't work well because it is easy to get lost in the FFT. Perhaps superimposing the FFT on the gigapan will work better. Watch this space for results.

Gigapan Comments (5)

Toggle Minimize gigapan_comment
  1. David Engle

    David Engle (July 16, 2009, 02:15PM )

    Just between you and I; anyone looking at all this technical discussion that we (you and I) have shared since this morning would think that you and I are from this place: www.gigapan.org/viewGigapan.php?id= 27965 and that not a bad thing to say because if you have any stress in your life, Hong Kong is a great place to lose it and never see it again.

  2. The Gigapanographer Currently Known as "Kilgore661"

    The Gigapanographer Currently Known as "Kilgore661" (July 16, 2009, 01:11PM )

    The simple answer to your question (as I understand it) is 'no' because images are usually stored as jpegs which are (as I understand it) compressed by using an algorithm that is based on FFTs. This, incidentally, is why a jpeg can never be saved in a lossless way: if you edit a jpeg and save it, even if you specify 'no compression' or 'highest quality', the jpeg is always saved using FFTs and that loses information. (Well, OK, if your image was a 2d graph of pure cosines like z = cos(x)*cos(2y) then the FFT will encode the image exactly.) Alternatively if your camera saves in a non-jpeg format, say raw, and you are asking 'can I save space by saving my raw image using FFTs' then the answer is 'yes' and the way you do that is to save it as a jpeg :-)

  3. David Engle

    David Engle (July 16, 2009, 12:13PM )

    Your reply is most interesting and has added a great deal of stimulus for me to go out tomorrow and take a non-FFT GigaPan, which may re-define the way I take panoramas; however, I may need more than a 4GB card (which is all that I have). Does FFT procedures allow you to compress jpg files so that a larger non-FFT file fit on a memory card due to enhanced FFT volitle procedures?

  4. The Gigapanographer Currently Known as "Kilgore661"

    The Gigapanographer Currently Known as "Kilgore661" (July 16, 2009, 09:37AM )

    Aha! I wondered if anyone would ask me about that. Here you go: www.gigapan.org/viewGigapan.php?id= 28196.IMy conclusions are that this technique is inconclusive because the interesting thing about the results is that they are not very interesting. I am currently looking at ways of refining the application of FFTs and looking at non-FFT methods - for example, looking at how similar a quadrant of a tile is to the whole tile. Boring areas like sky, sea - very similar, other areas - not so similar.

  5. David Engle

    David Engle (July 16, 2009, 06:56AM )

    Don't hold me in suspense, what will we be able to see when you superimpose the two images?

The GigaPan EPIC Series, Purchase an GigaPan EPIC model and receive GigaPan Stitch complimentary

Where in the World is this GigaPan?

Sorry, this gigapan has no location information.

Stitcher Notes


GigaPan Stitcher version 0.4.4090 (Windows)
Panorama size: 174 megapixels (19829 x 8808 pixels)
Input images: 28 (7 columns by 4 rows)
Field of view: 43.2 degrees wide by 19.2 degrees high (top=11.7, bottom=-7.5)
All default settings
Original image properties:
Camera make: Canon
Camera model: Canon EOS 400D DIGITAL
Image size: 3888x2592 (10.1 megapixels)
Capture time: 2009-05-31 13:08:43 - 2009-05-31 13:12:15
Aperture: f/2
Exposure time: 0.003125
ISO: 100
Focal length (35mm equiv.): 80.9 mm
White balance: Fixed
Exposure mode: Manual
Horizontal overlap: 31.0 to 33.1 percent
Vertical overlap: 19.4 to 20.5 percent
Computer stats: 3327.04 MB RAM, 4 CPUs
Total time 14:41 (0:31 per picture)
Alignment: 2:09, Projection: 1:40, Blending: 10:51

Member Log In