For another, the dependence on a random seed is just one example of how you can get different behavior. You could just as well get different results due to e.g. a tiny difference in prompt wording or punctuation or whitespace.

If a model passes some test on 70% of random seeds, and fails on the other 30%, then knowing the rough probability of success is much more useful than knowing one random sample of the outcome.

And empirically this kind of probabilistic success is quite common, because many LLM benchmarks report "pass@k" success rates that are much higher than the "pass@1" success rate on a single attempt.

If you wanted to use such a device as a simple oscillator, you just set it vibrating and measure the oscillation frequency. Since the material isn't perfectly elastic, the vibrations will eventually be damped and die out (I guess this is what you mean by "friction"), so you use a feedback mechanism to keep the oscillation going.

A gyroscope works the same way, except that you use feedback to maintain an oscillation in one axis, and measure how much of that oscillation couples to a different axis. Whatever effect the damping has on the final measurement, I would assume it can be easily calibrated out.

I don't really know how they physically manufacture these devices without damaging the tiny, delicate structures. It's kind of mindblowing that they're so incredibly cheap.

Vinge didn't quite get to see his rogue AI prediction become (sort of) reality, right on schedule, but he did at least outlive Credit Suisse.

Consider a very simple topology:

    A         C
     \       /
      S1===S2
     /       \
    B         D

S2 is receiving packets destined for C faster than it can forward them, but sending an Ethernet pause frame from S2 to S1 is not a very productive way to alleviate the situation, because it also disrupts any traffic that would be bound for D. It just moves the bottleneck elsewhere and causes collateral damage.

Stress doesn't cause your body to "immediately grenade itself", it causes gradual problems over an extended period. But you can imagine that evolutionarily speaking, a stressful situation would frequently be a situation involving imminent danger. A response that prioritizes short-term survival (e.g. releasing adrenaline and cortisol) regardless of the long-term consequences could easily improve evolutionary fitness.

The fact that the near side appears to have large areas with few craters, and the far side doesn't, is a result of many near-side craters having been erased by lava flows. It's not because it received fewer impacts.

> but for the overview and demo of it working, watch the following youtube video.

If you don't care about the overview and just want to see demos, they start around 9 minutes in.

I bought a new electric car recently. For the most part I've been quite happy with it. Shortly after I bought it, it started popping up a warning message saying "check EV system" every time I started it. By the time I brought it into the dealership, the warning had gone away, and the technician just told me something to the effect of "eh, I guess it just does that sometimes, let us know if it happens again." Hardware fault? Software bug? Who can say?

Like most modern cars, it has connectivity and Google Maps built into the infotainment system. The vast majority of the time, it works fine. Sometimes it says it has no connectivity (meaning no traffic data and suboptimal routes) for the duration of a drive, even in areas with a strong cell signal where it normally works fine. Sometimes the car says it has connectivity, but Google Maps still thinks it's offline. Sometimes Maps will actually load and display a route, but the "start navigation" button just spins forever as though it's still waiting for something. Are these related issues? Is there a common cause that might be fixable? Who can say?

(Conveniently enough, the warranty specifically does not cover any failures of software or firmware to operate correctly.)

If Flock had done a more competent job of securing their system, it would be harder to demonstrate this in a compelling way. To a technically-inclined person, it's obvious from the get-go that somewhere in Flock's pipeline, video is being recorded and archived, and is therefore vulnerable to misuse. But the more they're allowed to keep the implementation proprietary, the easier this is to sweep under the rug.

Also, 0.1% downtime in the form of a 45-minute outage per month is very different from 0.1% of requests failing in brief bursts. You often see downtime reported as "increased error rates" which is so vague as to be meaningless.

Google's "windowed user-uptime" attempts to deal with this a bit better, by exposing different views of the data instead of trying to condense uptime into a single number: https://www.usenix.org/system/files/nsdi20-paper-hauer.pdf

Anyway, it's clearly a labor of love. They have some very cool artifacts from the space program (e.g. a some of the Space Shuttle and Apollo main computers). And a large fraction of the floor space is devoted to a new, very comprehensive exhibit on the history of Apple, with just about every product they ever made plus some internal prototypes.