Engineering summary
A seven-step troubleshooting checklist for SeisComP installations where scautopick produces picks but scautoloc never forms events: config, modules, logs, metadata, thresholds, scolv and database.
In short: When SeisComP picks but no events reach the catalog, the usual cause is that the associator cannot satisfy its minimum pick and station requirements or a module is not running. Check global.cfg and the scautopick, scanloc and scautoloc configurations, confirm the three modules are started, read their logs under $SEISCOMP_ROOT/var/log, validate station metadata with seiscomp check, lower minimumTriggerStations or minThreshold, review picks in scolv, and verify database write permissions.
SeisComP is a powerful software package for seismological data acquisition, processing, and analysis. However, sometimes you might encounter an issue where SeisComP detects picks but no events appear in the catalog. This can be frustrating, but there are several steps you can take to troubleshoot and fix this issue.
1. Verify the SeisComP Configuration
Check global.cfg
The first step is to ensure your global.cfg configuration file is correctly set up. Pay close attention to parameters related to event detection and association. Here are some typical settings to verify:
- Picker Configuration:
picker.detecStream = ...- Event Detection Settings:
detector.triggerStations = ...
detector.minimumTriggerStations = ...- Associator Configuration:
associator.enable = trueCheck Module-Specific Configurations
Make sure the configurations for modules like scautopick, scanloc, and scautoloc are correctly set:
scautopick.cfg
scautopick.phaseName = P
scautopick.minThreshold = 3.0scanloc.cfg
scanloc.triggerSeconds = 10
scanloc.bindSeconds = 30scautoloc.cfg
scautoloc.associator.minimumPicksPerStation = 3
scautoloc.associator.minimumStationsPerEvent = 42. Ensure All Necessary Modules Are Running
Verify that the key SeisComP modules responsible for pick detection, association, and event creation are running. You can do this by starting the modules:
seiscomp start scautopick
seiscomp start scanloc
seiscomp start scautoloc3. Review Logs for Errors
Examine the log files for each module to identify any errors or warnings that might explain why events are not being created. Log files are typically found in the $SEISCOMP_ROOT/var/log directory.
Example:
less $SEISCOMP_ROOT/var/log/scautopick.log
less $SEISCOMP_ROOT/var/log/scanloc.log
less $SEISCOMP_ROOT/var/log/scautoloc.log4. Validate Network and Station Configuration
Ensure that all the seismic stations in your network are correctly configured and that their metadata is properly loaded into SeisComP. Use the seiscomp check command to validate the configuration:
seiscomp check5. Adjust Detection and Association Parameters
You may need to fine-tune the detection and association parameters to better suit your network and seismicity. For example, you might need to lower the thresholds or adjust the minimum number of stations required to form an event.
Example Adjustments:
- Lowering the minimum number of trigger stations:
detector.minimumTriggerStations = 3- Reducing the picker threshold:
scautopick.minThreshold = 2.56. Manually Review Picks
Use the Scolv tool to manually review picks and check if they are correctly detected and associated. This can help you identify any discrepancies or issues in the automated process.
Launch Scolv:
scolv7. Database Connection and Permissions
Ensure that SeisComP has the necessary permissions to write events to the database and that the database connection is configured correctly. Verify your database settings in global.cfg:
Example:
database.archive = mysql://user:password@host/database
database.events = mysql://user:password@host/databaseConclusion
By following these troubleshooting steps, you should be able to identify and fix the issue causing SeisComP to detect picks but not create events in the catalog. Proper configuration, module management, and parameter adjustments are key to ensuring that SeisComP operates effectively.
If you continue to experience issues, consider reaching out to SeisComP support or the user community for further assistance.
We hope you found this guide helpful. For more tips and guides on using SeisComP and other seismological tools, stay tuned to our blog. 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
- Verify global.cfg keys: picker.detecStream, detector.triggerStations, detector.minimumTriggerStations and associator.enable = true.
- Example settings: scautopick.minThreshold = 3.0, scanloc.triggerSeconds = 10, scanloc.bindSeconds = 30, scautoloc minimumPicksPerStation = 3, minimumStationsPerEvent = 4.
- Run seiscomp start scautopick, scanloc and scautoloc, then read each module's log in $SEISCOMP_ROOT/var/log.
- If events still do not form, lower detector.minimumTriggerStations to 3 and scautopick.minThreshold to 2.5, then review picks in scolv.
- Confirm database.archive and database.events in global.cfg point to a MySQL database SeisComP can write to.
Frequently Asked Questions
SeisComP detects picks but creates no events when the association stage fails. Common reasons are the associator being disabled in global.cfg, scanloc or scautoloc not running, too few stations meeting minimumTriggerStations or minimumStationsPerEvent, station metadata not loaded so picks cannot be located, or the database connection lacking write permission for events. Working through configuration, modules, logs, metadata and database settings in that order isolates the cause.
Three modules must be running: scautopick to generate picks from the detection streams, scanloc to cluster and associate picks, and scautoloc to locate and create the event. Start them with seiscomp start scautopick, seiscomp start scanloc and seiscomp start scautoloc, and confirm they stay up. If any one stops, picks continue to accumulate but no origins or events are written to the catalog.
To make SeisComP form events more readily, reduce the number of stations required and the pick threshold. In global.cfg set detector.minimumTriggerStations = 3 instead of a higher value, and in scautopick.cfg set scautopick.minThreshold = 2.5 instead of 3.0. Restart the modules afterward. Lower thresholds increase false picks, so review the resulting picks in scolv before accepting the new settings for routine operation.
SeisComP writes a log per module under $SEISCOMP_ROOT/var/log. Open them with less $SEISCOMP_ROOT/var/log/scautopick.log, scanloc.log and scautoloc.log. Errors about missing station inventory, failed database connections or association rejections usually appear there and explain why picks are not turning into events. Check the logs immediately after restarting the modules so the relevant messages are near the end of each file.
Open global.cfg and verify database.archive and database.events, which use the form mysql://user:password@host/database. The MySQL user must have write permission on the SeisComP schema, otherwise picks and origins are computed but never stored and the catalog stays empty. Run seiscomp check to validate the overall configuration and station metadata, and look for connection or permission errors in the module logs.
Related Articles
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.
Discover more from QuakeLogic
Subscribe to get the latest posts sent to your email.
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
- ISO documentation only when supported by source material
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.
