I used to work on an imaging team at a big insurance company and we were required to store our images with a very particular lossless compression in a TIF file specifically because the law does not hold lossy compression as reliable. <\/p>\n
But, regarding jessepollard's other statements: <\/p>\n
\"The place you don't want errors is in the instruction stream.\" <\/p>\n
That's not where the errors are. They're in the calculation results from the non-errored instructions. And then, only in specific types of calculations. <\/p>\n
\"Images already have errors generated by every lossy compression algorithm.\" <\/p>\n
True, but also irrelevant. <\/p>\n
\"Unfortunately, these same errors prevent it from being reliable in court.\" <\/p>\n
True. <\/p>\n
\"Also doesn't work well for facial recognition\" <\/p>\n
False. Facial recognition is already a fuzzy logic affair. Actually, facial recognition is a perfect example of inexactness in computing and would be a great application for these chips. <\/p>\n<\/p>\n
Read this article: <\/p>\n
A few errors could be key to super-efficient computer chips<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" I used to work on an imaging team at a big insurance company and we were required to store our images with a very particular lossless compression in a TIF file specifically because the law does not hold lossy compression as reliable. But, regarding jessepollard's other statements: \"The place you don't want errors is in the instruction stream.\" That's not where the errors are. Continue reading