Merge pull request #80 from lsst/tickets/DM-38498

DM-38498: Document that certain faro steps now need a band constraint.

pipelines/HSC/DRP-RC2_subset.yaml

@@ -400,10 +400,11 @@ subsets:
       - skyObjectStd
     description: >
       Tasks that can be run together, but only after the 'step1', 'step2',
-      'step3', and 'step4' subsets
+      'step3', and 'step4' subsets.
       This step includes patch-level aggregation Tasks. These should be
-      run with explicit 'tract' constraints in the data query, otherwise
-      quanta will be created for jobs with only partial visit coverage.
+      run with explicit 'tract' and 'band' constraints in the data query, or
+      quanta will be created for jobs with only partial visit coverage and
+      for bands with no columns in the object table.
   nightlyStep8:
     subset:
       - validateObjectTableCore

pipelines/_ingredients/HSC/DRP.yaml

@@ -72,3 +72,8 @@ subsets:
     description: |
       Set of tract-level faro metrics to be run on coadd products. These use Object
       Tables which are available after consolidateObjectTable (step3) is run.
+
+      These must have a band constraint in their data query to avoid generating
+      quanta for bands that do not have columns in the object table, since
+      using an object table dataset as input does not provide information to
+      the middleware about which tasks went into making the object table.

pipelines/_ingredients/LSSTCam-imSim/DRP.yaml

@@ -300,3 +300,8 @@ subsets:
     description: |
       Set of tract-level faro metrics to be run on coadd products. These use Object
       Tables which are available after consolidateObjectTable (step3) is run.
+
+      These must have a band constraint in their data query to avoid generating
+      quanta for bands that do not have columns in the object table, since
+      using an object table dataset as input does not provide information to
+      the middleware about which tasks went into making the object table.