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

Stdb updates #18

Merged
merged 4 commits into from
Dec 2, 2020
Merged

Stdb updates #18

merged 4 commits into from
Dec 2, 2020

Conversation

schaefferaj
Copy link
Collaborator

No description provided.

schaefferaj and others added 4 commits December 1, 2020 21:55
B/G: Some stdb can use long keys, which include the 2 char channel as part of the key name.
Currently, folder names were based on the stkey.

I added a -L --long-name option to all scripts. Default behaviour always names data folders NET.STN
instead of the key name. This means the default behaviour names the folders just NET.STN no matter
if a long key is used or not. If one specifies -L, then the full long key is used (if there are long
keys in the database).

As a result, if you have a station with both BH and HH data (non-overlapping in time for example), then
by creating a data base with long keys but running the rfpy scripts with short names (default, no -L),
then all RF data will be put in the same NET.STN folder, meaning that all rfpy scripts then
automatically merge the two component data together.

Signed-off-by: Andrew Schaeffer <aj.schaeffer@gmail.com>
A. Schaeffer 2020-12-02

Merge master updates into stdb. Mistakenly, this was not done before working on stdb_updates.
.
Major Update.

Backwards compatibility with stdb<=0.1.4 removed; now requires stdb>=0.2.0 for long key handling.

Updated all rfpy scripts to avoid duplicate processing of stations when long keys are used in the
database but short keys are used for station folder names (allows for BH and HH
at a single station to be combined in RF data processing).


Signed-off-by: Andrew Schaeffer <aj.schaeffer@gmail.com>
@paudetseis paudetseis merged commit 9be50d6 into master Dec 2, 2020
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.

2 participants