Turned out, it was noise / amplifier signal correlated with the adjacent chip dumping overexposed pixels on readout. He was embarrassed after a professor pointed out (after inspecting the files) that it always appeared on the same exact pixel coordinates on the array, but learned his lesson to try to disprove your own observations with independent tests.
I wonder how much some of these unidentified phenomena might be checked for some similar effects. Were the pilots reporting things seen with their eyes, or looking at imaging displays that have been processed. And maybe... were recently illuminated with lasers... hm? There certainly seem to be a pathology of similar reports of "the object never moved in the viewfinder, and would imply the ability to move suddenly at supersonic speeds"
Recently, with all that internet marketing and real surveillance tech, this worsened a lot. Some humans are just wired differently.
For example large part of IT professionals which contacts our support (https://poste.io) don't get difference between SMTP envelope and from/to headers.
Fowler's approach is amusing in that, in classic UML style, he models things which are optional in an authoritative way as if they are requirements, thus muddying the waters even further. While his adjustment implementations are interesting as a basis for feature comparison, there's a lot to be said for simplicity, and this effectively requires throwing out what the bean-counters are used to and reconsidering the need from scratch. The default correction is another transaction, and this requires no special implementation.
New systems recommendation:
(1) For account identification, use IIBAN which provides IBAN-compatible account identification and checksums and is an open system @ https://github.com/globalcitizen/iiban
(2) For all accounting, use UTC.
(3) For transaction identification, use UTC second of origination (UTCSO) + account of interest (AOI; eg. IIBAN) + intra-second transaction identifier (ISTI).
Free thoughts on forward-looking accounting systems @ https://raw.githubusercontent.com/globalcitizen/ifex-protoco...
EDIT: Mine is actually in a very wealthy neighborhood and the lady who runs the practice (I think that's how it works?) has a reputation for buying state-of-the art tech.
I have worked with many Indian programmers over the years. I only ran into a very small amount who were not brilliant, but were average. The rest where brilliant, and a few I learned some cool tricks from. For young Americans, most were good but none approached the level of smarts most of the Indians I worked with.
The US should send observers over to India and study their education system :)