this post was submitted on 06 May 2024
26 points (100.0% liked)

Science Memes

10905 readers
2356 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
 
top 19 comments
sorted by: hot top controversial new old
[–] merc@sh.itjust.works 6 points 6 months ago (2 children)

To me, the physics of the situation makes this all the more impressive.

Voyager has a 23 watt radio. That's about 10x as much power as a cell phone's radio, but it's still small. Voyager is so far away it takes 22.5 hours for the signal to get to earth traveling at light speed. This is a radio beam, not a laser, but it's extraordinarily tight beam for a radio, with the focus only 0.5 degrees wide, but that means it's still 1000x wider than the earth when it arrives. It's being received by some of the biggest antennas ever made, but they're still only 70m wide, so each one only receives a tiny fraction of the power the power transmitted. So, they're decoding a signal that's 10^-18 watts.

So, not only are you debugging a system created half a century ago without being able to see or touch it, you're doing it with a 2-day delay to see what your changes do, and using the most absurdly powerful radios just to send signals.

The computer side of things is also even more impressive than this makes it sound. A memory chip failed. On Earth, you'd probably try to figure that out by physically looking at the hardware, and then probing it with a multimeter or an oscilloscope or something. They couldn't do that. They had to debug it by watching the program as it ran and as it tried to use this faulty memory chip and failed in interesting ways. They could interact with it, but only on a 2 day delay. They also had to know that any wrong move and the little control they had over it could fail and it would be fully dead.

So, a malfunctioning computer that you can only interact with at 40 bits per second, that takes 2 full days between every send and receive, that has flaky hardware and was designed more than 50 years ago.

[–] flerp@lemm.ee 3 points 6 months ago (1 children)

And you explained all of that WITHOUT THE OBNOXIOUS GODDAMNS and FUCKIN SCIENCE AMIRITEs

[–] kuberoot@discuss.tchncs.de 2 points 6 months ago

Oh screw that, that's an emotional post from somebody sharing their reaction, and I'm fucking STOKED to hear about it, can't believe I missed the news!

[–] chimasterflex@lemmy.world 2 points 6 months ago (1 children)

Finally I can put some take into this. I've worked in memory testing for years and I'll tell you that it's actually pretty expected for a memory cell to fail after some time. So much so that what we typically do is build in redundancy into the memory cells. We add more memory cells than we might activate at any given time. When shit goes awry, we can reprogram the memory controller to remap the used memory cells so that the bad cells are mapped out and unused ones are mapped in. We don't probe memory cells typically unless we're doing some type of in depth failure analysis. usually we just run a series of algorithms that test each cell and identify which ones aren't responding correctly, then map those out.

None of this is to diminish the engineering challenges that they faced, just to help give an appreciation for the technical mechanisms we've improved over the last few decades

[–] trolololol@lemmy.world 0 points 6 months ago* (last edited 6 months ago) (1 children)

pretty expected for a memory cell to fail after some time

50 years is plenty of time for the first memory chip to fail most systems would face total failure by multiple defects in half the time WITH physical maintenance.

Also remember it was built with tools from the 70s. Which is probably an advantage, given everything else is still going

[–] orangeboats@lemmy.world 1 points 6 months ago

Also remember it was built with tools from the 70s. Which is probably an advantage

Definitely an advantage. Even without planned obsolescence the olden electronics are pretty tolerant of any outside interference compared to the modern ones.

[–] FlatFootFox@lemmy.world 4 points 6 months ago (2 children)

I still cannot believe NASA managed to re-establish a connection with Voyager 1.

That scene from The Martian where JPL had a hardware copy of Pathfinder on Earth? That’s not apocryphal. NASA keeps a lot of engineering models around for a variety of purposes including this sort of hardware troubleshooting.

It’s a practice they started after Voyager. They shot that patch off into space based off of old documentation, blueprints, and internal memos.

[–] BearOfaTime@lemm.ee 0 points 6 months ago (1 children)

I realize the Voyager project may not be super well funded today (how is it funded, just general NASA funds now?), just wondering what they have hardware-wise (or ever had). Certainly the Voyager system had to have precursors (versions)?

Or do they have a simulator of it today - we're talking about early 70's hardware, should be fairly straightforward to replicate in software? Perhaps some independent geeks have done this for fun? (I've read of some old hardware such as 8088 being replicated in software because some geeks just like doing things like that).

I have no idea how NASA functions with old projects like this, and I'm surely not saying I have better ideas - they've probably thought of a million more ways to validate what they're doing.

[–] Qli@lemmy.world 1 points 6 months ago

There is an fascinating documentary about the team that sends the commands to Voyager 1 and 2 called It's Quieter in the Twilight

[–] nxdefiant@startrek.website 1 points 6 months ago (1 children)

Imagine scrolling back in the Slack chat 50 years to find that one thing someone said about how the chip bypass worked.

[–] xantoxis@lemmy.world 1 points 6 months ago (1 children)

Imagine any internet company lasting 50 years.

[–] jaybone@lemmy.world 2 points 6 months ago

This is why slack is bullshit. And discord. We should all go back to email. It can be stored and archived and organized and get off my lawn.

[–] fsr1967@lemmy.world 1 points 6 months ago (1 children)

Interviewer: Tell me an interesting debugging story

Interviewee: ...

[–] sudo42@lemmy.world 0 points 6 months ago* (last edited 6 months ago)

Heh. Years ago during an interview I was explaining how important it is to verify a system before putting it into orbit. If one found problems in orbit, you usually can’t fix it. My interviewer said, “Why not just send up the space shuttle to fix it?”

Well…

[–] pruwybn@discuss.tchncs.de 1 points 6 months ago

Why do Tumblr users approach every topic like a manic street preacher?

[–] watersnipje@lemmy.blahaj.zone 1 points 6 months ago

Man I can’t even get my stupid Azure deployment to work and that’s only in Germany.

[–] Diplomjodler3@lemmy.world 1 points 6 months ago (1 children)

Still faster than the average Windows update.

[–] blackluster117@possumpat.io 0 points 6 months ago (1 children)
[–] bstix@feddit.dk 1 points 6 months ago

Absolutely. The computers on Voyager hold the record for being the longest continuously running computer of all time.