|| This explanation may be incomplete or incorrect: Created by a MISSING PHYSICAL PHENOMENON LOST DUE TO HIGH COMPRESSION. More on the title text - Dark matter and dynamic range issues need to be explained in more detail. Please mention here why this explanation isn't complete. Do NOT delete this tag too soon.|
If you can address this issue, please edit the page! Thanks.
Voyager 1 is a space probe launched by the United States in 1977. Originally designed to study the outer planets of the Solar System, it is now several decades into an extended mission beyond Neptune. The Voyager probe has made history for passing many milestones of our solar system.
When images are compressed by a lossy compression format (e.g. JPEG), visual artifacts are created. Randall here is suggesting that the probe has passed the artifacts as if the artifacts were an actual feature of the solar system rather than a consequence of our technology. The banding lines he has drawn are commonly seen in old images with low bit depth built by software that doesn't implement a technique to remove them called dithering. However, the slightly discolored regions often created by compression could also be a metaphor for the region of space that that solar radiation prevents from being a complete vacuum: because there is some gas in these areas, they may reflect light, causing banding lines when their density is high enough. Voyager 1 has passed through numerous such boundaries, as mentioned previously in 1189: Voyager 1.
Compression artifacts are often caused by large changes in coloration over a short distance, and Randall could feel that the drastic change in coloration from bright sun to dark vacuum could be creating a compression artifact around the Sun, somewhat like the Sun looking blurry due to low video quality. However, there is no definite region where solar radiation stops, only a boundary where it fades to a level lower than that of radiation from other sources. Some compression methods result in compression artifacts that behave in the same way, fading as the distance from the color boundary increases but never completely disappearing.
The 'solar system' in the snapshot appears to be a 4-bit greyscale-plane at a more pixelated level than the image given. It can be picked out as being in 16 'banded' levels from the brightest (closest zones, within this image, to the Sun) to darkest (the furthest illustrated expanses, heading into interstellar space), with irregular or non-trivial transitional edges but no obvious or dominant dithering/speckling or 'noise'. The Voyager image (and track) is overlaid at finer resolution in the white 'line drawing' format.
The 'apparent pixels' seem to be at a resolution close to the order of 1AU². A rough count of the pixelation boundaries from the craft to the leftmost edge, plus an additional allowance for the likely radius of the 'sun' (or, rather, its solar wind density, or similarly represented measure) still beyond the edge, is surprisingly close to to the ~150 AU current distance of Voyager 1.
For perspective, the Earth is then within/adjacent to the single lower-resolution 'pixel' that holds the Sun, and as of the comic's date of publication, over on its far side. But the Sun itself is not even visible, as the bright ball of pixels representing its environs is centered off the left side of the comic. It would be a dot so far beyond the left boundary of the image that Neptune, at around 30 'pixels' distance, may only just be placed within the leftmost extreme of this view at its own rightmost point in its orbit. The overlaid Voyager 'sketch' (in its more native resolution/bit-depth and antialiasing) stretches out over maybe a dozen such low-res pixels/AUs; this suggests that the viewpoint of the observer is close to the Voyager craft, making the craft appear large by comparison.
In the title text the mystery of the undetectable Dark Matter, which current mainstream physics supposes makes up most of the mass in the universe, is explained since this dark matter is rendered completely undetectable by our spacetime codec's dynamic range issues (thus brushing against the theme of a simulated universe).
Artifacts are evident in 1683: Digital Data, and mentioned in the title text of 331: Photoshops.
- [Irregular bands of gray are shown, shading from a white circular segment on the lower left side of the panel to completely black on the right. The bands have pixelated edges. A small white space probe is shown just outside the last dark gray band, in the completely black area. A dotted line starting from inside the dark gray area and ending at the space probe indicates that it is moving to the right, out of the gray area. Close to the white area, there are many bands packed closely together and with hard to define edges. But there are five gray areas clearly separated from the white, with a tendency to be elongated in the space probe's direction.]
- [Caption below the panel]: Milestone: Voyager has passed through the streaming video compression artifacts that mark the edge of the solar system
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!
"([Compression artefacts] may become literally unnoticeable because hexadecimal color values are discrete[...]" - disagree. Artefacts exist because of a discrete nature. Either of the RGB(/HSV/whatever) granularity, the lower the colour depth, or of the method used to get around the overheads of storing literal 24+ bits of colour-depth across a given image size. TrueColo(u)r should escape perceived colour-banding, but any image editor knows (or relies upon) that any flood-fill/by-colour-selection used with an absolute drift range away from the datum spot less than that across a gradient spills away from it can highlight 'hidden' edges between (say) #789ABC and #789BBC. What we have here is low bit-depth (grey-shade or equal-RGB, apparently 4-bit(/each), counting the 16 bands thanks to the mach-banding) non-dithered band-shading of a possibly nuanced (fractal?) shade fall-off. Possibly a 2D slice through 3D (or more, e.g. if animated) of voxelated (or hypervoxelated) stored values, which use up a lot of space in the Universe Simulator. Perhaps there's also something like Discrete Cosine Transform compression for easier block/chunk storage, retrieval and/or generation-on-demand (with detailed deltas for complex overlaying features such as Voyager). Because the Creator/Programmer of the universe has limited storage/processor cycles! 22.214.171.124 01:39, 21 January 2021 (UTC)
- tl;dr? — The 𝗦𝗾𝗿𝘁-𝟭 talk stalk 13:16, 21 January 2021 (UTC)
- TLDR is this Tom Scott video on the topic: https://youtu.be/h9j89L8eQQk. Short version: the difference between blacks #010101 and #020202 (a doubling of brightness) is more noticeable than the difference between whites #FEFEFE and #FDFDFD (a 0.00001% change in brightness). If your picture is dark, and especially if it is compressed, you will often get ugly bands of different shades of black. 126.96.36.199 16:50, 22 January 2021 (UTC)
- Nice. — The 𝗦𝗾𝗿𝘁-𝟭 talk stalk 05:33, 27 January 2021 (UTC)
I would suggest that more emphasis needs to be placed on 'dynamic range' and 'undetectable' in this explanation. Particularly noticeable in streaming video codecs, you often can't decipher any information in dark scenes/regions. So the joke is that the map beyond here is empty, mostly because it is too far down in the dynamic range of our lossy observations. 188.8.131.52 17:36, 21 January 2021 (UTC)
- Re "...stretches out over maybe a dozen such low-res pixels/AUs, which is equivalent to slightly more than the radius of Saturn's orbit or the entire diameter of Jupiter's!", this assumes that Jupiter and Voyager are the same distance from the imaginary "camera". I can completely cover the moon with my thumb, but that does not imply that they are similar in size, because my thumb is closer to my eye. (Unsigned!)
- I presume that this is the 'data' version of our system, straight from the 'cosmic computer' behind reality, viewed orthographically like a Minecraft map. But it matters not. The text quoted clearly gives scale context (on the justifiable presumption that the low-res grid is a 1AU-sized display of solar particle distribution) that "the range of the map the Voyager covers is like the size of these orbits". Just like "the area of the sky my thumb obscures is roughly a Moon-width". 184.108.40.206 01:18, 22 January 2021 (UTC)
- Re: "The Voyager image (and track) is overlaid at finer resolution", if it not unheard-of for a compression algorithm to render, say, 32x32 pixel blocks as if they were single, larger pixels if their immediate neighbors are almost the same shade, while rendering small, detailed, and high contrast portions of the image at a higher resolution. No "overlay" required. (Still unsigned!)
- Within an area of finer details, artefacts would be seen as the "meh, this is just one block" attitude is changed to incorperate detail of interest within a sub-block. There's no sign of fringe-artefacts (other than normal XKCS antialiasing of lines against background). I'd say it was a "solar wind" low-detail layer over which is incorporated a "Voyager" standard-detail layer with transparency, not a single layer of subject-aware tunable blockwise compression. (It might have come out differently if the composition was saved in an actual lossy-compression, by Randall, rather than .png, but for different reasons. Bit that's a meta-discussion issue, not nerd-sniping.) 220.127.116.11 01:18, 22 January 2021 (UTC)
This doesn't just happen in old images. I still see this frequently when watching movies, even new ones, where what should be a smooth gradation of tones shows steps. The other obvious defect is poor sprite handling, which causes artifacts like someone's facial features not moving with their head movements.
I'm not sure dithering would be a useful way to dispel the banding, since dithering would increase the compressed data size because you no longer have large areas of all-the-same-pixel-value.
The banding could also be an artifact of the decompression. If you consider that a format like JPEG uses something like Fourier transforms it seems it should be able to represent a gradation easily and the stepped banding with difficulty, so I might be tempted to blame the banding on the decompression code.18.104.22.168 13:46, 22 January 2021 (UTC)
I did a 'best fit' on the probable solar system, across this 'map' (which I think is slightly made up, because of certain issues when I started differentiations of the grey-levels, making me think it has been 'painted', or enhanced, not taking from real data - of the 'real thing' or not). I don't seem to get any Wiki upload/new-media rights, as an IP user, but if anyone wants to look at the image saved at https://imgur.com/KSqC1Nr and consider it/be inspired by it then I offer it up, gratis. It features the orbits of Earth, Mars, Jupiter, Saturn, Uranus and Neptune in body-appropriate hues, such that they are to scale with the true distance of Voyager from the focus of the likely circular orbts. (I think I left the 'Sun' pixel (image pixel, not 'artefact pixel') magenta, easier to see against the whitist-whiteout core shade.) I only refrained from adding Pluto (and Eris, etc) off because I don't have immediate into on the far more eccentric oval. Darn, I meant to add the asteroid belt. As a suitably fuzzy grey band. Not redoing it. 22.214.171.124 22:58, 24 January 2021 (UTC)
Source of Voyager 1
Given Voyager 1's distance and age now, wouldn't it be more appropriate to change the opening explanatory sentence to "Voyager 1 is a space probe launched from Earth in 1977."
The only sentient creatures who may still care about its origins in the United States are probably also from the United States. The next sentient beings to encounter Voyager 1 will have no understanding of what the United States is or was.
One more point: I think this XKCD is a play on the fact that every few years we hear once again that "Voyager has left the solar system". First because it passed the termination shock, then because it passed the heliopause. This article from NASA says that Voyager won't be officially out of the solar system until it passes the Oort cloud. These milestones seem arbitrary, so why not make up one more? Efalk (talk) 17:13, 24 January 2021 (UTC)