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
#2525 introduced a change to the app so that all labware of the same type will be flagged as calibrated once one labware of that type has been calibrated. However, when a labware is sharing a slot with something else (share=True, e.g. if it is on a module) the API will separate it's offset from other labware of the same type. Accordingly, the app will flag the share=True labware as calibrated when it is, in fact, not.
The text was updated successfully, but these errors were encountered:
Possibly related: Placing a piece of labware on top of the aluminum blocks of the temp deck causes my_labware.bottom() to slam the tip into the bottom of the container incorrectly. This bug occurs even when the labware on the temp deck is the only one of its type used. This does not seem to be an issue if the labware is placed directly on the temp deck with no aluminum block.
@emernic that sounds like an unrelated problem. The app doesn't have anything to do with robot/labware positioning (it's making simple API calls).
I would recommend reaching out to the support team and verifying that your protocol and calibration procedure is correct or opening a separate ticket with a minimum reproduction protocol
overview
#2525 introduced a change to the app so that all labware of the same type will be flagged as calibrated once one labware of that type has been calibrated. However, when a labware is sharing a slot with something else (
share=True
, e.g. if it is on a module) the API will separate it's offset from other labware of the same type. Accordingly, the app will flag theshare=True
labware as calibrated when it is, in fact, not.The text was updated successfully, but these errors were encountered: