Main Page: Difference between revisions

From formulasearchengine
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{Film|Filmmaking-task-force=yes|class=Start}}
If you want to talk to me about something, use my [[User_talk:Masudr|talk page]], and I will generally respond there.


Exposure value sounds right (I don't know for sure), but Canon calls it [http://www.canon-europe.com/For_Home/Product_Finder/Cameras/Digital/digicam_glossary.asp?ComponentID=29381&SourcePageID=180801#3 evaluation value] in the explanation for Exposure Compensation.
=Algorithms=


==Light gathered==
==Algorithmic analysis==


In trying to understand all the values, I must admit Im a bit confused now. The F-Number article tells that the higher the number, the smaller the hole the light comes through. That makes sense (given the numbers f/8 for bright and f/2 for dark of the human eye). Now Table1 in this article says for e.g. f/8 the EV at 60s is 0 and at 1/8000 second is 19. So taking this table only, the lower the EV, the more light has been gathered (same aperture + longer exposure makes more light in total). But then I totally do not understand Table2. shouldn't it show the light amount gathered vs EV? So following that Table, the higher the EV, the more light will be gathered, contrary to what I got and explained from the other parts. Could anyone clear this up? especially in the article?
:<math>f(n) \text{ is } \Theta(g(n)) \Leftarrow\ \exists\ c_1, c_2, n_0 \text{ s.t. } c_1 g(n) \le f(n) \le c_2 g(n)\ \forall\ n > n_0.</math>


:Table 2 explains what a meter does.  Luminance is how much light is coming from the scene; when it's low, you need a slower shutter or lower f-number, hence a lower EV, to properly expose a photo.  [[User:Dicklyon|Dicklyon]] 15:56, 18 August 2006 (UTC)
:<math>f(n) \text{ is } O(g(n)) \Leftarrow\ \exists\ c, n_0 \text{ s.t. } c g(n) \ge f(n)\ \forall\ n > n_0.</math>


==Link to C.R.I.S.==
:<math>f(n) \text{ is } \Omega(g(n)) \Leftarrow\ \exists\ c, n_0\ \text{ s.t. } c g(n) \le f(n)\ \forall\ n > n_0.</math>


I restored the link to C.R.I.S. Under &ldquo;kyoritsu test equipment,&rdquo; the links for the Multi  Camera Testers (e.g., EF-1) make reference to EV and K, and the links for Calibrated Light Sources (e.g., LBF-2000) make reference to LV at ISO 100 and K. The link is included to support comments in the text.
Order of functions with increasing growth rate:


I also made slight changes to section headings for consistency with the text ... which I forgot to note in the edit summaries.
<math>1,\; \log{\log{n}},\; \log{n},\; \sqrt{n},\; n,\; n\log{n},\; n^2,\; n^2\log{n},\; n^3,\; 2^n,\; n2^n,\; 3^n.</math>


[[User:JeffConrad|JeffConrad]] 22:00, 19 August 2006 (UTC)
==Sorting==


:Jeff, thanks for that explanation.  I won't delete it again, but would suggest we put a little explanation by the link, and maybe link deeper if possible to the relevant pages.  I found nothing on a quick first look there.  [[User:Dicklyon|Dicklyon]] 22:07, 19 August 2006 (UTC)
A sorting algorithm may have the following properties:


:The Flash makes it hard, but you can google up some URLs to use instead: [http://www.criscam.com/old/testers/ef1.htm] and [http://www.criscam.com/old/testers/lightsrc.htm] (both are in criscam's "old" section; someone needs to explain to them about URLs so they won't rely on the just the flash carp. [[User:Dicklyon|Dicklyon]] 22:12, 19 August 2006 (UTC)
* '''in-place''', if it requires Θ(1) extra space.
* '''stable''', if items of the same sorting key remain in the same relative order they were before the sort.


::Dick, I'm hesitant to link to an "old" page for fear that it might vanish. Does the comment that I added at least partially address your concern?  [[User:JeffConrad|JeffConrad]] 05:37, 23 August 2006 (UTC)
===Selection sort===


:::Partially. But don't be surprised if someone comes along and deletes it as link spam. [[User:Dicklyon|Dicklyon]] 05:57, 23 August 2006 (UTC)
Best time: Θ(n²).<br />
Average time: Θ(n²).<br />
Worst time: Θ().


::::Dick, see if the 24 August 2006 edit helps. If so, I'll make the same change in the Light value  article (I need to fix "C.R.I.S.S." anyway). [[User:JeffConrad|JeffConrad]] 02:03, 24 August 2006 (UTC)
Iterate through decreasing sublists, finding the largest item, and swapping that item with the item at the end.


:::::I like that much better. [[User:Dicklyon|Dicklyon]] 02:12, 24 August 2006 (UTC)
===Insertion sort===


==Edits of 7&ndash;18 October 2006==
Best time: Θ(n).<br />
Average time: Θ(n²).<br />
Worst time: Θ(n²).


A long discussion with Marc Lacoste has raised several issues about the
Iterate through increasing sublists, finding the correct position to place the item immediately following the sublist, shifting all greater elements in the sublist one place to the end. Finally place that item in the correct place.
style of this article (and by implication, similar articles on photographic
terms).  Some of the issues probably apply to Wiki articles in general, but
because a few are a bit esoteric, this may be the place to start.


The current version includes a combination of Marc's and my recent edits; if
===Bubble sort===
the format seems reasonable, perhaps it should be incorporated into similar
articles.  It does involve some effort, however, so if people don't like
it, I'd rather not bother.


===Citation of National and International Standards as Sources===
Average time: Θ(n²).<br />
Worst time: Θ(n²).


The authoritative sources for several of the photographic term articles are
Iterate through decreasing sublists, swapping two adjacent items if they are not in order, until the list is sorted.
national and international standards, such as from ANSI/ASA and ISO.  Such
references are comparatively uncommon, and are given little coverage in
most style guidelines.  As nearly as I can tell, they are not covered at
all in the Wikipedia Manual of Style ("WMoS").  With author-date
("Harvard") referencing, the Chicago Manual of Style, 15th ed., ("CMS")
would use citations such as (ISO 1974) or ISO (1974), depending on context.
Nearly universal practice within organizations that publish such standards
is a style such as (ISO 2720:1974) or ISO 2720:1974, and this style also
appears to be common in the photographic literature (see, for example, Ray
(2000 305&ndash;309), listed in the References fo the Exposure value
article; the chapter I mention here actually was written by Ralph
Jacobson).  This form also seems to find use in Wiki articles; see, for
example [[ISO 31]].  I prefer this form, which I have used in several of
the photographic-term articles on which I recently have worked; it would
seem to provide everything that strict CMS style offers, with the
additional benefit of the specific reference for those who may be familiar
with it.


===Citation of Self-Published Material as Sources===
===HeapSort===


I have avoided citation of self-published articles by Doug Kerr, Gordon
Worst time: Θ(n log n).
McKinney, and me as References, because Wiki guidelines
[http://en.wikipedia.org/wiki/Wikipedia:Reliable_sources#Self-published_sources expressly forbid it].
Although I agree with
[http://en.wikipedia.org/wiki/Wikipedia_talk:External_links#references_section_preference Marc's contention]
that Extenal links tend to collect all manner of garbage, I'd
rather adhere to the Wiki guidelines because I am afraid that, once the
door is opened to self-published material as sources, there will be no such
thing as a reliable source.  I'd rather we monitor external links and
remove obvious link spam.


:Jeff, I think there's a different standard for sources versus external links.  I agree that self-published materials as sources is seldom OK (the guidelines don't say it's forbidden, though); there are some gray cases, though, such as David Jacobson's Lens FAQ; it's self-published (I think), but has been through some years of use, review, and revision, so it's pretty reliable.  I think some of your stuff, and Doug's, are as good, but have not been subject to that kind of community exposure and feedback, so are not as good as sources.  Nonetheless, they don't have to pass as high as standard to be used as external links.  If they are non-commercial credible opinions or analyses related to the article topic, that's usually enough. Of course, you should hesitate to link your own papers. But if you choose to link some others, I'm going to add some of yours.  [[User:Dicklyon|Dicklyon]] 02:14, 13 October 2006 (UTC)
Take an array, start with the parent of the last element of the array, and work backwards, to ensure the heap property (see the remove operation on a heap). Then remove an item from the top and place in the newly vacated place, thus leaving a list in ascending order.


::I think we agree; I like to think that I hold external links to a fairly high standard, even if it less than the guidelines for a reliable source. There may indeed be a few exceptions, such as Jacobson's FAQ, which for many is still the gold standard of introductory treatments of the subject, and possibly Merklinger's The INs and OUTs of FOCUS, which has been around for a while and has been extensively quoted. Nonetheless, I don't think either has the same status as works by Ray, Stroebel, or Zakia, and I would cite either as firmly establishing a position only reluctantly&mdash;how does one make the call on which self-published materials are reliable? If Jacobson, why not Atkins, Koren, or Rockwell (or even Conrad or Lyon)? There is a lot of nonsense on photo-related web sites, and once the bar is lowered, it may be impossible to prevent free fall.
===QuickSort===


::Perhaps I'm shameless, but I'm not above linking to one of my papers (I'm sure not the only one to do such a thing), especially if it explains a point in more detail than may be appropriate for a Wiki article. [[User:JeffConrad|JeffConrad]] 09:36, 13 October 2006 (UTC)
Average time: Θ(n log n).<br />
Worst time: Θ().
²
Average space: Θ(log n).<br />
Worst space: Θ(n) can be remedied to Θ(log n) using a custom stack.


:::I hear you. Sometimes those Lyon papers are just what we need! [[User:Dicklyon|Dicklyon]] 15:01, 13 October 2006 (UTC)
Select a pivot as the first item in the list, then place items less than the pivot before it, and those greater after it. Use the final position of the pivot to split the list up into two sublists. Repeat (substituting the sublists for the lists) until the sublists are of size one or zero.


::::Let's put it this way: there are many far less appropriate links. It's the reader's choice to follow or not follow an external link, especially when it is not represented as authority; if the link to a potentially useful site or article is omitted, the reader does not have the choice. The key, I think, is the exercise of reasonable judgment when including links. When no endorsement is implied, the call isn't as critical. [[User:JeffConrad|JeffConrad]] 23:17, 13 October 2006 (UTC)
The worst case for running time is when the list is already sorted. To combat this, the pivot is selected randomly.


===Mathematics as Intimidating for Some Readers===
===Radix sort===


The definition of exposure value is imprecise without the math, but
Worst time: Θ(n).
precision may not be necessary for all readers, and may be offputting. I'm
inclined to put the formal definition in a separate section; would this
suffice to keep the article accessible?


:Jeff, to tell the truth, I am not keen on the math the way it is now. I preferred what I had back in June, which started off with just EV = AV + TV and then the (logarithmic) definitions of TV and AV based on exposure time and aperture. I do appreciate the logic of your approach, but it's a lot more complicated.  It brings issues of light meter calibration, photometry, and sensitometry right to the front, and defers the definition of EV to pretty deep in the intro, and involves squares and divisions with too many symbols for a naive user to get their head around. So, my suggestion would be to make a new section for all that stuff, and to put EV = AV + TV and not much else in the intro.  This is the simplest valid definition, right?  The rest is more about how to choose a good EV. [[User:Dicklyon|Dicklyon]] 02:22, 13 October 2006 (UTC)
Place items into ten lists based on least significant digit. Concatenate list. Repeat, but use the next most significant digit instead, until we reach the highest significant digit of any of the numbers.


::Isn't the simple (and hopefully intuitive) definition given in the article's opening sentence? The problem I see with with introducing AV and TV is that we dabble in APEX, a concept that essentially was stillborn. For practical purposes, AV and TV are superfluous except as historical footnotes. Having said that, perhaps the intial definition could deal only with the left-hand side of the exposure equation, with the more complete definition moved to an advanced section. Perhaps the APEX reference also should be moved to the advanced section. I wonder if squares and division are any more intimidating than logarithms (which still give me trouble ...). It sounds as if some simplification is indicated, however. Would putting the math in a section separate from that with the two images (with which it doesn't really belong) be a start? Perhaps the EV vs. camera setting table could be introduced before the math and without any reference to it. To my mind, the mathematical definitions and the relationship to luminance and illuminance are somewhat advanced topics that really aren't needed by most practical photographers.
==Searching==


::On choosing a good EV: one must of course know the proper EV, either from a meter reading or from another source, such as a table. I added a link to Fred Parker's EV table, but Marc suggested that Wikipedia should contain such a table directly. Perhaps this article is the proper place for it? [[User:JeffConrad|JeffConrad]] 05:25, 13 October 2006 (UTC)
===Linear search===


:::I agree that choosing a good EV is important, and your expert knowledge of that metering topic is appreciated.  But to me, the ''definition'' of EV is just TV + AV, and you can't really talk about it without knowing a bit of that APEX stuff.  The logs can be intimidating, it's true, so maybe small 1D tables to define AV and TV would be a way around that.
Best time: Θ(1).<br />
Average time: Θ(n).<br />
Worst time: Θ(n).


::::I would argue that the definition of EV is
Iterate through the list, until we find the desired item, if it exists.


:::::<math>\mathrm {EV} = \log_2 \frac {N^2} t</math>,
===Binary search===


::::which doesn't require mention of AV or TV. I'm working on a version that goes no further than this in the introduction. As nearly as I can tell, the concept of EV predated APEX by several years (some Hasselblad lenses had EV markings around 1957, while APEX was not proposed until 1960), so we should be able to handle the definition without mentioning AV or TV. I wish we could find a reader from Germany who was an actual witness (and can provide reliable sources, of course ;-) ). [[User:JeffConrad|JeffConrad]] 06:30, 13 October 2006 (UTC)
Works on lists sorted in non-decreasing order.


:::::Really?  It had not occurred to me that EV could pre-date APEX. Anyway, that definition is OK, but it's going to scare some people.  I thought using APEX was a way to make it much more accessible, but maybe I'm out of order.  [[User:Dicklyon|Dicklyon]] 06:48, 13 October 2006 (UTC)
Best time: Θ(1).<br />
Worst time: Θ(log n).


::::::I'm relying on comments in the forward to ASA PH2.5-1960 (long unavailable, unfortunately). As nearly as I can tell, the idea of EV was to simplify choosing among combinations of camera settings that would give the same exposure; the APEX proposal extended the concept, stating "There appears to be merit in the proposition that the exposure value concept be extended to include all the parameters of the camera exposure equation."
Compare with the item in the middle of the list. If larger, then check the upper half; if smaller check the lower, if matched then return.


::::::Some people are scared by any math, but I don't think my definition is any more intimidating than yours of 29 June 2006. In any event, I don't know how to simplify mine any further. [[User:JeffConrad|JeffConrad]] 07:15, 13 October 2006 (UTC)
=Data structures=


==Stack==


===Table of Exposure value vs. Camera Settings===
push(x): add an item to the top of the stack.<br />
pop(): returns the item at the top of the stack.<br />
makeEmpty(): removes all items.<br />
isEmpty(): returns true if empty, false otherwise.


I extended the EV vs. camera settings table to EV &minus;4 to cover the
push is Θ(1) if the underlying array isn't full, and Θ(n) if the underlying array is full. pop is Θ(1).
light from a full Moon; it could be argued that I should have gone to EV
&minus;6.  The logarithmic EV scale was not chosen without reason; when
linear sequences are used, some of the values can be come quite large, such
as the exposure time for EV &minus;4 at <var>f</var>/64.  Accordingly, I
expressed exposure times longer than 60 seconds in minutes, and appended
the symbol 'm' to those values to so indicate.  Apparently the meaning of
the 'm' in this context isn't clear to everyone, even with a note in the
table captions. The official SI abbreviation is 'min'; it's easy enough to
use it, though the presentation of the data becomes less attractive.
Alternatively, the really long exposure times simply could be eliminated,
as I have done with really short exposure times less than 1/8000 seconds.


[[User:JeffConrad|JeffConrad]] 01:57, 13 October 2006 (UTC)
==Queue==


:I think the fix here is just to put the "m" note by the table, not in a footnote. Jeff, thanks for all your hard work and serious attention on this article. It has benefitted enormously from your work (even if I don't like your mathiness up front so much). [[User:Dicklyon|Dicklyon]] 02:26, 13 October 2006 (UTC)
enqueue(x): add x to the end of the queue.<br />
dequeue(): return the item at the front of the queue.<br />
makeEmpty(): removes all items.<br />
isEmpty(): returns true if empty, false otherwise.


::This sounds simple enough (Marc had the same suggestion); it also follows style convention for tables. With the note that close, it probably doesn't need to be clickable, though that's not difficult if it's needed. The question now is the footnote style ... conventionally, notes for table data cells are alphabetical, though I'm not sure that applies to table captions. I don't think a superscripted number is a good idea because we already have a numerical series of notes. Perhaps an asterisk is the solution ... I'd first like to see if there are any other comments, though. As Marc pointed out, we 'Merkins sometimes forget that what is intutive to a native-English speaker is not so for others.
==List==


::As noted in my comment in the earlier section, it sounds as if the math needs some rework. [[User:JeffConrad|JeffConrad]] 05:21, 13 October 2006 (UTC)
length(): return length of list.<br />
begin(): return position at 0.<br />
end(): return position at end.<br />
next(p): return position at p + 1.<br />
prev(p): return position at p - 1.


===Edits of 14&ndash;15 October 2006===
get(p): return item at p.<br />
set(p, x): set item at position p to x.<br />
insert(p, x): insert item x at position p, right-shifting subsequent items.<br />
remove(p): remove item at position.


Dick, I left AV and TV out of the definition, in trying to cut the math to the absolute minimum. Put them in if you insist, but I still think they are irrelevant to this article (and they are well covered in the APEX article). The EV concept indeed was introduced to simplify setting camera controls, but without logarithmic markings on the camera controls, AV and TV are of no value. Presumably, when EV was introduced, the photographer would obtain the EV from a meter or tabulated exposure guide, and transfer that value to the guide. To the extent of my knowledge, the first use of EV was on Hasselbald lenses: one would depress the EV-lock button to change the EV, and then release it. The shutter time then would change with the <var>f</var>-number to maintain constant EV. There was no mention of AV or TV&mdash;the shutter and aperture markings were arithmetic. I don't think I've ever seen tables of AV and TV outside of obsolete ANSI standards and perhaps a photo book or two (I guess the Minolta Flashmeter III did specify <var>f</var>-number indication range in AV).
find(x): return first position at which x exists.<br />
nth(k): return nth position at which x exists.


:Well, I still don't see how you can omit EV = TV + AV in the section on EV and APEX.  The whole section uses the complicated multiplication, squaring, division, log type math instead of the additive math from the system that it's talking about.  Personally, I think APEX is useful and easy to understand, and even though it didn't catch on it's worth demonstrating a bit. [[User:Dicklyon|Dicklyon]] 00:41, 15 October 2006 (UTC)
===Array implementation===


::It depends on how complete this section needs to be. I tried to keep it to an absolute minimum, showing only how EV could be used as a measure of luminance or illuminance (necessary because nearly every equipment manufacturer uses EV in that sense). In particular, I had hoped to avoid essentially a complete duplication of the APEX system article, which covers the subject in depth. If people think it important, I can include some of the material from that article, but I'm always concerned about maintaining consistency in essentially parallel articles. Perhaps I also need to make it clear that EV as an indicator of luminance or illuminance is the only element of APEX that has survived. [[User:JeffConrad|JeffConrad]] 02:03, 15 October 2006 (UTC)
Operations insert, remove and find have a worst case running time of Θ(n). Everything else is Θ(1).


::Dick, I've added a one-sentence summary of the purpose of APEX, as well as a direction of the reader to that article. Does this help? [[User:JeffConrad|JeffConrad]] 02:53, 15 October 2006 (UTC)
===Linked list implementation===


::Dick, one other minor point that I missed last time: in light of the last sentence of the first paragraph in the article, isn't the sentence, "Each such increment is known as a change of one "stop" or one "step" in exposure" in the Formal definition section redundant? [[User:JeffConrad|JeffConrad]] 09:49, 15 October 2006 (UTC)
Insert and remove have a running time of Θ(1), random access is Θ(n).


:::Redundant, yes, a bit.  However, I think having it there will be very helpful to people who don't fully appreciate that that's what the log2 implies. These are the people who won't remember from the lead paragraph a line that would  help them interpret the definition. [[User:Dicklyon|Dicklyon]] 16:39, 15 October 2006 (UTC)
Can have a header node, a tail pointer, and can be doubly linked, which improves certain operations.


::::I still think the inclusion of the APEX values is superfluous. We now define EV in terms of two other terms that we haven't defined, I don't know how that can be done. I also question use of "definition"; ASA PH2.5-1960 said, "The equation then takes the form ..." I also question the statement, "proper exposure value can be computed from a film speed and a light meter reading by EV = SV + BV"; I've never seen a meter that indicated in terms of APEX BV (I changed the acronym to LV for consistency with the rest of the article). Even the ANSI exposure guides don't list the values in the form indicated by APEX BV or IV (but that's another issue for another time and place ...) Also, why would we include BV/LV but not IV? I won't beat this to death, but I think we open a can of worms by mentioning the APEX stuff here. I don't see how the APEX values for the RHS quantities can possibly help the reader determine or understand exposure. If the material does remain, it think some rearrangement is indicated so that the details develop in sequence (unfortunately, that also would require some additional math). I also wish we could be consistent in the use of "stop" (the popular expression) and "step" (the formally correct expression, preferred by most of the ISO standards). [[User:JeffConrad|JeffConrad]] 21:49, 15 October 2006 (UTC)
==Priority queue==


::::I've made a slight rearragement (we need the exposure equation before we can refer to it), trying to keep mention of the APEX stuff to an absolute minumum. I still don't think this material adds anything, but if you think it's needed, I won't bring it up again. One little issue that we get into by going back in time the conflict between current and previous standard letter symbols (e.g., <math>L</math> vs. <math>B</math>). We also are using acronyms vs. the quantity symbols that APEX employed. [[User:JeffConrad|JeffConrad]] 22:23, 15 October 2006 (UTC)
insert(x, p): add x to the queue, with priority p.<br />
remove(): return and remove the item with the highest priority.<br />
makeEmpty(): removes all items.<br />
isEmpty(): returns true if empty, false otherwise.


I reformatted the tables using inline styles; the coding is cluttered and ugly, but I don't know of a good alternative except for adding several new table styles to the Common CSS, which I doubt would amuse anyone.
===List which inserts in sorted order array===


I'm working on a table of exposure values based on the withdrawn ANSI exposure guides PH2.7-1973 and PH2.7-1986, and I hope to have it done in a day or two. Other sources, such as Kodak film data, have minimal data and several inconsistencies. The ANSI subcommittees that developed these guides were chaired by H.R. Condit and Leslie Stroebel, respectively, so they should be authoritative. Whatever I come up with will be an extreme simplification (the ANSI guides are 64 pages and 80 pages). I have some concerns about this, but most other tables, including the two in the external links, make similar simplifications.
remove is Θ(1), but insert is Θ(n).


I'm not sure that such a table belongs here, but I don't know where else to put it. It certainly doesn't belong in Light value. The more I look into this the more I am convinced that Light value, luminance value, incident-light value, or whatever are simply elaborately disguised forms of EV (when incident-light value is given for night scenes that consist primarily of light sources, one suspects that the values given do not derive from fundamental laws of physics). [[User:JeffConrad|JeffConrad]] 22:40, 14 October 2006 (UTC)
===Unsorted list===


I've added the table, for what it's worth. The location in the article probably is debatable, but I've assumed that a reader is primarily interested in using EV to set the proper exposure, and have tried to provide the necessary information for that first, with the stuff that is more of academic interest later. Considerably more subjects could have been included in the table, but the article already is getting quite long; hopefully, I have included situations of the most interest. [[User:JeffConrad|JeffConrad]] 09:49, 15 October 2006 (UTC)
insert is Θ(1), but remove is Θ(n).


On second thought, I wonder if including the Further reading section listing Kodak ''Existing-Light Photography'' book is appropriate for this article. It contains a wealth of information about determining exposures for low-light situations, but this really isn't an article about exposure determination. Perhaps an article on that topic would be the appropriate repository for the tabulated exposure values as well existing-light data. [[User:JeffConrad|JeffConrad]] 21:49, 15 October 2006 (UTC)
===Heap===


===Edits of 18&ndash;19 October 2006===
insert and remove have a worst time of Θ(log n).


I made a preliminary attempt to eliminate redundancy in some of the articles on photographic terms. Much of the material on exposure meter calibration was removed, referring the reader to the Light meter article. At the time the material originally was added to this article, it was not included in the Light meter article; now it is redundant here. At Dick Lyon's request, some of the APEX material was restored, and a specific referral to that article (which now is more comprehensive than it was when that article was written.
A full, binary tree which satisfies the heap property: the priority of every node is greater than or equal to the priority of the child nodes. This can be represented as an array, where the children of the node at index k are located at 2k+1 and 2k+2.


This article still is a bit long; in particular, I'm not sure that the exposure guide ("Tabulated exposure values") really belongs here. Moreover, I think the link to Doug Kerr's APEX article is redundant (it's also in the APEX article). For some reason, we tend to mention APEX the minute exposure value comes up; the reality is that, while exposure value continues in common use, APEX. whatever its merits, was a concept proposed 45 years ago that never caught on. Had exposure mmeters been added to cameras just a few years earlier than they were, APEX never would have been proposed. [[User:JeffConrad|JeffConrad]] 01:59, 19 October 2006 (UTC)
insert appends the item to the array (or inserts having vacated the relevant spot), but keeps swapping with parent if it has a higher priority than it.


:It's a big improvement.  Still too long, maybe; I wouldn't object to more trimming.  By the way, spurred by your comment I reviewed the APEX article, and made a few edits to the section about EXIF. Take a look.  And I completely removed this bit that didn't fit with EXIF, so see if you think it needs to go back into some other section (sorry, looks like I truncated it some place):
remove returns and removes the item at the top of the array, then inserts the item at the bottom of the array at the top. It then keeps swapping the newly placed item with the node that has greater priority, if possible.


The relationship between <math>I_v</math> and [[illuminance]] similarly
==Set==
depends on the speed scaling constant <math>N</math> and the incident-light
meter calibration constant <math>C</math>:


:<math>I = NC2^{I_v}</math>
add(x): adds x, if it doesn't already exist.<br />
remove(x): removes x.<br />
contains(x): tests for containership of x.<br />
size(): returns the size.


[[#CITEREFR_ASAPH2.12-1961|ASA PH2.12-1961]] recommended a value
===Open hash table===
for <math>C</math> of 20.8&nbsp;±&nbsp;5.  Using the nominal value,
an <math>I_v</math> of 0 was equivalent to 6.18 footcandles.  Comparison
with the recommendations in [[#CITEREFR_ISO2720:1974|ISO 2720:1974]]
suggest that this value of <math>C</math> applied
to a [[cosine]]-responding (flat) sensor rather a [[cardioid]]-responding
(hemispherical) sensor, but unfortunately,
[[#CITEREFR_ASAPH2.12-1961|ASA PH2.12-1961]] made no mention


My point being that APEX is alive and well in EXIF, if not exactly in full original form.
All operations have an average running time of Θ(1).
[[User:Dicklyon|Dicklyon]] 05:36, 19 October 2006 (UTC)


:It's alive, after a fashion (I originally added the EXIF material); whether it's well remains to be seen. See my latest edit of the APEX article&mdash;there is a bit of a conflict. I cannot see a home for the deleted material, so I've left it out.
We have an array of a certain size, each containing a pointer to an empty list. Calculate a hash of the item gives us the array index location. Append the item to the list located at that index.
:My edit also finds yet another awkward example of reference to standards. In this case, everyone knows the standard as EXIF 2.2, yet the official designation is JEITA CP-3451, which I doubt anyone but the developers would recognize. The first citation that I used (JEITA 2002) is the way ''The Chicago Manual of Style'' would do it; I personally find it a bit awkward though. [[User:JeffConrad|JeffConrad]] 09:52, 19 October 2006 (UTC)


== Tables and Formulas ==
The idea is to have about 25% of the table empty, and an efficient hash function so that the average length of each list is zero or one.


I like having the formulas in this article, but I'm somewhat confused about the relationship between the tables and formulas.
===Closed hash table===


It is stated that the EV in Table 2 is with reference to ISO 100, and that formulas are provided for conversion to different ISO values. Shouldn't the EV in Table 2 remain consistent regardless of what ISO one is using in their camera? For example: If the full moon has an EV = 15 (as per Table 2) shouldn't it always have this same value since it's supposed to represent the actual amount of light present? Maybe I'm misunderstanding EV, as I'm thinking that it's an absolute value, but perhaps it's actually a relative value?
Use just one array, but in the case of collisions, insert the item by probing linearly from its desired location, until we find an empty spot. Finding items relies on the same strategy.


I was expecting Table 1 to be referenced to ISO 100 instead, and that the formulas can be applied to correct for various ISO as required. Meaning if one wants to photograph a scene that has an EV = 12 using ISO 100, one would use the f/ and shutter speed as per Table 1, but if one wants to photograph this same scene using ISO 200, one would have to correct using the ISO formula(s)?
To avoid clustering, try quadratic probing.


My confusion arose when I used these same formulas to create similar tables specific for my camera, but the numeric results didn't make sense to me, hence my confusion. Can someone clarify this for me?
==Map==


--[[User:Pinao|Dennis Lee]] 18:52, 12 November 2006 (UTC)
get(k): returns the value v if the (k, v) pair exists in the map.<br />
put(k, v): puts (k, v) into the map, or replaces the the v if the k already exists.<br />
remove(k): removes the (k, v) if there is such a pair.<br />
containsKey(k): tests to see if the map contains a pair with key k.<br />
size(): returns the size.


:You need to re-read the article.  EV is an indication of a combination of f-stop and shutter speed; not a measure of light level.  To use it to refer to a light level, you need to add an assumed ISO speed and an assumed meter calibration.  At other ISO speeds, different f-number and shutter speed will be required to give a correct exposure.  [[User:Dicklyon|Dicklyon]] 20:07, 12 November 2006 (UTC)
For implementations, we can use either of the implementations for the Set, storing the (k, v) pair, and referencing using the key k.
 
::I think I understand now, I was confusing EV with LV (Light Value). Thanks. --[[User:Pinao|Dennis Lee]] 23:18, 12 November 2006 (UTC)
 
:::[[Light value]] is an even more confusing topic, since it has no standard definition. [[User:Dicklyon|Dicklyon]] 00:13, 13 November 2006 (UTC)
 
 
I'm not sure if this is the right place, but I think currently the correction for higher ISO values in the formula is incorrect. It says: log(N^2/t)+log(S/100) = EV(S), but I think the correct one is: log(N^2/t)+log(100/S), because when rewriting this to have t=100*N^2/S*EV(S) makes t inverse to S, which is more like reality (EV=1 at ISO=1600 will be effectively the same as EV=5). --SimonOosthoek
 
:You have misinterpreted.  It says the exposure you should use should satisfy EV(100)+log(S/100) = log(N^2/t).  Here, S is inverse with t as you require.  I think you'll find that to be consistent with the examples. [[User:Dicklyon|Dicklyon]] 21:37, 21 June 2007 (UTC)
 
::Thanks for the clarification, I see where I misinterpreted --SimonOosthoek
 
::It almost sounds as if we should mention, once again, that a greater EV indicates less exposure. This behavior seems to confuse a great number of people. [[User:JeffConrad|JeffConrad]] 06:35, 23 June 2007 (UTC)
 
 
Hello,
 
<br />    Check my numbers. If N=16 and t=1/60, you get about 14 for EV(100). My analog computer on my spot meter  <br /> incorporates the ISO too so let me set this at s=400. That is EV(400)= 12 NOT 16 like the formula on the page shows. There  <br /> should be a minus where there is a plus. It even shows up when I hold the 2 dials on my analog computer dial and turn  <br /> them. As ISO goes up, EV goes down. I recommend that the writer not debate with me and try out some examples first. I  <br /> admit that I am not so confident or arrogant to change someone else's page. [[User:Redding7|Redding7]] ([[User talk:Redding7|talk]]) 18:08, 8 February 2009 (UTC)ChrisRedding
 
:The formulas for adjusting EV for different ISO speeds apply only to the right-hand side of the meter calibration equation near the beginning of the section [[Light meter#Relationship of EV to lighting conditions|Relationship of EV to lighting conditions]]. If you set {{nowrap|1=''N'' = 16}} and {{nowrap|1=''t'' = 16}}, you have EV&nbsp;14, period. If you change the ISO speed on your camera, you will alter the exposure but not the EV. The values for EV<sub>100</sub> in Table&nbsp;2 derive from fixed lighting conditions; let's oversimplify a bit and assume that each condition is a fixed, uniform luminance. Then
 
::<math>2^\mathrm {EV} = \frac {LS} K \,.</math>
 
:If ''L'' is constant and ''S'' increases, EV also increases.
 
:The EV scale on a meter calculator dial (as on my Pentax Spotmeter&nbsp;V) indicates ''EV<sub>100</sub>'' rather than EV; the value on the calculator dial thus corresponds directly to the values in Table&nbsp;2, so you don't need to worry about conversion other than setting the proper ISO speed. If I have {{nowrap|1=''S'' = 100}}, and set {{nowrap|1=''N'' = 16}} and {{nowrap|1=''t'' = 1/60}}, I also get EV&nbsp;14. If I change the speed from 100 to 400, the indicated settings change to {{nowrap|1=''N'' = 16}} and {{nowrap|1=''t'' = 1/250}}, but the EV<sub>100</sub> doesn't change. When using the meter, the value on the EV is presumably transferred from a meter reading of an object; the luminance of the object doesn't change just because you change the ISO speed for the camera, and the setting on the EV scale shouldn't, either. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 04:37, 9 February 2009 (UTC)
 
Hi Jeff, I think you got my number. The spotmeter V EV is EV(100)!!! Boy am I stupid!! [[User:Redding7|Redding7]] ([[User talk:Redding7|talk]]) 16:50, 9 February 2009 (UTC)Chris Redding
 
I thank you Jeff. [[User:Redding7|Redding7]] ([[User talk:Redding7|talk]]) 17:20, 9 February 2009 (UTC)Chris Redding
 
:It would be nice if camera and meter people would adopt the “EV<sub>100</sub>” notation and use it when that's what they mean, but I doubt that this will happen. It's worth noting that the value also depends on the calibration constant ''K'', so the values in Table&nbsp;2 really are EV<sub>100/12.5</sub> or something like it. But this would be too much for most readers to digest, so I avoided it. You might note that your Spotmeter&nbsp;V has a ''K'' of 14, so if it's in calibration, it should indicate an EV 1/6-step less than the values in the table (at least for a single object of uniform luminance). In practice, a 1/6-step difference doesn't merit a great deal of worry. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 08:21, 10 February 2009 (UTC)
 
I would like to resurrect the question of the sign for the ISO term in the EV equation.  I have been trying to use the Ev calculation as a way to "correct" exposures taken for panoramas, when I have used a camera that does not allow me to fix the exposure for all shots.  I suppose the first question is whether or not it is valid to calculate the Ev for two photos, then use software to adjust one of those photos up or down to match the other.  I have done this using photo editing software, and visually, these look correct.  My confusion comes from using the [[Hugin_(software) | Hugin]]<ref>[http://hugin.sourceforge.net Hugin home page]</ref> panorama application, which calculates Ev for automatic exposure optimization.  Their algorithm subtracts the ISO term from the EV100 term, as opposed to adding it.  Can anyone comment on this?  Thanks!  [[User:Sydthackerr|Sydthackerr]] ([[User talk:Sydthackerr|talk]]) 11:16, 28 March 2011 (UTC) [[User:Sydthackerr|Jack Gould]]
 
:We have several “EV equations”; the only one I can find with an “ISO term” is
 
::<math>\mathrm{EV}_{S} = \mathrm{EV}_{100} + \log_2 \frac {S} {100} \,,</math>
 
:which is correct as it stands. Were the sign on the second term negative, an imaging medium “faster” than ISO 100 would require ''more'' exposure, which makes no sense (recall that greater EV indicates ''less'' exposure). Note that the adjustment we describe is for different ISO speeds; I don’t see how this would normally be an issue with panoramas—although EV might differ among the various images, the ISO would not normally change. I’m not familiar with Hugin, and a quick glance at the documentation doesn’t indicate how or where it is doing what you describe. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 22:44, 28 March 2011 (UTC)
 
:Though it seemed obvious to me, perhaps something I could have added is that the equation assumes the same scene luminance, simply adjusting the EV for ISO speeds other than 100. Again, this usually would not apply to a pano in which some images had different exposures because of variations in lighting or metering. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 03:54, 29 March 2011 (UTC)
 
==Exposure Value Chart==
 
{| class="wikitable"
|-
! ===EV Graph===
|-
| [[Image:Exposure_Value_Chart.jpg|thumb|Exposure Value Chart]]
|}
 
Lazaro Gimena, it is generally considered a bit of a [[WP:COI]] or [[WP:OR]] to publish your own original creations in wikipedia this way.  I move it here, so other editors can consider it.  If someone finds it to be useful, gets you fix the errors, and wants to include it in the article, we can consider that then.  Please do not put it back yourself. [[User:Dicklyon|Dicklyon]] 03:42, 9 February 2007 (UTC)
 
:I tend to agree with Dick. To me, this seems to present the concept of exposure value as more novel than it is; the concept has been around for almost 50 years, though I'll concede that in recent years, the average photographer's familiarity with the basics is not what it once was. I cannot see how over- and under-exposure as shown in the graph relates to the rest of the graph. Perhaps I miss something, but I don't think this graph contributes anything that isn't already covered in the article. To my mind, the extra ornaments tend to distract rather than elucidate.
 
:This graph implies the more traditional table of EV presented as f-number vs. shutter time. The article had such a table until the edit of 7 October 2006; if people think it would be helpful to include the traditional arrangement as well as the current, I'd be glad to restore that table, formatted to match the current article style. [[User:JeffConrad|JeffConrad]] 08:14, 9 February 2007 (UTC)
 
Lázaro Gimena 12:43, 9 February 2007 (UTC)
<br />First of all, I want to thank expressly, for not deleting the EV Chart. I have to beg your pardon, because I am new in "wiki" and it's been a hard work for me, just to understand how it works. But I insist of my gratitude.
<br />Respect to the EV Chart, that is what it is, ''a chart''; ''not a table'', ''not a graph'', ''not a picture'', I will explain.
<br />If you have the time to have a deep insight on it, you will realized that most basic concepts related in camera shots are simply explained and related.
<br />Normally, "new" photographers, confuse all these values (see light gathered coment above as an example).
<br />The fact is that the camera, ''grosso modo'', have to receive an "amount of light" (light flow) to fix the image. It depends on the environment (outdoor or indoor, bright or dimmed scene, for example) to set the shutter speed  and aperture area, obviously.
<br />For the ''same'' light state (EV number given by the photometer) there are different options to capture this mentioned light measured: ''faster and bigger'' or ''slower and smaller'' (in terms of shutter speed and aperture).
<br />There are also other factor that is involved, the "film (or LCD) sensitivity" which it is also expressed in the chart.
<br />Respect to the JeffConrad's comment, I have to say that I agree that design, colors and "ornaments" could confuse at the first sight and can be improved.
<br />But they are not casual:
:* decolorize from dark (grey) to bright (white) represents EV value (more or less light). Diagonal straight (thanks to algorithms) lines represents same light states or EV numbers. That's why if you take the shot above the line, the  photo will be overexposed (more light than needed) and if it is below it will be underexposed (less light than needed).
:* I agree, clouds and sun, seem to be not very serious, but representative of some normal lighting conditions (Table 2).
:* It can also be seen that for a same state, the aperture chosen (with its corresponding speed-time) influence the depth of field represented by such kind of bow tie (wide or narrow).
:* Below the shutter speed, there is a representation of time (represented with yellow in different widths)  shots and how it influence the nitid or blurred photo and also the need of tripod use.
:* There is also a rectangle that simulates the capacity that some cameras have (bracketing) to shoot varying a little bit the light conditions to avoid over and under exposure (it really takes three photos, normal, over and under, and you choose the best).
 
In the EV Chart there is no way to be confused once understood. Besides, there are not special maths procedure (at least superficially).
<br />Thank you again, and hope this comment will clarify the EV Chart and could be useful for readers.
<br />P.S. I've correct the errata.
<br />Lázaro Gimena 12:43, 9 February 2007 (UTC)
 
==Referencing styles==
 
The [[WP:MOS]] allows both author-date ("Harvard") and endnote-style referencing; one style is no more proper than the other. The MOS specifically forbids changing from one style to another without prior discussion (see [[WP:CITE#HOW]]). We went through this same thing a while back; please don't do it again without some discussion and reasonable consensus.
 
The author-date system here essentially conforms to that described in the ''Chicago Manual of Style'', 15th ed. I'm not especially fond of the coding style, either, but at present, the "Harvard" referencing templates have some issues. I'm certainly open to discussion on how to improve the current format, but far less receptive to capricious changes. [[User:JeffConrad|JeffConrad]] 23:27, 16 March 2007 (UTC)
 
:If the citation style is a real problem, then fine. You didn't have to revert ''both'' of my changes. My first edit didn't touch the references. This article still needs a clean up.
:* Join up the multi-line paragraphs into single lines like my first edit. It's the style generally followed on Wikipedia. Breaking a paragraph into multiple lines makes it more troublesome to edit and diffs aren't as easy to read. Just let everyone's web browsers do the line wrapping.
:* Replace all the HTML entities with their simple ASCII/Unicode equivalents. e.g &amp;ldsqo;/&amp;rdsqo; => "
:* I don't like the way the references are wikilinks that look just like all the other links in the article. That's confusing and deceptive, especially when the majority of other Wikipedia articles uses a different system.
:* I also don't like the mis-use of the reference tags to add "notes". Just put that stuff right in the text. The Sekonic "note" is just pointless.
:* I think the article also makes rather heavy use of HTML and table markup to tweak the appearance.
:Still on the HTML issue, was this copied from a web page? Simplifying the markup would make the article easier to edit. As it is now, it's a mess. All I want to do is make this article more consistent with the rest of Wikipedia. --[[User:Imroy|Imroy]] 23:55, 16 March 2007 (UTC)
 
::Whether my choices were the best is open to question, but I assure you that none was capricious.
::* Ease of editing is in the eye of the beholder. I find the single-line paragraphs (such as here) much more confusing to edit. I also often use an external text editor, and for me, it's much easier to break the line. I rely on the UA to do the filling. Some of this may simply be habit; for years, I used [[troff]], and failure to break input lines generally was considered bad style because it made editing with [[vi]] more difficult. I carried the practice over into HTML coding.
::*I strongly disagree with replacing the HTML quote entities with ASCII quotes. Opening and closing quotes aren't the same; although they may look similar in the default Wiki sans-serif font, the neutral quotes look awful if a user has specified a serif font in his user CSS file, or if the user prints a page using a serif font.
::* The Harvard templates give a similar appearance to the reference links used here. I originally had the references without links, but objections were raised, so I added the links. I'm open to a better approach. I've played with revised "Harvard" templates, but thus far, have found it quite a difficult task--programming in assembly language is easier.
::* The use of reference tags for footnotes is ''not'' a misuse--see [[WP:FOOT]]. As with many other articles, this one seems (to me) to benefit from having both references and footnotes. One of the primary reasons the ''Chicago Manual of Style'' suggests the author-date reference system is that endnote-style references and footnotes really don't mix, even in a paginated medium. In a non-paginated medium such as WP, the combination of footnotes and endnotes is simply a mess. Incidentally, the purpose of the Sekonic footnote is to support the claim that Sekonic use a K of 12.5. There is so much nonsense bandied about when discussing meter calibration that an authoritative reference seemed appropriate.
::* I agree that I've used a lot of table markup. I dislike including all this junk as much as anyone, but HTML table facilities are quite primitive, and wikitables even more so. For all of the terrible things said about troff and [[tbl]] (many of them justified), the tables were quite parametric, and could be accomplished with comparatively little markup. I originally used an HTML table, but someone wanted the wikitable style, so I used it. I made the decision to favor readability of the article over code minimization. Ideally, we would have both, but changes to the wikitable template would be required, and I didn't see that as my role to implement.
::I'm as much a believer in clean code as anyone else, but not at the expense of proper presentation. Again, I'm open to improving the appearance and structure of the article, but I'd like to have some discussion prior to sweeping arbitrary stylistic changes. [[User:JeffConrad|JeffConrad]] 01:17, 17 March 2007 (UTC)
 
:I should have mentioned that my issue with [[User:Imroy|Imroy]]'s first edit was more with the elimination of the HTML entities than with reformatting the paragraphs. A few common characters (opening and closing quotes, and horizontal punctuation such as hyphens, minus signs, and em and en dashes) look the same in typewritten copy (i.e., ASCII) but are quite different in typeset copy. I think using the proper characters precludes ambiguity and improves readability, and I think readability takes precedence over simpler coding. Some others may disagree, however. [[User:JeffConrad|JeffConrad]] 23:08, 17 March 2007 (UTC)
 
==Exposure for circuses==
 
Sources vary, but the one (ANSI PH2.7-1973, Photographic Exposure Guide) with the most specific recommendation for circuses, gives a value equivalent to EV&nbsp;8 for ISO 100. A later version of that guide, ANSI PH2.7-1986, gives a value of EV&nbsp;8&ndash;EV&ndash;9 for "Brightly lit sports events, stage shows, and the like" (included in the article's table), but makes no mention of circuses. The ''Kodak Professional Photoguide'' (Publication R-28, 1986), and Kodak's ''Existing-Light Photography'' (Publication KW-17, 1991) suggest values closer to EV&nbsp;7. The recommendation could be broadened to include values from R-28, but doing so would properly require every other value to be re-examined as well. There probably are additional sources that merit equal consideration, so going beyond the current sources could be a bit of a project.
 
For now, I've revised the table to mention that the values for circuses and ice shows assume floodlighting. [[User:JeffConrad|JeffConrad]] 02:22, 20 April 2007 (UTC)
 
== EV as an indicator of camera settings ==
 
I don't get it. According to ''Table 1.'' faster shutter speed results in higher exposure value. While IMHO it should be the opposite. If we get 0 EV with 1/100 then setting shutter to 1/200 should give us -1 EV. The table is completely wrong i think. Can anybody correct me if I'm wrong? [[User:Jan Winnicki|<span style="background-color:#fff; color:#000; border:1px solid #f0f0f0; padding:4px; font:9px Tahoma, Verdana;">Jan Winnicki</span>]] [[User Talk:Jan Winnicki|<span style="color:#fcc200;">*</span>]] 11:01, 30 September 2007 (UTC)
 
:No, the table doesn't say that faster shutter speed '''''results in''''' higher exposure value; it says that faster shutter speed '''''is''''' a higher exposure value; that's what it means.  Think of it this way:  in higher light levels, your meter tells you to use a higher EV setting, to let less of that light into the camera, so you set a faster shutter speed. [[User:Dicklyon|Dicklyon]] 15:59, 30 September 2007 (UTC)
 
== Hasselblad gets all the credit? ==
 
Weren't Kodak Retinas the first cameras to use the LVS as it was originally known? Al Olson, who could probably provide authoritative sources, has written that the LVS was used on the IIc (1954) and the IIIc (1954). LVS was renamed EVS in '57 with the IIIC (1957). Doug Kerr has added the Ib (1954) and IB (1957). The Vitessa L (1954) has settings that are numerically equivalent to EV and an uncoupled light meter that gave a readout in EV (source: my Vitessa L). Seikosha introduced the MXL shutter in 1956. This had permanently-coupled LV/EV settings. The Aires 35-II-L, Konica III, Olympus LS/2C and Ricoh 500 (with "Triggermatic" rapid wind) all had the MXL. The MXL could be set to half LV settings. Because of the shutter speed series (eg 1/2, 1/5) the integer LVs did not all match to a standard aperture. (source: a 1957 article in US Camera about the Aires, Olympus, Ricoh and Konica cameras that used the Seikosha shutter with EV markings. The article refers to 'light value system also known as the exposure value system'.)
[[User:Helen Bach|Helen Bach]] 22:06, 11 October 2007 (UTC)
 
==Dimensional consistency in definition of EV==
 
Here is something more mathematical to think about: The definitions EV = log<sub>2</sub>(N<sup>2</sup>/t) or 2<sup>EV</sup> = N<sup>2</sup>/t are mathematically inappropriate: A scientist or a mathematician would not take the logarithm of a quantity with physical units (in this case, seconds).
 
To put it another way, consider the definition 2<sup>EV</sup> = N<sup>2</sup>/t = LS/K in terms of the exposure equation. An exponent (in this case, EV) of some power (in this case, two) cannot have and should not have physical units. Exponents should be pure numbers. EV should be measured in stops, and stops should not depend on units. Stops are simply the number of multiples of two in a (pure) number. Nevertheless, the right-hand side of the definition N<sup>2</sup>/t has units of reciprocal seconds. Logically, the definition is incorrect.
 
(Examples of empirical laws with an exponential or logarithmic form abound: the Beer-Lambert Law, the Weber-Fechner Law, first-order chemical kinetics, biological growth. In each case, we have the logarithm of a ratio in which the physical units cancel.)
 
This would not be a problem if there were a t<sub>o</sub> in the exposure equation and particularly in the definition of EV with physical units that would cancel the units of time. For instance, 2<sup>EV</sup> = N<sup>2</sup> / (t/t<sub>o</sub>) = L(t<sub>o</sub>)S/K is a correct mathematical statement.
 
Note well that N = f/D<sub>aperture</sub> and S = H<sub>o</sub>/H<sub>sp</sub> are pure numbers. (H<sub>o</sub> is mathematically the speed point exposure for S = 1.) L(t<sub>o</sub>)/K is also a pure number, though you might not recognize it as such because the exposure meter constant K is regularly quoted incorrectly with units of lux or lumen per square meter instead of lux seconds or lumen seconds per square meter. The definition of A<sub>v</sub> is not a problems because N<sup>2</sup> or A<sup>2</sup> is a pure number. (Although using N as the aperture number is a problem because the APEX system uses N for scaling constant and A for the aperture number.) The definition of T<sub>v</sub> is a problem that could be rectified using T<sub>v</sub> = log<sub>2</sub>(t<sub>o</sub>/t) (where t is used instead of the T used in the APEX notation.) (Note that T<sub>v</sub> is then the ''relative shutter speed'' in stops.) S<sub>v</sub> is not a problem because film speed is a pure number. B<sub>v</sub> is a problem and should be defined so that we are calculating the logarithm of the pure number log<sub>2</sub>(L t<sub>o</sub>/K). The APEX scaling constant N = 2<sup>1.7</sup> should be eliminated as unnecessary (in the face of a clever choice of K).
 
The authors of ANSI PH2.5-1960 should be taken as the authors of the APEX system. They were no doubt influenced by the German D.I.N. sensitometric naming system that used logarithms and that could very well have been around prior to the 1950s. Unfortunately, the authors were not strict theoreticians. The traditional definition of the exposure value should be referenced, but since this is an encyclopedia, the mathematically correct expressions should be used.
As to what comes first (the topic of this discussion), it seems appropriate to start with the (correct) definition in terms of aperture number and exposure times (or relative shutter speed), to recognize that this ratio appears in the common (midtone) exposure equation whose purpose is to give a pair of camera settings, and to note that the binary logarithm converts these values into stops--particularly stops that can be added or subtracted:  EV = stops(A<sup>2</sup>) + stops(t<sub>o</sub>/t) where t<sub>o</sub>/t is simply the denominator of the fractional exposure time. I don't see any reason to introduce the APEX monikers. You could allow that the various ''terms'' that go into the calculation are those quantities in ''stops''.  It should mention that the purpose of the EV is to make exposure calculations simpler. It does when you have stop tables for A2, t<sub>o</sub>/t, S/K and measured values of Lt<sub>o</sub>. Table 2 in the article would be more useful for calculations if it gave values of Lt<sub>o</sub> instead of EV.<br />
--[[User:Calculist|Calculist]] ([[User talk:Calculist|talk]]) 20:42, 15 October 2008 (UTC)
 
:Indeed, the Germans who inspired the concept of EV were not strict theoreticians; the exposure formula in its various forms has never been other than a rule of thumb. But to devise a “correct” system of definitions would constitute original research, which we cannot do. I've added a mention that the definition of EV is dimensionally inconsistent; see if that addresses the problem. Because EV isn't a physical law, I've also added that exposure time is in seconds.
 
:I agree that we don't need the APEX monikers, as I had previously suggested. They've never seen any practical application and serve more to distract than inform. But that suggestion did not meet with much favor, so I dropped the matter.
 
:On the issue of strict correctness, EV differences are measured in ''steps'' (divisions of the exposure scale) rather than ''stops'' (devices that control the amount of light transmitted). But the proper terminology seemed to confuse most people, so it was relegated to a footnote. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 22:05, 15 October 2008 (UTC)
 
::As an alternative to your wording "so properly, the denominator is the numerical value of the exposure time in seconds" (which took me a moment to recognize what you meant), what about "so properly, the denominator should be divided by a standard exposure time, such as one second, to cancel the physical units in t and to leave a dimensionless number (in the same way that the aperture number N, the ratio of the focal length and the aperture diameter, is a dimensionless number)."
 
:::I had similar misgivings about the wording; I've tried to simplify it a bit—see what you think. I think discussing a standard exposure time <var>t<var><sub>0</sub> is more likely to confuse than inform; perhaps more to the point, though, I'm not sure that dimensional consistency really applies to other than physical laws, and if we get too carried away with correctness here, we may imply that EV is more than it really is—just a number that conveniently encodes combinations of camera settings. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 23:30, 16 October 2008 (UTC)
 
::Steps and stops: that is something that even I have avoided.
 
::My other suggestion is a different form of the EV table. I find a table of EV values with aperture numbers and "shutter speeds" along top and side useful. I have, for instance, along the top, the representative aperture numbers, the actual aperture numbers, and the number of stops (steps). In that way the reader can see the two components that add together and the stripes of equal EV values for equivalent camera settings. I can give you a copy if you want it.
 
:::We originally had the table in that form (as in this [http://en.wikipedia.org/w/index.php?title=Exposure_value&oldid=75225208 12 September 2006 version]),  but some people objected, and we put the table in its current form, which, in my experience, is less common than the one you propose. There is some argument for the current form, however; if one first determines the EV required by certain lighting conditions, putting EV as the stub column does make for a fairly logical index into acceptable combinations of camera settings. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 23:30, 16 October 2008 (UTC)
 
::Again and finally, a table of Kodak Lvs is easier to use in calculations than a table of Evs. You have to be careful, though. If you or Kodak has used the values from the ANSI Exposure Guide (1986), there is that inappropriate scaling factor N = 2<sup>1.7</sup> that needs to be removed.  --[[User:Calculist|Calculist]] ([[User talk:Calculist|talk]]) 21:50, 16 October 2008 (UTC)
 
:::This article is about exposure value, so I don't see how we could give the LVs more than a mention. If we do so, they probably also should get mentioned in the Light value article. I don't have an authoritative source for Kodak LVs, but if you have one, I'd be glad to help get it added, especially to the Light value article—we've covered almost all other uses of the term, so addition of the Kodak values would be good for the sake of completeness, as well as to demonstrate that the concept has been around for quite some time.
 
:::Tables in ANSI PH2.7-1986 gave incident-light value <var>I<sub>v</sub></var>, defined as in ANSI PH2.5-1960. All values that I used in Table 2 of this article were converted to EV for ISO 100 using
 
::::<math>\mathrm{EV} = I_v + S_v</math>;
 
:::the scaling factor (strictly, 2<sup>−1.75</sup>) was incorporated when calculating the speed value <var>S<sub>v</sub></var>. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 23:30, 16 October 2008 (UTC)
 
I've slightly tweaked the explanation for the dimensional inconsistency, and moved it to a note to avoid needless repetition in the article. I'm still not sure whether it adds to or detracts from the article; if the former, we should add similar notes to [[APEX system]] and similar articles; if the latter, we should remove it from this article. The photographic literature is filled with sloppy use of terminology; as [[User:Dicklyon|Dicklyon]] mentioned in [[Talk:Shutter_speed#Speed_measured_in_seconds.3F|Talk:Shutter speed]], it is not our prerogative to change that terminology, however wrong we think it may be. We probably could address most of the technical inaccuracies by adding notes such as the one I added to this article, but in doing so we could be opening a can of worms. Opinions, anyone? [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 21:57, 17 October 2008 (UTC)
 
I agree with Calculist; it takes only one line to clarify that <math>t_0</math> = 1 sec. [[User:Nfette]]  <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/68.226.31.48|68.226.31.48]] ([[User talk:68.226.31.48|talk]]) 17:41, 23 December 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->
 
:It would be easy to add, but I fear we’d be venturing into [[WP:OR]]. The way we have it is how it’s done by every published source I’ve ever seen. Lack of dimensionless function arguments is actually quite common; for example, glass manufacturing usually deals with the log of viscosity, and we speak of log exposure in photography. Although this practice goes against what many of us have learned, our role here is to document rather than criticize or “improve” a formula or “educate” those who we think misuse them. We may already be pushing it with the note I added in response to Calculist’s comment. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 00:23, 24 December 2010 (UTC)
 
== EV of the Sun Surface ==
 
I've added an EV value for the Sun surface: EV 34.
 
I realize this seems somewhat bizarre.  Hardly anyone takes pictures of the sun surface with a DSLR, and it actually can't be done without special equipment, since even ISO 50, f/32, and 1/3200 sec, which is about the bright limit for most cameras, is only good for an EV 24 scene.  You need a Baader film (optical density D=5, which corresponds to 17 stops) to cut the light in order to take a sensible picture or view the sun safely.
 
Bizarre or not, I've found this value useful in the design of cameras.  An interline CCD for instance, might have a specification of 1000x antiblooming.  That means that when the wells overflow, 99.9% of the electrons end up in the overflow drain, and 0.1% end up in the adjacent wells.  Because the sun is often 1,000,000x brighter than the rest of the scene, there can be a significant overflow current into those adjacent wells.  You might then ask what exposure setting would be necessary to eliminate the big streak through the picture when the sun is in the frame.  The calculation has many details, but one of the inputs to the calculation is the surface brightness of the sun.  And if you try to reproduce the problem in the lab, it turns out that many things that are bright, such as halogen spotlights pointed directly into the camera lens, or the Space Shuttle rocket plume, are not nearly as bright as the surface of the Sun.  Focussed laser beams can be.
 
I also realize that the value I've supplied does not come with a reference.  It can be independently derived from the other data in the article: the full moon surface is listed as EV 15, and a scene under full moonlight is listed as EV -3.  A scene under bright sunlight is listed as EV 15, 18 stops brighter than full moonlight.  Because the moon and sun are nearly the same angular size in the sky, the 18 stop brighter lighting must be coming from an 18 stop brighter surface.  Thus the surface is EV 15+18 = EV 33.  My own measurements give a value of EV 34, and I can't account for the 1 stop difference.  If someone wants to change the listed value in the article to EV 33 I'm fine with that.
 
[[User:Iain.mcclatchie|Iain McClatchie]] ([[User talk:Iain.mcclatchie|talk]]) 09:02, 17 December 2008 (UTC)
 
:And what if we're not fine having your [[WP:OR]] instead of [[WP:Verifiability]]?  Notice that an official source is cited for the table data, but your new item is not in that source, so it would need at least a footnote to explain how it's verifiable; but if you're not even sure which is the right answer, it's hard to see how you will be able to cite something reliable.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 13:00, 17 December 2008 (UTC)
 
:The argument is reasonable, if somewhat oversimplified. A note explaining it would definitely be needed, though it's tough to say whether such a note would suffice absent support from a verifiable source. Using various methods, I get values between about EV 33.1 and EV 33.5 for an altitude of 40°. Describing any of these methods in sufficient detail to support the value obtained would require a note comparable in complexity to a small article, so I don't think that's the right approach.
 
:I'm not too concerned that there is a range of values; this consistent with the caveat stated below Table&nbsp;2. But I agree with Dick that adding it without support from a verifiable source is marginal. In any event, the Sun doesn't have phases, so the “Full” line is inappropriate. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 23:35, 17 December 2008 (UTC)
 
:I forgot to mention that your “measured” value is definitely [[WP:OR]] and therefore inappropriate; using the derived value of EV&nbsp;33 remains marginal. I'm not suggesting that your measured value is wrong, but simply that WP guidelines disallow putting it in the article. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 01:36, 18 December 2008 (UTC)
 
[[Image:Vogel Moon.png|right|thumb|150px|Moon, New York, 6 March 1865 - Moon photo of [[Lewis Morris Rutherfurd]], mentioned in the 1888 Britannica]]
 
[http://books.google.com/books?id=eznlTmfuQyIC&pg=PA116&dq=brightness+sun+moon+surface&ei=-eVJSZvHEZXyNqGxtdwN#PPA116,M1 Here's a source] that talks about the sun relative to moon brightness as well as absolute numbers.  Not connected to EV, but it would be a simple step... [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 06:01, 18 December 2008 (UTC)
 
The magnitude difference given there, 14.29, corresponds to almost exactly 19 stops (1 magnitude being a ratio 10^0.4 of 1.33 stops), which would give your EV 34 number if the subtended angles are equal (and since the sun size within the range of variation of moon size, that's close enough to ignore).  Jeff, should we consider adding this odd one after the chart, with citation to this book and a brief explanation of the change of unit? [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 06:38, 18 December 2008 (UTC)
 
By the way, this 19 stops, or factor of just over 500,000, is also in pretty near agreement (within 1/4 stop) with ratios around 600,000 reported in the [http://books.google.com/books?id=hakMAAAAYAAJ&pg=RA1-PA802&dq=brightness+sun+moon+surface&ei=HPBJSf22BYGMNoa6we8N 1888 Britannica]. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 06:45, 18 December 2008 (UTC)
 
And one more thing:  if EV 15 is the right exposure setting for ISO 100, typical scene in daylight, the 19 stops less light might suggest using EV -4 in moonlight; yet the ANSI exposure guide suggests -3 to -2, which would seem to be a stop or two underexposed.  I believe the explanation of the discrepancy is that in daylight you're generally trying to capture some shadow detail, and white highlights, while for a moonlit scene, unless you want it to look like a sunlit scene, you want black shadows and excellent highlight detail closer to the midtones.  They seem to have worked that into the table, which is why Iain's 15-(-3) didn't lead to the number that his measurments and the sources agree on.  So these numbers shouldn't be interpreted as implying a definite illuminance level, but rather just what they are, suggested exposures.  When you take pictures of the moon, like the Rutherfurd one that the Britannica talks about (bottom of col. 1 p.802), an exposure guide is what's relevant (Iain, I have the original print of this one if you'd like to see it, the frontispiece of the book by Vogel).  For the sun, it might be best to leave the quantification in some other form; unless you want to take pictures of it. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 07:08, 18 December 2008 (UTC)
 
:I think the currently accepted ratio (for a full moon) is about 402,000, or 18.6 steps; it's fairly simple to derive this from consideration consideration of several parameters for which the values are generally agreed upon. Even so, some massaging is needed. The Moon's reflectance is about 15% at opposition, but we never see it at opposition except during a lunar eclipse. The reflectance falls off rapidly as the Moon moves away from opposition, and a more typical value is about 12%. I think it's easy enough to find a source for the latter value, but in most cases the sources are telling only part of the story.
 
:The luminance ratio is the same as the illuminance ratio, but using the scene EVs from the table involves a bit more than may be apparent. The EVs for scenes (based on the illuminances from the Sun and Moon) include the contributions of direct illuminance from the bodies and indirect illuminance from the sky. It seems reasonable enough to me that both the direct and indirect contributions scale linearly with the intensity of the light sources, but I don't think I've seen a source that explicitly says this, and I'm not sure what seems obvious to me would meet [[WP:Verifiability]].
 
:We could avoid some of this problem by using the absolute values. Even so, there are a few issues. The value given in the source in the link is for the Sun at zenith, which is never observed outside the tropics. Because the [[airmass]] at zenith is 1, the reduction from 1.85×10<sup>9</sup>&nbsp;cd/m<sup>2</sup> to 1.4×10<sup>9</sup>&nbsp;cd/m<sup>2</sup> evidently assumes an extinction coefficient of about 0.28, and we'd need this value to arrive at an EV of 33.2 (which I assume we'd round to EV&nbsp;33) for a solar altitude of 40°. It's easy enough to show how this is obtained, but it's a matter of what liberties we may take and how much we need to explain them. It would help if there were a more expansive article on [[atmospheric extinction]], but at present, such an article doesn't exist.
 
:One other problem we might face: it's hard to find two sources with the same values for some parameters. I got a value of 1.6×10<sup>9</sup>&nbsp;cd/m<sup>2</sup> for the Sun's zenith luminance from the IES Handbook (though I seem to have lost the copy of the relevant page), and values for the extinction coefficient range from the “standard” value of 0.21 to almost 0.40 for some urban areas. Perhaps, though, we simply need to accept that, as with so many things photographic, the EV for the Sun isn't something that's meaningfully taken to six significant figures.
 
:Most values in the ANSI exposure guides are rounded to the nearest whole EV (actually, they're given as L<sub>v</sub> and I<sub>v</sub>, respectively, in the 1973 and 1986 guides). Conversion to EV requires the S<sub>v</sub> for ISO 100 speed. Assuming that, at the time, ISO 100 was actually <math>128/^3\sqrt 2</math>, this works out to 4.92, so there's some additional rounding in Table&nbsp;2 of the article.
 
:If we do add the value, I think it should be in the table, else no one is likely to find it. The real issue is what we would need to support whatever value we might add. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 08:37, 18 December 2008 (UTC)
 
:Expanding briefly on Dick's final comment: in a few simple circumstances (e.g., a broad light source or a single scene element with uniform luminance), it's possible to directly relate EV to scene luminance, but for the most part, Table&nbsp;2 in the article is an exposure guide. Most of the values are taken from the 1986 ANSI exposure guide, which give incident-light values. These obviously make little sense when applied to a light source such as the Moon, or to a dark scene (such as a night street scene) with a few small light sources; the tabulated values are really meant to suggest camera settings that will result in a satisfactory picture. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 09:12, 18 December 2008 (UTC)
 
 
:Absent some additional ideas or a published value for a reasonable solar altitude, I think we should remove the EV for the Sun from the table. As I indicated previously, there probably are many ways in which a reasonable value could be provided and supported, though doing so would require getting into astronomical photometry in some detail, and that isn't the purpose of this article.
 
:I have a problem basing relative luminance on Rougier's 1933 value of −12.46 for the Moon's visual magnitude, because that value differs significantly from more recent values (e.g., Allen (1973) gives –12.73 and Lumme and Irvine (1982) give −13.04). The latter value is based on zero phase, which, as mentioned, can't be observed from Earth; under more typical conditions, the value would decrease to about −12.8. The difference then would be about 18.5 EV; if combined with the unrounded value of EV&nbsp;14.9 for the full Moon's luminance, the rounded value for the Sun's luminance would be EV&nbsp;33, so I don't think giving a value of EV&nbsp;34 would be appropriate.
 
:It is fairly simple to show that a celestial body's luminance is related to its direct illuminance by
 
::<math>L =\frac {E} {\pi \sin^2 s} \,,</math>
 
:where ''L'' is the luminance, ''E'' is the direct illuminance from the body, and ''s'' is the body's angular semidiameter. It then could be shown that the luminance ratio for two bodies is the same as the illuminance ratio if the semidiameters are same, provided that it could be shown that the effects of indirect illuminance from the sky could be ignored.
 
:It would be better to start from absolute values, either published or derived from basic parameters. The extraterrestrial solar illuminance is
 
::<math>E_\mathrm S = K_\mathrm S E^\prime_\mathrm S \,,</math>
 
:where ''K''<sub>S</sub> is the luminous efficacy of sunlight and ''E''′<sub>S</sub> is the extraterrestrial solar irradiance (i.e., the solar constant). The extraterrestrial luminance is then
 
::<math>L_\mathrm S =\frac {K_\mathrm S E^\prime_\mathrm S} {\pi \sin^2 s_\mathrm S} \,.</math>
 
:Except for an astronaut, there is little value in an extraterrestrial luminance. There's also not much value in a terrestrial value at zenith; the article is about photographic exposure, not theoretical astronomical photometry. It would seem reasonable to give a value for same altitude, 40°, as used for the Moon. Consequently, we would need to account for atmospheric extinction, even with a published value (unless it were given for 40°).  The effect of atmospheric extinction is
 
::<math>L = L_\mathrm{xt} \, \mathrm e^{-cX} \,,</math>
 
:where ''L''<sub>xt</sub> is the extraterrestrial luminance, ''c'' is the extinction coefficient, and ''X'' is the [[airmass]]. The complete expression would be
 
::<math>L_\mathrm S =\frac {K_\mathrm S E^\prime_\mathrm S} {\pi \sin^2 s_\mathrm S}
\, \mathrm e^{-cX} \,;</math>
 
:we'd need values for ''K''<sub>S</sub>, ''E''′<sub>S</sub>, ''s''<sub>S</sub>, and ''c'', and would need to calculate ''X'' (though at an altitude of 40°, almost any method would suffice). Using values of 94.2&nbsp;lm/W, 1366&nbsp;W/m<sup>2</sup>, 0.26656°, and 0.21, respectively, and using the secant formula for ''X'', the result is
 
::<math>L_\mathrm S = \frac {94.2 \times 1366 } {\pi \sin^2 0.26656^\circ}
\,\mathrm e^{-0.21 \times 1.556} = 1365 \; \mathrm{Mcd/m^2} \,,</math>
 
:equivalent to EV&nbsp;33.4. The Budding and Demircan extraterrestrial luminance of 1850&nbsp;Mcd/m<sup>2</sup> would give EV&nbsp;33.3.
 
:But we'd need to source or derive everything used above, and a derivation would seem to be pushing it with respect to [[WP:OR]]. Even if a derivation were acceptable, it would make for the mother of all notes. And it's way off the topic of the article.
 
:Again, short of finding a good published value for the Sun's luminance, I think it would be difficult to justify adding it to Table&nbsp;2. If no one objects, I'll remove this value. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 05:52, 21 December 2008 (UTC)
 
::I agree.  It's an interesting and useful estimate, but not suitable for wikipedia. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 07:31, 21 December 2008 (UTC)
 
:A reread of Kodak Technical Publication P-150, ''Astrophotography Basics'', [http://www.kodak.com/cluster/global/en/consumer/products/techInfo/p150/p150b.shtml Solar Eclipse] (the complete publication is [http://www.kodak.com/cluster/global/en/consumer/products/techInfo/p150/P_150.pdf available in PDF]) gives the formula (p. 11 of the PDF)
 
::<math>f^2 = St \, 10^{7-D} \,;</math>
 
:where ''f'' is the lens ''f''-number, ''S'' is the ISO speed, ''t'' is the exposure time in seconds, and ''D'' is the filter density. With some rearrangement, ISO 100 speed, and a ''D'' of zero (i.e., no filter), this gives
 
::<math> \frac {f^2} t = 2^\mathrm {EV} = 10^9 \,,</math>
 
:which works out to EV&nbsp;32.9, and supports a value of EV&nbsp;33 for the table. Or does it? As we've discussed, Table&nbsp;2 is primarily an exposure guide, and actually attempting an exposure without a filter would probably fry the sensor as well as the photographer's eye. What P-150 really suggests is using a 5.0 density filter and EV&nbsp;16.3. Again, this article is about photographic exposure rather than the luminances of solar system objects, so unless we decide to expand coverage to astrophotography, including filter recommendations, I think it may be a good idea to simply leave the Sun's EV (and the attendant caveats) for another topic. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 04:02, 23 December 2008 (UTC)
 
::If anyone is reading this, PLEASE DO NOT LOOK AT THE SUN THROUGH YOUR VIEWFINDER.
::That said, taking a shot with the sun in frame does not fry the sensor.  CMOS sensors can point at the sun all day long, for months, without obvious ill effect (I haven't tested this down to f/1.4, though, and I haven't tested it on DSLRs, which have fancy autofocus sensors and specific warnings not to point them into the sun).  CCD sensors produce the previously mentioned large blooming artifacts.
::I'll note that both of you have managed to come up with better support for a sun EV value than I did.  Is there no way to put this useful information into Wikipedia somehow?  Can I make a "EV of the Sun" article, and include your discussion here, and then reference that from this article?
::[[User:Iain.mcclatchie|Iain McClatchie]] ([[User talk:Iain.mcclatchie|talk]]) 21:12, 3 January 2009 (UTC)
 
:::Iain (what a funny name!), you need to get it published in a realiable source first; then we can write an article on it, sourced to that. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 21:35, 3 January 2009 (UTC)
 
 
:::Iain, it's fairly easy to support a value for the ''luminance'' of the Sun; I could probably cite at least half a dozen credible sources (which nonetheless vary slightly, though differences in EV would be minor). Absent a source that specifically gives an EV for stated conditions (e.g., altitude of 40°), the conditions used to derive a value would need to be stated, as I've said. As an example, Allen's ''Astrophysical Quantities'' (3rd ed, 1973) gives the Sun's luminous intensity as 2.84×10<sup>27</sup>&nbsp;cd; with a solar radius of 6.955×10<sup>8</sup>&nbsp;m, it's easy to get an extraterrestrial luminance of 1869&nbsp;Mcd/m<sup>2</sup>. A terrestrial value would require assumptions about air mass and extinction coefficient that would need to be stated and perhaps justified. The ANSI exposure guide doesn't state how the values for the Moon were obtained, but a read of the guide suggests they were determined from measurement or practical experience or combination thereof rather than from astrophysical considerations. Consequently, a direct comparison might be difficult, though I may be splittting hairs here.
 
:::I come back to the basic question: is the real objective to give a recommendation for photographic exposure or to give a value for the Sun's luminance? If the former, it should be related to conditions under which someone might actually take a picture, i.e., using a filter, as I mentioned. If the latter, such as for designing a sensor, wouldn't the photometric (or even radiometric) value be more useful? I agree that the information is useful, but think it might better fit in an article on physical and photometric properties of the Sun. I have generally been less concerned about using EV as a measure of luminance than have some authors, but I'm not sure the concept makes much sense outside of a photographic context (or perhaps using an exposure meter as a poor man's luminance photometer). [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 02:22, 4 January 2009 (UTC)
 
::::Or one could make an article on [[solar photography]] from [http://books.google.com/books?q=%22solar+photography%22+exposure+filter&um=1&as_brr=3 these book sources]. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 02:37, 4 January 2009 (UTC)
 
:::::Or one could add it to the [[Astrophotography]] article, which currently says nothing about the Sun. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 07:14, 4 January 2009 (UTC)
 
== EV—illuminance conversion ==
 
I don't know what was intended by the Ray 1993 reference, and I can't find a match in the Library of Congress database. In any event, the revised values were not in accord with the formulas (which are correct and in agreement with ISO 2720 and many other sources). The previous values were also in agreement with two different Minolta meter manuals, so it's quite unlikely that they're wrong. Without seeing the claimed source, it's tough to determine why it might differ from the previous version of Table&nbsp;3 in this article, but something is amiss. Regardless of the values in the claimed source, they cannot reasonably be put in the table without reconciling differences with the formulas and other sources. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 02:56, 13 January 2009 (UTC)
 
:The ref was confused, mentioning both 1993 and 2002.  The Ray 2002 has a bit on [http://books.google.com/books?id=cuzYl4hx-B8C&pg=PA592&dq=intitle:%22Applied+Photographic+Optics%22+inauthor:Ray+EV&lr=&as_brr=0&as_pt=ALLTYPES&ei=kQtsSdmEF4fEkAT4lrXBAQ#PPA592,M1 this page] that might be the basis of different numbers. I haven't quite interpreted it yet. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 03:56, 13 January 2009 (UTC)
 
::I think the editor's confusion arose simply from copying and pasting another citation of Ray (2002).
 
::Figure 66.2 on p. 592 of Ray (2002) is not easily interpreted ... There's some confusion in the figure caption, which states that the luminance is in apostilbs, or lumen&nbsp;m<sup>−2</sup>; the latter is a measure of illuminance rather than luminance. But the values appear to be for luminance, measured in apostilbs {{nowrap|1=(asb; 1 asb = 0.3183 cd m<sup>−2</sup>)}}, using an ISO arithmetic speed of 12.5 and a calibration constant of 12.5 rather than illuminance. Then
 
:::<math>\mathrm{EV} = \log_2 \left( \frac {LS} K \right ) = \log_2 \left ( 0.3183 L \right ) = \log_2 L - 1.65</math>
 
::Thus EV&nbsp;5 corresponds to a scene luminance of 100&nbsp;asb, as is shown in the table. So the table does seem to be for luminance, and inapplicable to the previous edit.
 
::: Apologies. It was me what done it. My copy of Ray, et al.'s Manual of Photography is the 1993 print of the 1988 edition. I was trying (with humiliating ineptness) to hint that page numbers might be different whilst guessing that the data has not changed in the newer edition ... my bad. Sorry for the confusion. The table of data I referred to is entitled ''Table 20.3 Photometric units and camera exposure. Approximate corresponding values of various units of luminance and illuminance related to exposure value (EV) for camera determination with a film of speed ISO 100/21°'' and plots EV (-2 to 18) against cd/m<sup>2</sup>, stilb, apostilb, cd/ft<sup>2</sup>, lambert, foot-lambert, lux, phot, and lm/ft<sup>2</sup>. --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 23:29, 4 February 2009 (UTC)
 
::::I think Table 20.3 in Ray (1993) is essentially the same as Table 19.3 in Ray (2000). [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:02, 5 February 2009 (UTC)
 
::I believe the reverted data were taken from a table equivalent to Table&nbsp;19.3 on p.&nbsp;323 of Ray (2000). The header for the rightmost column indicates that the illuminance values give an EV for 100% reflectance, and that appears to be the problem. The values in Table&nbsp;3 differ from those in Ray (2000) by a factor of 6.25; dividing 100 by this gives a reflectance of 16%, very close to the reflectance assumed in relating the luminance and illuminance values in Table&nbsp;3 (reflectance is given by π''K''/''C''; with {{nowrap|1=''K'' = 12.5}} and {{nowrap|1=''C'' = 250}}, reflectance is 15.7%). Consequently, those data are inapplicable to this article. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:24, 13 January 2009 (UTC)
 
:::If we use a similar format for the formulae, defining, comparing and explaining K and C should become a little easier.
::::L = K/S * 2^EV and
::::E = C/S * 2^EV
:::Where L = luminance cd/m<sup>2</sup>; E = illuminance lm/m<sup>2</sup>; S = ISO sensitivity. --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 23:29, 4 February 2009 (UTC)
:::: Ray (2000 p315) hints that K = Key-tone: ''Measurement of a key tone: A subject zone of intermediate luminance, i.e. a midtone, is selected and located at a fixed point on the characteristic curve. Typically an exposure 10 to 16 times more than that for the shadow or speed point is given. This key tone may be a Caucasian flesh tone (about 25 per cent reflectance)... [or] a medium grey card (18 per cent reflectance) is held so as to receive the same illumination as the subject it is replacing... The ‘arrow’ setting of the original Weston meter was calibrated for such a mid-tone, as are most metering systems.'' ... "exposure 10 to 16 times over speed point" encompasses the K=12.5 value. [[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 12:48, 5 February 2009 (UTC)
 
:::::I don't see any such implication. The key tone is a simplified application of the [[Zone system]]. The calibration constant ''K'' was empirically determined to give the “best” exposure from measurements made with wide-area averaging meters. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 21:17, 5 February 2009 (UTC)
 
:::(Incidentally, it may be worth noting that Ray, Fujifilm and others use log<sub>10</sub>(''H'') for illuminance rather than log<sub>10</sub>(''E''). My guess is E is the proper notation for illuminance, and H has crept into photography from mis-translating Hurter-Driffield's "''HD'' curve" as a plot of H (for illuminance) against D (for density) :) --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 23:29, 4 February 2009 (UTC)
 
::::I'd be surprised to see a plot of ''D'' vs. log(illuminance), because it wouldn't make much sense. I've never seen other than ''D'' vs. log(exposure). [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:02, 5 February 2009 (UTC)
 
::::: Yes I see my error. Exposure = Illuminance * Time. So if H = exposure and E = Illuminance, ... The Illustration (H&D_curve.png) at [[Hurter–Driffield_curve]] shows Exposure as "<sub>log</sub>E<sub> C.M.S</sub>" ... any idea what C.M.S stands for? Cock-ups per Moron per Second? --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 12:48, 5 February 2009 (UTC)
 
::::::Pretty close.  Probably candle-meter-seconds, where a "candle meter" is a bastard illuminance unit analogous to a "[[footcandle]]", I think – that article says "Some sources do however note that the "lux" can be thought of as a "metre-candle" (i.e. the illuminance cast on a surface by a one-candela source one meter away).".  So think of it as Lux seconds. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 20:42, 5 February 2009 (UTC)
 
:::::::I won't get into the unit's parentage, but C.M.S. is a mighty unusual way to state it; far more common was meter-candle seconds, or mcs—long ago, Kodak film characteristic curves gave exposure in mcs (strictly, they gave log(exposure) in log(mcs)). As Dick mentioned, it's the same as lux seconds. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 21:17, 5 February 2009 (UTC)
 
::: After reading http://www.natmus.dk/cons/tp/lightmtr/luxmtr1.htm I concluded that Ray's data correlates with C=πK and K=12.5. The C=πK proof is worth pursuing not only as a really easy formula, but more importantly to determine the "application caveats" for valid luminance values deduced from illuminance readings and vice versa. An article by Schlyter (http://stjarnhimlen.se/comp/radfaq.html#6) appears to suggest that converting cd/m<sup>2</sup> to π lm/m<sup>2</sup> encompasses spherical geometry and lambertian reflection. Although I don't fully understand the maths, I will attempt to summarise. SI unit definitions state: 4π lumens = 1 candela = 1 lumen/steradian. Reflection at a surface occurs only into a hemisphere (so 2π lm/cd) and then Lamberts Cosine Law kicks in (as a reflectance averaging?) to arrive at (π lm/cd) C=πK. In trying (unsuccessfully) to understand the lambertian step, I found the average value of the cosine of all angles between 0° and 90° tends towards 2/π = 0.6366 which might be related to the 6.25 factor? I must emphasise that maths is not my thing and I am out of my geometrical depth, so any corrections and clarifications are most welcome.--[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 23:29, 4 February 2009 (UTC)
 
::::{{nowrap|1=''C'' = π''K''}} applies only to an object of 100% reflectance. The more general relationship, using consistent units (such as SI) is
 
:::::<math>C = \pi \frac K R</math>,
 
::::where ''R'' is the reflectance.  With {{nowrap|''R'' ≈ 15.7%}}, {{nowrap|1=''C'' = 20''K''}}, consistent with {{nowrap|1=''C'' = 250}} and {{nowrap|1=''K'' = 12.5}} used in the article. Bear in mind that {{nowrap|1=''C'' = 250}} is for a flat (cosine-responding) receptor rather than a hemispherical (cardioid-responding) receptor usually used to meter a three-dimensional subject, so you can't meaningfully compare the illuminance values in Table&nbsp;3 with Table&nbsp;2. The main value of the relationship of EV to luminance and illuminance is for making approximate photometric measurements with a photographic exposure meter. There is no need to normalize values in either table. The relationship between ''C'' and ''K'' is discussed in detail in the [[Light meter]] article, and in much greater detail in the paper Exposure Metering: Relating Subject Lighting to Film Exposure linked at the end of that article. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:02, 5 February 2009 (UTC)
 
::: As far as I can tell, C=πK makes no allowance for arbitrary average reflectance (16%, 18% etc) so it should be used to reference a white surface (eg snow). If so, this is definitely noteworthy (as an "application caveat"). Luminance and Illuminance values in table 3 should be normalised with table 2 values (or vice versa :). It is not currently explicit, but I would guess that table 2 values represent average scene luminance ≈ 18% reflectance.  --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 23:29, 4 February 2009 (UTC)
:::: Stop press! the Luminance value is already reflected and so L effectively includes the 2 reflectance factors: the 15+/-3%avg and the cosine diffusion. To derive C from K, both of these need to be included: so C=πK/p or K=Cp/π, where p is average reflectance due to surface colour. Phew. My diffusion has lifted and my formulae are beginning to look distinctly Cyrillic ... :) --[[User:Redbobblehat|Redbobblehat]] ([[User talk:Redbobblehat|talk]]) 03:56, 5 February 2009 (UTC)
 
:::::The reflectance ''p'' isn't necessarily related to surface color—it applies to a neutral surface (such as a test card) as well. Whether or not you need the factor π depends on the units of luminance; you need it with SI units like cd/m<sup>2</sup>, but not with comparative units like the lambert or footlambert. The easiest way to get the relationship between ''C'' and ''K'' is from the meter calibration equation. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 21:17, 5 February 2009 (UTC)
 
::::Table 2 gives recommended camera settings for the best picture; most derive from average luminance of sunlit outdoor scenes, but some (e.g., a cityscape at night) simply derive from experience. Incidentally, typical snow reflectance is only about 90%, so it's not well represented by an object of 100% reflectance. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:02, 5 February 2009 (UTC)
:::::I have been using Magnesium Carbonate blocks for my tests.  The have a p=98.4%. [[User:Kq6up|Kq6up]] ([[User talk:Kq6up|talk]]) 18:53, 11 June 2013 (UTC)
 
 
::Incidentally, I trust you noticed the oblique sans-serif ''f'' in Ray's Figure&nbsp;66.2 ... [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 06:24, 13 January 2009 (UTC)
 
:::Didn't notice.  GBS won't show me that page, and the book is back at the office.  And you know I'm blind to such things. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 06:56, 13 January 2009 (UTC)
 
::::This is your lucky day ... the same figure is on p.&nbsp;319 of ''The Manual of Photography'' (Ray 2000), replete with oblique sans-serif ''f''. The caption even appears to be correct, and includes an explanation of the rectangle in the center of the figure. Yeah, I know, the MoP is probably also at the office. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 09:30, 13 January 2009 (UTC)
 
:::::Page 62 in the same book says "italic f", which I would interpret in terms of [[Italic type]].  The figure you pointed out says "f-number", does not show an "f/#" construct.  Opinions are pretty split as to whether to set the f in f-number the same as the f in f/#; I don't like to italicize it in f-number, but Ray does, apparently, though in the figure the oblique f was not a true italic (see [[Italic_type#Oblique_type]]).  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 22:52, 13 January 2009 (UTC)
 
== Confusion about use of tabulated values with speeds other than ISO 100 ==
 
Dick, I'd be surprised if the edit you reverted on 13 October 2009 was vandalism—vandals usually aren't that carefully consistent. But it certainly was boneheaded and boorish for an IP to make such an edit without at least some discussion, so perhaps there's little practical difference. In any event, the way in which the ISO speed conversion works is obviously confusing people (hence my comment in the [[Exposure compensation]] article). Offhand, I don't have any great ideas for fixing this. A glance at the ANSI standards offers no help whatsoever; they're probably far more difficult to apply than the simple table based on EV<sub style="font-size: 70%">100</sub>. I've made a couple of minor tweaks, but I don't think they will really be of much help. Perhaps we could replace ''greater'' with ''higher'' or “faster”, though the physical implication, especially with the latter (shades of “shutter speed” ...) is somewhat of a misnomer. And I'm not even sure such a change would help. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 01:54, 14 October 2009 (UTC)
 
:Sometimes with an uncommented anonymous edit inverts the sense of something, like changing true to false or plus to minus, it's simple vandalism; I was giving him the benefit of the doubt, rather than assert that he was just confused and wrong.  Hopefully the small clarification I added will help; thanks for fixing my spelling typo. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 03:50, 14 October 2009 (UTC)
 
::I guess we can see how long it is before this section is “corrected” again. I have no additional ideas. With the revised wording and the examples, I can't think of what else to say. Perhaps we should consider the expanded explanation SOP whenever discussing EV conversions.
 
::There may be some folks who don't know how to calculate base-2 logarithms. But I suppose this article isn't a basic math tutorial, and the folks who really don't get this section probably won't be dealing with logarithms anyway. In any event, I'd rather stick with exact expressions using base 2 than use base-10 logs with magic conversion factors. [[User:JeffConrad|JeffConrad]] ([[User talk:JeffConrad|talk]]) 04:10, 14 October 2009 (UTC)
 
== Sign errors ==
 
[http://en.wikipedia.org/w/index.php?title=Exposure_value&diff=550842971&oldid=540417454 This uncommented diff] introduced a bunch of sign errors.  I notice when a partial fix was done today.  I'm pretty sure it was correct before, so I'll fix it.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 22:38, 24 May 2013 (UTC)
 
== Table 3 Confusion ==
 
I have been trying to understand this page completely for some time now.  I have a strong math/physics background and the math is no problem.  The concepts are very confusing, so I could be off base here.  If I am, I will consider any corrections a teachable moment.  The bright sunlight provides a measurement (I have performed myself) of approximately 10,000 footcandles.  I have also read that in several places that is the correct value.  EV15@ISO100 would be the correct settings on the camera for a good exposure of an average scene under these conditions.  As you know -- it is the sunny 16 rule.  However, Table 3 has the illuminance of EV15@100 as 7611fc.  This is 1/3 of a stop away from the value I expect to see here. Comments? [[User:Kq6up|Kq6up]] ([[User talk:Kq6up|talk]]) 17:21, 11 June 2013 (UTC)
 
:One-third of a stop is generally considered a negligible difference in photography rules of thumb.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 17:25, 11 June 2013 (UTC)
 
::Granted, however the table should represent scientific data derived from calculations or empirical measurements.  33% error would indicate that either an instrument is crude, miscalibrated, or broken.  If the data was derived, then there is a calculation error some where.  This could lead to someone trying to get a deep gut understanding of how all the pieces fit together to bang there head needlessly.  Back to the salt & pepper notebook and head scratching [[User:Kq6up|Kq6up]] ([[User talk:Kq6up|talk]]) 18:21, 11 June 2013 (UTC)
 
:::7611 fc is only 24% lower than 10000; if the rule of thumb gives the right exposure for 7611, it will be slightly over on your typical sunlit scene, which is exactly the direction that you want your rule of thumb to be a little off.  Maybe it's that simple?  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 19:15, 11 June 2013 (UTC)
 
::::The concern I raised was not addressed by the last comment.  Moreover, the table is also ambiguous as it stands.  The illuminance is very straight forward since there is no consideration of placement of tones photographically.  It is simply luminous flux per unit area.  However, there is no clue as to what shade of grey the luminance values would be rendered as photographically (what zone are we talking here? -- zone V?).  The ratio of illuminance to luminance is 20:1 for the metric side of table.  I can understand a factor of 4*pi for the units to line up, and then there is the whole lambertian defuse reflector cosine factor.  When this is integrated over a hemisphere throws in another factor of pi some how.  All very confusing even for a huge science nerd as myself.  This is hard enough to comprehend without the ambiguities in the table.  A paragraph explaining the luminance values especially.  Sorry for the rant.  I just hope my critique will make for a clearer article.  Thanks [[User:Kq6up|Kq6up]] ([[User talk:Kq6up|talk]]) 20:29, 11 June 2013 (UTC)
 
:::::Well, it's all rules of thumb.  As the article says of luminance metering, "Values for the reflected-light calibration constant K vary slightly among manufacturers."  The problem is that scene luminance, or illuminance, is not enough to determine a "best" exposure.  Both reflected and incident light meters, and the sunny 16 rule, give you a guideline, but you can adjust it based on what tonality you're trying to achieve.  The history of standards around metering is complicate; ask Jeff Conrad, iirc he's the expert on this.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 00:04, 12 June 2013 (UTC)
 
::::::I understand it is all a big ol' mess.  I am just trying to get my head around the photometry involved.  Once that makes good sense, I can sort it all out later.  That being said if one sticks to the modern formulas and definitions, it should all be internally consistent.  I doubt the standards themselves are er.  Just that most people don't really understand them.  Just look at some of the replies on Yahoo Answers.  They are horrendous.  One final question.  How do you get notified that there has been a change made to this page?  You responded very quickly.  Also how would I get in touch with Jeff Conrad? [[User:Kq6up|Kq6up]] ([[User talk:Kq6up|talk]]) 01:39, 12 June 2013 (UTC)
:::::::Unfortunately, Jeff seems to have left Wikipedia quite some while ago: [[User:JeffConrad]]. You could try to email him, perhaps he'll answer. --[[User:Matthiaspaul|Matthiaspaul]] ([[User talk:Matthiaspaul|talk]]) 01:54, 12 June 2013 (UTC)
::::::::Indeed, I miss him.  [http://en.wikipedia.org/w/index.php?title=Light_meter&diff=189866942&oldid=189409585 Here are some of his relevant edits] to [[Light meter]]. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 03:37, 12 June 2013 (UTC)
:::::::I don't get notified except by checking my watchlist, which has a few thousand articles on it.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 03:37, 12 June 2013 (UTC)
 
== Sign confusion ==
 
I had an email from an editor concerned about the plus sign in the formula for adapting the table numbers in [[Exposure value#Tabulated exposure values]] to different ISO values, pointing out that dpreview and others go the other direction as at [http://www.dpreview.com/glossary/exposure/exposure].  I have just done an edit to resolve that confusion, showing that the equation with the minus sign goes the other direction.  I added an example showing how it relates to what dpreview says.  Both were correct, but now the relationship should be more clear.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 23:19, 19 January 2014 (UTC)
 
§§ Thank you Dick for looking at this; however, the algebraic sign shown is still wrong - please try and prove this to yourself using the following formulae:
[[File:Formulae.png|thumb|Formula and legend of terms in calculations for Exposure Value]]
 
[[File:EV-chart.png|thumb|A typical EV chart with an independent example proof of concurrence]]
 
Once you've done the mathematical proof, I hope you'll correct the article as I'll leave that you :)
 
Thank you!
 
Kelly
 
[[User:Kbellis|Kbellis]] ([[User talk:Kbellis|talk]]) 01:26, 21 January 2014 (UTC)
 
:Kelly, your formula with the minus sign (which is not justified anywhere that I can see) shows that if you switch to a higher ISO then you should use a lower EV, which corresponds to opening up or using a longer exposure.  That's backwards.  That's not what the dpreview calculator is showing, as I explained.  It is correct, but it is not calculating what we mean by the EV setting to use at a different ISO.  It is calculating the EV100 meter reading (an LV as their footnote explains) that you can use with a particular setting of shutter and aperture.  The article has example of both directions; do you think either example is giving a wrong result?  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 04:58, 21 January 2014 (UTC)
 
:Also, the formula you use for EV<sub>100</sub> is actually the formula for EV, which depends only and N and t, while EV<sub>100</sub> depends only on light level (scene luminance).  The formula for a recommended EV based on metering, that takes speed S and light level L and metering constant K into account is in a later section:
:<math>\mathrm {EV} = \log_2 {\frac {L \cdot S} {K} } \,.</math>
:which clearly implies a plus sign for the effect of S.  You got things the wrong way around.  [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 05:43, 21 January 2014 (UTC)

Revision as of 15:57, 25 August 2014

If you want to talk to me about something, use my talk page, and I will generally respond there.

Algorithms

Algorithmic analysis

f(n) is Θ(g(n))c1,c2,n0 s.t. c1g(n)f(n)c2g(n)n>n0.
f(n) is O(g(n))c,n0 s.t. cg(n)f(n)n>n0.
f(n) is Ω(g(n))c,n0 s.t. cg(n)f(n)n>n0.

Order of functions with increasing growth rate:

1,loglogn,logn,n,n,nlogn,n2,n2logn,n3,2n,n2n,3n.

Sorting

A sorting algorithm may have the following properties:

  • in-place, if it requires Θ(1) extra space.
  • stable, if items of the same sorting key remain in the same relative order they were before the sort.

Selection sort

Best time: Θ(n²).
Average time: Θ(n²).
Worst time: Θ(n²).

Iterate through decreasing sublists, finding the largest item, and swapping that item with the item at the end.

Insertion sort

Best time: Θ(n).
Average time: Θ(n²).
Worst time: Θ(n²).

Iterate through increasing sublists, finding the correct position to place the item immediately following the sublist, shifting all greater elements in the sublist one place to the end. Finally place that item in the correct place.

Bubble sort

Average time: Θ(n²).
Worst time: Θ(n²).

Iterate through decreasing sublists, swapping two adjacent items if they are not in order, until the list is sorted.

HeapSort

Worst time: Θ(n log n).

Take an array, start with the parent of the last element of the array, and work backwards, to ensure the heap property (see the remove operation on a heap). Then remove an item from the top and place in the newly vacated place, thus leaving a list in ascending order.

QuickSort

Average time: Θ(n log n).
Worst time: Θ(n²). ² Average space: Θ(log n).
Worst space: Θ(n) can be remedied to Θ(log n) using a custom stack.

Select a pivot as the first item in the list, then place items less than the pivot before it, and those greater after it. Use the final position of the pivot to split the list up into two sublists. Repeat (substituting the sublists for the lists) until the sublists are of size one or zero.

The worst case for running time is when the list is already sorted. To combat this, the pivot is selected randomly.

Radix sort

Worst time: Θ(n).

Place items into ten lists based on least significant digit. Concatenate list. Repeat, but use the next most significant digit instead, until we reach the highest significant digit of any of the numbers.

Searching

Linear search

Best time: Θ(1).
Average time: Θ(n).
Worst time: Θ(n).

Iterate through the list, until we find the desired item, if it exists.

Binary search

Works on lists sorted in non-decreasing order.

Best time: Θ(1).
Worst time: Θ(log n).

Compare with the item in the middle of the list. If larger, then check the upper half; if smaller check the lower, if matched then return.

Data structures

Stack

push(x): add an item to the top of the stack.
pop(): returns the item at the top of the stack.
makeEmpty(): removes all items.
isEmpty(): returns true if empty, false otherwise.

push is Θ(1) if the underlying array isn't full, and Θ(n) if the underlying array is full. pop is Θ(1).

Queue

enqueue(x): add x to the end of the queue.
dequeue(): return the item at the front of the queue.
makeEmpty(): removes all items.
isEmpty(): returns true if empty, false otherwise.

List

length(): return length of list.
begin(): return position at 0.
end(): return position at end.
next(p): return position at p + 1.
prev(p): return position at p - 1.

get(p): return item at p.
set(p, x): set item at position p to x.
insert(p, x): insert item x at position p, right-shifting subsequent items.
remove(p): remove item at position.

find(x): return first position at which x exists.
nth(k): return nth position at which x exists.

Array implementation

Operations insert, remove and find have a worst case running time of Θ(n). Everything else is Θ(1).

Linked list implementation

Insert and remove have a running time of Θ(1), random access is Θ(n).

Can have a header node, a tail pointer, and can be doubly linked, which improves certain operations.

Priority queue

insert(x, p): add x to the queue, with priority p.
remove(): return and remove the item with the highest priority.
makeEmpty(): removes all items.
isEmpty(): returns true if empty, false otherwise.

List which inserts in sorted order array

remove is Θ(1), but insert is Θ(n).

Unsorted list

insert is Θ(1), but remove is Θ(n).

Heap

insert and remove have a worst time of Θ(log n).

A full, binary tree which satisfies the heap property: the priority of every node is greater than or equal to the priority of the child nodes. This can be represented as an array, where the children of the node at index k are located at 2k+1 and 2k+2.

insert appends the item to the array (or inserts having vacated the relevant spot), but keeps swapping with parent if it has a higher priority than it.

remove returns and removes the item at the top of the array, then inserts the item at the bottom of the array at the top. It then keeps swapping the newly placed item with the node that has greater priority, if possible.

Set

add(x): adds x, if it doesn't already exist.
remove(x): removes x.
contains(x): tests for containership of x.
size(): returns the size.

Open hash table

All operations have an average running time of Θ(1).

We have an array of a certain size, each containing a pointer to an empty list. Calculate a hash of the item gives us the array index location. Append the item to the list located at that index.

The idea is to have about 25% of the table empty, and an efficient hash function so that the average length of each list is zero or one.

Closed hash table

Use just one array, but in the case of collisions, insert the item by probing linearly from its desired location, until we find an empty spot. Finding items relies on the same strategy.

To avoid clustering, try quadratic probing.

Map

get(k): returns the value v if the (k, v) pair exists in the map.
put(k, v): puts (k, v) into the map, or replaces the the v if the k already exists.
remove(k): removes the (k, v) if there is such a pair.
containsKey(k): tests to see if the map contains a pair with key k.
size(): returns the size.

For implementations, we can use either of the implementations for the Set, storing the (k, v) pair, and referencing using the key k.