Shadow mapping - Revision history

en>Oranjelo100: /* Miscellaneous */

2014-11-05T20:23:53Z

Miscellaneous

← Older revision		Revision as of 22:23, 5 November 2014
Line 1:		Line 1:
	In [[computer science]], '''proof complexity''' is a measure of efficiency of [[automated theorem proving]] methods that is based on the size of the proofs they produce. The methods for proving contradiction in [[propositional logic]] are the most analyzed. The two main issues considered in proof complexity are whether a proof method can produce a polynomial proof of every inconsistent formula, and whether the proofs produced by one method are always of size similar to ~~those produced by another method.~~		Nice to satisfy you, my name is Figures Held although I don't truly like being called like that. Managing people is his profession. Minnesota is where he's been living for many years. Doing ceramics is what my family members and I enjoy.<br><br>Also visit my web blog home std test - [http://indianrajneet.com/groups/best-strategies-for-keeping-candida-albicans-from-increasing/ description here],

	~~==Polynomiality of proofs==~~

	Different [[propositional proof system]] for theorem proving in propositional logic, such as the [[sequent calculus]], the [[cutting-plane method]], [[Resolution (logic)\|resolution]], the [[DPLL algorithm]], ~~etc. produce different proofs when applied to the same formula. Proof complexity measures the efficiency of a method in terms of the size of the proofs it produces.~~

	~~Two points make the study of proof complexity non-trivial:~~

	~~# the size of a proof depends on the formula that~~ is ~~to be proved inconsistent;~~
	# proof methods are generally families of algorithms, as some of their steps are not univocally specified; for example, resolution is based on iteratively choosing a pair of clauses containing opposite literals and producing a new clause that ~~is a consequence of them; since several such pairs may be available at each step, the algorithm has to choose one; these choices affect the proof length~~.

	~~The first point~~ is ~~taken into account by comparing the size of a proof of a formula with the size of the formula~~. ~~This comparison~~ is made using the usual assumptions of [[computational complexity]]: first, a polynomial proof size/formula size ratio means that the proof is of size similar to that of the formula; second, this ratio is studied in the asymptotic case as the size of the formula increases.

	~~The second point is taken into account by considering,~~ for ~~each formula, the shortest possible proof the considered method can produce.~~

	The question of polynomiality of proofs is whether a method can always produce a proof of size polynomial in the size of the formula. If such a method exists, then [[NP (complexity)\|NP]] would be equal to [[coNP]]: this is why the question of polynomiality of proofs is considered important in computational complexity. For some methods, the existence of formulae whose shortest proofs are always superpolynomial has been proved. For other methods, it is an open question.

	~~==Proof size comparison==~~

	~~A second question about proof complexity is whether a method is more efficient than another~~. ~~Since the proof size depends on the formula, it~~ is ~~possible that one method can produce a short proof of a formula~~ and only long proofs of another formula, while a second method can have exactly the opposite behavior. The assumptions of measuring the size of the proofs relative to the size of the formula and considering only the shortest proofs are also used in this context.

	~~When comparing two proof methods, two outcomes are possible:~~

	~~# for every proof of a formula produced using the first method, there is a proof of comparable size of the same formula produced by the second method;~~
	~~# there exists a formula such that the first method can produce a short proof while all proofs obtained by the second method are consistently larger~~.

	~~Several proofs of the second kind involve contradictory formulae expressing the negation of the [[pigeonhole principle]], namely that <math>n+1</math> pigeons can fit~~ <~~math~~>n<~~/math~~> ~~holes with no hole containing two or more pigeons.~~

	~~==Automatizability==~~

	~~A proof method is automatizable if one of the shorter proofs of a formula can always be generated in time polynomial (or sub~~-~~exponential) in the size of the proof. Some methods, but not all, are automatizable. Automatizability results are not in contrast with the assumption that the~~ [~~[polynomial hierarchy]] does not collapses, which would happen if generating a proof in time polynomial in the size ''of the formula'' were always possible.~~

	~~==Interpolation==~~

	Consider a tautology of the form <math>A(x,y) \rightarrow B(y,z) </math>. The tautology is true for every choice of <math>y</math>, and after fixing <math>y</math> the evaluation of <math>A</math> and <math>B</math> are independent because are defined on disjoint sets of variables. This means that it is possible to define an ''interpolant'' circuit <math>C(y)</math>, such that both <math>A(x,y) \rightarrow C(y)</math> and <math>C(y) \rightarrow B(y,z)</math> hold. The interpolant circuit decides either if <math>A(x,y)</math> is false or if <math>B(y,z)</math> is true, by only considering <math>y</math>. The nature of the interpolant circuit can be arbitrary. Nevertheless it is possible to use a proof of the initial tautology <math>A(x,y) \rightarrow B(y,z) </~~math> as a hint on how to construct <math>C<~~/~~math>. Some proof systems (e.g~~. ~~resolution) are said to have ''efficient interpolation'' because the interpolant <math>C(y)<~~/~~math> is efficiently computable from any proof of the tautology <math>A(x,y) \rightarrow B(y,z)<~~/~~math> in such proof system. The efficiency is measured with respect to the length of the proof: it is easier to compute interpolants for longer proofs, so this property seems to be anti~~-~~monotone in the strength of the proof system.~~

	Interpolation is a weak form of automatization: a way to deduce the existence of small circuits from the existence of small proofs. In particular the following three statements cannot be simultaneously true: (a) <math>A(x,y) \rightarrow B(y,z)</math> has a short proof in a some proof system; (b) such proof system has efficient interpolation; (c) the interpolant circuit solves a computationally hard problem. It is clear that (a) and (b) imply that there is a small interpolant circuit, which is in contradiction with (c). Such relation allows to turn proof length upper bounds into lower bounds on computations, and dually to turn efficient interpolation algorithms into lower bounds on proof length.

	~~==Non~~-~~classical logics==~~

	~~The idea of comparing the size of proofs can be used for any automated reasoning procedure that generates a proof. Some research has been done about the size of proofs~~ for ~~propositional non-classical logics, in particular, intuitionistic, modal, and non-monotonic logics.~~

	~~==See also==~~

	* [[Automated theorem proving]]
	* [[Computational complexity]]
	* [[Intuitionistic logic]]
	* [[Non-monotonic logic]]

	~~==References==~~

	* P. Beame and [[Toniann Pitassi\|T. Pitassi]] (1998). [http://eccc.uni-~~trier.de/eccc~~-~~reports/1998/TR98~~-~~067/index.html Propositional proof complexity: past, present and future]. Technical Report TR98~~-~~067, Electronic Colloquium on Computational Complexity.~~
	* J. Krajíček, [http://www.karlin.mff.cuni.cz/~krajicek/ecm.pdf Proof complexity], in: Proc. 4th European congress of mathematics (ed. A. Laptev), EMS, Zurich, pp.221-~~231, (2005).~~
	* J. Krajíček, [http://www.karlin.mff.cuni.cz/~krajicek/ds1.ps Propositional proof complexity I.] and [http://www.karlin.mff.cuni.cz/~krajicek/ds2.ps Proof complexity and arithmetic].
	* P. Pudlák, The lengths of proofs, in: Handbook of Proof Theory (ed. S.R.Buss), Elsevier, (1998).
	* Stephen Cook and Phuong Nguyen, [http://www.cup.es/us/catalogue/~~catalogue.asp?isbn=9780521517294 Logical Foundations of Proof Complexity~~], ~~Cambridge University Press, 2010 ([http://www.cs.toronto.edu/~sacook/homepage/book draft from 2008])~~

	~~==External links==~~
	* [http://www.cs.cmu.edu/afs/cs/project/jair/pub/volume21/dixon04a-html/node9.html Proof Complexity]

	* [http://list.math.cas.cz/listinfo/proof-complexity Proof complexity mailing list.]

	~~[[Category:Computational complexity theory]]~~
	~~[[Category:Logic in computer science]]~~
	~~[[Category:Automated theorem proving]]~~

82.101.232.108: /* Filtering */

2013-12-27T12:19:13Z

Filtering

← Older revision		Revision as of 14:19, 27 December 2013
Line 1:		Line 1:
	~~They call me Emilia~~. ~~What I adore doing~~ is ~~performing ceramics~~ but ~~I haven~~'~~t made~~ a ~~dime~~ with it~~. Years ago we moved~~ to ~~North Dakota~~. ~~My working day occupation~~ is a ~~meter reader~~.<br><br>~~Look at my web blog~~ :: [http://~~apcbook~~.~~com~~.ng/~~index~~.~~php~~?do=/~~profile~~-~~446~~/~~info~~/ ~~at home std test~~]		In [[computer science]], '''proof complexity''' is a measure of efficiency of [[automated theorem proving]] methods that is based on the size of the proofs they produce. The methods for proving contradiction in [[propositional logic]] are the most analyzed. The two main issues considered in proof complexity are whether a proof method can produce a polynomial proof of every inconsistent formula, and whether the proofs produced by one method are always of size similar to those produced by another method.

			==Polynomiality of proofs==

			Different [[propositional proof system]] for theorem proving in propositional logic, such as the [[sequent calculus]], the [[cutting-plane method]], [[Resolution (logic)\|resolution]], the [[DPLL algorithm]], etc. produce different proofs when applied to the same formula. Proof complexity measures the efficiency of a method in terms of the size of the proofs it produces.

			Two points make the study of proof complexity non-trivial:

			# the size of a proof depends on the formula that is to be proved inconsistent;
			# proof methods are generally families of algorithms, as some of their steps are not univocally specified; for example, resolution is based on iteratively choosing a pair of clauses containing opposite literals and producing a new clause that is a consequence of them; since several such pairs may be available at each step, the algorithm has to choose one; these choices affect the proof length.

			The first point is taken into account by comparing the size of a proof of a formula with the size of the formula. This comparison is made using the usual assumptions of [[computational complexity]]: first, a polynomial proof size/formula size ratio means that the proof is of size similar to that of the formula; second, this ratio is studied in the asymptotic case as the size of the formula increases.

			The second point is taken into account by considering, for each formula, the shortest possible proof the considered method can produce.

			The question of polynomiality of proofs is whether a method can always produce a proof of size polynomial in the size of the formula. If such a method exists, then [[NP (complexity)\|NP]] would be equal to [[coNP]]: this is why the question of polynomiality of proofs is considered important in computational complexity. For some methods, the existence of formulae whose shortest proofs are always superpolynomial has been proved. For other methods, it is an open question.

			==Proof size comparison==

			A second question about proof complexity is whether a method is more efficient than another. Since the proof size depends on the formula, it is possible that one method can produce a short proof of a formula and only long proofs of another formula, while a second method can have exactly the opposite behavior. The assumptions of measuring the size of the proofs relative to the size of the formula and considering only the shortest proofs are also used in this context.

			When comparing two proof methods, two outcomes are possible:

			# for every proof of a formula produced using the first method, there is a proof of comparable size of the same formula produced by the second method;
			# there exists a formula such that the first method can produce a short proof while all proofs obtained by the second method are consistently larger.

			Several proofs of the second kind involve contradictory formulae expressing the negation of the [[pigeonhole principle]], namely that <math>n+1</math> pigeons can fit <math>n</math> holes with no hole containing two or more pigeons.

			==Automatizability==

			A proof method is automatizable if one of the shorter proofs of a formula can always be generated in time polynomial (or sub-exponential) in the size of the proof. Some methods, but not all, are automatizable. Automatizability results are not in contrast with the assumption that the [[polynomial hierarchy]] does not collapses, which would happen if generating a proof in time polynomial in the size ''of the formula'' were always possible.

			==Interpolation==

			Consider a tautology of the form <math>A(x,y) \rightarrow B(y,z) </math>. The tautology is true for every choice of <math>y</math>, and after fixing <math>y</math> the evaluation of <math>A</math> and <math>B</math> are independent because are defined on disjoint sets of variables. This means that it is possible to define an ''interpolant'' circuit <math>C(y)</math>, such that both <math>A(x,y) \rightarrow C(y)</math> and <math>C(y) \rightarrow B(y,z)</math> hold. The interpolant circuit decides either if <math>A(x,y)</math> is false or if <math>B(y,z)</math> is true, by only considering <math>y</math>. The nature of the interpolant circuit can be arbitrary. Nevertheless it is possible to use a proof of the initial tautology <math>A(x,y) \rightarrow B(y,z) </math> as a hint on how to construct <math>C</math>. Some proof systems (e.g. resolution) are said to have ''efficient interpolation'' because the interpolant <math>C(y)</math> is efficiently computable from any proof of the tautology <math>A(x,y) \rightarrow B(y,z)</math> in such proof system. The efficiency is measured with respect to the length of the proof: it is easier to compute interpolants for longer proofs, so this property seems to be anti-monotone in the strength of the proof system.

			Interpolation is a weak form of automatization: a way to deduce the existence of small circuits from the existence of small proofs. In particular the following three statements cannot be simultaneously true: (a) <math>A(x,y) \rightarrow B(y,z)</math> has a short proof in a some proof system; (b) such proof system has efficient interpolation; (c) the interpolant circuit solves a computationally hard problem. It is clear that (a) and (b) imply that there is a small interpolant circuit, which is in contradiction with (c). Such relation allows to turn proof length upper bounds into lower bounds on computations, and dually to turn efficient interpolation algorithms into lower bounds on proof length.

			==Non-classical logics==

			The idea of comparing the size of proofs can be used for any automated reasoning procedure that generates a proof. Some research has been done about the size of proofs for propositional non-classical logics, in particular, intuitionistic, modal, and non-monotonic logics.

			==See also==

			* [[Automated theorem proving]]
			* [[Computational complexity]]
			* [[Intuitionistic logic]]
			* [[Non-monotonic logic]]

			==References==

			* P. Beame and [[Toniann Pitassi\|T. Pitassi]] (1998). [http://eccc.uni-trier.de/eccc-reports/1998/TR98-067/index.html Propositional proof complexity: past, present and future]. Technical Report TR98-067, Electronic Colloquium on Computational Complexity.
			* J. Krajíček, [http://www.karlin.mff.cuni.cz/~krajicek/ecm.pdf Proof complexity], in: Proc. 4th European congress of mathematics (ed. A. Laptev), EMS, Zurich, pp.221-231, (2005).
			* J. Krajíček, [http://www.karlin.mff.cuni.cz/~krajicek/ds1.ps Propositional proof complexity I.] and [http://www.karlin.mff.cuni.cz/~krajicek/ds2.ps Proof complexity and arithmetic].
			* P. Pudlák, The lengths of proofs, in: Handbook of Proof Theory (ed. S.R.Buss), Elsevier, (1998).
			* Stephen Cook and Phuong Nguyen, [http://www.cup.es/us/catalogue/catalogue.asp?isbn=9780521517294 Logical Foundations of Proof Complexity], Cambridge University Press, 2010 ([http://www.cs.toronto.edu/~sacook/homepage/book draft from 2008])

			==External links==
			* [http://www.cs.cmu.edu/afs/cs/project/jair/pub/volume21/dixon04a-html/node9.html Proof Complexity]

			* [http://list.math.cas.cz/listinfo/proof-complexity Proof complexity mailing list.]

			[[Category:Computational complexity theory]]
			[[Category:Logic in computer science]]
			[[Category:Automated theorem proving]]

146.140.28.15 at 11:30, 16 August 2012

2012-08-16T11:30:56Z

New page

They call me Emilia. What I adore doing is performing ceramics but I haven't made a dime with it. Years ago we moved to North Dakota. My working day occupation is a meter reader.<br><br>Look at my web blog :: [http://apcbook.com.ng/index.php?do=/profile-446/info/ at home std test]