Hacker News new | ask | show | jobs
by CommieBobDole 1577 days ago
Each of the detectors has a detail graph of radiation over time if you click on it - a lot of them show a many-fold increase in radiation in the last few hours.

Particularly concerning are some near the reactor building itself that went to a fairly high reading very quickly (65500 nSv/h in one case, which is likely offscale high) and then stopped reporting at 21:50 local time (it's currently 03:30).

65500 nSv/h is definitely not 'you're going to die right now' radiation levels, but it's definitely getting into the territory of stuff you don't want stand around in for too long. If I've done the math right, I think that's about three times the allowed annual exposure for radiation workers every hour.

Edit: I think I didn't do the math right and am off by 1000x. 65500 nSv/h is like three chest x-rays an hour. Which is still not good, but would take quite a bit longer to get really dangerous.

2 comments

Note that

65500 = round(typemax(UInt16)/100)*100

and no higher value exists on the map it might actually be worse how much we can't tell though.

What a grim coincidence if this type of saturation error pops up again in relation to Chernobyl.
Is it a coincidence? Or are dosimeters commonly calibrated for a maximum reading of "not great, not terrible" for best sensitivity in the range they're likely to be needed for? This maximum reading is 50 times less than the famous "3.6 Roentgens".
Nice use of Julia to communicate with humans.

However, since you've chosen to communicate through code, strictly speaking it ought to be '==' :p

Yes, I write Julia but I didn't use Julia on purpose. It just feels natural syntax, which I guess is an compliment to Julia.
Very helpful, thanks!