Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat (abr-testing): Low Volume 96ch Protocols + Full Liquid Set up Pr…
…otocol (#17475) <!-- Thanks for taking the time to open a Pull Request (PR)! Please make sure you've read the "Opening Pull Requests" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests GitHub provides robust markdown to format your PR. Links, diagrams, pictures, and videos along with text formatting make it possible to create a rich and informative PR. For more information on GitHub markdown, see: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax To ensure your code is reviewed quickly and thoroughly, please fill out the sections below to the best of your ability! --> # Overview Low Volume 96ch pipette protocol ## Test Plan and Hands on Testing - tested protocols on robots ## Changelog Added 3 protocols - 2 96ch low volume ones at api 2.23 - corrected some error recording issues with retrieving protocol files - created protocol to fill all plates for robots with a 96ch ## Review requests @sfoster1 I have noticed that the robots will have their protocol files saved in different numbered folders with opentrons-robot-server. How can I get this scrip to iterate these folders to find the file that matches the protocol_id? ## Risk assessment <!-- - Indicate the level of attention this PR needs. - Provide context to guide reviewers. - Discuss trade-offs, coupling, and side effects. - Look for the possibility, even if you think it's small, that your change may affect some other part of the system. - For instance, changing return tip behavior may also change the behavior of labware calibration. - How do your unit tests and on hands on testing mitigate this PR's risks and the risk of future regressions? - Especially in high risk PRs, explain how you know your testing is enough. -->
- Loading branch information