# Talk:Condition number

## Contents

## Additions

I think it would be useful in the introduction to mention the condition number rule of thumb. It was mentioned to me in a Numerical Analysis class, and found that it cleared up some questions I had. The rule of thumb is if , then you lose digits of accuracy on top of what would be lost to the numerical method due to loss of precision from arithmetic methods. This can be seen in Numerical Mathematics and Computing, by Cheney and Kincaid. What do you guys think? Mikesmith00 (talk) 01:16, 24 September 2010 (UTC)

Does Cheney and Kincaids rules of thumb apply in computations outside of the 2 norm? In the book they have it listed as **Failed to parse (Conversion error. Server ("cli") reported: ""): {\displaystyle \kappa(A)=||A||_2||A^{-1}||_2}**
And then they proceed to say that $k$ digits of precision lost resulting from the base ten logarithm of the aforementioned computation of the condition number.

There needs to be more clarification if this is not the case.

--Faraz.yashar (talk) 16:52, 20 November 2010 (UTC)

## question about condition number

I'll move this to the reference desk in a day or two if someone isn't watching here.

Can someone help me with an estimate of how big a condition number actually has to be before a matrix is considered "ill conditioned?" I'm sure it's dependent on many things but I'd like to get a grasp on it.

I'm trying to show that in a bunch of cases (200 or so) two 2D vectors are "approximately" multiples of one another. So I make a 2x2 matrix out of these two vectors, and I find the condition number. On average the condition number is around 2e6, and the minimum is 9e4. Does this make the vectors approximately multiples of one another? moink 16:58, 7 Apr 2004 (UTC)

The error in the approximate solution is no greater than the (condition number) x (relative error in the initial solution). If the new approximate solution is not within the desired precision of the actual solution, then the system would be "ill-conditioned." Also, to obtain a higher precision in an ill-conditioned system, a much more accurate initial condition is required.Jaboles 20:49, 23 August 2006 (UTC)

It depends on how accurately you know these vectors. The amount of significant digits you lose is equal to log(condition number), so if you only have the vector components 3 digits accurate, then a condition number>1000 will produce garbage.131.155.215.153 (talk) 16:05, 7 September 2012 (UTC)

## Confusing

"wheras a large condition number will enhance error in b." I think this is confusing because we are talking about the bad conditioning increasing the amount of error in the calculated x due do a small error in b (and not really doing anything to b). Richard Giuly 08:53, 1 November 2006 (UTC)

- I agree. The next step is that you think of a better formulation and edit the article. These articles don't write themselves ;) Don't worry too much about making mistakes; they will be corrected. -- Jitse Niesen (talk) 10:44, 1 November 2006 (UTC)

- I tried to change it myself. -- Jitse Niesen (talk) 11:20, 8 November 2006 (UTC)

- I added a plausible derivation of the condition number for operator (induced) matrix norms. I hope it helps. Perdelsky 03:09, 5 August 2007 (UTC)

## Relevance of precision

I am not sure if the relevance of finite/infinite precision is clear. If you have infinite precision, and do not assume any kind of errors in the input, the condition number is of no relevance. Berland 12:42, 18 January 2007 (UTC)

- If you use exact arithmetic (infinite precision), and an iterative method to compute an approximation to your solution (whose rate of convergence degrades with increasing condition number), then the condition number is of great relevance. Lunch 17:38, 18 January 2007 (UTC)
- You are absolutely right. I think these (subtle?) issues could/should be addressed in the article. Berland 21:22, 19 January 2007 (UTC)

"if the condition number is large, even a small error in b may cause a large error in x", is it just opposite? i think a large condition number means a small error in x cause a large error in b. Shangkun (talk) 11:35, 28 July 2008 (UTC)

- Both are true. If the condition number is large, then a small error in
*b*may cause a large error in*x*and a small error in*x*may cause a large error in*b*. That's because . -- Jitse Niesen (talk) 13:17, 28 July 2008 (UTC)

## Two problems with this article

And these they are:

- The definition has a link to
__ill-conditioned__that redirects to this article. So there is a need to explain what__well-conditioned__and__ill-conditioned__are and to remove this link. - The definition writes about
__problem's amenability to__. However, in the section for condition number of a matrix it is mentioned that conditioning is a property of the matrix and not of floating point arithmetics or rounding off errors.**digital computation**

TomyDuby (talk) 02:07, 18 December 2008 (UTC)

## The maximum value (for nonzero b and e) is easily seen to be the product of the two operator norms:

I don't find this so easy - please could somebody give more details about this line.Nlinton (talk) 13:18, 9 October 2009 (UTC)

Seconded. I'm mathematically literate enough to be interested in this article, but haven't been able to guess the principles that ought to be invoked to find this maximum. GRB, 15 August 2011. — Preceding unsigned comment added by 99.24.63.46 (talk) 13:54, 15 August 2011 (UTC)

If you are free to choose e and b such that the quantities are maximum, then ||A^(-1) e||/||e||=||A^(-1)|| and ||b||/||A^(-1) b||=||A||131.155.215.153 (talk) 16:13, 7 September 2012 (UTC)

It's obvious for the first part whose upper bound is by definition (see induced matrix norm), not immediately for the second one though. Here's my attempt: First off, maximizing is equivalent to minimizing . Or in other words, finding the smallest factor by which stretches vectors. Since is the largest stretch factor for the mapping , the smallest stretch for consequently is , and hence . --138.246.2.58 (talk) 18:21, 7 February 2013 (UTC)

## Mention 'error' or 'uncertainty' in early introduction

I think it would be very helpful for more general readers if the introduction (in particular the first paragraph---currently 2 sentences) mentioned that the condition number is generally used to evaluate how large the error/uncertainty of a function will be, given a certain error/uncertainty in the data/parameters. As it stands, the introduction is somewhat vague---while it is quite clear, *once* I know what its talking about. All Clues Key (talk) 00:16, 1 October 2012 (UTC)