Andrew Cooke | Contents | Latest | RSS | 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

Choochoo Training Diary

Last 100 entries

[Bike] Gearing On The Back Of An Envelope; [Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life; [Link, Bike] Cheap Cycling Jerseys; [Link, Music] Music To Steal 2017; [Link, Future] Simulated Brain Drives Robot; [Link, Computing] Learned Index Structures; Solo Air Equalization; Update: Higher Pressures; Psychology; [Bike] Exercise And Fuel; Continental Race King 2.2; Removing Lowers; Mnesiacs; [Maths, Link] Dividing By Zero; [Book, Review] Ray Monk - Ludwig Wittgenstein: The Duty Of Genius; [Link, Bike, Computing] Evolving Lacing Patterns; [Jam] Strawberry and Orange Jam; [Chile, Privacy] Biometric Check During Mail Delivery; [Link, Chile, Spanish] Article on the Chilean Drought; [Bike] Extended Gear Ratios, Shimano XT M8000 (24/36 Chainring); [Link, Politics, USA] The Future Of American Democracy; Mass Hysteria; [Review, Books, Links] Kazuo Ishiguro - Never Let Me Go; [Link, Books] David Mitchell's Favourite Japanese Fiction; [Link, Bike] Rear Suspension Geometry; [Link, Cycling, Art] Strava Artwork; [Link, Computing] Useful gcc flags; [Link] Voynich Manuscript Decoded; [Bike] Notes on Servicing Suspension Forks

© 2006-2017 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