QR codes come with (differing levels of) error correction. You could decode it and take the amount of corrected errors as a score.

I don’t know what unit/chunk of data the error correction works on but you could alternatively dive a bit into information theory and calculate how close any of the chunks are to an uncorrectable error and use that as a score.

Since the first uncorrectable error will cause the scan to fail this would match your problem definition fairly well.

One benefit of this approach would be that it’s a single scan and done vs searching n permutations of the same code.
Or maybe you’d want to scan it a couple of times to rule out any additional errors introduced by the camera or environment.

Randall’s timing is impeccable sometimes

Why not? And you probably need the additional traction for that kind of acceleration out of corners

A little unfair towards SLS which did land its capsule xD

Yes

Within the same gravitational field, all bodies accelerate in vacuum at the same rate, regardless of the masses or compositions of the bodies; [1]

Wikipedia: Gravitational Acceleration first paragraph. Follow the [1] citation for a better source than Wikipedia.

Additionally orbital mechanics would break down. If a dragon spacecraft at the same altitude as the ISS wouldn’t experience the same gravitational acceleration they would have differing orbital periods and thus velocities and could never dock (or perform proximity operations).

No it doesn’t. That’s literally its main distinguishing point.

Classic physics experiment: Drop a block of steel and a feather in a vacuum. Which hits the ground first? (On earth, with the same fall height, etc)

Indeed

Losing both uv and ruff in one fell swoop sucks.

Sorry to ruin your day but solar frickin roadways is currently doing another funding round.

And for some unexplainable reason people are still giving them more money.

I ran into the same issue not so long ago and at least for no_std I had to resort to using the async_trait crate. (The project is no_std but has alloc)

I can’t recall the exact error so it might have been due to mixing async and non-async methods in the same trait. I would have to look at it again…

Absolutely. Maybe a poor choice of words on my part. My intention was to state that this is not a thing you simply hang out in the wind and leave, but instead a vehicle that needs to be controlled to stay within its operational envelope.

I can imagine problems like tethers or lines getting crossed when the vehicle makes fast turns due to wind shear or frequent direction changes. You probably can’t operate it in those conditions.

You would think so but even normal ground-fastened wind turbines shut off when winds get too strong.

This being somewhat of an aircraft I absolutely expect them having to land it before storms roll in.

If you land it facing up- or downwards and deflate the balloon segments it would probably be fairly flat and compact for storage.

I have never used them but there are some tools that advertise being able to run GitHub Actions locally, like WRKFLW.

Indeed

Its a fully electric drivetrain with a gas generator. When the battery runs low you can recharge it (even while driving) using the generator.

So you don’t have the complexity of a combined hybrid drivetrain, but instead a normal BEV one plus a power generator, both of which are very well understood problems.

Another benefit is that the generator can always run at its most efficient rpm/power point and is decoupled from the speed of the wheels.

Interestingly Wankel engines have been making a bit of a comeback for this purpose since they can be built more compactly for the same output power.

A drawback compared to hybrid drivetrains is that both components need to be built for “full” load, whilst a hybrid drivetrain can combine powers to reach maximum performance, meaning each of the motors only has to carry half (or part) of the total load.

I assume you mean AVIF? Because AV1 is not an image (file) format but a video compression format (that needs to be wrapped in container file formats to be storable).

Well the front didn’t fall off, so this could be typical for the new boosters.

The std::offload project is kinda cool. Hadn’t heard about that before.

It’ll be interesting to see where that leads.

I mean it sounds like they do have a working lifeboat in case of problems on the station.

Its just that their lifeboat can’t (safely) return to earth.

I was under the impression that the compiler already optimizes out a lot of clones where the clone is primarily used to satisfy the borrow checker. Is that not the case?