-
Notifications
You must be signed in to change notification settings - Fork 7
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-49175: Adjust configs/warnings for LSSTCam dense PTC #301
Changes from all commits
c3e5c01
b7d1204
110e5d1
e48d3b5
5b6b51d
b4f7ae3
85b7ff5
b8a5d89
0466ad9
8025bb2
d05be02
c5ff93a
6206bb9
4c6cf56
3ddcf84
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,10 +2,11 @@ pipelineYaml: "${CP_PIPE_DIR}/pipelines/${INSTRUMENT}/cpDefects.yaml" | |
|
||
project: "${TICKET}" | ||
campaign: "${TICKET}" | ||
submitPath: "${SCRATCH}/submit/{outputRun}" | ||
|
||
biasBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/biasBootstrapGen.$RERUN/run${BOOTSTRAP_RUN_NUMBER}" | ||
darkBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/darkBootstrapGen.$RERUN/run${BOOTSTRAP_RUN_NUMBER}" | ||
flatBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/flatBootstrapGen.$RERUN/run${BOOTSTRAP_RUN_NUMBER}" | ||
biasBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/biasBootstrapGen.${RERUN}/run${BOOTSTRAP_RUN_NUMBER}" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do any of the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that the braces are optional, but I meant to standardize on using it (like the quotes) in which case |
||
darkBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/darkBootstrapGen.${RERUN}/run${BOOTSTRAP_RUN_NUMBER}" | ||
flatBootstrapRun: "${USER_CALIB_PREFIX}$INSTRUMENT/calib/$TICKET/$TAG/flatBootstrapGen.${RERUN}/run${BOOTSTRAP_RUN_NUMBER}" | ||
|
||
payload: | ||
payloadName: "${INSTRUMENT}_${TICKET}_defects" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a two sentence explanation for this? My understanding was that this was needed for the PTC extract step to ensure that things get paired correctly, but I didn't think we needed it for ISR processing as well. Is it as simple as "makes it go faster"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having a short explanation of the clustering configs would be great, yes! But I do know that Jim Chiang told us "use these when doing any LSSTCam ISR tasks".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's there because ISR is so fast that HTCondor can't keep up when there are a lot of input exposures, and many quanta running in parallel. While other pipelines won't have as many input exposures as the PTC and linearizer pipelines, this is there to force it to cluster by exposure and specifically "slow it down" (it's not changing the total run time, just moving from many fast quanta to a small number of slower quanta). It also makes bps report faster since it only needs walk through less sub directories in submit/
I'll add a comment to the bps templates