-
Notifications
You must be signed in to change notification settings - Fork 178
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
fix(protocol-designer): auto-generate trashBin for flex if no pipetting commands exist #14857
Conversation
if ( | ||
!cutouts.includes(FLEX_TRASH_DEFAULT_SLOT) && | ||
!moduleSlots.includes('A3') | ||
) { | ||
return FLEX_TRASH_DEFAULT_SLOT | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now unnecessary logic since we are listing 'A3' as the first cutout in the array to map through
question when I added waste chute, export and import the protocol into pd, trash bin is generated but waste chute is gone. |
@koji oops that is definitely a bug! Thanks for catching it. |
@koji actually, if you did not add any waste chute commands, it is not a bug since we remove any staging area slot and waste chute that is not used in the protocol. But if you did add waste chute commands, it is a bug. |
@jerader I added waste chute from the initial setup wizard. |
one more question I compared two json. making pipetteTiprackAssignments item nested (adding left right |
@koji oh i think what's happening is when you reimport, it goes through the 8.1 migration because the version when you export is This is a great catch though! i forgot that we have to do this. |
@koji got it, this sounds like expected behavior. if you didn't add any step using the waste chute then it isn't being used in the protocol and won't generate upon reimport or even if you upload it to the app. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for answering to all my questions.
LGTM!
closes AUTH-267
Overview
In PD in production, if you create a Flex protocol with no pipetting steps and reupload it to the app, it does not auto generate a trash bin for you. Technically there is a way around it by adding a trash bin entity. But its a weird state because return tip and no trash entity is not supported in PD.
Ot-2 does not have this issue because it always ensures a hardcoded fixed trash is generated
So this PR auto-generates a trash bin for a flex if there is none when importing a protocol.
Test Plan
I created a test case to test all scenarios, so it should work as expected.
However, you can create a flex protocol and add a pause step. Download the protocol and reimport it back to PD. See that the trash bin is generated.
Changelog
Review requests
see test plan
Risk assessment
low