News for hackers. Stuff that matters.
Re:Singular Value Decomposition by tjpick on Wednesday February 23, 2011 @01:44PM (#2255208)
Re:Singular Value Decomposition by kunjaan on Wednesday February 23, 2011 @01:53PM (#2255226)
These kinds of posts just open an endless and meaningless debate.

For example, why not list rules from boolean logic? Why don't we have concept of induction? I use tree concepts more often than I use SVD.

Re:Singular Value Decomposition by tomrod on Wednesday February 23, 2011 @04:03PM (#2255797)
Because these are among the most important mathematical concepts a programmer needs to understand--not "almost" the most important :-)
Re:Singular Value Decomposition by Adrock on Wednesday February 23, 2011 @01:24PM (#2255133)
It's not obvious to me why this is so important to programmers. Can someone explain?
Re:Singular Value Decomposition by gte910h on Wednesday February 23, 2011 @01:29PM (#2255157)
You use this to project and move objects to different orientations, shapes and sizes. So if you're doing animation, UI programming or graphics, it's very useful.

If you're doing analysis, you can use SVD to isolate independent forces, and to quantify the relationships of dependent forces.

Some compressions/specification techniques rely on it.

Basically, it's very important to know how to do for some, vaguely informative for others, and very important for yet another group.

Re:Singular Value Decomposition by rabidsnail on Wednesday February 23, 2011 @02:02PM (#2255270)
For UI programming and animation transformation matrices (http://en.wikipedia.org/wiki/Transformation_matrix) (plus some simple calculus) are really all you need.
Re:Singular Value Decomposition by gte910h on Wednesday February 23, 2011 @02:17PM (#2255336)
Depends on what part of the animations you're doing. SVD is a technique you'll do on Transformation matrices to find certain things out.

I'm not saying the OP's contention that SVD is fantastically useful is that true. I am saying understanding matrix math down to the point of SVD and being able to do it when you spend much of your day doing transforms is useful for animation beyond setting EaseInOut and going about your day.

Re:Singular Value Decomposition by tomrod on Wednesday February 23, 2011 @04:00PM (#2255779)
In response to ha-hn:

The intent to this post is not to create mathematical elitism, but to highlight an important mathematical concept that comes up in programming--and many programmers may work with or around it without realizing it.

As I understand it, this concept is used in: * Compression Algorithms * Signal Analysis * Pagerank * Factor Analysis * Animation (especially when considering more than 3 points of information for each vector) * Clustering in Machine Learning * Noise reduction in DSP * Match.com's dating algorithm * Principal Component analysis * Image scaling * Control theory

I know it has been used in many more applications beyond this list.

I'm sorry you feel a smack of mathematical elitism. The concepts here are not inherently difficult, just a little complex. Here is a great resource to learn more: http://www.puffinwarellc.com/index.php/news-and-articles/art...

Re:Singular Value Decomposition by ethereon on Wednesday February 23, 2011 @02:10PM (#2255309)
That's quite the hyperbole.

When I was studying Electrical Engineering, I noticed that SVDs cropped up frequently. From memory, a quick list of situations where I can recall using SVDs :

- For computing homographies in Computer Vision

- For clustering in Machine Learning

- For noise reduction in DSP

In general, when the problem can be modeled using linear algebra, SVD often proves to be a versatile tool ( for linear optimization, eigenvalue problems, least squares, etc).

However, that doesn't make it the most important topic. I could just as easily name a bunch of other techniques that are also frequently used : FFTs, Linear programming, Monte Carlo methods. If you're an electrical engineer, all of these would be useful. Yet, I wouldn't call any of them the most important topic.

Re:Singular Value Decomposition by patrickc on Wednesday February 23, 2011 @02:52PM (#2255509)
Re:Singular Value Decomposition by jhrobert on Thursday February 24, 2011 @11:30AM (#2258593)
Addition, subtraction and order relationships (ie > & <) are the only math that really matters.

Not convinced? Count the number of * and / in any source file and compare that to the number of + and -

Not to say that math is not useful, it's useful if math related stuff is what you do, which is a very small subset of what CS is about.

Re:Singular Value Decomposition by tbrownaw on Wednesday February 23, 2011 @01:37PM (#2255183)
What about algorithmic complexity and induction/deduction?
Re:Singular Value Decomposition by edge17 on Wednesday February 23, 2011 @01:56PM (#2255242)
i'm going to go with the 80-20 rule as the most important math concept a programmer can learn
Re:Singular Value Decomposition by tomrod on Wednesday February 23, 2011 @03:24PM (#2255644)
I like it. But this is more of a business and economic rule, no?
Re:Singular Value Decomposition by edge17 on Wednesday February 23, 2011 @04:28PM (#2255896)
Sure, but also it's better to look for the common case (i.e. the 80%) and make sure that's fast. It's not always worth optimizing the uncommon case (like branch misses with a branch predictor).
Re:Singular Value Decomposition by petegrif on Wednesday February 23, 2011 @01:30PM (#2255161)
depends on the style of language a) imperative 1+1 = 2 (increment) b) functional f(x) = c) object = if you can't see it, it doesn't matter how much math you know