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.
Last reviewed: 2026-07-04
Executive Summary
Data acquisition systems synchronize, digitize, store, transmit, and quality-check sensor signals used in seismic, vibration, acoustic, and SHM workflows. This article has been expanded as an engineering resource for readers evaluating data acquisition systems concepts, instrumentation choices, and monitoring workflows. The discussion is educational and should be paired with project-specific review by qualified engineers, applicable codes, owner requirements, and equipment documentation.
Key Takeaways
- Define the engineering objective before selecting sensors, test equipment, trigger thresholds, or reporting workflows.
- Use calibrated instrumentation, documented installation practices, time synchronization, and traceable data handling where measurement quality matters.
- Interpret measured data in context: site conditions, structure type, noise environment, sampling rate, bandwidth, and boundary conditions all affect conclusions.
- Use authoritative references and project-specific criteria rather than relying on generic thresholds or unsupported performance claims.
Technical Explanation
In practical data acquisition systems work, the engineering system is more than a sensor or a test platform. A credible workflow includes the measurement objective, instrument selection, mounting or boundary conditions, sampling and timing strategy, data validation, event or response detection, engineering review, and reporting. Weakness in any part of that chain can reduce confidence in the final interpretation.
For monitoring applications, engineers should document sensor orientation, coupling, environmental exposure, dynamic range, frequency bandwidth, data logger configuration, clock synchronization, communications, and maintenance procedures. For testing applications, engineers should document input motion, fixture design, payload properties, control limits, safety interlocks, acceptance criteria, and post-test data review.
Engineering Applications
| Application | Engineering Question | Typical Evidence Needed |
|---|---|---|
| Research and education | How does a structure, component, or sensor respond under controlled conditions? | Test plan, calibrated data, input motion, boundary conditions, and repeatable observations. |
| Critical infrastructure | Is the asset response normal, changing, or potentially unsafe after an event? | Baseline data, event records, thresholds, inspection workflow, and engineering sign-off. |
| Industrial facilities | Can monitoring support operational continuity and response decisions? | Site-specific criteria, reliable telemetry, alarm logic, maintenance records, and documented procedures. |
People Also Ask
What should be specified before buying equipment?
Specify the measurement objective, frequency range, amplitude range, environment, data format, timing needs, installation constraints, reporting requirements, and applicable standards or owner criteria.
Why do references and standards matter?
They provide terminology, acceptance criteria, test methods, and documentation expectations. They do not replace engineering judgment, but they reduce ambiguity and make results easier to review.
How should data quality be checked?
Review calibration status, timing, clipping, sensor orientation, signal-to-noise ratio, environmental artifacts, data completeness, and whether the record supports the engineering decision being made.
Related QuakeLogic Resources
- How to Access and View Detected Events in SeisComP
- How to Download Waveform Data from SeisComP
- Safeguarding Seismic Instrumentation: A Guide to Power Surge Protection
- TTL vs RS232 vs RS485: Choosing the Right Communication Standard for SHM
- Related QuakeLogic products and technologies
- QuakeLogic Engineering Blog topic resources
References
Recommended Diagram or Download
Media placeholder: Add an original diagram showing the measurement chain from sensor or test platform to data acquisition, analysis, engineering interpretation, and reporting. Where this article becomes a buyer guide or application note, create a downloadable PDF version after engineering review.
Discuss a Monitoring or Testing Application
QuakeLogic supports seismic monitoring, earthquake early warning, structural health monitoring, infrasound monitoring, vibration monitoring, data acquisition, and shake table testing applications. For project-specific guidance, contact QuakeLogic with the asset type, measurement objective, site constraints, and required deliverables.
