Skip to content

feat(step-generation): use new flow_rate argument for aspirate() and dispense()#18391

Merged
ddcc4 merged 1 commit intoedgefrom
dc-pdpy-flowrate
May 19, 2025
Merged

feat(step-generation): use new flow_rate argument for aspirate() and dispense()#18391
ddcc4 merged 1 commit intoedgefrom
dc-pdpy-flowrate

Conversation

@ddcc4
Copy link
Copy Markdown
Contributor

@ddcc4 ddcc4 commented May 19, 2025

Overview

We added the flow_rate argument to aspirate() and dispense() (AUTH-1627, PR #18326), so now in PD Python generation, we can just set the flow rate directly, instead of the hacky ratio we were emitting before.

This makes the generated code much cleaner and easier to read.

Test Plan and Hands on Testing

Updated unit tests.
Examined generated code by hand.
I also re-exported Python for a test protocol and confirmed that it passes analyze.

Risk assessment

Low.

@ddcc4 ddcc4 requested a review from jerader May 19, 2025 18:25
@ddcc4 ddcc4 requested a review from a team as a code owner May 19, 2025 18:25
@codecov
Copy link
Copy Markdown

codecov Bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.12%. Comparing base (140735d) to head (d2bc92d).
Report is 1 commits behind head on edge.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #18391      +/-   ##
==========================================
+ Coverage   58.04%   58.12%   +0.07%     
==========================================
  Files        3241     3241              
  Lines      275215   275297      +82     
  Branches    32211    32315     +104     
==========================================
+ Hits       159761   160024     +263     
+ Misses     115261   115080     -181     
  Partials      193      193              
Flag Coverage Δ
protocol-designer 19.34% <100.00%> (+0.09%) ⬆️
step-generation 4.76% <100.00%> (-0.02%) ⬇️

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

Files with missing lines Coverage Δ
...-generation/src/commandCreators/atomic/aspirate.ts 85.99% <100.00%> (+0.66%) ⬆️
...tion/src/commandCreators/atomic/aspirateInPlace.ts 97.91% <100.00%> (-0.09%) ⬇️
...-generation/src/commandCreators/atomic/dispense.ts 84.21% <100.00%> (+0.36%) ⬆️
...tion/src/commandCreators/atomic/dispenseInPlace.ts 74.50% <100.00%> (-0.97%) ⬇️

... and 6 files with indirect coverage changes

🚀 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.

Copy link
Copy Markdown
Collaborator

@jerader jerader left a comment

Choose a reason for hiding this comment

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

yay

@ddcc4 ddcc4 merged commit 31037e7 into edge May 19, 2025
23 of 24 checks passed
@ddcc4 ddcc4 deleted the dc-pdpy-flowrate branch May 19, 2025 19:44
ddcc4 added a commit that referenced this pull request May 19, 2025
…thon codegen (#18396)

# Overview

PR #18391 updated step-generation to use the new Python `flow_rate`
argument in `aspirate()` and `dispense()`. QT also has tests for Python
code generation, but for some reason, the failures in the QT tests
didn't show up until after I merged that PR.

This updates the QT tests as well.

## Test Plan and Hands on Testing

Ran the tests again.

It looks like `app/src/organisms/Desktop/Devices/RobotSettings/AdvancedTab/AdvancedTabSlideouts/__tests__/DeviceResetSlideout.test.tsx`
is still failing at HEAD, but I really don't think that's related to
step-generation at all.

## Risk assessment

Low, hopefully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants