What it calculates
GMPS provides workflows for record preparation, scaling, spectral matching, pulse review and record comparison.
- Sa, Sv and Sd response spectra
- Target-spectrum scaling and spectral matching
- PGA, PGV, PGD and selected intensity measures
- Record quality checks and X/Y component pairing
Inputs
Import acceleration records with units and component information, then select or provide a target spectrum.
- AT2, FAC, ACC, ASC, TXT, DAT or CSV records
- X/Y component identity and acceleration units
- Target spectrum from TBDY 2018, Eurocode 8, ASCE 7-22 or a T-Sa file
- Baseline, filter and window settings for processing
Outputs and reports
Each mode presents processed records, spectral measures and selected comparison results in exportable formats.
- Acceleration, velocity and displacement histories plus Sa/Sv/Sd arrays
- Matched record, scale factor, misfit and convergence state
- Pulse and intensity measures, comparison plots and quality-control summary
- TXT, CSV, PNG, DOCX, ZIP and GMPS project exports
Validation
The GMPS validation document scopes results from different engines and workflows separately.
- Golden matching fixtures report commercial-resilience 6/6 and strict-parity 6/6 PASS, with repeat determinism below 1e-9.
- A Fortran smoke comparison reports spectrum PASS for 7 of 11 components and waveform PASS for 0 of 11; full waveform parity is not supported.
- External numerical comparisons for pulse and intensity measures are listed as pending in the documentation.
Who it is for
GMPS is for earthquake and structural engineers who process records and review design spectra or record matching.
- Engineers preparing ground-motion sets
- Technical teams reviewing response spectra and component results
Frequently asked questions
Why does acceleration-unit selection matter?
The unit scale affects every result. Documented scale values are 981 for cm/s² and 9.80665 for m/s².
Can the Shahi–Baker 2014 pulse method use one component?
The guide requires an X/Y component pair for this method.
How does a matched record behave outside the target band?
The guide says RSPMatch21 preserves out-of-band character more closely than REQPY; review results together with the target range.
Does it generate second-generation Eurocode 8 target spectra automatically?
The source documentation says the second-generation target curve must be supplied by the user.