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

feat: add basic move-to command to protocol engine #6763

Closed
1 task
mcous opened this issue Oct 14, 2020 · 0 comments · Fixed by #6943
Closed
1 task

feat: add basic move-to command to protocol engine #6763

mcous opened this issue Oct 14, 2020 · 0 comments · Fixed by #6943
Assignees
Labels
api Affects the `api` project feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping. robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience).
Milestone

Comments

@mcous
Copy link
Contributor

mcous commented Oct 14, 2020

overview

As part of basic pipetting over HTTP, the protocol engine should have support for a very basic "move to" command that:

  • Takes a pipette, labware, and well references
  • Moves the pipette to that well

This functionality will serve as a base for basic tip and liquid handling commands.

out of scope

  • Moving to locations other than the top center of a well

acceptance criteria

  • Protocol engine / live protocol session accepts a "move to" command

implementation details

  • Translate command request + state into existing Deck, Labware (geometry/impl), and Well (impl) objects
  • Add state to track current Location for future moves
  • Pass those object to existing motion planning utilities
  • Call HC correctly based on required movements
@mcous mcous added this to the CPX Sprint 20 milestone Oct 14, 2020
@mcous mcous added api Affects the `api` project robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience). feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping. labels Oct 14, 2020
@mcous mcous self-assigned this Oct 14, 2020
@mcous mcous modified the milestones: CPX Sprint 20, CPX Sprint 21 Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Affects the `api` project feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping. robot-svcs Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant