kkappler

In both fdsn data and synthetic data (both built in aurora) the v020 files are ~3x larger than v010. Channel summaries look the same to first order 57M Aug 4...

There should not be any aurora dependencies on the synthetic dataset originally from EMTF that is used for testing and validation in aurora. Therefore this method could be moved to...

Opening in write mode basically flushes the data in the mth5, which makes it easy to make a mistakenly lose data you have saved on system.

run_summary

3

In the same way that mth5 has a channel_summary method, that returns a dataframe with info about each channel, it would be nice to have a lighter-weight version that only...

mt_code nomenclature definitions

4

**ex, ey, hx, hy vs e1, e2, h1, h2** Inside mth5/mth5/utils/fdsn_tools.py there are rules for assigning an "mt_code" to channels. This is called when we make channels from obspy in...

make_mth5 from atomic list of streams

3

Here is some rough pseudocode for a Requested Function: This is a conceptual sketch of a method that we would want to expand on in future. There are some classes...

This PR is about formalizing metadata structures for weights.

TLDR: I think this is being addressed in the pydantic upgrade underway, but wanted to document an issue I encountered while adding metadata about feature weighting during TF estimation. I...

This is why `test_aurora_processing.py` is failing in **mtpy** (tests/processing/aurora/test_aurora_processing.py) As a workaround I added the following lines to both `TestProcessRRCompare` and `TestProcessSingleStationCompare` in `mtpy-v2`. To make the test fail again,...