https://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres...
A good reminder that the bug can be anywhere, and when things stop working we often need to get very dumb, and just methodically troubleshoot.
I used to install T1 lines a long time ago. One day we had a customer that complained that their T1 was dropping every afternoon. We ran tests on the line for extended periods of time trying to troubleshoot the problem. Every test passed. Not a single bit error no matter what test pattern we used.
We monitored it while they used it and saw not a single error, except for when the line completely dropped. We replaced the NIU card, no change.
Customer then hit us with, "it looks like it only happens when Jim VNCs to our remote server".
Obviously a userland program (VNC) could not possibly cause our NIU to reboot, right?? It's several layers "up the stack" from the physical equipment sending the DS1 signal over the copper.
But that's what it was. We reliably triggered the issue by running VNC on their network. We ended up changing the NIU and corresponding CO card to a different manufacturer (from Adtran to Soneplex I think?) to fix the issue. I wish I had had time to really dig into that one, because obviously other customers used VNC with no issues. Adtran was our typical setup. Nothing else was weird about this standard T1 install. But somehow the combination of our equipment, their networking gear, and that program on that workstation caused the local loop equipment to lose its mind.
This number-swapping story hit me the same way. We would all expect a compression bug to manifest as blurry text, or weird artifacts. We would never suspect a clean substitution of a meaningful symbol in what is "just a raster image".
tldr: Specific packet content triggers a bug in the firmware of an Intel network card and bricks it until powered off.
I have seen weird artifacts on MRI scans, specifically the FLAIR image enhancement algorithm used on T2 images, i.e. white spots, which could in theory be interpreted by a radiology as small strokes or MS...so I always take what I see with a grain of salt..
MRI artifacts though are a whole can of worms, but fundamentally most of them come from a combination of the EM physics involved, and the reconstruction algorithm needed to produce an image from the frequency data.
I'm not sure what you mean by "image enhancement algorithm"; FLAIR is a pulse sequence used to suppress certain fluid signals, typically used in spine and brain.
Many of the bright spots you see in FLAIR are due to B1 inhomogeneity, iirc (it's been a while though)
DICOM is a vast standard. In it's many crevasses, it contains wire and file encoding schemas, some of which include (many different) image data types, some of which allow (multiple) compression schemes, both lossy and lossless, as well as metadata schemes. These include JPEG, JPEG-LS, JPEG-2000, MPEG2/4, HVEC.
I think you have to encode the compression ratio as well, if you do lossy compression. You definitely have to note that you did lossy compression.
The main problems is that that typical imaging researchers are too far from actual clinical applications, and often trying to solve the wrong problems. It's a structural problem with academic and clinical incentives, as much as anything else.
> a bit of a danger of this method: One must not be fooled by the quality of the reconstructed features — the content may be affected by compression artifacts, even if it looks very clear
... plus an excellent image showing the algorithm straight making stuff up, so I suspect the author is aware.
Very sketchy to use a super resolution for diagnostics. In research (flourescence), sure.
ref: my direct experience of pathology slide scanning machines and their setup.
I do think, however, the primary application of these newer generation of generative models will be useful for more sophisticated data augmentation. For example, a lung nodule detection AI trained on a combination of synthetic and real lung nodules may perform better than one trained on real data alone. Do you think there are any other responsible applications?
Maybe something like dividing the image into small squares, computing the L2 difference between original and compressed. If any square has too large L2 difference then compression failed. Th metric might need to be informed by the domain.
Edit: Or maybe PSNR+SSIM?
I was told that the GPT-2 text compression variant was a lossless compressor (https://bellard.org/libnc/gpt2tc.html), why is stable diffusion lossy?
However, a cautionary tale on AI medical image "denoising":
(and beyond, in science)
- See the artifacts?
The algorithm plugs into ambiguous areas of the image stuff it has seen before / it was trained with. So, if such a system was to "denoise" (or compress, which - if you think about it - is basically the same operation) CT scans, X-rays, MRIs, etc., in ambiguous areas it could plug-in diseased tissue where the ground-truth was actually healthy.
Or the opposite, which is even worse: substitute diseased areas of the scan with healthy looking imagery it had been trained on.
Reading recent publications that try to do "denoising" or resolution "enhancement" in medical imaging contexts, the authors seem to be completely oblivious to this pitfall.
(maybe they had a background as World Bank / IMF economists?)