Jump to content

Fudge factor

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Xowets (talk | contribs) at 17:55, 2 January 2014 (Undid revision 581699987 by Jeremyregan (talk) - has no credibility to decide that by him self -> talk page). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A fudge factor is an ad hoc quantity introduced into a calculation, formula or model in order to make it fit observations or expectations. Examples include Einstein's Cosmological Constant, dark energy, dark matter and inflation.[1]

Examples in science

Some quantities in scientific theory are set arbitrarily according to measured results rather than by calculation (for example, Planck's constant). However, in the case of these fundamental constants, their arbitrariness is usually explicit. To suggest that other calculations may include a "fudge factor" may suggest that the calculation has been somehow tampered with to make results give a misleadingly good match to experimental data.

Cosmological constant

In theoretical physics, when Einstein originally tried to produce a general theory of relativity, he found that the theory seemed to predict the gravitational collapse of the universe: it seemed that the universe should either be expanding or collapsing, and to produce a model in which the universe was static and stable (which seemed to Einstein at the time to be the "proper" result), he introduced an expansionist variable (called the Cosmological Constant), whose sole purpose was to cancel out the cumulative effects of gravitation. He later called this, "the biggest blunder of my life."[2]

However it was later found that the constant was necessary. Current results record the constant to be non-zero to 99.7% certainty.[citation needed]

Expected error margins

A common feature of "fudge factors" in science is their arbitrariness, and their retrospective nature.

However, in project management it's common to build a certain error margin into the predicted "resource cost" of a project to make predictions more realistic: there are many unforeseen factors that may delay a project or make it more costly, but very few factors that could result in it being delivered before time or under the calculated budget ... so to some degree, "unexpected" overruns are to be expected, even if their precise nature can't be predicted in advance. Experienced planners may know that a certain type of project will tend to overrun by a certain percentage of its calculated resource requirements, and may multiply the "ideal" calculations by a safety margin to produce a more realistic estimate, and this margin may sometimes be referred to as a fudge factor. However, when planning ahead for expected unpredictabilities, these "error margins" are usually assigned other, more specific names : for instance in warehouse stock control, where a certain amount of stock is expected to disappear naturally through damage, pilfering or other unexplained problems, the discrepancy is referred to as shrinkage.

In engineering, a "fudge factor" may be introduced to allow a margin of error in unknown quantities.

In computer programming

Inexperienced programmers will sometimes insert arbitrary values into badly written source code in order to correct the output without addressing the underlying problems with the code itself. One example of this was uncovered by John Graham-Cumming during the Climatic Research Unit email controversy (Climategate), with 'fudged' values being entered into source code used by the Climactic Research Unit (CRU). The values were entered to correct bad programming which provided incorrect output.[3][4]


References

  1. ^ Donald Goldsmith (1997), Einstein's Greatest Blunder?: The Cosmological Constant and Other Fudge Factors in the Physics of the Universe, Harvard University Press, ISBN 9780674242425
  2. ^ Kenneth William Ford (2004), The Quantum World: Quantum Physics for Everyone, Harvard University Press, ISBN 9780674037144
  3. ^ Leaked source code used by the Climactic Research Unit
  4. ^ Blog post by John Graham-Cumming