Quickstart
A first session on the bundled sample dataset: set the project up from the
command line, then do the processing in the TUI. It assumes AIMBAT is
installed and on PATH.
Get the sample data
This downloads teleseismic recordings from several events into a sample-data/
directory. Aimbat Defaults covers how to change that
path.
Create a project
This creates aimbat.db in the current directory. All project state lives in
that one file. See Project for its location and how to
point AIMBAT at a different one.
Add the data
Preview the import first with --dry-run, then run it for real:
The shell expands the glob before AIMBAT runs. Each SAC file carries its station,
event, and initial pick in its header. --dry-run reports which stations,
events, and seismograms would be created without touching the database. Import
also deduplicates, so re-running the real command is safe. See
Adding Data for JSON sources, subset selection, and what
--dry-run catches.
Open the TUI
The rest of the work happens here:
- Project tab — select an event to work on.
- Live data tab — the seismogram table for that event. Adjust parameters, run ICCS, and inspect the alignment.
- Snapshots tab — save the parameter state, and export results from a snapshot.
Press ? at any point for the context-aware key bindings.
Next
- Using AIMBAT — the three interfaces and when to use each
- The ICCS Stack and Aligning with ICCS — the alignment loop in detail
- MCCC Alignment — the final pass for formal timing errors
- Exporting Results — the output format