Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:
-
Story Points:7
-
Epic Link:
-
Sprint:AP S22-1 (December)
-
Team:Alert Production
-
Urgent?:No
Description
Remove all Gen 2 support from ap_verify. This includes:
- Running ap_verify_dataset_template/scripts/add_gen3_repo.py --drop-gen2 on each dataset repository, then deleting the script and all convertRepo_*.py configs.
- Updating all documentation of the ap_verify dataset format to be Gen 3 only.
- Removing the --gen2 and --gen3 command-line flags from the ap_verify scripts.
- Removing the Gen 2 ingest and pipeline execution code.
- Removing the metrics.py module entirely (including its command-line flags).
- Removing the Gen 2 metrics config files config/default_*_metrics.py.
- Reviewing the documentation to ensure there is no remaining Gen 2 content.
- Removing Gen 2 runs from Jenkins and alerts from SQuaSH.
- Removing Gen 2 display from SQuaSH.
This ticket does not cover removing Gen 2 support from the lsst.verify.MetricTask framework, as that might still be in use by other parties.
Attachments
Issue Links
- blocks
-
DM-28628 Actually adopt new calibs in ap_verify HiTS datasets
- In Progress
-
DM-33254 Remove Gen 2 support from ap_pipe
- Done
-
DM-33256 Remove Gen 2 support from verify
- Done
-
DM-33039 Re-examine how to handle dataset management scripts
- Done
- is blocked by
-
DM-29042 Remove support for old-style names in ap_verify
- Done
-
DM-29857 Create pure Gen 3 dataset management scripts for ap_verify datasets
- Done
- relates to
-
DM-20572 Remove "Generation 2" Middleware
- Done
-
DM-34237 Remove ap_verify dataset Gen 2 config files
- Done
Eric Bellm, Ian Sullivan, I just realized we never actually ticketed this work. Any objections to scheduling it for January? Note that this would include removing the "Gen 2 vs. Gen 3" display from SQuaSH.