Four of them operating in a redundant set and the fifth performing non critical task, as descripted in [1]. The fifth is also programmed by a different contractor in a different programming language: #1-4 running the Primary Avionics Software System (PASS) programmed by IBM in HAL/S and #5 programmed by a different team of Rockwell International in assembly. [2]
[1] https://people.cs.rutgers.edu/~uli/cs673/papers/RedundancyMa...
[2] https://ntrs.nasa.gov/api/citations/20110014946/downloads/20...
My understanding with the Voyagers 1 and 2 is (a) they will run out of power before they would ever get far enough to benefit from a relay and (b) they benefited from gravity slingshots due to planetary alignments that happen only once every 175 years.
So building on the Voyager probes is a no-go. But probes sent toward Alpha Centauri that relay signals? Toward the center of the Milky Way? Toward Andromeda? Yes it would take time scales far beyond human lifetimes to build out anything useful, and even at the "closest" scales it's a multi year round trip for information but I think Voyager, among other things, was meant to test our imaginations, our sense of possible and one thing they seem to naturally imply is the possibility of long distance probe relays.
Edit: As others rightly note, the probes would have to communicate with lasers, not with the 1970s radio engineering that powered Voyagers 1 and 2.
Gravity assists with more than one planet are more frequent. Cassini-Huygens [2] as example had five (Venus, Venus, Earth, Jupiter, Saturn)
I would suspect when the goal ist only to leave the solar system as fast as possible (and don't reach a specific planet) they are much more often.
[1] https://en.wikipedia.org/wiki/Grand_Tour_program [2] https://en.wikipedia.org/wiki/Cassini%E2%80%93Huygens
"Why Bell Labs Worked" [1]
"The Influence of Bell Labs" [2]
"Bringing back the golden days of Bell Labs" [3]
"Remembering Bell Labs as legendary idea factory prepares to leave N.J. home" [4] or
"Innovation and the Bell Labs Miracle" [5]
interesting too.
[1] https://news.ycombinator.com/item?id=43957010 [2] https://news.ycombinator.com/item?id=42275944 [3] https://news.ycombinator.com/item?id=32352584 [4] https://news.ycombinator.com/item?id=39077867 [5] https://news.ycombinator.com/item?id=3635489
Well documented spec, easy to bolt on extras either as public tags - GeoTIFFs added projection metadata - or private, for your own needs.
Back in the day, to improve a desktop application's performance I found it was simple to create a custom reader and writer to handle cases where tiles were completely one single colour removing the need to decompress at run time.
Thank you TIFf!
Just stick to winter time (because that's the correct one) and adjust all working hours once and for all to be like summer time, for e.g. instead of business opening at 7AM and closing at 10PM they can open at 6AM and close a 9PM. There will be a period of adjustment, but we have a period of adjustment twice a year already, so nothing is lost.
Why match working hours to summer time? Because I want to have more sunlight by the time I'm done with work. Especially during winter. We have it completely backwards, if we are going to adjust our clocks we should adjust them in a way that gives us more sunlight during winter, not less. I don't care if it's dawning by the time I'm going to work where I will be stuck indoors for nine hours, I want sunlight when I'm free again.
I first heard the term 'winter time' when it was discussed to decide weather to keep DST permanently or if people would like to keep 'winter time' always. And of course who would want to have winter-something always. ;)
[1] https://www.flickr.com/photos/130561288@N04/albums/721576504...
I hope it is not yet important for me as I never allowed a TV access to my LAN/WLAN. But with smart devices using accessible open WLANs to transmit who knows.
[1] https://arxiv.org/abs/2409.06203 / https://arxiv.org/pdf/2409.06203