Skip to content
View di-omics's full-sized avatar

Block or report di-omics

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
di-omics/README.md

Di Hu

full-stack scientist - building autonomous labs

Bridging the embodiment gap between scientific expertise and robotic execution, with sequential, baked-in, measurable QC.

My work turns protocols, acceptance criteria, and failure responses into gated, auditable execution across laboratory hardware. This profile is a public portfolio of reusable automation, omics, robotics, and evaluation systems.

Oxford PhD / joint first author in Nature Communications / wet lab, genomics, automation, computation, and ML.

The argument / Benchmarks / LinkedIn / Writing

Highlights

8 environments: RL for drug development, every reward validated like an assay. drugdev-gym 4 instruments as agent-callable MCP tools, simulation by default. plr-mcp 5 playbooks for bringing lab instruments with no API under Python. plr-reverse-engineer 4 legs of a closed loop, computed: it names the one that breaks. autonomous-lab

  • drugdev-gym -- new in November 2026. Eight RL environments for cell assays and drug development, each running on a simulated liquid handler. Every reward is validated like an assay before it is scaled: the expert protocol against named bench mistakes, over the same seeds. More than 500 tests. Simulation only.
  • plr-mcp -- a liquid handler, a plate reader, a thermocycler, and a heater-shaker as MCP tools that any agent can call. Simulation by default, with hardware permission enforced in code.
  • plr-reverse-engineer -- capture, decode, and guarded replay for instruments with no automation API. Five playbooks so far, each with its status stated: a cell sorter, an LC/MS, a solvent evaporator, a DNA sequencer, and a single-cell dispenser.
  • autonomous-lab -- computes whether a lab can close a loop from hypothesis to evidence across four legs (execute, measure, decide, record), and names the one that breaks.

Now

What I am building in the open right now. The status column says how far along each one is.

The question Status
drugdev-gym Can the context in bench scientists' heads be captured in a form a model can hill-climb on, with the reward proven true before it is scaled? v0.1, simulation only. Eight environments; nothing has touched hardware, cells, or compounds
robot-policy-evals Is the gain real? A known-truth audit of how robot-policy checkpoints get picked and reported, piloted on Reacher-v5, then on Diffusion Policy / PushT plan and draft pre-registration committed; nothing run yet beyond environment checks
liquid-policy-robustness Do liquid neural networks control a robot arm better under sensor noise than matched-size MLPs and LSTMs? teacher, demonstrations, and student training run; the noise sweep has not been run
ml-foundations The PyTorch training loop from the inside, on FashionMNIST warm-up, in progress

Capabilities

Autonomous lab orchestration, QC gates, provenance, recovery, honest hardware boundaries autonomous-lab
Robotics arm control under PyLabRobot, eye-in-hand vision, instrument reverse engineering plr-lab-robot
Computer vision and image analysis detection, state, tracking, camera-verified execution, scored blind lab-cv
RL environments simulated assay, potency, and stability environments, with rewards validated like assays drugdev-gym
ML for biology protein design loops, Bayesian assay optimization, conformal QC ml-design-loops
Benchmarks and evals the metric each capability is scored on, and which numbers are still pending benchmarks

Each row states its own evidence boundary. Most of this is simulated, and every repository says so.

What it is all for

Every layer here exists to serve one number: how much a lab learns per dollar per experimental cycle. Orchestration is buildable: scheduling instruments, moving plates, tracking samples, and holding provenance are engineering with known shapes, and the code here does them. What is genuinely scarce is laboratory intelligence: knowing what a result means, what to run next, when a clean-looking plate should be thrown away, and what a robot must prove before it is trusted with the step.

So the portfolio is built around making that judgment explicit, attributable, and checkable. The full argument, the four legs of a closed loop, and the order the stack has to be built in are in THESIS.md.

Current evidence boundary

Some named operations have been executed on physical instruments under human supervision. Most of the portfolio remains simulated. There is no customer deployment and no full wet end-to-end biological endpoint yet. Each repository states its own evidence and validation boundary, and the language is deliberately narrow:

  • Simulated -- exercised without attached instruments.
  • Hardware-executed under supervision -- a named interaction ran on a physical instrument and its observed result is recorded.
  • Wet/bio-validated -- measured biological data met a stated acceptance criterion.

Unknowns stay unknown until evidence clears the next gate. A simulator result never becomes a hardware or biological claim by wording alone.

The supervised physical-instrument run cards and observed failures live in plr-tested (private). It is private because the work is high stakes, and a reader who cannot inspect the evidence should not be shown a claim resting on it.

Repositories

Autonomous lab

autonomous-lab evidence and permission for autonomous labs: computes whether a loop closes, and names which leg breaks
plr-mcp typed, agent-callable lab tools; the arming model is enforced in code, not documented
plr-reverse-engineer capture, decode, guarded replay for no-API instruments; incomplete maps stay blocked from actuation
benchmarks the evaluation index: what each capability is scored on, and which numbers are still pending
plr-tested (private) supervised physical-instrument run cards and observed failures, kept as evidence

RL environments and ML

drugdev-gym RL environments for cell assays and drug development on a simulated liquid handler, with every reward validated like an assay
ml-design-loops ESM-2 protein design, Bayesian assay optimization under a conformal gate, and an agentic design-build-test-learn engine
robot-policy-evals a known-truth audit of how robot-policy checkpoints get picked and reported
liquid-policy-robustness liquid neural networks against matched-size MLPs and LSTMs under sensor noise
ml-foundations a first PyTorch training project, kept as a lab notebook

Robotics and vision

plr-lab-robot a simulation backend for PyLabRobot's arm API, which upstream ships without
lab-cv detection, state classification, tracking, camera-verified liquid handling, and microscopy image analysis; every demo scored blind against a plant
awesome-wetlab-cv curated CV for labs that see, decide, and act -- with CI that checks every link
robotics-devkit plugin marketplace and template for the code-to-simulation-to-real-robot ladder, with MCP tools and test agents

Instruments and protocols

opentrons-drivers serial GCode for the OT-One Smoothieboard, HTTP for OT-2 and Flex, with a simulator
ot-flex-automation Opentrons Flex workflows for whole-genome sequencing, methylation sequencing, and TIP-seq, with explicit off-deck handoffs and validation status
fullstack-omics simulator-only scRNA-seq and whole-genome sequencing workflows, from planning through analysis handoffs
omics-demos synthetic, ground-truth demos for scRNA-seq, methylation sequencing, and PCR enrichment QC; no wet-lab claims
plr-minimum-effective finds the cheapest sequencing library prep that still gives a callable answer: unique reads per dollar, gated on in-process CV
spatial-flow spatial-biology lab operations: specimen lineage and TMA batch-balance planning

Hack days

bay-hack verified tube access: no verified opening, no pipetting -- enforced in code and in the sealed receipt
someplace a voice companion inside a generated world

About

Python / PyLabRobot / MCP and agent harnesses / robotic manipulation and computer vision - single-cell and low-input NGS.

LinkedIn / Writing / thesis

Pinned Loading

  1. autonomous-lab autonomous-lab Public

    Evidence and permission for autonomous labs: expert QC gates, workcell orchestration, provenance, recovery, and honest hardware boundaries.

    Python

  2. plr-lab-robot plr-lab-robot Public

    Simulation-first lab robotics: PyLabRobot arm control, eye-in-hand vision, dexterous manipulation, and auditable workcell tasks.

    Python 1

  3. plr-mcp plr-mcp Public

    Auditable MCP tools for PyLabRobot: run and sample context, typed provenance, simulation by default, and explicit hardware permission.

    Python 1

  4. plr-reverse-engineer plr-reverse-engineer Public

    Capture, decode, and guarded-replay tooling for no-API lab instruments; incomplete maps remain blocked from actuation.

    Python

  5. lab-cv lab-cv Public

    Computer vision and image analysis for the bench: detection, state classification, tracking, and camera-verified execution, each scored blind against planted ground truth. CPU-only, clean-room synt…

    Python

  6. ml-design-loops ml-design-loops Public

    Closed-loop ML for biology: ESM-2 protein design by simulated annealing, Bayesian assay optimization with a split-conformal accept/reject/escalate gate, and an agentic design-build-test-learn engin…

    Python