Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added a script to calculate the moment magnitude from the output of QM #145

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tmgreenfield1101
Copy link
Collaborator

What is the purpose of this Pull Request?

To add functionality to calculate moment magnitudes

Relevant Issues

none

Test cases

This doesn't alter the core code, but instead adds a new folder scripts where scripts and functionality can be easily added

  • [ 1] All examples run without any new warnings
  • [ 1] test_benchmarks.py reports all example tests pass

System details

macosx

Final checklist

  • [1 ] develop base branch selected?
  • [ 1] All tests still pass.
  • [1 ] Any new features or fixed regressions are covered by new tests.
  • [1 ] Any new or changed features are fully documented.
  • [1 ] Significant changes have been added to CHANGES.md.
  • [1 ] First time contributors have added your name to CONTRIBUTORS.md.

…uakeMigrate. The approach follows that of various Abercrombie papers. QM functions are used to remove the instrument response. Then a new package (mtspec) is used to calculate calculate the spectra around the pick times. A brune-type source function is fit to the spectra. Functions are included to convert the corner frequency, long-period spectra level and attenuation parameter (Q) into moment, moment magnitude, radius and stress drop. Everything is output to a csv file in the "locate" directory.

The script works and includes various options to customize the script. However, some functionality isn't implemented yet, but would be easy to add.
@hemmelig
Copy link
Member

hemmelig commented Feb 14, 2023

I have changed the PR to point at the master branch, rather than develop (which is out of sync right now).

@hemmelig hemmelig changed the base branch from development to master February 14, 2023 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants