Skip to content

Api reference

Resources

ServiceResources

pythonlab.resources.services.analysis.PlateReaderServiceResource

Bases: ServiceResource

multi-cavity / single cavity ? associated labwares, like lids, stacks

Parameters:

Name Type Description Default
Resource [type]

[description]

required

run_series(labware, protocols, **kwargs)

runs more than one protocol

pythonlab.resources.services.labware_storage.LabwareStorageResource

Bases: ServiceResource

multi-cavity / single cavity ? associated labwares, like lids, stacks

Parameters:

Name Type Description Default
Resource [type]

[description]

required

pythonlab.resources.services.labware_storage.LabwareStorageResourcePool

pythonlab.resources.services.incubation.IncubatorServiceResource

Bases: ServiceResource

multi-cavity / single cavity ? associated labwares, like lids, stacks

Parameters:

Name Type Description Default
Resource [type]

[description]

required

pythonlab.resources.services.incubation.IncubatorServiceResourcePool

pythonlab.resources.services.moving.MoverServiceResource

Bases: ServiceResource

mover

Parameters:

Name Type Description Default
Resource [type]

[description]

required

pythonlab.resources.services.centrifugation.CentrifugeServiceResource

Bases: ServiceResource

Centrifuge resource

Parameters:

Name Type Description Default
Resource [type]

[description]

required

LabwareResources

pythonlab.resource.DynamicLabwareResource

Bases: LabwareResource

__init__(proc, name, priority=None, lidded=False, outside_cost=0, **kwargs)

Dynamic Labware is a special type of labware, where order of usage is (dynamically) determined during the process execution, e.g. a reagent trough that is used when addition of a reagent to a certain labware is required, depending on an outcome of a descision, like a pH measurement or induction after a certain Absorbtion is reached.

Parameters:

Name Type Description Default
proc
required
name str
required
priority
None
lidded bool
False
outside_cost

Some reagents need to be stored under special properties (e.g. cooled). These costs get translated to waiting_costs between getting it out and putting it back

0
kwargs
{}