onnoonno

Another fun one:

a=[]

a.append(a)

If you behave lawful, you'll create one single tracking history for everything tied to your real life person. If you don't, you apparently can get away with stuff like that AND on top of that you won't create a single, coherent stream of data for big brother.

These are fucked up incentives.

Oh you are right. It actually _does_ have a time shift. I take back what I said and assert the opposite!

Thanks for the explanation.

I see, thanks. But that rather sounds like the buoy itself is switching modes?

From the look of all the plots, even the far-away ones, it rather looks to me like they have been remotely switched into event mode (with that 15s stuff being plotted at about the same time)?

I guess I am really confused about the time stamps.

The spike corresponds to about 15min delay between the quake at 9:31 UTC. But some kind of spike visible in all stations at that time, even very far away ones, like Mendocino bay.

Honestly, this looks to me rather like some bad data due to the buoys switching mode because of radio commanding 15min after the quake rather than any wave arriving. (Like the other poster suggested)

Even if the shock would travel through an Earth made out of steel, it wouldn't have reached Mendocino bay that fast.

EDIT: There is actually a time shift and it seems to be enough, as wiredfool pointed out. Thanks!

At least the time stamps in the plots seem to correspond to current time in GMT.

> My assumption, guess really, is that they were remotely activated into "Tsunami Mode" -- a more rapid-pulse reporting mode or similar, which just is a bit noisier perhaps?

That sounds like a very good guess. But then, the spikes that are purported to be the Tsunami in the media is just the ADC having a couple bad samples from being switched into a different mode or so :-)

If any USGS person is reading this thread here: Take it as a issue report that your page should be readable and understandable by lay persons, at least lay persons with a non-geophysics STEM background :D

What I don't get is that nearly all the buoys that have that moving icon "Tsunami alert" show some excitation at the ~9:45GMT mark.

But I would of course expect the buoys that are farther away to only show some kind of peak when the wave actually reaches them. And it looks like they are thousands of km away, so some of them should not even have been reached yet.

Some what is going on there? Is the data time actually shifted and not in GMT but 'earthquake propagation time'? Am I reading the plots wrong?

I have easily more than 100 firefox crashes for each kernel crash, and I guess that is similar for other people(?)

So I think the session restore is almost always used in a case where firefox crashed, but the system is fine.

I think versatility and the absolutely easy on-ramp are Python's killer app. The 'absolute noob' can start writing simple python code after 5min of introduction (you can start using it like BASIC), while the 'senior dev' can still write python after years and isn't turned off or overly constrained by the language. (Yes, of course, warts exists, no language is perfect)

And regarding Django being the killer app: There are other people for which numpy/scipy is Python's killer app, for example.

Are you sure? Bonnie++ has byte-wise and block-wise tests. Yes, the byte-wise tests are CPU bound (as expected), but I have not seen that for the block-wise tests on any machine so far?

You have a calculation error:

707 x .32m ~= 230m