-
Notifications
You must be signed in to change notification settings - Fork 5
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
Aurora Pipeline Fails when NCEDC is down #159
Comments
This happened again on April 23 at 0900 Pacific time. The error is:
I have attached the hz data from PKD for the time interval that we use for the tests ... @timronan Can you or Laura look at adding this hz data to the IRIS archive? Then we can set up the tests to use IRIS (or try NCEDC and catch exception use IRIS). |
in tests/parkfield/ calling This file could actually be used as a source of data and metadata that we could push to IRIS, see issue 99 in mth5: |
Here's a new one, Sept 2, 2022: Client(base_url="NCEDC")
|
The lxml error is due to NCEDC changing their urls. See Issue 3134 https://github.com/obspy/obspy/issues/3134 |
This does not solve the larger issue, but it is intended to allow all tests to pass on github when PKD and SAO are unavailable due to NCEDC communications issues. [Issue(s): #159]
Here is a new one again Dec 2022
Note the The first time through is in the After
This metadata update is what triggers the failure, because after the metadata update: I followed the trail for awhile, and the error occurs when an auxiliary channel is encountered...
|
Regarding the second flavor of failure, ... this might be related to the obspy version. Only a month after v1.3.1 was released, out popped v1.4, November 2022. This version requires python>=3.8. It is not clear the value of maintaining v3.7 compatibility. In any case, to fix the v3.7 issue, one need only replace the kwarg: This argument is passed as To reproduce the error:
but replacing with
works. This is discussed in comment by alexhutko. To fix the py38 issue, one only needs to be using obspy v1.4 |
- [x] simplify FDSNDatasetConfig so it doesn't need additional methods from xml_sandbox. - [x] Drop methods from xml_sandbox now in FDSNDatasetConfig - [x] rename FDSNDatasetConfig to FDSNDataset - [x] Place client method in FDSNDataset - [x] move describe_inventory_stages from xml_sandbox to inventory_review - [x] tidy comments in make_mth5_helpers Issues: [#159]
Now that these tests are working again, there are a couple of things that can be done to simplify the parkfield tests:
|
- replaced all pkd_test_00 with pkd_sao_test_00 - result is that there is only one h5 file built for parkfield tests [Issue(s): #159]
- Added ensure_h5_exists() method to make_parkfield_mth5 - Deprecated config_path from ConfigCreator() - removed any references to config_path [Issue(s): #159]
I pushed an h5 of the combined PKD and SAO data to When this is done, I suggest that the making of the PKD data, when using IRIS be done using make_mth5, instead of the NCEDC kluge we have implemented to work around their non-FDSN complient nomenclature. |
Parkfield tests fail on gitactions runner because the data and metadata cannot be called when NCEDC is suffering an outage.
First observed on 17 Mar, 2022.
Since NCEDC is not a stakeholder at this point, we cannot expect them to be concerned about this issue.
We could:
The text was updated successfully, but these errors were encountered: