Open Source RoboticsRobots, software & learning

Science Jubilee

Software

Python labware and tool orchestration for an existing Jubilee motion platform, with separate tool designs/configuration and controller interfaces. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

Installation & first result →Official websiteGetting started

For
Robotics and lab-automation developers configuring an existing Jubilee platform [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Science Jubilee provides Python orchestration for an existing Jubilee motion platform fitted with laboratory tools and labware. The repository includes a machine driver, deck definitions, tool modules and example designs. Its own README presents these as starting points that may need adaptation, not complete protocols for arbitrary scientific tasks. This entry covers that robotics software/tool ecosystem, not a new complete machine or a validated pipetting system. [1]

Is this for you?

Known limitations
  • Existing Jubilee machine, deck, tools and consumables are not supplied by Python installation.
  • HTTPsyringe10cc holder sample and OT2pipette are different tools; one holder is not a complete platform/tool BOM.
  • Explicit simulation is not physical communication; crash_detection defaults false and source comments flag interruption/tool-offset recovery work.
  • No machine connection, homing, tool calibration, pipetting volume/accuracy or assay was tested.

Editorial source-scope assessment; no execution, fit or compatibility test.

[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] · Editorial assessment

What you need

Dependencies
  • Python>=3.8 per setup.cfg
  • pyserial, requests, numpy, Jinja2 and ipywidgets; optional tool extras separate
  • Configured Jubilee/Duet/RepRapFirmware platform, deck/tool definitions and matching labware

[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

Installation & first result

Open the upstream getting-started guide [1]

  • Choose one Jubilee tool/deck/labware configuration and inspect its software/controller route before attempting motion or an assay.
  • Follow the selected source installation/configuration route only after reconciling the stated version, hardware and dependency gaps.

Editorial source-scope assessment; no execution, fit or compatibility test.

[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] · Editorial assessment

Project notes

Install the software independently of the machine configuration

At reviewed revision bb918fa78f300f57cc379a80731cfca7bdb55c66, setup.cfg requires Python 3.8 or later and lists pyserial, requests, numpy, Jinja2 and ipywidgets; additional instrument/tool dependencies are separate. The install guide documents a virtual environment, activation and python3 -m pip install -e ., with a separate Jupyter kernel step for notebooks. No environment was installed here. [4] [7] [8]

The documented Machine/deck/Pipette example is a configuration sketch, not a complete working program: it needs actual deck, labware, tool indices and configuration files. The README's four-argument Pipette constructor does not match the pinned implementation. Inspect Pipette.from_config(index, name, config_file) and add_tiprack before adapting that example; this is a source-inspection route, not a tested replacement program. The inspected driver uses HTTP/G-code communication with a configured controller; a software import does not establish a Jubilee/Duet/RepRapFirmware connection or matched tool. [1] [5] [9]

Keep physical tools and software modes distinct

The OT2-pipette instructions and the sampled HTTPsyringe 10cc holder are different tools. For an OT2 investigation, its README points to the designs directory, assembly_docs/OT2_Wiring_Diagram.pdf and duet_config/OT2_Pipette_Configuration.md; inspect those and match deck/labware definitions. Those referenced files were not inspected here. We checked the original holder's Fusion archive bytes/ZIP integrity and corresponding STEP payload; that does not validate an entire syringe tool, pipette, deck or Jubilee machine. Do not use one printable holder as a complete laboratory-build budget. [6] [10] [11]

The driver has an explicit simulated flag, defaulting to false, and crash_detection also defaults to false. Simulated operation is not device communication. A source comment identifies interruption/tool-offset recovery work; this review does not establish safe interruption, collision protection or successful tool state recovery. Those configuration and recovery limits matter before moving hardware or attempting an experiment. [5]

The MIT software notice does not automatically settle the parent platform, bought-in OT2 hardware, external labware or every tool/media asset. No complete machine/tool/consumable price, machine connection, homing, calibration, volume accuracy, pipetting or assay was tested. Original design payloads stay private and are linked upstream rather than redistributed. [2] [3] [9]

What we checked

Source research only. Selected text and original artifact byte/container identities inspected; no upstream compilation, dependency installation, native CAD application/fit/strength validation, simulation, manufacturing, wiring/calibration, powered commissioning, control performance or assay performed. Original CAD remains private; source links are not permission to redistribute vendor/third-party material.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
bb918fa78f300f57cc379a80731cfca7bdb55c66; original CAD snapshot identities retained separately

Source files and licenses

Distinct inspectable robotics software/tool ecosystem with actual source and a bounded next step. Original file inspection is not fabrication, physical operation or complete support qualification.

LayerAvailability / license
softwareavailable · MIT
Scoped repository declaration; purchased components, external software/labware/tool assets and vendor bodies have separate terms. No commercial/manufacturing or experimental-performance clearance implied. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]
documentationavailable · MIT
Scoped repository declaration; purchased components, external software/labware/tool assets and vendor bodies have separate terms. No commercial/manufacturing or experimental-performance clearance implied. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

No model weights/dataset or separate hardware manufacturing claim selected for the initial source-inspection workflow.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history