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-31580: Move consolidateDiaSourceTable to step6 #340

Merged
merged 1 commit into from Sep 1, 2021

Conversation

hsinfang
Copy link
Contributor

No description provided.

- drpAssociation
- drpDiaCalculation
description: >
Tasks that can be run together, but only after the 'step1', 'step2',
'step3', and 'step4' subsets

These DIA aggregation steps include both a visit-level aggregation
step consolidateDiaSourceTable and tract-level aggregation steps
These DIA aggregation steps include tract-level aggregation steps
drpAssociation and drpDiaCalculation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that the description isn't responsible for explaining which are tract-level and which are visit level, we don't have to call out all the tasks in this step. We should also include a recommendation on the data query: include tract. (It's less important here that people include tract in the data query because diaSources will only exist where a template was found that covers the detector, and "tract" was specified in step 3, but you'll still end up with a ragged edge and bad dia stats.

"This step includes tract-level aggregation Tasks. These should be run with explicit 'tract' constraints because otherwise quanta will be created for jobs with only partial visit coverage."

- consolidateDiaSourceTable
description: >
Tasks that can be run together, but only after the 'step1', 'step2',
'step3', and 'step4' subsets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

, and 'step5'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does consolidateDiaSourceTable depend on drpAssociation and drpDiaCalculation (step5)?
I thought these new step5 and step6 aren't blocking either other?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. They're not blocking each other at the moment.
I was thinking ahead to running forced phot on the diaObject centroids associated in step5.

Tasks that can be run together, but only after the 'step1', 'step2',
'step3', and 'step4' subsets

This DIA aggregation step includes a visit-level aggregation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can also simplify now that all tasks here will be visit level:
"This step includes visit-level, aggregation tasks. Running without..."

This makes step5 a clear per-tract step and
step6 a per-visit step.
@hsinfang hsinfang merged commit e12052c into master Sep 1, 2021
@hsinfang hsinfang deleted the tickets/DM-31580 branch September 1, 2021 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants