| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

Last 100 entries

Re: Python's sad, unimaginative Enum; Some explanation; Printing binary trees sideways; About "Python's sad, unimaginative Enum"; Atoms in python; Some good feedback here; Frustration Understood; I agree with you #nt; What would be imaginative?; Re: Enum; this is fucking useless; Enum; Python's sad, unimaginative Enum; Possible Fix; Work, Exhaustion, Vacation; VirtualBox with Centos 6.3 to 6.4, client; Matasano - Programming Lessons Learned; PDF to HTML; Alternate Substitution; Why RSA Works; Trigger; Dreaming of Death; Example: Tracing; Using Coroutines In Protocol Simulations; Python 3.3 Only; Pure Python SHA1 and MD4 Implementations; Ubuntu on VirtualBox; Starting TOR as a service on OpenSuse 12.3; 1001 Albums; Using fail2ban on OpenSuse 12.3; PPPoE on OpenSuse 12.3; Good Article on Unified Physics; It's Police (Carabineros); Linux Software for Listening to and Exploring Music; Android is Pretty Bad; Lucky Number; 3D Printing for Casting; Cover Art for MPDroid; Who'd a thought the French were so bigoted?; PS Input Signal; Small Problem with Roksan K2 Amp; Roksan K2 Amp + ATC SCM7 Speakers; Do What Makes Sense; Re: Arguing About Tests, Still; Arguing About Tests, Still; Images; Good Article on NY Drummers; Related Bug Report; Getting Python 3.3 and Virtualenv Working in OpenSuse 12.3; How I Am; Awesome video about digital audio; The Difference Between Dimensional and Normalized Databases; The rise of the new Chinese bogeyman; Updated Syntax; Very First Steps to C-ORM; The Ideal User Interface For Music Exploration; Can The Republicans Be Saved?; Rate Limiting Calls to EchoNest; Mods to Cache; Comparing UYKFG and UYKFD/E/F; Someone Else is Concerned; EchoNest-based Playlist Generator for MPD; Example Voting Results; A Heavyweight Python Cache; Identifying Artists with EchoNest; Notes on Pregalex / Pregabalina / Lyrica; The Neil Cowley Trio; Drake - Make for Data; A Reliable Python Web Service; Useful Python Date/Time Library?; Need to Sleep, But this is Good; Command Line Set Difference; Little Details...; Linux Command Line Tricks; AutoTools Tutorial; Hangman Tactics; A Tor Proxy Embedded In A Web Page; Tree (Nested Dicts) in Python; Sleeping at Parties; I Know Someone Who Hurts Other People; Light and Tea; Description of the LCS35 Time Capsule Crypto-Puzzle; Re: I can relate to that ...; I can relate to that ...; Re: It's 2012 Why Does My IDE Suck?; My Own Alternative Medicine; Nice explanation of SVM; Why and How Writing Crypto is Hard; Re: It's 2012 Why Does My IDE Suck?; Incremental Regular Expressions; BBC Map Confused at Pole; Social Media: Ground Zero in the Culture War; My Visit to the Psycho Doc; Learning Modern 3D Graphics Programming; Hope you got some crackers to go with the cheese; Re: But how easy would it be ...; But how easy would it be ...; Powerline Freq Fingerprinting of Audio; The Folly of Scientism; Cheese - Because You're Going to Die Anyway; Another GPU Success - PyCUDA, Cross-Correlations

© 2006-2013 Andrew Cooke (site) / post authors (content).

Depth of Field

From: "andrew cooke" <andrew@...>

Date: Sun, 23 Dec 2007 16:58:36 -0300 (CLST)

From
http://www.flickr.com/groups/panasonicdmc-lx1/discuss/72157603526533457/#comment72157603525884094

in
http://www.flickr.com/groups/panasonicdmc-lx1/discuss/72157602866039023/#comment72157602895143765
the depth of field in compact p&s cameras was shown to be much greater
than in a 35mm lens at the same aperture (f number).

why is this?

naively i would expect that if you take a lens and put it in a magic
"shrinking machine" that scales it to (say) half size, then you 
would get much dimmer pictures (smaller absolute aperture - 1/4 area of
lens) that cover a smaller area of the focal plane (1/4 area of sensor),
but that  he f number would stay the same (it does, right?).

furthermore, since everything seems to be "the same but smaller"
i would expect the depth of field to be the same (when you make a photo 
smaller or bigger in photoshop the depth of field in the image doesn't 
change).

yet clearly this isn't the case, and it's the thing i miss most in my
camera.  does anyone have a good intuitive explanation why?

[...]

ok, so it's quite simple really :)

in my argument above (which is a "scaling argument") i imagined
taking a lens (well, an entire optical system) and shrinking it.

what i forgot is that when i shrink the camera i also have to shrink the
world it is inside!

less cryptically, there's an extra distance, in the "real world"
that i had forgotten to take into account - the distance from the camera
to the subject.  this may seem unusual, because typical, simple geometric
optics considers subjects that are at an "infinite" distance -
this simplifies things (shrinking infinity is still infinity) and is often
a reasonable assumption.  but depth of field doesn't work "at
infinity", it only works for relatively close objects, so this is not
a good approximation to make.  this is why, incidentally, the first link
above keeps talking about "intermediate distances".

so, once you realise that the distance from the lens to the subject is
important things become a lot clearer.  the shrinking argument is correct,
but you have to shrink the distance to the subject too.

so, for example, the depth of field for a 50mm lens with a 35mm sensor at
10m is the same (in relative terms) as a 25mm lens with a 17.5mm sensor at
5m (we have simply shrunk everything by a factor of 2, geometry - angles
and relative resolutions - stay unchanged).

almost there...

the problem then, of course, is that when we compare depth of field for
different sized sensors we are implicitly talking about taking pictures of
things <em>at the same distance</em>.  and we all know that as you get
closer to the lens depth of field becomes more important (ie smaller). 
conversely, moving further away makes depth of field effects less
pronounced.

so if we want to compare depth of field for two different sensor sizes
<em>with the subject at the same distance</em> then in the smaller sensor
case it is "as if" the subject was futher away (compared to
where it would be if we simply scaled everything).  and, as a consequence,
depth of field for the smaller sensor is larger (less pronounced).

i don't know if that helps anyone except me, but i find that much more
intuitive than looking at formulae...

Comment on this post