Trellis Tools

Supporting plant biology

Every plasmid, stock, seed and page, linked as the work happens.

Trellis Tools puts a lab's Golden Gate parts, sequences, notebook, seeds, stocks, equipment and genomes behind one sign-in, on your own server. Each record remembers the one before it, so two years on you can still say where a line came from, who made it and what was done to it.

  • Eight tools, one sign-in
  • Runs on your server with Docker
  • Nightly backups
  • Open source
Seed Bank · Family tree of DEMO-L-0004
One page, every tool. The family tree of a cross: the construct and the reads that confirmed it, its glycerol stocks and where they are, the parents back to Col-0, the notebook pages about each step, and the seed it led to.

Why it exists

A plasmid is designed in one place and its seeds end up in someone's spreadsheet. The connection is what fails.

Academia is inherently transient. Students graduate and postdocs move on every few years, and the knowledge of which construct is in which tube, and which line carries it, leaves with them. Trellis Tools keeps that knowledge with the lab, not with the person.

Trellis Tools makes the connections as the work happens. Here is one construct from the teaching demo, followed from a part in the freezer to a T2 plant, through five tools. Every step below is a link you can follow both ways.

  1. PartDEMO p35Spromoter, GGAG to AATG
  2. PlasmidpDEMO-L1 35S:tRFPsequence confirmed, clone 2
  3. Glycerol stockDEMO-G-0002GV3101, −80 °C freezer 1 / box 3 / A2
  4. LineDEMO-L-000335S:tRFP #3, transgenic
  5. Seed lotDEMO-S-0003T2, harvested from one T1 plant
  6. Plants#13–#24drought, growth chamber 3, day 36
  7. NotebookT2 drought trialresults, linked to the lot and plants
Made where the work happens

Confirming a clone by sequencing makes its glycerol stock. Harvesting a plant makes the next seed lot. Nobody copies a code by hand.

One lab code on everything

Your lab's short code begins every code it issues, in every tool: GL-G-0042 is a glycerol stock, GL-S-0042 a seed lot of the same lab.

Links that go both ways

Type @ in a notebook page to link a plasmid, stock, seed lot or genome track, and that record lists the page in return.

The tools

Eight tools that already know about each other

Every screen below is the real software, recorded in the teaching demo that ships with it. Click a screenshot to see it full size.

MoClo Library Tool

Plan Golden Gate assemblies that work the first time

The lab's parts library, with each part's fusion sites, who made it and where the tube is. Assemble on screen, and the tool keeps you to parts that fit.

  • Compatibility checking finds clashing or missing overhangs and internal BsaI or BpiI sites, and names the part at fault.
  • Level 1 and Level 2 assemblies drawn as the plasmid you will make, with the reaction mix scaled to your number of reactions.
  • CRISPR Designer turns guide sequences into a tRNA–sgRNA array and a full Level 2 construct.
MoClo · Cassette Assembly
RecordingPick a promoter and only the parts that fit stay on the list. Three parts make a 1,425 bp cassette, every junction checked.
Sequence Editor

Map it, clone it in silico, and prove the clone

Edit and annotate any sequence, simulate the cloning, and align the sequencing reads against it. Assemblies from MoClo open here directly.

  • Maps, digests and virtual gels; Golden Gate, Gibson, ligation and Gateway LR simulated, the product keeping both parents' features.
  • Sanger reads aligned with chromatograms and every mismatch marked. Confirm the clone and its glycerol stock is made in Lab Stocks.
  • Primer design, and the lab's own primers that already bind, found by sequence before anyone orders another.
  • Bisulfite primers for DNA methylation, checked against a reference genome with BLAST, with an explanation of what to change when nothing passes.
Map view
pDEMO-L2, 4,349 bp and 106 features, as the editor draws it.
Sequencing
Two reads, one mismatch: T→C at 681 in the tRFP CDS, found and named.
Sequence Editor · Bisulfite primers
Lab Notebook

A notebook that knows what you are writing about

A page for every day, filed under its month and year. Write as you work; the page saves itself and keeps its earlier versions.

  • Type @ to link a plasmid, stock, seed lot, track or page. The link survives renaming, and the record links back.
  • Protocols with active tables that scale and calculate, and steps ticked off with who and when.
  • MoClo reactions, gel photos and bookings arrive on the day: the mix as a table, the lanes named, the microscope you were on.
  • A week's to-do list under every day of the week, with tagged tasks that can move on to next week.
Lab Notebook · To do, week 46
RecordingThe week's to-do list: tag a plasmid with @, tick a task, move one on to next week.
Lab Notebook · Next: knocking out tRFP
One sentence, three links: the plasmid, the seed lot and the glycerol stock, each a click away and each listing this page in return.
Seed Bank

Lineage you never have to piece together

Lines, seed lots and plants, kept apart the way they really are: a line is a genetic identity, a seed lot is a bag, a plant is a pot.

  • Sow from a lot and every plant gets a code, a position and a treatment. Pot labels carry a QR code that opens the plant.
  • Score phenotypes against named traits across a whole sowing, with photos and 3D scans attached.
  • Harvest and the seeds become the next lot, remembering the plant they came off, back to the first generation.
  • The family tree of any line, lot, plant, plasmid or stock gathers the whole history across all the tools.
Seed Bank · Growing
Every plant still alive, by where it grows, with its lot, age and treatment. Tick a row to score, move or label a whole sowing.
Lab Stocks

The tube and the proof are one record

Glycerol stocks, primers, chemicals, antibodies and plant material, numbered with your lab's code and kept where everyone can find them.

  • Glycerol stocks made when a clone is confirmed, linked to the reads that proved it and to the box and position of the tube.
  • Primers searchable by sequence, chemicals with CAS numbers and safety data sheets, antibodies with host and supplier.
  • Labels for DYMO printers, an order list the lab admins handle, and an optional copy in eLabJournal.
Lab Stocks · DEMO-G-0001
DEMO-G-0001: clone 2 in DH5α, −80 °C freezer 1 / box 3 / A1, one click from its plasmid and its reads.
Booking

Rooms and equipment, booked where the lab already is

Meeting rooms, microscopes, growth chambers and thermocyclers on a week calendar, shared with the labs their owner chooses.

  • Find a free slot by kind of equipment, place, length and time of day.
  • Tag the people in a booking, and it shows on the day in each of their notebooks.
  • A picture can always be traced to the microscope that took it, from the notebook day it was written on.
Booking · Meeting room 2.14
A week at a glance, today highlighted. The same lab meeting appears at the top of each attendee's notebook day.
Genome Browser

Your data on the genome, ready for the figure

Reference genomes and a library of aligned tracks in an IGV browser. Arabidopsis TAIR10 with the Araport11 annotation comes ready to use.

  • Add tracks from BAM, bigWig, BED or GFF; large files are converted on the server, and methylation tracks are recognised and measured as a level.
  • Find any gene by its code, symbol or full name — FLC, flowering locus c — in the genome's own annotation.
  • Mark a sequence: CRISPR guides, primer sites or any motif, found on both strands and kept as a track.
  • Analyses with deepTools: profiles and heatmaps whose clusters become gene lists, replicate checks, fingerprints, and methylation against expression, each with a guide to reading it.
  • Circos plots and figures exported as SVG or put into the notebook with the code to make them again; primers checked against a genome with BLAST.
Genome Browser · TAIR10, HSP101
HSP101 on chromosome 1, with the guide designed against it marked as a track of its own.
HPC Terminal

Start the big job, close the laptop, pick it up anywhere

A terminal on the lab's HPC machines, in the browser. The heavy work runs on the cluster; the suite keeps the session going while you are away and the record of what you ran.

  • Saved connections opened from a link; your password, and a one-time code, are asked each time and never kept.
  • Sessions keep running with the browser closed. Open the link at home and see what it printed meanwhile; with tmux the work survives even a restart of the suite.
  • Into the notebook: each session recorded under the day it ran, and job scripts picked from the cluster and saved by hand.
  • Only the lab's machines, on the lab's networks, each checked against its host key; administrators and lab leads see who is connected, never what is on their screen.
HPC Terminal · Cluster (ada)
A job script on the cluster, inside tmux: submit it, close the page, and come back to it from anywhere.

How it fits together

Built for how a lab actually shares its work

One sign-in

Sign in once at the front door and every tool knows who you are. One account, one password.

Labs and chair groups

A lab's stocks, seeds, plasmids and equipment belong to the lab, so they stay when people leave. Neighbouring labs in a chair group can see each other's records without changing them.

Your notebook is yours

Until you share it, a page at a time or the whole notebook with your lab. Pages shared to work on together are edited by both.

Nothing disappears quietly

Pages keep their earlier versions, records keep a history of who changed what, and deleted pages can be brought back.

Your data, your server

Plain SQLite databases with the files inside them, backed up every night to a folder or network drive you choose, with a console to check and restore.

Alongside eLabJournal

Where your institute uses eLabJournal, Lab Stocks copies stocks there with their box and position, and brings over what eLab already holds.

Get started

Running in about ten minutes

One script installs the whole suite, and running it again later updates it. Each lab gets its own space, its own code and its own records.

  • A Linux server or workstation the lab can reach
  • Docker with the compose plugin
  • On Windows, run it from Git Bash or WSL
  1. Install

    Get the suite and run the installer. It shows what it will do, asks once, and starts every tool.

    $ git clone https://github.com/Gardiner-Lab/Trellis-Tools.git cd Trellis-Tools ./install.sh
  2. Open it and sign in

    Open the address the installer prints, such as https://your-server:8080. Sign in as the administrator and choose your own password before anything else opens. Each computer trusts the lab's certificate once.

  3. Set up your lab

    In the dashboard, create your lab and choose its short code. Colleagues register on the sign-in page with the lab's registration code.

  4. Try it with the teaching demo

    Load a demo chair group with two labs and one connected experiment in every tool, walled off from your real labs.

    $ make demo
Already running the MoClo Library Tool?

Run the same installer on that machine. It keeps a snapshot of MoClo's data, moves its users, parts and plasmids into the suite, checks every table, and starts on the port MoClo used, so bookmarks keep working and nobody has to sign in again. ./install.sh --rollback goes back to the old MoClo if you need to.

Updating

Run ./install.sh again. Each release is installed after a snapshot and a count of every record, compared again afterwards, and ./scripts/check.sh confirms every tool answers.

Backups

Every database is copied each night to wherever you choose, a folder or a network drive, and the backup console shows each copy and restores from it.

An ongoing project

Trellis grows with the labs that use it

Trellis Tools is built alongside the daily work of plant biology labs, and new releases come out often. Every tool began as something a lab needed. If it does not yet do what your lab needs, we want to hear about it.

A project of the community. We want Trellis to belong to the labs that use it. Collaboration is how we make it better: every bug report, idea and new module makes it better for the next lab too. Trellis is built in the time left over from running a lab, which is never much, so more hands make a real difference. We are always happy to find new collaborators.

Open an issue on GitHub