Accidental implosion yields new measurement for ocean's deepest point
nationalgeographic.com
nationalgeographic.com
The glass is made in two hemispheres and the contact surface is ground flat. There’s no glue or mechanical attachment; the hemispheres are carefully lined up by hand and then they pull vacuum. Atmospheric pressure alone keeps them mated prior to submersion. Then of course they are pushed together harder and harder as they descend.
The engineers talked a university into letting them use their hyperbaric chamber for testing. One of the prototypes failed at high pressure, which sounded like a bomb going off. The glass was reduced to tiny slivers, which the university was still finding in nooks and crannies years later. (The Nat Geo team was not allowed back after that.)
The probes were timed on the bottom by using thin steel wire to attach the weight. Basically the wire would rust until it broke, then the globe would float to the surface and start broadcasting a radio beacon for pickup. They adjusted the time by varying the thickness of wire.
They also stuffed the globes with LED lights and used them as “sun-like” sources of illumination for underwater cave photography.
I don’t know if cold welding is really welding but contact bonding is certainly not like welding.
I'm guessing it was not very close to vacuum? The article mentions air explicitly:
> As the instrument's glass collapsed under the weight of five miles of water, it released a pocket of air that oscillated under pressure before splintering into a veil of tiny bubbles.
"It sounds a bit sadistic," he says. "But it's a really good exercise to do.""
Anyone else finding beauty in this?
The meticulous and tedious, often thankless nature of scientists and their work. Also a nice strategy to implement for some other projects/fields.
Once I write tests for all the things that could go wrong and verify the correct behavior, I feel a lot better than if I only test the happy path (when everything goes right).
I wish software developers would take more time to think about how things could go wrong.
I wish more PMs understood the need to spend developer hours on it.
Only when you've written them all down, do you have a list of things to actively expect to go wrong, and prevent or mitigate.
It is the difference in handling risk between using knowledge, skill, technology, and planning to manage risk, vs relying on Pure Dumb Luck and hoping to get away with something.
Also, for some reason I always assumed the Challenger Deep was in the mid Atlantic Ocean. It’s not, it’s a few hundred miles southwest of Guam in the Pacific Ocean.
Sounds like there is a self-reinforcing effect at play here?
That kind of goes towards the answer of why it was useful, but also begs the question of why there haven't been more scientists there.
Heard a cool podcast on Embedded FM 363 Squishy Nature
Talks about electronic design under deep water pressure/Rovers
Also enjoyed the Deepsea Challenge James Cameron free (w ads) on YT.
Also, it seems like a great scifi premise to stir up the kraken/cthulu/hydra.
[1]http://www.deepseachallenge.com/the-expedition/1960-dive/