As I understand it, the studies done with mice suggest that microgravity prevents normal embryo development. The ISS should therefore be regarded as a teratogenic environment, and I'd be shocked if women of childbearing age weren't prescribed highly-effective contraceptives (ie. IUD/IUS or implant) before, during, and after spaceflight.
I’m sure they were prescribed, but it’s always possible for them to fail.
I’m curious at what point in the embryo’s development the zero-g becomes an issue, if its immediate vs long term thing. It’s very possible that if it was pregnancy, the embryo is already not viable but she still needs some procedures to ensure her own health (a DnC, etc) that are important but not enough for an emergency evac.
Yes. Sex isn’t allowed on the ISS due to complications with pregnancy, but it’s not crazy to imagine that maybe they just did it anyway. (Who wouldn’t want to? It’s sex in space and it sounds amazing.)
They should have just taken some research notes to let them leverage the Mythbusters excuse: "The only difference between screwing around and science is writing it down."
or at least they can cache the results for a while and update so they can compare the answers over time and not waste the planet's energy due to their dumb design.
> There seems to be some confusion on this so let me clear this up. No, after the model gave its original response, I then proceeded to ask it if it could solve the problem with C=k/logN arbitrarily large. It then identified for itself what both I and Tao noticed about it throwing away k!, and subsequently repaired its proof. I did not need to provide that observation.
so it was literally "yo, your proof is weak!" - "naah, watch this! [proceeds to give full proof all on its own]"
> Distributed systems are notoriously hard to get right (i.e., guaranteeing correctness) as the programmer needs to reason about numerous control paths resulting from the myriad interleaving of events (or messages or failures). Unsurprisingly, programmers can easily introduce subtle errors when designing these systems. Moreover, it is extremely difficult to test distributed systems, as most control paths remain untested, and serious bugs lie dormant for months or even years after deployment.
> The P programming framework takes several steps towards addressing these challenges by providing a unified framework for modeling, specifying, implementing, testing, and verifying complex distributed systems.
reply