Apps Part of Pocketlab

Pocketlab Seismograph (accelerometer CSV → peaks and events)

Peak and RMS shaking, a seismogram trace and STA/LTA events from an accelerometer recording.

One row per sample: time, then 1–3 acceleration columns; header optional. Up to 200 000 rows.

Used when no file is uploaded. Comma, semicolon, tab or space separated — the CSV the Pocketlab recorders download fits.

More options

An event starts when the 0.5 s average of the shaking is this many times the 10 s average; it ends below 1.5.

Try an example: ·

More about this tool

How it works

Turns an accelerometer recording from a phone lying on a table or floor into a seismogram: peak and RMS acceleration after removing gravity, the strongest axis and a list of events (footsteps, a slammed door, a passing truck) found by the classic STA/LTA trigger. Same engine as the Pocketlab seismograph.

  • Each axis' mean is removed (gravity, tilt and sensor offset); the dynamic acceleration is the magnitude of what remains. Peak and RMS refer to it.
  • Events use the STA/LTA trigger of seismology: the short-term average (0.5 s) of the squared acceleration is divided by the long-term average (10 s). An event starts when the ratio reaches the trigger level and ends when it drops below 1.5; the long-term average is frozen during an event. The first 10 s only fill the long window.
  • The trace is the largest |a| per time bucket (at most 800 points), so short knocks stay visible.

A phone is not a seismometer: it is far less sensitive, its sample rate is irregular and it cannot measure earthquake magnitudes. Use it to compare shaking at home, never for safety decisions.

Sources

Part of Pocketlab

  • Pocketlab Phone sensor instruments & measurement log

    Your phone as 14 pocket instruments, with a measurement log you can export and share.

    Open Pocketlab

Related tools

How to use the Pocketlab Seismograph

Turn an accelerometer recording into a seismogram with peak and RMS shaking and a list of events found by the STA/LTA trigger.

What it is for

A phone lying on a table or floor feels footsteps, a slammed door, a washing machine in spin or a truck passing outside. This tool turns an accelerometer recording of that into a seismogram. It gives the strongest shaking (peak acceleration), the average shaking (RMS), the strongest axis and a list of events: the moments when something happened.

It is the same analysis as the seismograph in Pocketlab. Record there, download the CSV and you can look at it again here, for example with a different trigger.

A phone is not a seismometer. It can tell you when and how strongly the floor shook, not the magnitude of an earthquake or whether a building is safe.

Worked example

The tool's example is 40 seconds of a phone lying on a table at 50 samples a second: footsteps nearby, then a slammed door. With the default Trigger ratio of 3 the tool reports:

  • Peak acceleration: 0.938 m/s² (0.0956 g) at 30.0 s
  • RMS acceleration: 0.048 m/s²
  • Events: 2

The events table lists the first event from 13.10 s to 13.62 s with a peak of 0.060 m/s² (the footsteps) and the second from 30.02 s to 31.22 s with 0.938 m/s² (the door).

With the trigger ratio raised to 6, only the door remains: 1 event, 30.02 s to 31.22 s. The peak and RMS values stay the same, because the trigger only decides what counts as an event.

How to read the result

Peak acceleration is the largest shaking in any direction after gravity has been removed, also given in g. RMS is the typical level over the whole recording — compare it between two recordings made the same way.

The seismogram chart shows the shaking over time. The per-axis peaks tell you the direction: with the phone flat, a large z (up–down) peak points to footsteps or a knock on the table, large x or y peaks to sideways rocking.

Each event has a start, an end and its own peak. An event starts when the average shaking over half a second rises to the trigger ratio times the average over ten seconds. It ends when that ratio falls below 1.5. Seismologists use this STA/LTA trigger to pick earthquakes out of background noise.

Tips and common mistakes

  • Lay the phone flat on a hard surface and do not touch it while it records. Taps on the screen are the strongest events you will see.
  • The first ten seconds only build the long-term average, so nothing in them is reported as an event. Start the recording early.
  • Lower the trigger ratio (2 to 2.5) to catch weak events, raise it (5 or more) when steady machine noise makes too many.
  • Use g as the acceleration unit when your logger writes values near 1.0 instead of 9.8.
  • Compare RMS values only between recordings with the same phone in the same place; phones and surfaces differ a lot.
  • For the frequency of a machine's vibration, use the Pocketlab vibration spectrum on the same file.

FAQ

Can my phone detect earthquakes?

Strong nearby earthquakes, yes — the shaking shows up like any other event. But phones are far less sensitive than seismometers and their own noise hides weak or distant quakes. Rely on official seismic services, not this tool.

Why is gravity not in the numbers?

The mean of each axis is removed before anything is computed. What remains is the shaking itself, whichever way the phone lies.

What sample rate do I need?

Most phones record 50 to 200 samples a second, which is plenty for footsteps and doors. At low rates short knocks can fall between two samples and be missed.

Which file format does it read?

A CSV or text file with a time column and one to three acceleration columns. The Pocketlab instruments write time_s,ax,ay,az.

Guide last updated:

For scripts and AI agents

  • JSON API: POST https://pocketlabseismograph.usefulweb.app/api/v1/calculate (same calculation as this page)
  • Interface description: OpenAPI 3.1 · AI guide: llms.txt
  • MCP server (Streamable HTTP): https://pocketlabseismograph.usefulweb.app/mcp · tool name pocketlab_seismograph
Example request
curl -s -X POST https://pocketlabseismograph.usefulweb.app/api/v1/calculate \
  -H 'content-type: application/json' \
  -d '{…see OpenAPI examples…}'
Feedback · ideas & bug reports welcome