There’s much news from the Jezero Crater on Mars this week, and all of it was good. Not only did the Ingenuity helicopter make history by making the first powered, controlled flight of an aircraft on another planet, it made a second longer, more complex flight just a couple of days later. This time, the autonomous rotorwing craft flew to a higher altitude than the maiden flight, hovered for a bit longer, and made a lateral move before landing safely again on the surface. Three more flights of increasing complexity (and risk) are scheduled over the next two weeks, with the next set to happen early Sunday morning. I have to admit that even though the Ingenuity tech demonstration seemed a little like a publicity stunt when I first heard about it, especially when compared to the Perseverance’s main mission of searching for evidence of life on Mars, the Ingenuity team’s successes have made a believer out of me.
Speaking of technology demonstrations, NASA fired up the MOXIE experiment aboard Perseverance for the first time. Intended to explore the possibility of producing oxygen from the thin carbon dioxide-rich Martian atmosphere, the Mars Oxygen In-Situ Resource Utilization Experiment made about 5.4 grams of oxygen total at a rate of about 6 grams an hour. We detailed the technology MOXIE uses, called solid-oxide electrolysis, which depends on a scandium-stabilized zirconium oxide ceramic electrolyte to strip the oxygen from superheated carbon dioxide using an electric current. Should the technology prove itself over the planned total of ten MOXIE runs over the next few months, a scaled up version of the device could someday land on Mars and produce the estimated 55 metric tons of oxygen needed to fuel a return trip from a crewed mission.
By now we’ve all heard about the global semiconductor shortage, or perhaps felt the pinch ourselves while trying to procure parts for a build. It’s easy to count the crunch as yet another follow-on from the COVID-19 shutdowns and the logistics woes the pandemic begat, so one might have hope that with lockdowns easing up around the world, the shortage will soon be over as manufacturers ramp up production. But not so fast — it looks like the machines needed to make the chips are the latest victims of the shortage. According to Nikkei Asia, wire bonding machines, wafer dicers, and laser drilling machines are all in short supply, with orders for new machines booked out for a year. Like toilet paper this time last year, chip makers are hoarding machines, ordering 50 or 100 of them at a time, in the hopes of having enough to meet production goals. And when machines are available, travel restrictions are making it difficult to get on-site installation and support from factory reps. The bottom line — this isn’t over yet, not by a long shot.
We all know the Stack Overflow memes, and few of us who are being honest haven’t squirmed a bit when thinking about just how screwed we’d be without being able to copy a bit of code to get us past that rough part in a project. But just how often do people copy code from Stack Overflow? Quite a lot, actually, if SO’s analysis of the use of copy commands on their pages is to be believed. For two weeks, SO monitored the number of times the Ctrl-C (or Command-C, if that’s your jam) key combination was pressed. They toted up over 40 million copies, most often from the answers to questions and almost always from the code blocks within them. We suppose none of this is exactly unexpected — memes are memes for a reason, after all — but what we found surprising is that one in four visitors to Stack Overflow copied something within five minutes of loading a page. Being charitable, we’d say the speed with which coders accept someone else’s work is an indication that maybe they were almost at an answer themselves and just needed a little reminder. On the other hand, it could be a sign of separation driving them to get something working.
And finally, while we know we’ve recommended videos from Grady at Practical Engineering recently, we couldn’t help but plug another of his videos as a must-watch. This time, Grady tackles the Suez Canal blockage, and he presents it in the same dispassionate, informed way that he previously handled the engineering roots of the Texas blackouts. If you think the Ever Given grounding was just a case of poor seamanship, think again — Grady makes a compelling case for possible hydrodynamic causes of the incident, including “squatting” and the bank effect. He also speculates on the geotechnical forces that held the ship fast, in the process of which he helpfully introduces the concept of dilatancy and how it explains the way your feet seem to “dry out” a zone around them as you walk across the beach.
> On the other hand, it could be a sign of separation driving them to get something working.
Desperation?
Separation from a source of income.
Since the text has not changed since my post or your reply I assume yours is not meant to be sarcastic/funny but the original sentence is just a quirk in the English language I’m not privy to?
How does “Separation from a source of income” make sense in that sentence where it’s a “sign of separation”?
I’m confused…
I’d understand “sign of desperation not to be separated from a source of income” but just “sign of separation”?! no.
CRLL-C
Am I the only one to cringe at the idea that a site has visibility on when and where I type CTRL-C?
That’s why, BTW, I disable Javascript on almost all the sites I visit, including SO and its ilk. Now SO has found a new way to nag us in form of an oversized cookie consentment overlay.
Next escalation stage: a proxy filtering out stuff. Yes, a proxy. I only half-trust my browser
My thought exactly. I was wondering why and how the site could even tell if I hit Ctrl-C, or even a mouse right-click copy. If it’s JS doing the nefarious deed I’m going to have to pay more attention to what else it does. *sigh* Another Firefox profile to manage.
Well you see when you press a key on your keyboard the OS sends a signal to whatever application has focus, in this case the web browser.
You miss the entire point.
Ctrl-C should be entirely confined to the local machine. That’s the whole point. You’re copying a local representation of the data to a local buffer.
There is absolutely no reason for that Ctrl-C signal to leave the machine. In principle, even the browser application itself should not need to be aware of it — it could be entirely an OS-level operation (like a screen capture).
Or perhaps it’s time to inject a lot of Ctrl-C events to flood their database with junk.
Maybe, but then we never would have learned this bit of social behavior.
Are you the only one to cringe at the idea that software is aware of the keystrokes you’re using when interacting with it?
Probably. If it weren’t you wouldn’t be able to interact with your browser at all. That’s just how computers and web browsers have worked for a very, very long time, at least since Netscape.
You could always go back to BBS on a terminal.
Moxie uses 300 watts to make 6 grams of oxygen per hour. Not actually that bad. If you were to burn that oxygen again (with hydrogen, methane, carbon, whatever), you’d get back around 100 W. I was expecting the MOXIE process to be much less efficient, particularly at this small scale.
But 6 g/h just isn’t very much: you need 10x that to keep a human alive, assuming perfect recycling (open loop, it’s 10x worse). So, 3 kW. A lot, but not ridiculous. It likely more than that to keep a human breathing even here on earth (solar input to plants, etc.).
That 3 kW will need 30 square meters of solar panels. Again, a lot, but not insane.
But what about that 55t fuel requirement? If you’ve got 2 years to make it, that’s 3 kg/h, or a plant 500 times MOXIE’s size, sucking 150 kW. Way, way too much for a RTG, probably too big for a solar array. A fission plant is probably the only way to do it. With all the ancillary stuff, you’re probably looking at a megawatt of power requirement.
If you’re considering megawatt-scale reactors, it might be time to consider nuclear-ion propulsion too, and reduce the propellant requirement still further. Keep the ISRU propellant for the mars-to-orbit hop.
“Mars Oxygen In-Situ Resource Utilization Experiment”
That is so close to making MOxIe RUsE!
Excellent video by Grady!
We should send MOXIE to Venus, they got a shit ton of CO2 there! (By the way I mean an Imperial shit ton, but not a British Imperial shit ton but an American shit ton, as for the metric tonne de merde (TdM) I have no idea,)