Xerox devices randomly altering numbers

  • Thread starter Thread starter nsaspook
  • Start date Start date
  • Tags Tags
    Numbers
Click For Summary

Discussion Overview

The discussion revolves around the issue of Xerox devices allegedly altering numbers in scanned documents. Participants explore the implications of this problem, potential causes, and the response from Xerox regarding the scanning algorithms used in their devices.

Discussion Character

  • Debate/contested
  • Technical explanation

Main Points Raised

  • Some participants suggest that the issue may be related to compression hash collision errors in the scanning process.
  • One participant expresses surprise at the possibility of such errors occurring in Xerox machines, implying that the scanning algorithms are complex.
  • Another participant criticizes the design choices of the programmers, arguing that the prioritization of document space over image integrity is problematic, particularly with lossy compression techniques.
  • It is noted that Xerox may have been aware of the issue, as it is mentioned in their user manual, raising questions about their handling of the problem.
  • A later reply mentions that Xerox plans to release a patch to address the scanning software error, suggesting an acknowledgment of the issue.

Areas of Agreement / Disagreement

Participants express a range of views on the causes and implications of the scanning errors, with no clear consensus on the best approach to address the issue or the adequacy of Xerox's response.

Contextual Notes

Limitations include the potential for varying interpretations of the scanning algorithms and the implications of lossy compression, as well as the lack of detailed technical specifications regarding the errors.

nsaspook
Science Advisor
Messages
1,560
Reaction score
5,162
Last edited by a moderator:
Computer science news on Phys.org
Holy crap. I would have never imagined a xerox machine could make that sort of error. Their scanning algorithms must be pretty darn clever to even have that sort of bug.
 
Those eunuch programmers have gotten too clever. :biggrin:
 
jtbell said:
Those eunuch programmers have gotten too clever. :biggrin:

They were very clever, to the point that saving document space became more important than document image integrity. Lossy compression should never be used when you expect the fidelity of the result to be a limited only by the resolution of the scanning process and the ability of the compression process to eliminate 'redundant' information. It's much better to see a blurry blob than a clear image that's completely wrong in any document scanning operation. Lossy compression usually goes beyond the 'redundant' and starts 'guessing' about different but similar patterns. In this case some numbers are deemed visually similar at some lossy compression ratio so it (the software classifier/comparator) selected a previously stored (seemly random) version to save space.
 

Similar threads

  • · Replies 2 ·
Replies
2
Views
4K
  • · Replies 13 ·
Replies
13
Views
4K