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.

Sign up for GitHub

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

Jump to bottom

Pipette Gen2: Alert User in Modal if Pipette Mismatched #3598

Closed
4 tasks
umbhau opened this issue Jun 17, 2019 · 1 comment
Closed
4 tasks

Pipette Gen2: Alert User in Modal if Pipette Mismatched #3598

umbhau opened this issue Jun 17, 2019 · 1 comment
Assignees
@b-cooper
Labels
app Affects the `app` project feature Ticket is a feature request / PR introduces a feature small
Milestone
Pipette Single Ge...

Comments

@umbhau
Copy link

umbhau commented Jun 17, 2019 •
edited
Loading

As a Run App user, I would like to be alerted if my pipettes are compatible but mismatched, so I can be aware of any behavioral differences.

Acceptance Criteria

  • Alert user in a modal if pipette attached to robot is different than pipette specified in protocol, but will work.
  • User should be informed that pipette on robot will perform with the same range as the pipette specified in the protocol
  • Recommend that user update the protocol
  • If robot and protocol both have two mismatched pipettes, list all pipette names in modal

Compatibility

The following pipettes are compatible

  • GEN2 P20 instead of GEN1 P10
  • GEN2 P300 instead of GEN1 P300
  • GEN2 P1000 instead of GEN1 P1000

Full list of compatibilities here:
https://docs.google.com/spreadsheets/d/1M6azQXZocWTqnEZDQ1Bpp9V1F9Fn86otdd4Go_LTIlQ/edit#gid=0

Design

Single mismatched pipette:
https://app.zeplin.io/project/5aa97729db58a2192f10d0d6/screen/5d0217088ac43c5dd4da8ef9

Two mismatched pipettes:
https://app.zeplin.io/project/5aa97729db58a2192f10d0d6/screen/5d0323f7ade24819ee212941
@umbhau umbhau added feature Ticket is a feature request / PR introduces a feature app Affects the `app` project labels Jun 17, 2019
@umbhau umbhau added this to the Pipette Gen2: DVT/Production milestone Jun 17, 2019
@b-cooper b-cooper self-assigned this Sep 3, 2019
@mcous mcous mentioned this issue Oct 7, 2019
Closed
2 tasks
b-cooper added a commit that referenced this issue Oct 28, 2019
@b-cooper
feat(app): allow inexact cross-generational pipette compatibility
cd1ac64 
If user possesses more modern hardware (pipettes) that can be used in the same spec ranges as older
hardware specified in a given protocol, allow running protocol, and highlight difference with
support article CTA.

Closes #3598
@b-cooper b-cooper mentioned this issue Oct 28, 2019
Merged
3 tasks
b-cooper added a commit that referenced this issue Oct 29, 2019
@b-cooper
feat(app): allow inexact cross-generational pipette compatibility (#4311
95dae6a 
)

If user possesses more modern hardware (pipettes) that can be used in the same spec ranges as older hardware specified in a given protocol, allow running protocol, and highlight difference with support article CTA.

Closes #3598
@btmorr
Copy link
Contributor

btmorr commented Oct 29, 2019

Merged into release branch, will be going into master and edge after release QA

@btmorr btmorr closed this as completed Oct 29, 2019
b-cooper added a commit that referenced this issue Oct 29, 2019
@b-cooper
feat(app): allow p1000 gen2 to fallback to specced p1000 gen1
202c271 
When a robot has an attached P1000 Single GEN2, the and the uploaded protocol has a P1000 Single
GEN1 attached, the app should accept the newer actual pipette as an inexact match. This mirrors the
case of P300 GEN2 -> P300 GEN1 and P20 GEN2 -> P10 GEN1.

re #3598
@b-cooper b-cooper mentioned this issue Oct 29, 2019
Merged
b-cooper added a commit that referenced this issue Oct 30, 2019
@b-cooper
feat(app): allow p1000 gen2 to fallback to specced p1000 gen1
679cf52 
When a robot has an attached P1000 Single GEN2, the and the uploaded protocol has a P1000 Single
GEN1 attached, the app should accept the newer actual pipette as an inexact match. This mirrors the
case of P300 GEN2 -> P300 GEN1 and P20 GEN2 -> P10 GEN1.

re #3598
sfoster1 pushed a commit that referenced this issue Oct 30, 2019
@b-cooper @sfoster1
feat(app): allow p1000 gen2 to fallback to specced p1000 gen1 (#4316)
0e33f65 
When a robot has an attached P1000 Single GEN2, the and the uploaded protocol has a P1000 Single
GEN1 attached, the app should accept the newer actual pipette as an inexact match. This mirrors the
case of P300 GEN2 -> P300 GEN1 and P20 GEN2 -> P10 GEN1.

re #3598
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@b-cooper b-cooper

Labels
app Affects the `app` project feature Ticket is a feature request / PR introduces a feature small
Projects
None yet
Milestone
Pipette Single Gen2: Production
Development

No branches or pull requests
4 participants
@umbhau @b-cooper @btmorr @Laura-Danielle