컴퓨터 과학에서 결정론적 알고리즘은 특정 입력이 주어졌을 때 항상 동일한 출력을 생성하며, 기반이 되는 기계가 항상 동일한 상태 순서를 거치는 알고리즘이다. 결정론적 알고리즘은 가장 많이 연구되고 널리 알려진 종류의 알고리즘이며, 실제 기계에서 효율적으로 실행할 수 있어 가장 실용적인 알고리즘 중 하나이기도 하다.

Deterministic algorithm

In [[computer science]], a '''deterministic algorithm''' is an [[algorithm]] that, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states. Deterministic algorithms are by far the most studied and familiar kind of algorithm, as well as one of the most practical, since they can be run on real machines efficiently.

Formally, a deterministic algorithm computes a [[function (mathematics)|mathematical function]]; a function has a unique value for any input in its [[function domain|domain]], and the algorithm is a process that produces this particular value as output.

== Formal definition ==

Deterministic algorithms can be defined in terms of a [[state machine]]: a ''state'' describes what a machine is doing at a particular instant in time. State machines pass in a discrete manner from one state to another. Just after we enter the input, the machine is in its ''initial state'' or ''start state''. If the machine is deterministic, this means that from this point onwards, its current state determines what its next state will be; its course through the set of states is predetermined. Note that a machine can be deterministic and still never stop or finish, and therefore fail to deliver a result.

Examples of particular [[abstract machine]]s which are deterministic include the [[deterministic Turing machine]] and [[deterministic finite automaton]].

== Non-deterministic algorithms ==

A variety of factors can cause an algorithm to behave in a way which is not deterministic, or non-deterministic:

If it uses an external state other than the input, such as user input, a [[global variable]], a hardware timer value, a [[Randomness|random]] value, or stored disk data.
If it operates in a way that is timing-sensitive, for example, if it has multiple processors writing to the same data at the same time. In this case, the precise order in which each processor writes its data will affect the result.
If a hardware error causes its state to change in an unexpected way.

Although real programs are rarely purely deterministic, it is easier for humans as well as other programs to reason about programs that are. For this reason, most [[programming language]]s and especially [[functional programming]] languages make an effort to prevent the above events from happening except under controlled conditions.

The prevalence of [[multi-core processor]]s has resulted in a surge of interest in determinism in parallel programming and challenges of non-determinism have been well documented.{{cite web | author = Edward A. Lee | url = http://www.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-1.pdf | access-date = 2009-05-29 | title = The Problem with Threads}}{{cite conference |first1=Robert L. |last1=Bocchino Jr. |first2=Vikram S. |last2=Adve |first3=Sarita V. |last3=Adve |first4=Marc |last4=Snir |title=Parallel Programming Must Be Deterministic by Default |conference=[[USENIX]] Workshop on Hot Topics in Parallelism |year=2009 |url=https://www.usenix.org/legacy/event/hotpar09/tech/full_papers/bocchino/bocchino_html/}} A number of tools to help deal with the challenges have been proposed{{cite web | url = http://software.intel.com/en-us/videos/intel-parallel-inspector-thread-checker/ | access-date = 2009-05-29 | title = Intel Parallel Inspector Thread Checker}}{{cite web | author = Yuan Lin | url = http://developers.sun.com/sunstudio/documentation/product/sd_west_threadAnalyzer.pdf | title = Data Race and Deadlock Detection with Sun Studio Thread Analyzer | access-date = 2009-05-29}}{{cite web | author = Intel | url = http://software.intel.com/en-us/intel-parallel-inspector | access-date = 2009-05-29 | title = Intel Parallel Inspector}}{{cite web | url = http://sdtimes.com/link/33497 | title = Intel addresses development life cycle with Parallel Studio | author = David Worthington | access-date = 2009-05-26 | archive-url = https://web.archive.org/web/20090528030044/http://www.sdtimes.com/link/33497 | archive-date = 2009-05-28 | url-status = dead }} to deal with [[Deadlock (computer science)|deadlock]]s and [[race condition]]s.

== Disadvantages of determinism ==

It is advantageous, in some cases, for a program to exhibit nondeterministic behavior. The behavior of a card shuffling program used in a game of [[blackjack]], for example, should not be predictable by players — even if the source code of the program is visible. The use of a [[pseudorandom number generator]] is often not sufficient to ensure that players are unable to predict the outcome of a shuffle. A clever gambler might guess precisely the numbers the generator will choose and so determine the entire contents of the deck ahead of time, allowing him to cheat; for example, the Software Security Group at Reliable Software Technologies was able to do this for an implementation of Texas Hold 'em Poker that is distributed by ASF Software, Inc, allowing them to consistently predict the outcome of hands ahead of time.{{cite web |author-link1=Gary McGraw |first1=Gary |last1=McGraw |author-link2=John Viega |first2=John |last2=Viega |title=Make your software behave: Playing the numbers: How to cheat in online gambling. |website=[[IBM]] |url=http://www.ibm.com/developerworks/library/s-playing/#h4 |url-status=dead |access-date=2007-07-02 |archive-date=2008-03-13 |archive-url=https://web.archive.org/web/20080313043638/http://www.ibm.com/developerworks/library/s-playing/#h4 }} These problems can be avoided, in part, through the use of a [[cryptographically secure pseudo-random number generator]], but it is still necessary for an unpredictable [[random seed]] to be used to initialize the generator. For this purpose, a source of nondeterminism is required, such as that provided by a [[hardware random number generator]].

Note that a negative answer to the [[P=NP problem]] would not imply that programs with nondeterministic output are theoretically more powerful than those with deterministic output. The complexity class [[NP (complexity)]] can be defined without any reference to nondeterminism using the [[NP (complexity)|verifier-based definition]].

== Determinism categories in languages ==

=== Mercury === The [[Mercury (programming language)|mercury]] logic-functional programming language establishes different determinism categories for predicate modes as explained in the reference.{{Cite web |url=http://www.mercury.csse.unimelb.edu.au/information/doc-release/mercury_ref/Determinism-categories.html |title=Determinism categories in the Mercury programming language |access-date=2013-02-23 |archive-url=https://web.archive.org/web/20120703001434/http://www.mercury.csse.unimelb.edu.au/information/doc-release/mercury_ref/Determinism-categories.html#Determinism-categories |archive-date=2012-07-03 |url-status=dead }}{{Cite web |url=http://www.mercury.csse.unimelb.edu.au/information/doc-release/mercury_ref/Predicate-and-function-mode-declarations.html |title=Mercury predicate modes |access-date=2013-02-25 |archive-url=https://web.archive.org/web/20120703001411/http://www.mercury.csse.unimelb.edu.au/information/doc-release/mercury_ref/Predicate-and-function-mode-declarations.html#Predicate-and-function-mode-declarations |archive-date=2012-07-03 |url-status=dead }}

=== Haskell === [[Haskell]] provides several mechanisms:

Non-determinism or notion of Fail ** the ''Maybe'' and ''Either'' types include the notion of success in the result. ** the ''fail'' method of the class Monad, may be used to signal ''fail'' as exception. ** the Maybe [[Monad (functional programming)|monad]] and MaybeT monad transformer provide for failed computations (stop the computation sequence and return Nothing){{cite web|url=https://www.haskell.org/haskellwiki/Monad#Common_monads |title=Representing failure using the Maybe monad}}
Neterminism/non-det with multiple solutions ** you may retrieve all possible outcomes of a multiple result computation, by wrapping its result type in a MonadPlus [[Monad (functional programming)|monad]]. (its method ''mzero'' makes an outcome fail and ''mplus'' collects the successful results).{{cite web|url=https://www.haskell.org/haskellwiki/MonadPlus |title=The class MonadPlus}}

=== ML family and derived languages ===

As seen in [[Standard ML]], [[OCaml]] and [[Scala (programming language)|Scala]]

The ''option'' type includes the notion of success.

=== Java === In [[Java (programming language)|Java]], the ''null'' reference value may represent an unsuccessful (out-of-domain) result.

== See also ==

[[Randomized algorithm]]

== References ==

[[Category:Analysis of algorithms]]