groundmotion-processing icon indicating copy to clipboard operation
groundmotion-processing copied to clipboard

Parsing and processing ground motion data

Results 51 groundmotion-processing issues
Sort by recently updated
recently updated
newest added

## Difficulty of per-earthquake reports for large "projects" For gmprocess "projects" with hundreds of earthquakes, it is difficult to quickly review the data using the report and station maps that...

feature

Computing station metrics is one of the slowest steps when processing datasets (if you use multiple processes), because it runs on a single process. In looking to see how we...

bug

In the gmrecords subcommands, use the previously define global configuration -- rather than loading from the various sources. This is meant to simplify the process of loading the configuration. This...

In some cases, users may want to reprocess thier data with different parameters (ie comparing filter settings or differentiation methods) and gmprocess stores the config file that is read during...

feature

It is important that the SNR be normalized such that the result is not a function of the difference in duration between the signal and noise windows. Currently, we do...

bug

It is currently it's own program and so it re-implements the handling of projects and only supports system level projects. If we make it a subcommand it can more directly...

feature

**Is your feature request related to a problem? Please describe.** The dependency tree is vast. Just to read the h5 files that are produced requires a 2 GB conda environment....

feature

Lots of station have two sets of channels with different location codes for different sample rates. For example: http://ds.iris.edu/mda/NP/1582/ I think these data will be rejected by our current algorithms,...

feature