Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:
-
Story Points:4
-
Epic Link:
-
Sprint:AP F20-4 (September), AP F20-5 (October)
-
Team:Alert Production
-
Urgent?:No
Description
The Gen 3 Middleware changes introduced in w_2020_39, particularly calibration collections, have broken the Gen 3 code in ap_verify (particularly how it handles repository abstraction). Iterate between updates to ap_verify_ci_hits2015 and ap_verify_ci_cosmos_pdr2 and to ap_verify's drivers until everything works in at least HSC.
Attachments
Issue Links
Activity
Since conversion of HiTS is blocked on DM-27018 but we can't run it in Gen 3 anyway (DM-23985), I'm pushing just the Cosmos dataset for now.
Jim Bosch, can you take a look at the code changes here? I don't think there's any point to looking at the Cosmos repository, as it's mostly file moves and a registry rewrite.
Krzysztof Findeisen
added a comment - Since conversion of HiTS is blocked on DM-27018 but we can't run it in Gen 3 anyway ( DM-23985 ), I'm pushing just the Cosmos dataset for now.
Jim Bosch , can you take a look at the code changes here? I don't think there's any point to looking at the Cosmos repository, as it's mostly file moves and a registry rewrite. 
This issue has scope-creeped quite a bit, as it turns out that
DM-26629broke some of the assumptions made by ap_verify, so it's not possible to test the repositories without substantial code changes. I've revised this issue accordingly.