You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(api): better names for liquid probe commands (#15578)
<!--
Thanks for taking the time to open a pull request! Please make sure
you've read the "Opening Pull Requests" section of our Contributing
Guide:
https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests
To ensure your code is reviewed quickly and thoroughly, please fill out
the sections below to the best of your ability!
-->
# Overview
Edit detect_liquid_presence, require_liquid_presence, and
measure_liquid_height as per the standup today.
Change instrument_context tests to check for the right
error(LiquidNotFoundError)
Split find_liquid_level into two functions: liquid_probe_with_recovery
and liquid_probe_without_recovery
<!--
Use this section to describe your pull-request at a high level. If the
PR addresses any open issues, please tag the issues here.
-->
# Test Plan
<!--
Use this section to describe the steps that you took to test your Pull
Request.
If you did not perform any testing provide justification why.
OT-3 Developers: You should default to testing on actual physical
hardware.
Once again, if you did not perform testing against hardware, justify
why.
Note: It can be helpful to write a test plan before doing development
Example Test Plan (HTTP API Change)
- Verified that new optional argument `dance-party` causes the robot to
flash its lights, move the pipettes,
then home.
- Verified that when you omit the `dance-party` option the robot homes
normally
- Added protocol that uses `dance-party` argument to G-Code Testing
Suite
- Ran protocol that did not use `dance-party` argument and everything
was successful
- Added unit tests to validate that changes to pydantic model are
correct
-->
Added unit tests for liquid_probe_with_recovery and liquid_probe_without
recovery to test_instrument_core.py
Added unit tests for detect_liquid_presence, require_liquid_presence,
and measure_liquid_height to test_instrument_context.py
After the PR is merged, these API calls will be tested on the robot.
# Changelog
<!--
List out the changes to the code in this PR. Please try your best to
categorize your changes and describe what has changed and why.
Example changelog:
- Fixed app crash when trying to calibrate an illegal pipette
- Added state to API to track pipette usage
- Updated API docs to mention only two pipettes are supported
IMPORTANT: MAKE SURE ANY BREAKING CHANGES ARE PROPERLY COMMUNICATED
-->
# Review requests
<!--
Describe any requests for your reviewers here.
-->
Accidentally merged #15555 too soon, this is a continuation of that PR.
# Risk assessment
<!--
Carefully go over your pull request and look at the other parts of the
codebase it may affect. Look for the possibility, even if you think it's
small, that your change may affect some other part of the system - for
instance, changing return tip behavior in protocol may also change the
behavior of labware calibration.
Identify the other parts of the system your codebase may affect, so that
in addition to your own review and testing, other people who may not
have the system internalized as much as you can focus their attention
and testing there.
-->
Low: Since all the work was done in newly created functions, the risk
that it breaks existing code is minimal.
However, the new API calls still do need to be tested on a robot before
they can be used in other parts of the system.
0 commit comments