Units handling and fdsn authenication
Created by: jrekoske-usgs
- Readers will now set the 'units_type', which indicates whether the instrument natively measures acceleration or velocity. This was to fix some problems related to tr.stats.standard.units. The StationTrace validator will now check that tr.stats.standard.units agrees with the remove_response provenance entry. tr.stats.standard.units is now used to describe the actual time series data, while tr.stats.standard.units_type is just based on the instrument code. In the readers, tr.stats.standard.units was left alone under the assumption that the remove_response provenance steps were set correctly. Closes #333 (closed)
- One thing to be careful of is that reading FDSN data (e.g. from a miniseed file and XML file) will always treat the data as raw counts, since the FDSN reader does not add a remove_response provenance entry.
- Add a config section for FDSN usernames and passwords, which are used by the FDSN Fetcher. Closes #328 (closed)
- Processing now modifies the process_level of traces.
- The broadband / strong motion test was moved up to best tests in tests/bin/gmprocess to test a larger part of the workflow.
- Fixed a bug in handling duplicates that caused a warning message to appear when traces weren't actually being removed.