Skip to content
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

DM-37785: Document need for a skymap constraint in certain steps. #55

Merged
merged 1 commit into from
Feb 15, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 6 additions & 3 deletions ingredients/LSSTCam-imSim/DRP.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,12 @@ subsets:
Tasks that can be run together, but only after the 'step1'.

This is a mix of visit-level, tract-level, and collection-level tasks
that must not be run with any data query constraints other than
instrument. For example, running with 'tract' (and 'patch') constraints
will select partial visits that overlap that region.
that must be run with a skymap data query constraint only (an instrument
constraint is fine, but generally unneccessary). For example, running
with 'tract' (and 'patch') constraints will select partial visits that
overlap that region. A skymap constraint is necessary to prevent
isolatedStarAssociation from producing results for all skymaps in the
data repository.

Visit-level tasks include consolidateSourceTable, consolidateVisitSummary,
finalizeCharacterization, updateVisitSummary.
Expand Down
10 changes: 7 additions & 3 deletions pipelines/HSC/DRP-RC2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -93,9 +93,13 @@ subsets:
- isolatedStarAssociation
description: |
Global tasks: This is a mix of visit-level and tract-level tasks that
must not be run with data query constraints other than instrument. This
only works with small to medium jobs. Use DRP-Prod for large production
subsets.
must be run with a skymap data query constraint only (an instrument
constraint is fine, but generally unneccessary). For example, running
with 'tract' (and 'patch') constraints will select partial visits that
overlap that region. A skymap constraint is necessary to prevent
isolatedStarAssociation from producing results for all skymaps in the
data repository. This only works with small to medium jobs. Use DRP-Prod
for large production subsets.

skyCorr requires full visits, and 'tract' and 'patch'
constraints will always select partial visits that overlap that region.
Expand Down