They're assuming very quick transfers (rush hour service). But then again, a lot of transit planning seems to assume rush hour commutes are the only reason why it's there.
There are a few -- select the 79th street station on the #1 line (farthest west in Manhattan) and look at Brooklyn, due pretty much directly south. The 36th Street station on the D/N/R lines is reachable in 40 minutes because it gets express service, but the stations to the north and south are local stops, and for that reason, take longer to get to.
OpenAI is extremely cagey about what's in their test data set generally, but absent more specific info, they're widely assumed to be grabbing whatever they can. (Notably including copyrighted information used without explicit authorization -- I'll take no position on legal issues in the New York Times's lawsuit against OpenAI, but at the very least, getting their models to regurgitate NYT articles verbatim demonstrates pretty clearly that those articles are in the training set.)
Obfuscation isn't really possible. The identities of the crew are very public, and they all got hospitalized, so there isn't even room for guessing games about which one.
This caught me out when I was a teenager. Luckily, there was a chap in the Museum of Computing who was spending his Sunday working on the Colossus, and he was happy to let me in and show me around! I'll never forget that kindness, it was truly a fascinating trip.
I was there a few years ago and will echo the fact that the folks I interacted with at the museum of computing were truly world class fantastic. When someone loves what they do and where they are it really shows.
My boss at Experian took our team to Bletchley Park intending to go to the NMOC but not having checked that was actually open. Hilarious.
Fortunately the small Memorial to the Polish Cryptographers who are the reason this was worth attempting is outside so we could visit that, about a third of the team were Polish (we hired away some subcontractors from a Polish firm, and then we were in turn bought by Experian) so visiting this memorial was a key part of our intent.
Also IIRC at that time the Bombe was still not in TNMOC, and Colossus was in a separate building so you could see it, but the rest of TNMOC was closed.
I've also seen an even earlier incarnation of TNMOC when I was younger, just basically a room heaped with obsolete computer gear, with some nerds who know roughly what it is but aren't equipped to properly exhibit or explain it. I remember they'd set up some video game consoles, something like the original Sonic The Hedgehog maybe, because they wanted children to have some positive impression, obviously a kitchen appliance sized "disk drive" doesn't mean anything to a child, but it's obvious Sonic is a game even if you're used to much flashier graphics.
I found chatting to the people working on stuff was the best bit.
Almost the level of ignoring the exhibits and look at the bits of stuff being worked on around.
SFO security is run by some company "under contract" to TSA -- probably required to follow all the same procedures, so it's not clear the business arrangement makes that much difference to the passengers. I've been through there a few times, and haven't found it any more organized or pleasant...
Also, some of this is accounted for by a difference in development philosophy. The typical NASA project tests finished designs to make sure that they'll work. SpaceX frequently (currently for Starship) tests half-finished designs because they want to know how they will fail, for future revision. (Example: between starship flight tests 1 and 2, the whole staging method changed; forward fins are being relocate on Starship starting, I think launch after next to reduce heating in reentry, etc.)
They do tests on production vehicles too, e.g. the static fires that precede just about every launch, but those aren't directly comparable to the stuff they deliberately blow up to see how that happens.
In an ideal world NASA would also do this (see the Apollo program). The optics of a government program ‘failing’ are so spectacularly bad they simply cannot afford to do this.
Yes, permanent teflon deformation. Problem is, if the deformation observed in ground tests was permanent, why did the ones in space eventually seem to recover?
That's what's making it harder to trust the thrusters I think.
I understood what they were saying about the simulations as that the teflon seemed to have expanded slightly and disrupting the oxidizers input, meaning the thrusters wouldn't work as they should.
Skip down to the bottom for a simple approach that just works, in sufficiently recent PG releases (MERGE). Back up just a bit for something that's nearly as good, and works with everything since Postgresql 10 (INSERT ... ON CONFLICT). Most of the post describes more complicated approaches that have subtle race conditions, and are worth looking at mainly to understand what the problems are.
reply