-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Glenn Thompson edited this page Nov 4, 2021
·
13 revisions
Welcome to the kitchensinkGT wiki!
Miscellaneous research codes, organized into projects with a common set of libraries. This is just where I actively work, before packing codes up for release when publishing papers, datasets etc.
- Automatic Reclassification of Volcano Seismic Signals from Soufrière Hills Volcano, Montserrat, 1996 to 2008 (AGU Fall Poster, 2021)
- Converting CALIPSO and SEA-CALIPSO data
- Recovering data from MVO analog seismic network
- Classifying events from the MVO analog seismic network
- Understanding Montserrat seismicity, 1992-1996 with VDAP
- ICEWEB: Reconstructing the spectrogram browser, reduced displacement plots, tremor alarm system, web-based configuration. And tools to plot SSAM, FFT and RSAM data too. Also look at my separate IceWebPy repository (perhaps incorporate it here?)
- MiamiLakes: Codes to automatically process events identified by Steve McNutt. Could convert these to PyMSEC and apply AAA.
- PyMSEC browser. A web browser for PyMSEC format, e.g. browse event seismograms, spectra, spectrograms, ESAM, event count plots etc.
- Energy-magnitude scale. Pull from PyMSEC.
- ASL. Pull from PyMSEC.
- RocketSeis. Codes for downloading, processing and analyzing rocket seismic events.
- SHAARC. Various non-sensitive codes that might be useful for this project.
- SteveKrupa. Includes useful workflow for quantifying PGD, PGV and PGA measurements and estimates from real and simulated earthquakes.
- Financial. Assorted personal finance tools, none of which contain any personal info.
- For seismic waveform files: MiniSEED is target format, though sometimes have to convert from Seislog, Seisan, Reftek RT130, Nanometrics Apollo, SUDS WVM and DMX, etc.
- For seismic event metadata: QuakeML should probably be target, but I tend to work with Seisan S-files (Nordic format), and CSS3.0 event, origin, arrival, assoc tables etc.
- For seismic instrument response metadata: StationML should probably be target, though I have to convert from Seisan response format, RESP files, dateless SEED, SAC pole-zero etc.
- CSV files are ideal for any waveform measurements made
- All seismic waveform data should be read into ObsPy Stream/Trace objects
- One or many seismic events should be read into ObsPy Catalog objects
- All seismic instrument response metadata should be read into ObsPy Inventory objects
- CSV files should be loaded into pandas DataFrame objects
- SeisComP3 Data Structure
- IRIS/PASSCAL BUD Structure
- Seisan continuous database
- CSS3.0 relational database
- Seisan event database
- CSS3.0 relational database
- PyMSEC format - Python Meta Seismic Event Catalog format PyMSEC might need a better name, e.g. SeismicPandas for the CSV file formats I define.