Engineering summary
Step-by-step: open the scolv GUI, run scevtls against the SeisComP database, or use the web interface to browse events, and find the catalog settings in global.cfg.
In short: To view detected events in SeisComP, launch the scolv GUI from a terminal and browse the event list, run seiscomp exec scevtls -d mysql://user:password@host/database on the command line, or open the SeisComP web interface if configured. The event catalog itself lives in a MySQL or PostgreSQL database whose connection strings are set by database.archive and database.events in global.cfg.
SeisComP is a widely used software package for seismological data acquisition, processing, and analysis. One of its core features is the detection and cataloging of seismic events. In this guide, we will walk you through the steps to access and view detected events in SeisComP, and explain where the event catalog is stored.
Viewing Detected Events in SeisComP
Using the SeisComP GUI (Scolv)
The Scolv tool in SeisComP is a graphical user interface designed for reviewing and manually locating seismic events. Here’s how you can use it:
- Launch Scolv:
- Open a terminal and type
scolvto start the application. - Alternatively, you can launch it from the SeisComP graphical interface if available.
- Browse Events:
- Once Scolv is open, you can browse through the list of detected events.
- Click on an event to view detailed information such as magnitude, location, and origin time.
Using the Command Line Interface
SeisComP provides powerful command-line tools for querying and managing events. Here’s an example of how to list events using the command line:
Open Terminal:
- Open a terminal window.
Run Query:
- Use the
seiscompcommand to list events. For example:bash seiscomp exec scevtls -d mysql://user:password@host/database - Replace the database connection string with your actual SeisComP database connection details.
Using the SeisComP Web Interface
If your SeisComP setup includes the web interface, you can access it via a web browser to view detected events:
Open Browser:
- Open your preferred web browser.
Navigate to SeisComP Web Interface:
- Enter the URL of your SeisComP web interface.
- Browse to the event list page where you can filter and view events.
Understanding the Event Catalog Location
The event catalog in SeisComP is typically stored in a database. The type and location of this database depend on your SeisComP configuration:
Database Configuration
SeisComP supports various database backends such as MySQL and PostgreSQL. The connection details are specified in the SeisComP configuration files, usually found in /etc/seiscomp3 or a similar directory.
Configuration File (global.cfg)
To find the database settings, open the global.cfg configuration file. Look for entries like these:
database.archive = mysql://user:password@host/database
database.events = mysql://user:password@host/database
These entries specify the connection details for the event catalog database.
Database Tables
Event information is stored in various tables within the database, including Event, Origin, Magnitude, and more.
Steps to Access the Event Catalog
Ensure SeisComP is Running
First, ensure that SeisComP services are running. You can start them using the following command:
seiscomp start
Accessing Scolv
To access Scolv, open a terminal and type:
scolv
Using the Command Line
To list events using the command line, run:
seiscomp exec scevtls -d mysql://user:password@host/database
Web Interface
Open your web browser and navigate to the SeisComP web interface URL, if configured.
Conclusion
By following these steps, you can easily view the events detected by SeisComP and understand where the event catalog is stored. Whether you prefer using the graphical interface, command line, or web interface, SeisComP provides flexible options to manage and review seismic event data.
Stay tuned for more tips and guides on using SeisComP and other seismological tools!
We hope you found this guide helpful. If you have any questions or need further assistance, feel free to reach out to our support team. Happy seismographing!
About QuakeLogic
QuakeLogic located in northern California is a leading provider of advanced seismic monitoring solutions, offering a range of products and services designed to enhance the accuracy and efficiency of seismic data acquisition and analysis. Our innovative technologies and expert support help organizations worldwide to better understand and mitigate the impacts of seismic events.
Contact Information
- Email: sales@quakelogic.net
- Phone: +1-916-899-0391
- WhatsApp: +1-650-353-8627
- Website: www.quakelogic.net
For more information about our products and services, please visit our website or contact our sale team. We are here to help you with all your seismic monitoring needs.
Thank you for choosing QuakeLogic. We look forward to assisting you with your seismic monitoring projects.
Key Takeaways
- Type scolv in a terminal to open the GUI and click an event to see magnitude, location and origin time.
- List events from the command line with: seiscomp exec scevtls -d mysql://user:password@host/database.
- The event catalog is stored in a MySQL or PostgreSQL database defined in global.cfg (database.archive and database.events).
- Event data is spread across database tables including Event, Origin and Magnitude.
- Start services with seiscomp start before querying; configuration usually lives under /etc/seiscomp3.
Frequently Asked Questions
Open a terminal and type scolv to start SeisComP's graphical event viewer, or launch it from the SeisComP GUI if one is installed. scolv shows the list of detected events; clicking an event displays its magnitude, location, depth and origin time and lets you review the waveforms and picks. Make sure the SeisComP services are running first with seiscomp start.
Use scevtls, the event list tool, through the seiscomp wrapper: seiscomp exec scevtls -d mysql://user:password@host/database. Replace the connection string with your own database credentials and host. scevtls prints event IDs from the catalog and accepts time-window options, which makes it useful for scripts and for checking the catalog on headless servers without a GUI.
SeisComP stores detected events in a relational database, typically MySQL or PostgreSQL, rather than in flat files. The connection details are defined in global.cfg, usually under /etc/seiscomp3 or the installation's etc directory, as database.archive and database.events entries of the form mysql://user:password@host/database. Inside the database, information is split across tables such as Event, Origin and Magnitude.
Yes, if your installation includes the SeisComP web interface. Open a browser, enter the URL of the web interface for your server and navigate to the event list page, where events can be filtered and inspected. The web interface reads from the same event database that scolv and scevtls use, so all three methods show the same catalog.
The most common causes are that the SeisComP services are not running, or that scolv is pointed at the wrong database. Run seiscomp start to bring up the services, then check that database.archive and database.events in global.cfg contain valid connection strings. If a scevtls query on the command line returns events but scolv does not, the GUI's messaging or database connection settings need to be corrected.
Related Articles
- How to Download Waveform Data from SeisComP
- Troubleshooting SeisComP With a Closely Spaced Station Network
- Understanding the Difference Between SCOLV and SCAUTOPICK in SeisComP
- Dataless SEED and Response Files in Seismology Explained
Need help with a project? QuakeLogic designs and supplies seismic monitoring, earthquake early warning, structural health monitoring, infrasound, and shake table systems. Browse QuakeLogic products or contact our engineering team with your site, structure, or test requirements.
Related
Discover more from QuakeLogic
Subscribe to get the latest posts sent to your email.
Reviewed by
QuakeLogic
Published by QuakeLogic engineers and seismic monitoring specialists. QuakeLogic designs earthquake early warning, structural health monitoring, infrasound, vibration monitoring, and shake table testing systems for infrastructure, research, public safety, and industrial engineering teams.
Topic cluster
Related engineering knowledge areas
- Structural Health MonitoringMonitoring for bridges, buildings, dams, tunnels, industrial facilities, and resilient infrastructure.
- Earthquake Early WarningOn-site detection, alerting workflows, seismic switches, and critical infrastructure warning systems.
- Seismic SensorsSeismometers, accelerometers, geophones, sensor selection, calibration, and field deployment.
- Infrasound MonitoringLow-frequency acoustic sensing for environmental noise, blast, UAV, volcano, and defense applications.
Definitions and references
Terms, standards, and source cues
- SHM: related to Structural Health Monitoring in this QuakeLogic knowledge cluster.
- damage detection: related to Structural Health Monitoring in this QuakeLogic knowledge cluster.
- earthquake early warning: related to Earthquake Early Warning in this QuakeLogic knowledge cluster.
- seismic switch: related to Earthquake Early Warning in this QuakeLogic knowledge cluster.
- seismometers: related to Seismic Sensors in this QuakeLogic knowledge cluster.
- accelerometers: related to Seismic Sensors in this QuakeLogic knowledge cluster.
- infrasound sensors: related to Infrasound Monitoring in this QuakeLogic knowledge cluster.
- low-frequency noise: related to Infrasound Monitoring in this QuakeLogic knowledge cluster.
Standards mentioned
- SeisComP documentation and configuration references
Next reading
Related engineering articles
Need project support?
Talk with QuakeLogic about monitoring, testing, or warning systems.
Get engineering guidance for seismic monitoring, structural health monitoring, infrasound, vibration, earthquake early warning, and shake table applications.

