QuakeLogic Blog Archive

Acceleration or Velocity Data for Earthquake Monitoring?

Accelerometer and broadband seismometer recordings compared for earthquake monitoring

In short: Choose acceleration or velocity data based on what you need to detect: accelerometers suit near-field strong motion because they capture high frequencies and measure peak ground acceleration directly, while broadband seismometers recording velocity have lower noise and clearer low-frequency signals for small, distant or deep earthquakes. Many networks use both sensor types, and SeisComP can process either.

In earthquake monitoring, the choice between using acceleration data or velocity data for event detection depends on several factors, including the objectives of your monitoring system, the type of sensors available, and the specific characteristics of the seismic events you are interested in detecting. Both types of data have their own advantages and disadvantages. Let’s explore these in detail.

Acceleration Data

Pros

  1. High Sensitivity to Ground Shaking: Accelerometers are highly sensitive to ground shaking and can capture high-frequency components of seismic waves. This makes them ideal for detecting strong ground motions close to the epicenter of an earthquake.
  2. Broad Frequency Range: Acceleration data can cover a broad frequency range, allowing for the detection of both high-frequency and low-frequency seismic events.
  3. Capturing Peak Ground Acceleration (PGA): Accelerometers provide direct measurements of PGA, which is a crucial parameter for assessing the intensity of shaking and potential damage during an earthquake.
  4. Structural Health Monitoring: In addition to earthquake detection, acceleration data is valuable for structural health monitoring and assessing the dynamic response of buildings and infrastructure.

Cons

  1. Noise Sensitivity: Acceleration data can be more sensitive to noise, especially from human activities and environmental factors. This can make it challenging to distinguish between seismic events and noise.
  2. Complex Integration for Velocity: To derive velocity data from acceleration data, numerical integration is required. This process can introduce errors, especially at low frequencies, due to baseline drifts and noise.

Velocity Data

Pros

  1. Lower Noise Levels: Velocity data, typically recorded by broadband seismometers, generally has lower noise levels compared to acceleration data, making it easier to detect small and distant earthquakes.
  2. Clearer Low-Frequency Signals: Velocity data is better at capturing low-frequency signals, which are important for detecting and analyzing distant and deep earthquakes.
  3. Direct Use for Seismic Analysis: Many seismic analysis methods, such as spectral analysis and moment tensor inversion, are based on velocity data. This makes velocity data more straightforward to use in these applications.
  4. Continuous Monitoring: Velocity data is well-suited for continuous monitoring of seismic activity, as it provides a clearer picture of the overall seismic background.

Cons

  1. Limited High-Frequency Sensitivity: Velocity sensors are less sensitive to high-frequency components of ground motion, which can limit their effectiveness in detecting near-field, high-frequency seismic events.
  2. Additional Equipment Cost: Broadband seismometers that record velocity data are generally more expensive than accelerometers, which can increase the overall cost of the monitoring system.

Practical Considerations

Application-Specific Choices

  • Near-Field Earthquake Detection: If the primary goal is to detect and analyze strong ground motions near the earthquake source, accelerometers and acceleration data are preferable due to their high sensitivity to ground shaking and ability to capture high-frequency signals.
  • Far-Field Earthquake Detection: For detecting distant or deep earthquakes, broadband seismometers that record velocity data are more suitable due to their ability to capture low-frequency signals and their lower noise levels.
  • Comprehensive Monitoring Systems: Many advanced seismic monitoring systems use both types of sensors to take advantage of the strengths of each type of data. This hybrid approach provides a more complete picture of seismic activity and allows for robust event detection and analysis.

SeisComP Usage

SeisComP, a popular seismic monitoring software, can handle both acceleration and velocity data. The choice of which type of data to use with SeisComP depends on the specific goals of your monitoring system. SeisComP can process and integrate data from both types of sensors, allowing you to customize your setup based on your needs.

Conclusion

Both acceleration and velocity data have their own advantages and disadvantages for earthquake monitoring. The choice between the two should be based on the specific requirements of your monitoring system, including the type of seismic events you aim to detect, the proximity to the seismic source, and the available budget. By carefully considering these factors, you can design an effective seismic monitoring system that meets your needs.

For expert guidance and support, consider reaching out to QuakeLogic, your seismic monitoring expert. QuakeLogic provides advanced seismic monitoring solutions tailored to enhance the accuracy and efficiency of seismic data acquisition and analysis.


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 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

For more information about our products and services, please visit our website or contact our sales 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

  • Accelerometers: high sensitivity to strong shaking, broad frequency range, direct PGA, useful for structural health monitoring.
  • Accelerometer drawbacks: more sensitive to cultural noise; integrating to velocity introduces low-frequency errors from baseline drift.
  • Broadband seismometers (velocity): lower noise, clearer low-frequency signals, direct input to spectral analysis and moment tensor inversion.
  • Velocity drawbacks: weaker high-frequency sensitivity for near-field events and higher instrument cost.
  • Near-field monitoring favors accelerometers, far-field favors seismometers; hybrid networks and SeisComP handle both.

Frequently Asked Questions

When should I use an accelerometer instead of a seismometer for earthquake monitoring?

Use an accelerometer when the goal is to record strong ground motion close to the epicenter. Accelerometers are highly sensitive to ground shaking, capture high-frequency components, measure peak ground acceleration directly and are also valuable for structural health monitoring of buildings. Their trade-offs are greater sensitivity to human and environmental noise and errors when integrating to velocity at low frequencies.

Why is velocity data better for detecting distant earthquakes?

Velocity data from broadband seismometers has lower noise levels and captures low-frequency signals more clearly, which is what distant and deep earthquakes produce at a station. That makes small and far-field events easier to detect, and many seismic analysis methods such as spectral analysis and moment tensor inversion work directly on velocity records. The downsides are reduced high-frequency sensitivity and higher sensor cost.

Can SeisComP process both acceleration and velocity data?

Yes. SeisComP can ingest, process and integrate data from both accelerometers and velocity sensors, so a monitoring system can be configured around whichever data type, or both, best matches its objectives. The choice depends on the events you target, proximity to the source and budget rather than any software limitation.

What problems arise when integrating acceleration to velocity?

Deriving velocity from acceleration requires numerical integration, and that process amplifies low-frequency errors caused by baseline drift and noise in the accelerometer record. The result can be unreliable at long periods unless careful baseline correction and filtering are applied, which is one reason broadband seismometers are preferred when low-frequency content matters.

Should a seismic network use both accelerometers and seismometers?

Many advanced seismic monitoring systems deploy both sensor types to combine their strengths: accelerometers for strong near-field shaking and PGA, broadband seismometers for low-noise detection of small and distant events. This hybrid approach gives a more complete picture of seismic activity and more robust event detection, at the cost of additional equipment.

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.

Troubleshooting SeisComP: Picks Detected but No Events in the Catalog

SeisComP event list showing detected earthquakes with magnitude, location and origin time

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 = true

Check 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.0

scanloc.cfg

scanloc.triggerSeconds = 10
scanloc.bindSeconds = 30

scautoloc.cfg

scautoloc.associator.minimumPicksPerStation = 3
scautoloc.associator.minimumStationsPerEvent = 4

2. 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 scautoloc

3. 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.log

4. 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 check

5. 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.5

6. 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:

scolv

7. 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/database

Conclusion

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

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

Why does SeisComP detect picks but not create events?

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.

Which SeisComP modules must be running for events to appear in the catalog?

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.

How do I lower SeisComP detection thresholds to get more events?

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.

Where are the SeisComP log files for scautopick, scanloc and scautoloc?

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.

How do I check that SeisComP can write events to the database?

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.

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.