Skip to content

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

Merged
merged 13 commits into from
Jul 7, 2025
Merged

feat(app) add third step to blowout #18760

merged 13 commits into from
Jul 7, 2025

Conversation

koji
Copy link
Contributor

@koji koji commented Jun 26, 2025

Overview

noticed that I forgot to add third screen to BlowOut

clsoe AUTH-1931

Test Plan and Hands on Testing

Changelog

  • add third screen
  • remove test for the previous BlowOut

Review requests

Risk assessment

low

@koji koji requested review from ncdiehl11 and jerader June 26, 2025 23:58
Copy link

codecov bot commented Jun 27, 2025

Codecov Report

Attention: Patch coverage is 0.65789% with 302 lines in your changes missing coverage. Please review.

Project coverage is 62.73%. Comparing base (f823458) to head (9eff8a5).
Report is 5 commits behind head on edge.

Files with missing lines Patch % Lines
...sferFlow/QuickTransferAdvancedSettings/BlowOut.tsx 0.00% 150 Missing ⚠️
...ms/ODD/QuickTransferFlow/utils/getMaxUiFlowRate.ts 0.00% 66 Missing ⚠️
...ickTransferFlow/utils/generateQuickTransferArgs.ts 0.00% 23 Missing ⚠️
...TransferFlow/utils/getExtractTiprackTypeFromURI.ts 7.69% 12 Missing ⚠️
...ansferFlow/QuickTransferAdvancedSettings/index.tsx 0.00% 10 Missing ⚠️
...isms/ODD/QuickTransferFlow/utils/getPipetteName.ts 9.09% 10 Missing ⚠️
...erFlow/Dispense/hooks/useDispenseSettingsConfig.ts 0.00% 9 Missing ⚠️
...w/QuickTransferAdvancedSettings/DisposalVolume.tsx 0.00% 9 Missing ⚠️
.../QuickTransferFlow/utils/getInitialSummaryState.ts 0.00% 7 Missing ⚠️
...pp/src/organisms/ODD/QuickTransferFlow/reducers.ts 0.00% 5 Missing ⚠️
... and 1 more
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #18760      +/-   ##
==========================================
- Coverage   62.81%   62.73%   -0.08%     
==========================================
  Files        3250     3253       +3     
  Lines      257655   257824     +169     
  Branches    32754    32717      -37     
==========================================
- Hits       161835   161742      -93     
- Misses      95622    95884     +262     
  Partials      198      198              
Flag Coverage Δ
step-generation 5.34% <0.65%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
app/src/organisms/ODD/QuickTransferFlow/types.ts 100.00% <ø> (ø)
...src/organisms/ODD/QuickTransferFlow/utils/index.ts 100.00% <ø> (ø)
...Flow/QuickTransferAdvancedSettings/PipettePath.tsx 96.27% <0.00%> (-0.54%) ⬇️
...pp/src/organisms/ODD/QuickTransferFlow/reducers.ts 1.09% <0.00%> (-0.02%) ⬇️
.../QuickTransferFlow/utils/getInitialSummaryState.ts 76.00% <0.00%> (-8.06%) ⬇️
...erFlow/Dispense/hooks/useDispenseSettingsConfig.ts 51.50% <0.00%> (-0.53%) ⬇️
...w/QuickTransferAdvancedSettings/DisposalVolume.tsx 83.89% <0.00%> (-0.75%) ⬇️
...ansferFlow/QuickTransferAdvancedSettings/index.tsx 91.20% <0.00%> (-1.46%) ⬇️
...isms/ODD/QuickTransferFlow/utils/getPipetteName.ts 9.09% <9.09%> (ø)
...TransferFlow/utils/getExtractTiprackTypeFromURI.ts 7.69% <7.69%> (ø)
... and 3 more
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@koji koji marked this pull request as ready for review June 27, 2025 05:23
@koji koji requested a review from a team as a code owner June 27, 2025 05:23
? liquidSpecs.lowVolumeDefault.supportedTips[tipType]
: liquidSpecs.default.supportedTips[tipType]
const minFlowRate = 1
const maxFlowRate = Math.floor(flowRatesForSupportedTip?.uiMaxFlowRate ?? 0)
Copy link
Collaborator

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!

Copy link
Collaborator

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)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

path === 'multiDispense'
? {
location: trashConfigCutout,
speed: flowRatesForSupportedTip.defaultDispenseFlowRate.default,
Copy link
Collaborator

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

Copy link
Collaborator

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

Copy link
Contributor Author

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.

@koji koji requested a review from jerader July 1, 2025 01:56
@@ -31,18 +31,21 @@ export function useDispenseSettingsConfig({
const { makeSnackbar } = useToaster()

const getBlowoutValueCopy = (): string | undefined => {
Copy link
Collaborator

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Collaborator

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?

Copy link
Contributor Author

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.

Copy link
Collaborator

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

Copy link
Contributor Author

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PD post-launch backlog?

@koji koji requested a review from ncdiehl11 July 7, 2025 19:02
Copy link
Collaborator

@ncdiehl11 ncdiehl11 left a 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.

Copy link
Collaborator

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

Copy link
Contributor Author

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.

https://opentrons.atlassian.net/browse/AUTH-2039

@koji koji merged commit fe37979 into edge Jul 7, 2025
48 of 50 checks passed
@koji koji deleted the feat_add-third-step-to-blowout branch July 7, 2025 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants