Pypetting
Pypetting provides a simple set of wrappers to write complex worklists for the Tecan EVOware pipetting software. Unfortunately it does not entirely avoid interacting with the original software, but it reduces the necessary interactions with it to a minimum.
Installation
Install using pip with pip install pypetting.
Pypetting has only been tested with Python 3.10.0.
Examples
Define a position on the grid
from pypetting import GridSite
site = GridSite(grid=36, site=1, carrier="MP 3Pos")
Define labwares
from pypetting import Labware
greiner96 = Labware(name="96 Well Griner", rows=8, columns=12, spacing=1)
trough100 = Labware("Trough 100+25ml", 8, 12)
Pipetting from one column to the next
from pypetting import GridSite, Labware, aspirate, dispense, write_gwl
pipetting_site = GridSite(36, 1, "MP 3Pos")
labware = Labware("96 Well Greiner", 8, 12, spacing=1)
ALL = 8 * [True]
worklist = [
aspirate(pipetting_site, 1, ALL, 50, "LB CD ZMAX", labware=labware),
dispense(pipetting_site, 2, ALL, 50, "LB CD ZMAX", labware=labware),
]
write_gwl("worklist.gwl", worklist)
Place plate in the incubator
from pypetting import GridSite, Labware, transfer_labware, return_plate, write_gwl
src = GridSite(36, 0, "MP 3Pos")
dest = GridSite(68, 0, "StoreX 22Pos")
labware = Labware("96 Well Greiner", 8, 12, spacing=1)
worklist = [
transfer_labware(src, dest, labware),
return_plate(1, 1),
]
write_gwl("worklist.gwl", worklist)
How to avoid EVOware
The authors of Pypetting have strong opinions about the design of EVOware. To implement more complex workflows, modern techniques for modularization and abstraction of logic are required. ANY general purpose programming language provides these tools. Thus outsourcing as much logic as possible is desirable.
We suggest the following workflow for any form of iterative task:
- Call an application to generate the workflow, store the return value of the
application in a variable e.g. called
return_value - Execute workflows
- Jump to the application when
return_valueis non-zero
License
MIT License
Copyright (c) 2021 Nicolas Ochsner
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Metadata
Release files for pypetting 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pypetting-1.0.1.tar.gz | 12.5 kB | Without provenance | Details for pypetting-1.0.1.tar.gz |
Release files / pypetting-1.0.1.tar.gz
| Download URL | pypetting-1.0.1.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c8379803eb566eda3dd58c3da23dc16818a924c252b014c8c03a6c2b472d4fb
|
|
BLAKE2b-256 checksum How to use checksums |
d19276465e47fa71866b99004b8fdb03d7a4282b5494de3bd3a9d5881ea034c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Security for pypetting 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.