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-42220: Incorporate ModelPackage Butler datasets into Prompt Processing #164

Merged
merged 1 commit into from Feb 21, 2024

Conversation

kfindeisen
Copy link
Member

This PR removes the pre-emptive blocker that prevented rbClassify from being run in LATISS (specifically, Prompt Processing). It must be merged after lsst-dm/prompt_processing#125.

We now support rbClassify both in shared repos and in Prompt
Processing, so there's no reason not to run it.
class: lsst.ap.association.TransformDiaSourceCatalogTask
config:
# TODO: prompt_prototype does not yet support R/B analysis: DM-42220.
doIncludeReliability: False
Copy link
Contributor

Choose a reason for hiding this comment

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

Should pipelines/LSSTComCamSim/ApPipe.yaml be updated too, assuming the model can be added to /repo/ops-rehearsal-3-prep?

Copy link
Member Author

Choose a reason for hiding this comment

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

In theory, yes. But everyone seemed skeptical that that was a good idea. I can add it now, or save it for a later issue after we've seen how it works on LATISS-prod...

Copy link
Contributor

Choose a reason for hiding this comment

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

Leaving it for later is totally fine

@kfindeisen kfindeisen merged commit 36dc990 into main Feb 21, 2024
2 checks passed
@kfindeisen kfindeisen deleted the tickets/DM-42220 branch February 21, 2024 01:19
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