Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:4
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
https://lsstc.slack.com/archives/C2JPMCF5X/p1633479166053600v
While debugging a draft of DM-32029 wherein a faro pipeline was included in obs_subaru. The problem was that not all the tasks were excluded from the pipeline in ci_hsc_gen3. The symptom was the cryptic:
RuntimeError: 2 dataset(s) of type ‘matchedCatalogTract’ was/were present in a previous query, but could not be found now.This is either a logic bug in QuantumGraph generation or the input collections have been modified since QuantumGraph generation began
|
Can't count on DM-32029 to be done, so To reproduce
In obs_subaru:
Add $FARO_DIR/pipelines/metrics_pipeline_jointcal_fgcm.yaml to the import list.
And add an incomplete subset named `faro`. If you don't see AM1_info in the list, then it's incomplete.
e.g.: https://github.com/lsst/obs_subaru/blob/tickets/DM-32029/pipelines/DRP.yaml
in ci_hsc_gen3: add faro to the exclude list:
+++ b/pipelines/DRP.yaml
|
@@ -6,6 +6,8 @@ imports:
|
- fgcm
|
# Don't run jointcal here...
|
- jointcal
|
+ # Exclude faro because the dataset is not sufficient for most faro metrics.
|
+ - faro
|
and run ci_hsc_gen3
I'm just going to keep posting mistakes that trigger it because Jim Bosch and Nate Lust asked for ways to trigger it.
I'm sure there's a minimal how to reproduce, but I don't have time to make one