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-35902: Remove getAmpImage #419

Merged
merged 1 commit into from Sep 14, 2022
Merged

DM-35902: Remove getAmpImage #419

merged 1 commit into from Sep 14, 2022

Conversation

timj
Copy link
Member

@timj timj commented Aug 15, 2022

Gen2-specific.

Copy link
Member

@RobertLuptonTheGood RobertLuptonTheGood left a comment

Choose a reason for hiding this comment

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

Looks good, given that gen3 addresses this natively.

However, I am worried that there may be client code (e.g. camera team notebooks) that use this API. Should we provide a helper function, or at least a function that says, "Please use butler.get(..., amp=1)" (or whatever the syntax is)?

@timj
Copy link
Member Author

timj commented Sep 1, 2022

If any existing camera notebooks are using this then those notebooks will be breaking long before they get to this part of the code. They can no longer access a gen2 butler so they can't be at the point where they have anything to pass to this function. I don't think adding a message in this function will ever trigger for existing notebooks.

Gen2-specific.
@timj timj merged commit 53e9e7f into main Sep 14, 2022
@timj timj deleted the tickets/DM-35902 branch September 14, 2022 19:16
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