-
Notifications
You must be signed in to change notification settings - Fork 1
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
tickets/DM-41840: Implement new detection tasks #100
Conversation
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.
See individual comments.
|
||
peaks = cT.Input( | ||
doc="Catalog of detected peak positions", | ||
name="{inputCoaddName}_coadd_multiband_peaks", |
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 this in anticipation of RFC-1049? I debated this myself; it might be premature to move to full snake case before it's implemented and deepCoadd
changes.
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 think it's fine to do this now. Jim seemed to give his support to this naming scheme: https://lsstc.slack.com/archives/CAVQQ6SBX/p1726691030465659?thread_ts=1726688938.272269&cid=CAVQQ6SBX Besides, I don't see the need to create one more thing that needs to be changed shortly anyway.
No description provided.