Worldwide Earthquake Statistics · 101 days ago

Ok, time for a little Science™.

Recently I was intrigued by some reports on the Internet showing drastically increased earthquake activity in recent years. The data claims to be sourced from the USGS website. So naturally, I decided to download the data and analyze it for myself.

After all that work, I decided I should post something here for anyone else interested.

First off, full disclosure of my sources:

My data comes from the USGS, from two datasets. The first dataset is called the “Centennial Earthquake Catalog”, and it can be found here. It does not include any earthquakes less than M 5.5, and extends from 1900 to April 2002. For reasons mentioned below, I only looked at data from 1973 onward.

The second dataset is called the “USGS/NEIC (PDE)”, and a query tool can be found here. This has a much larger set of entries for the time period we are considering. The NEIC dataset begins at 1973, which is why I only use the Centennial dataset from 1973 onward.

A word about the data

The Centennial dataset is by far the smaller of the two datasets for the time period I am considering. During any particular time period, it appears to have only a small fraction of the entries that the NEIC dataset would have during the same time period, even for M 6.0 and greater. It also terminates in April 2002. I believe this dataset represents earthquake statistics gathered by the USGS from published sources. You can see that it often correlates many different reports on the same quake, if you look at the data.

The NEIC dataset is much denser, and as far as I can tell it is made of up data that is constantly being fed from seismographs worldwide. Thus, I would expect this dataset to have a definite increase in density over time, as earthquake reporting improves and more seismographs are installed. Someone please correct me if I’m wrong.

I downloaded the entire Centennial dataset, and queried the NEIC dataset for the years 1973-2010, M 3.0 or greater. All data was converted to a common csv format and imported into a MySQL database. There are 8333 entries from the Centennial dataset, and 448624 entries from the NEIC dataset.

Frequency Graphs

I produced a number of different graphs to help me analyze the data. First, I wanted to see to total number of earthquakes per year.

USGS NEIC Earthquakes M ≥ 3 Per Year

This graph shows the number of earthquakes per year, M 3.0 or greater, categorized by magnitude range, from the NEIC dataset.

Here is the data from the Centennial dataset. Notice that the data only shows quakes M 5.5 or greater:

USGS Centennial Earthquakes M ≥ 5.5 Per Year

I made another graph of the NEIC data showing only quakes M 5.0 or greater for comparison:

USGS NEIC Earthquakes M ≥ 5 Per Year

Force Graphs

After looking at this data for a while, I started to think “lots of small earthquakes may not be as significant as a few large ones”. This is because the Richter scale is a logarithmic scale. An increase of 1 unit on the Richter scale equals 10x the ground motion (displacement). And furthermore, increase of 1 unit on the Richter scale equals about 32x the destructive force (energy). See here.

So I made some new graphs showing total magnitude, total displacement, and total energy of all earthquakes in a given year.

Now, the “total destructive force” for all earthquakes in a single year is a very large, absolutely meaningless number. As is total ground motion. As is “total” magnitude on the Richter scale. It would be hard to relate these numbers to anything, let alone put them on the same graph. So here’s what I did:

I found the maximum for all 3 sets, and then graphed each set as a percentage of the maximum. This is why I am calling them “normalized” values on the graphs below. In this way, you can easily see the overall trends as well as the relationship between these 3 values. Just keep in mind that there is no “absolute” relationship between the lines, so if one goes above or below another that doesn’t mean anything. What is important is how they track each other following the trends.

Ok, enough of that. If you want the formulas for how I calculated the numbers, they are below the first graph.

First, the NEIC data:

USGS NEIC Earthquakes M ≥ 3 Normalized Total Forces

The blue line shows total magnitude (sum of magnitudes) for all quakes during a given year. (Probably a meaningless metric)

The green line shows total displacement (movement of the earth) for all quakes during a given year. This is calculated as ∑(10M) for each year.

The yellow line shows total energy (destructive power) for all quakes during a given year. This is calculated as ∑((101.5)M) for each year. This is probably the most important metric.

Now the Centennial data:

USGS Centennial Earthquakes M ≥ 5.5 Normalized Total Forces

Finally, the NEIC data restricted to M 5.0 and above, for better comparison with the Centennial data:

USGS NEIC Earthquakes M ≥ 5 Normalized Total Forces

Conclusion

As you can see, there is a lot a variation in the graphs, but there is also an overall constancy. I will refrain from any special interpretation here.

You can definitely see a slightly upward linear trend in the NEIC data, especially when we include quakes below M 5.0. This is probably due to the constant improvement in detection and reporting worldwide, which mostly results in a greater number of recorded small-magnitude quakes. This conclusion is also supported by the USGS’ own explanation.

It is much harder to see a trend in the Centennial dataset. It is a much more sparse dataset and covers a narrow range of magnitudes over a shorter time. Overall the linear trend here seems almost flat.

When we look at the force graphs, here again we can see a slight upward linear trend, especially in the NEIC dataset. The interesting thing to note here is that this trend is still visible even when we restrict ourselves to M 5.0 and higher. Why?

Probably somewhat due to more and better reporting, but if you compare the frequency and force graphs, you will notice that there have been a few more large earthquakes in the last 10 years or so, and because of the math, it makes a big difference.

The most significant real-world impact is probably represented by the yellow “energy” line, representing total destructive force. It peaked in 2004, almost entirely as a result of the Asian Tsunami quake of that year.

2008 had an unusually high number of small-magnitude earthquakes. This gives you peak magnitude and displacement totals in 2008, but yields only an average total destructive energy. 2008 is still the most unusual year in the data, IMHO.

The Centennial graphs show peaks in 1995 and 2000-2001. These look really big but keep in mind they are just normalized values. They correspond to the moderate bumps in 1995 and 2000-2001 on the NEIC graphs.

Also notice that the last datapoint on all the graphs is lower than it should be; the totals for 2002 (Centennial) and 2009 (NEIC) are incomplete. The Centennial data ended on April 1, so you could roughly estimate the correct value by multiplying by 4. I believe The NEIC data is current through December 1, so it’s about 92% there.

If anyone wants a copy of my dataset, shoot me an email.

— Kevin H. Patterson

Comment [2]

---

Using the Yamaha MOTIF XS with Snow Leopard · 108 days ago

I recently upgraded my laptop to Mac OS X 10.6 Snow Leopard, and discovered that my mLAN driver (which connects my system to the XS 8 over firewire) no longer worked. (This would also apply to the MOTIF XS 6 or 7 with the optional firewire card.)

It appears that Yamaha is replacing the mLAN driver with something called the “Yamaha Steinberg FW Driver”. I don’t know if the new driver does everything that mLAN does, but I just need to connect my DAW with this keyboard for now.

Here’s what I did to get things working:

Warning: The firmware updates on this page can permanently damage your MOTIF if Yamaha’s instructions are not followed carefully, or if the update process is interrupted by power loss, cable disconnection, etc. Make sure everything is plugged into a UPS and don’t do anything stupid. The author will not he held responsible for anything that happens following this guide. Proceed at your own risk.

1. Make sure your MOTIF XS OS Firmware is at least 1.10 or later before starting.

As of the time of this writing, the latest available OS firmware is 1.55, which you can download here under the title “MOTIF XS OS Updater V1.55”

Please follow the directions carefully if you need to update your firmware. (If your firmware is 1.10 or later, you don’t need to upgrade to 1.55 at this step.)

2. Upgrade your MOTIF XS Firewire firmware to 1.07 or later. This is necessary to support the new “Yamaha Steinberg FW Driver”. This updater can be found here under the title “IEEE1394 Firmware Updater Ver.1.07 for Mac OS X”

Please follow the directions carefully if you need to update. The updater application will show you what version you have before you start the update.

3. After the Firewire firmware update has successfully installed and you have restarted your MOTIF, you need to change a setting on the MOTIF. This can be accessed by pressing [UTILITY], [F1 / General], [SF4 / AutoLoad]. Change the “IEEE1394 Driver” setting to “FW”. You will need to press [STORE] and then restart the MOTIF.

4. Install the “Yamaha Steinberg FW Driver” software, which can be downloaded here under the title “Yamaha Steinberg FW Driver V1.1.0 for Mac OS X”.

5. It’s probably a good idea to restart your Mac. The new driver has a control application located in /Applications/Yamaha.

At this point the basic functionality should be working. You may also want to download updates to Yamaha’s utility applications, like Studio Manager, XS Editor, Steinberg DAW Extensions, etc.

This would also be a logical time to consider upgrading the MOTIF XS OS firmware to the latest version, as described in step 1. Remember to back up ALL the user content on the MOTIF to a USB drive first!

— Kevin H. Patterson

Comment

---

BIOS-Kill · 754 days ago

Don't try this at home...

kevpattkhp: hey
kevpattkhp: HEY!!!
kevpattkhp: hey, when you see this, I have a story to tell you that will blow your mind
kevpattkhp: brb
adamreiswig: ok
adamreiswig: blow my mind :-)
adamreiswig: kaboom, they set us up the bomb :-):-)
kevpattkhp: you there?
kevpattkhp: so this time I set myself up the bomb
adamreiswig: yeah, what happened?
kevpattkhp: this has to be the all-time stupidest thing I've ever done to a computer
kevpattkhp: This even tops you plugging in the power cable to my HD upside down...
adamreiswig: oooh, now you have my attention :-)
adamreiswig: :hahahahaha
kevpattkhp: remember I told you I was contemplating flashing a beta bios?
adamreiswig: oh brother, I warned you !!!!!
kevpattkhp: yeah, you did
adamreiswig: moron :-)
kevpattkhp: well I had 2 different bioses
kevpattkhp: 1.02 (non-beta) and 1.02b (beta)
kevpattkhp: my system was running 1.01
kevpattkhp: I had downloaded the 2 new ones from tyan's ftp site.
kevpattkhp: anyway...
kevpattkhp: I took your advice and decided not to use the beta version
adamreiswig: ok
kevpattkhp: so I got myself a Win98/DOS boot disk and proceeded to flash
kevpattkhp: while the flash program was reading the rom file from the disk I noticed a model number in the file name ... 2875
kevpattkhp: I thought "that
adamreiswig: uh huh
kevpattkhp: is strange... I thought my mobo was a 2885"
kevpattkhp: and then the flash procedure was done
kevpattkhp: and my system rebooted
kevpattkhp: for the very last time
kevpattkhp: :-(
adamreiswig: oh no
kevpattkhp: I STUPID DOWNLOADED THE WRONG MORON FLASH FILE FOR SOME OTHER MTOHERBOARD!!!
adamreiswig: oh my goodness
adamreiswig: no way of fixin it?
kevpattkhp: a visit back to tyan's site (with my laptop) confirmed this
kevpattkhp: there is no 1.02 for my mobo, only 1.01
adamreiswig: oh brother
kevpattkhp: Anyway, it would not do anything. No beeps, buzzes, boot, video, sound, nothing. Just a power led and total utter silence.
kevpattkhp: MY 500 DOLLAR MOTHERBOARD COMPLETELY TOAST!!!
adamreiswig: surely, tyan can help or something
kevpattkhp: now does that top you frying my HD or what?
adamreiswig: yeah, that stupid hard drive only cost me around $40
kevpattkhp: well I went to their support site and they had 2 outfits that will sell you a new BIOS chip
kevpattkhp: cost is about $30... not too bad I guess, except I would want it shipped overnight cause I wanted to bring my system out this weekend.
kevpattkhp: So that would be more like $50
kevpattkhp: but then I started thinking...
kevpattkhp: this is what will blow your mind
kevpattkhp: btw, did have you ever done a bad flash?
adamreiswig: nope
kevpattkhp: well I made a home-brew chip puller out of a paperclip, and pulled the bad bios chip off my mobo
adamreiswig: yeah?
kevpattkhp: and I thought to myself "how can I reprogram this thing"
adamreiswig: oh brother
kevpattkhp: Then it came to me.
adamreiswig: only you :-)
kevpattkhp: The student Casey, just built an AthlonFX-51 system that is somewhat similar to mine
adamreiswig: same mb?
kevpattkhp: I know the BIOSes look almost the same and they are both Opteron-style systems
kevpattkhp: no different mobo.
adamreiswig: please don't tell me you killed his too??!?!?!?!?
kevpattkhp: Mine is Tyan K8W dual-opteron with AMD8000 chipset, his is ASUS SK8N single-opteron with nForce3 chipset
kevpattkhp: hahaha
kevpattkhp: the "midas touch"
kevpattkhp: This was my plan:
adamreiswig: oh.....my.....goodness.....!!!!!!!!!!!!!
kevpattkhp: His bios chip was probably very similar to mine
adamreiswig: this has got to be your finest hour hahahahahahahahahahaha
kevpattkhp: I could reprogram mine in his system, except his system would of course not boot up with my chip installed
kevpattkhp: so this is what I did:
kevpattkhp: we booted up his system normally (untouched) to my boot floppy
kevpattkhp: THEN, with the power on, we PULLED OUT his BIOS chip and popped mine in
kevpattkhp: and then I ran the flash program off the floppy
kevpattkhp: :-)
kevpattkhp: unbelievably enough, the flash program seemed to work properly, and rebooted his system when it was donw
adamreiswig: you are such an idiot, imho
kevpattkhp: of course I killed the power immediately so his system would not try to boot off my bios
kevpattkhp: then put his back in and powered it on...
kevpattkhp: (smoke test)
adamreiswig: holy cow
kevpattkhp: well it seemed to start up normal (with his chip back in place) except it said "BIOS Checksum incorrect"
kevpattkhp: and it was trying to do some auto-recovery flash procedure asking for a floppy....
kevpattkhp: I was starting to get scared, but honestly, I was glad it was working at all
kevpattkhp: anyway I couldn't see how his flash chip could have been damaged (other than pulling it from his mobo with the power on)
kevpattkhp: so we power-cycled the system a couple times
kevpattkhp: and I re-seated the chip in its socket
kevpattkhp: then it went back to normal and seemed to work fine
kevpattkhp: just for good measure, we flashed his bios with a new CORRECT version for his motherboard and loaded new CMOS settings
kevpattkhp: he booted into windows and everything seemed normal
kevpattkhp: what a relief
kevpattkhp: anyway... so now I had my old chip which MIGHT be correctly programmed for my system again...
adamreiswig: you are soooo unbelieveable :-)
kevpattkhp: so I took it back to my house and popped it into my mobo
adamreiswig: why is your pc answeing the phone??

— Kevin H. Patterson

Comment

---

First Post · 755 days ago

Welcome to my new site. It’s based on TextPattern, plus extra goodness.

— Kevin H. Patterson

Comment [1]

---