30 years ago? What took so long for broad adoption? Patents? edit Article doesn't elaborate on why that might be, but it does note: "an alternative that has been given a new lease on life is low-density parity check (LDPC) codes, invented in the early 1960s by Robert Gallager at MIT but largely forgotten since then...Now researchers have implemented LDPC codes so that they actually outperform turbo codes and get even…
Not an expert, but I've encountered Reed Solomon error correction extensively in my career, and this seems to be replacing RS applications? I wouldn't be surprised if there was a fair amount of inertia to overcome given how widely used and how well RS worked for a very long time. RS was critical for things like ADSL data transmission over POTS and other similar large scale applications. The wikipedia page for RS sugg…
Closing in on the “perfect code” (2004)
11–20 of 38 posts
Re: Closing in on the “perfect code” (2004)
#12The article is from 2004.
Re: Closing in on the “perfect code” (2004)
#1330 years ago? What took so long for broad adoption? Patents? edit Article doesn't elaborate on why that might be, but it does note: "an alternative that has been given a new lease on life is low-density parity check (LDPC) codes, invented in the early 1960s by Robert Gallager at MIT but largely forgotten since then...Now researchers have implemented LDPC codes so that they actually outperform turbo codes and get even…
Unfortunately, one of the common scenarios when it comes to percolating results from academia to industry is the following: 1. Academics make discovery/invent something. 2. Academics attempt to convince industry to adopt discovery. 3. Discovery is laughed out of industry as "impractical", "academic", etc. 4. Academics teach discovery to their students. 5. Students get into industry. 6. Students get into position of t…
Re: Closing in on the “perfect code” (2004)
#14Re: Closing in on the “perfect code” (2004)
#15See also Fountain Codes, e.g. RaptorQ: https://en.wikipedia.org/wiki/Fountain_code
Re: Closing in on the “perfect code” (2004)
#16Earlier quoted context omitted.
Unfortunately, one of the common scenarios when it comes to percolating results from academia to industry is the following: 1. Academics make discovery/invent something. 2. Academics attempt to convince industry to adopt discovery. 3. Discovery is laughed out of industry as "impractical", "academic", etc. 4. Academics teach discovery to their students. 5. Students get into industry. 6. Students get into position of t…
> 3. Discovery is laughed out of industry as "impractical", "academic", etc. To be fair, sometimes academic inventions are impractical given the technical landscape du jour. They only become feasible as technology and society progresses, say 30 years. Also, your observation does not mean any invention is meaningful (and will eventually be recognized as such). I for one, learned a bunch of "impractical", "academic" no…
Re: Closing in on the “perfect code” (2004)
#17Earlier quoted context omitted.
Unfortunately, one of the common scenarios when it comes to percolating results from academia to industry is the following: 1. Academics make discovery/invent something. 2. Academics attempt to convince industry to adopt discovery. 3. Discovery is laughed out of industry as "impractical", "academic", etc. 4. Academics teach discovery to their students. 5. Students get into industry. 6. Students get into position of t…
1.5 More established academics deride, scoff, and do their best to extinguish this new work.
When I was an academic, I never encountered (or heard of) such situations, though.
Re: Closing in on the “perfect code” (2004)
#1830 years ago? What took so long for broad adoption? Patents? edit Article doesn't elaborate on why that might be, but it does note: "an alternative that has been given a new lease on life is low-density parity check (LDPC) codes, invented in the early 1960s by Robert Gallager at MIT but largely forgotten since then...Now researchers have implemented LDPC codes so that they actually outperform turbo codes and get even…
Edited to add an early link to more granular technical work: https://ipnpr.jpl.nasa.gov/progress_report/42-120/120D.pdf
Re: Closing in on the “perfect code” (2004)
#19The article is from 2004.
Yes, wanted to share an interesting story of how great ideas can come from folks who are not the most popular names in a field. I feel the same will happen with AI now.
Re: Closing in on the “perfect code” (2004)
#20How is perfect data transmission a make or break feature for lossy compression and transmission of audio and video?