-
Notifications
You must be signed in to change notification settings - Fork 184
feat(app) add third step to blowout #18760
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
Conversation
add third screen to blow out close AUTH-1931
? liquidSpecs.lowVolumeDefault.supportedTips[tipType] | ||
: liquidSpecs.default.supportedTips[tipType] | ||
const minFlowRate = 1 | ||
const maxFlowRate = Math.floor(flowRatesForSupportedTip?.uiMaxFlowRate ?? 0) |
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.
i think @ncdiehl11 is using some util to get max flow rate for PD - probably want them to align!
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.
Hey @koji, I have a utility for getMaxUIFlowRate
that maybe you can use for consistency
pipetteName = pipetteName + `_96` | ||
} | ||
|
||
const pipetteName = getPipetteName(state.pipette) |
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.
nice!
...src/organisms/ODD/QuickTransferFlow/QuickTransferAdvancedSettings/__tests__/Blowout.test.tsx
Outdated
Show resolved
Hide resolved
path === 'multiDispense' | ||
? { | ||
location: trashConfigCutout, | ||
speed: flowRatesForSupportedTip.defaultDispenseFlowRate.default, |
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.
ya lets check on this speed flow rate too. i think @ncdiehl11 uses a util for this in PD as well
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.
We want to get our initial advanced args based on the following:
- volume
- pipette
- tip
- path
- liquid class
I have a large utility getLiquidClassesValues
in PD that takes in the above information, and returns a flattened PD form with the liquid class defaults. I think we probably need something similar here for QT, but instead of mapping to a form, it will map to the QT state. Maybe we should chat about this in more depth
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.
i have a working branch for getLiquidClassesValues
.
this will be resolve by a following pr.
@@ -31,18 +31,21 @@ export function useDispenseSettingsConfig({ | |||
const { makeSnackbar } = useToaster() | |||
|
|||
const getBlowoutValueCopy = (): string | undefined => { |
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.
does this need to be a function?
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.
yes
app/src/organisms/ODD/QuickTransferFlow/QuickTransferAdvancedSettings/BlowOut.tsx
Outdated
Show resolved
Hide resolved
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.
Should we consolidate the same utility to a shared location rather than have two instances of it, one in PD
and one in 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.
PM team's request is to aling app's functionality with pd's one, so having the shared utility would be great.
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.
Maybe we can ticket this so we don't forget? I'm OK with addressing in a followup, though
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.
where would be a good place for the ticket?
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.
PD post-launch backlog?
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.
I'm good with merging this! I left one comment about consolidating logic for max UI flow rate in PD/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.
As discussed in comment above, let's ticket a refactor to share this utility with PD/App in a followup
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.
issued the ticket for this.
i will follow up when I finish the QT work.
Overview
noticed that I forgot to add third screen to BlowOut
clsoe AUTH-1931
Test Plan and Hands on Testing
Changelog
Review requests
Risk assessment
low