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-29338: Incorporate Gen 3 crosstalk in HiTS runs #80
Conversation
Also rename the BPS template for running ApPipe.yaml
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.
Very helpful comments and descriptions throughout, thank you.
|
||
submitPath: ${PWD}/bps/{outCollection} | ||
computeSite: ncsapool | ||
# Memory allocated for each quantum, in MBs |
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.
Do you know the maximum that can be requested? If so, that would be good to include.
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.
I don't know, and therefore haven't included it 🙃 in practice, 2000-4000 is enough for most jobs, and bumping it up to 12000 or so is enough to get the occasional held job through.
# Note: keep timestamp in outCollection so you don't get a zillion sub-runs | ||
output : 'u/${USER}/{payloadName}' | ||
outCollection: '{output}/{timestamp}' | ||
# UPDATE THIS to specify what data to process |
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.
Perhaps expand this comment to include the additional keys beyond "band" and "instrument" that people might want to specify.
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.
This is a good suggestion, but I have empirically found that doing DECam runs with complex data queries can lead to an extremely lengthy (many days) query time. The example is intentionally minimal, but may be able to be a bit more instructive in the future when this is resolved.
The default ApPipe coadds have been goodSeeing since at least June 2021 (#80).
The default ApPipe coadds have been goodSeeing since at least June 2021 (#80).
The default ApPipe coadds have been goodSeeing since at least June 2021 (#80).
This PR updates a whole bunch of pipelines and adopts a new default AP Pipeline template name,
goodSeeing
(instead ofdeep
).