Source · soonGet started
PUBLIC BETA
QT-1Photonic chip digital twin

q-twin · digital twin for photonic chips

Predict a photonic chip before it is made.

q-twin is a digital twin of your photonic chip. Describe it with your foundry’s PDK and what fabrication must deliver, run it as many virtual chips, and see which gates fail before you pay for a tape-out.

$ python -m studies.s2_calibration --design <pack>
Simplified schematic of the QT-1 twinDesign pack inputs (topology, PDK, profile, bench and gates) feed one twin containing an engine, a Monte Carlo over virtual chips and a scoring stage. Outputs are a gate by corner matrix, pass probability, evidence label and reports, evaluated at the best, nominal and weak corners.TOPOdesign.yamlPDKadapter + pinPROFvalue · status · srcBENCHsource, detectorsGATEyour thresholdsQT-1pack "demo-6"ENGINEone virtual chip per seedMONTE CARLOstudies S-1 … S-8SCOREagainst the pack's gatesdata only · no user codeMTXgate × cornerYLDpass probabilityEVIDworst input labelRPTfigures · PDFBESTlow range endNOMnominalWEAKhigh range endPACKRESULTSIllustrative pack shown.
Figure 1. Simplified schematic: one pack in, every gate at every corner out

1Features

  • Validate before fabrication: every acceptance gate checked on virtual chips at nominal, weak and best corners, before the first wafer
  • Your layout stays private: describe the chip with parameters and expectations in 6 plain files; no GDS, no layout upload
  • Built on foundry PDKs: choose an existing foundry PDK from the supported list; component models and tolerances come from it. CORNERSTONE coming soon
  • A library of studies: loss, calibration yield, interference, gate fidelity, drift, sensitivity and design comparison, each scored against your gates
  • Evidence on every number: measured, literature, calculated or target, and each result carries the worst label of its inputs

2Applications

  • Pre-tape-out design validation
  • Programmable photonic meshes
  • Tolerance and yield budgets
  • PDK and foundry choice
  • Quantum photonic circuits
  • Photonic AI and signal processing

3Description

A tape-out takes months and a mask set. q-twin builds one virtual chip per seed from your design pack, with loss, split-ratio spread, heater nonlinearity, thermal crosstalk, drift and detector imperfections, runs many of them, and reports the probability that the design passes each of its own gates.

One engine serves every design; only the pack changes. For one or two photons a linear optical network is computed exactly from its N × N matrix, so the uncertainty lives in the inputs, and the twin shows it instead of hiding it.

Table 1. Device Information

PartPackageBody size
QT-1design pack6 files (YAML)
Interfaceweb · CLIPDF report
StudiesS-1 … S-83 corners each

4Why a Digital Twin

A photonic tape-out costs a mask set, a fabrication slot and months of waiting. Most of what can go wrong is decided before the wafer exists. q-twin moves the first test before the first wafer, so a failing gate costs a rerun, not a fabrication run.

4.1Validate before you fabricate

The twin runs your design as many virtual chips at the nominal, weak and best corners of your process, and scores every acceptance gate. You see which gates bind, and by how much, while a change is still a line in a file.

4.2Your design stays yours

You describe what the chip is and what fabrication must deliver: mesh topology, component parameters, test bench and gates. No GDS, no layout file. Packs are data only, the twin runs no user code, and projects are private to their owner.

4.3Pick your foundry’s PDK

Choose an existing foundry PDK from the supported list. Component models and tolerances load from it, labelled with the PDK as their source. Generic specifications work today;CORNERSTONE support is coming soon.

Table 4-1. Where a design problem is found

Without a twinWith q-twin
WhenAfter fabrication, on the test benchBefore tape-out, in a study run
What it costsA new mask set and fabrication runA change to the pack and a rerun
What you learnOne chip, one measurementPass probability over many virtual chips, at every corner
What you hand over to test itThe layout (GDS), to a simulation or test partnerParameters and expectations only; no layout

5Functional Diagram and Pack Map

q-twin models the chip you will tape out: light enters at the facet, crosses a mesh of interferometers and reaches the detectors. Every element is a line in the design pack. Hover or focus a number to see the line that drives it, or the result a run gives back.

OFF-CHIPDIE · TOP VIEWTWINSOURCE012345DET9VER10FIG11RPT12EVID13YLD14MTX15CTL2CELL5PROF1TOPO8GATE7BENCH3IO4PDK6CORN
Figure 5-1. 6-mode programmable photonic die (Clements mesh of 15 MZIs), top view, with the pack map. Illustrative layout.
demo-6/*.yamlInputs 1–8
# design.yamlmodes: 6mesh: { family: clements }cell: { splitter: mmi2x2, theta: undercut }io:   { ports_in: [photon×6, reference, loopback×2] }# pdk.yamladapter: generic_specs# profile.yamlheaters.p_pi_mW:  value: [100, 300]   status: literature  corners: { best: 100, weak: 300 }# bench.yamldetectors: { kind: apd, efficiency: 0.25 }# gates.yaml- { id: G4, name: calibration, threshold: "mean ε < 1 %" }
s2_calibration · demo-6Outputs 9–15
demo-6  v0.3 · 2026-11-12 · frozenS-2     50 virtual chips × 3 cornersG4      nominal PASS  weak FAIL  best PASSlabel   target (worst input)fig     fig_yield.svgreport  report.pdfctl     compare v0.2 → v0.3 · download pack

Sample pack and output for an illustrative design. Not a real chip.

Table 5-1. Pack Map

No.NameI/OPack file / outputDescription
1TOPOIdesign.yaml meshThe mesh: Clements, Reck, multiport or custom, and its number of optical modes.
2CELLIdesign.yaml cellOne Mach–Zehnder interferometer: two couplers, two arms, and the phase shifters on them.
3IOIdesign.yaml ioEdge couplers at the facet and their roles: photon, laser, reference, loopback, monitor.
4PDKIpdk.yamlWaveguide, bend, coupler and heater models from the PDK adapter, labelled literature with the PDK as source.
5PROFIprofile.yamlEvery number, such as heater Pπ, loss and split ratio, as value, status and source.
6CORNIprofile.yaml cornersNominal, weak and best. A design range, like a coupler’s split spread, resolves by corner, never per element.
7BENCHIbench.yamlOff-chip: photon source, detectors, driver and temperature control.
8GATEIgates.yamlThe design’s own acceptance gates, read on the outputs. Studies read them; nothing is hard-coded.
9VEROrun recordEach run reads a frozen version of the pack and records its version, date and commit.
10FIGOfiguresSVG figures per study: yield, loss, visibility and gate curves.
11RPTOreportReport per run with inputs, method and verdicts. Download as PDF.
12EVIDOevidence labelEvery result carries the worst evidence label of its inputs.
13YLDOpass probabilityMonte Carlo over virtual chips: the share of chips that pass each gate.
14MTXOgate × cornerEvery gate at every corner on one matrix, with verdict words, not colour alone.
15CTLI/OCLI · dashboardRun, compare versions, see what changed, download pack and report.

6Study Run Timing

A study run is a signal you can read. The pack is frozen, loaded and checked, then each corner simulates its batch of virtual chips and is scored against the pack’s gates. Run it, then weaken the corner and watch the verdict change.

Timing diagram of one study run across three cornersThe pack is frozen and loaded, then the nominal, weak and best corners each simulate a batch of virtual chips in turn. A gate check follows each corner. In the second scenario the weak corner fails its gate and the run records the verdict.
s2_calibration · demo-6 · all cornersv0.3
    Share of virtual chips simulatedGate check
    Figure 6-1. One study run across three corners. Sample run; timings are illustrative and shown compressed.

    6.1Recommended Run Conditions

    ParameterMinTypMaxUnit
    Virtual chips per corner150—‡chips
    Target unitaries per chip1100—‡targets
    Corners per run133corners
    Parallel workers14—‡workers

    6.2What each gate reads

    MetricStudyExample gate
    Fibre-to-fibre lossS-1≤ 4.0 dB
    Calibration errorS-2mean ε < 1 %
    HOM visibilityS-3> 95 %
    CZ truth-table fidelityS-4> 90 %
    Phase driftS-5< 5 mrad/min

    ‡ Limited by your quota on the public host, or by your machine when self-hosted. Example gates come from an example pack; every pack sets its own.

    7Typical Characteristics

    The twin answers with curves, not single numbers: how yield falls as a parameter spreads, and how far each corner sits from the gate. Both graphs below are illustrative shapes, drawn to show what a study returns, not results for any chip.

    Illustrative calibration yield against split spread, per cornerThree falling curves for the best, nominal and weak corners. Yield stays near 100 percent at small split spread and falls to near zero as spread grows; the weak corner falls first.bestnominalweak0±1±2±3±40255075100Split spread (± %)Chips under the error gate (%)ILLUSTRATIVE
    Figure 7-1. Calibration yield vs. split spread, three corners (S-2). Illustrative shape, not twin output.
    Illustrative HOM visibility against normalised path mismatchTwo Gaussian curves falling as path mismatch approaches the coherence length. Source purity sets the peak: 98 percent for one source, 92 percent for the other, which therefore keeps less margin above the 90 percent example gate.example gate > 90 %purity 0.98purity 0.9200.511.520255075100Path mismatch ΔL / coherence length L_cHOM visibility (%)ILLUSTRATIVE
    Figure 7-2. HOM visibility vs. normalised path mismatch, two source purities (S-3). Illustrative shape, not twin output.

    8Detailed Description

    Build, run, read. Each step works on the same pack, so a result can always be traced back to the exact version and values that produced it. Use the hosted platform in a browser, or the same engine on your own machine.

    8.1Build

    Build the pack on 7 screens: Basics, Topology, PDK, Parameters, Bench, Gates and Review, with the YAML shown live. Start blank, from an example, or import a .zip. The same loader as the command line flags any value without a status or source before you save.

    $ ls designs/my-chip
    design.yaml  pdk.yaml  profile.yaml
    bench.yaml   gates.yaml  README.md
    6 files · every value labelled

    8.2Run

    Queue a study on our server within your quota, or run it locally. Each run reads a frozen version of the pack. The jobs list shows what is queued and running, and a failed job keeps its log.

    $ python -m studies.s2_calibration \
        --design my-chip --corner all
    nom  weak  best   50 chips each
    G4   PASS  FAIL  PASS

    8.3Read

    The dashboard leads with what binds: the gates that fail or are at risk. Below it, the gate × corner matrix, version history, what changed between versions, and a PDF report. Verdicts are always words, never colour alone.

    $ open dashboard · my-chip v3
    binds   G4 calibration · weak FAIL
    risk    G1 loss · weak AT RISK
    report.pdf · worst label: target

    Figure 8-1. Dashboard gate matrix, sample

    GateRequirementNominalWeakBestEvidence
    G1 loss · S-1≤ 4.0 dBPASS
    3.1 dB
    AT RISK
    3.9 dB
    PASS
    2.6 dB
    literature
    G4 calibration · S-2mean ε < 1 %PASS
    yield 93 %
    FAIL
    yield 38 %
    PASS
    yield 98 %
    target
    G6 HOM · S-3> 95 %PASS
    97.2 %
    PASS
    95.6 %
    PASS
    98.1 %
    target
    G8 drift · S-5< 5 mrad/minNOT RUN
    queued
    NOT RUN
    —
    NOT RUN
    —
    target
    Sample values for an illustrative pack. Thresholds come from the pack’s gates.yaml; the word is the verdict.

    9Typical Application

    Replacing the per-chip pile. On the left, what a team typically keeps by hand to answer the same questions for one chip. On the right, what it keeps with q-twin.

    Before: per chip, by hand

    1. 01Loss budgetspreadsheet
    2. 02Calibration errorscript per mesh size
    3. 03Interference visibilitynotebook
    4. 04Gate fidelityseparate model
    5. 05Drift intervalestimate in a doc
    6. 06Sensitivityone input at a time, by hand
    7. 07Design comparisontable copied between docs
    8. 08Where a number came froma footnote, if any

    After: one pack, every study

    my-chip/gates.yaml1 pack
    gates:  - { id: G1, name: loss,        study: S-1,      threshold: "≤ 4.0 dB",      status: target }  - { id: G4, name: calibration, study: S-2,      threshold: "mean ε < 1 %",  status: target }  - { id: G6, name: HOM,         study: S-3,      threshold: "> 95 %",        status: target } # corners, labels, figures and reports# come with every run

    Corners, evidence labels, figures and the report are properties of the run, not documents beside it.

    Table 9-1. Example packs

    ExampleModesWhat it shows
    4-mode test chip4loss, calibration and interference
    6-mode mesh6adds a post-selected two-photon gate
    16-mode mesh16adds an on-chip encoder for photonic AI

    3 example packs ship with q-twin, read-only. Copy one into a project to start, or begin blank with your own design. Their values are design targets, labelled as such.

    Describe one pack. See every gate before tape-out.

    Install the engine and the dashboard, copy an example pack, and run your first study. Every result arrives with its corner, its verdict and the evidence behind it.

    $ pip install -e ".[api,test]"
    10 Availability
    OptionStatusGet it
    Source (FSL-1.1-ALv2)SOONSource · soon
    Self-hosting guidePREVIEWGet started
    Hosted public betaPREVIEWRequest access
    CORNERSTONESOONGet notified
    Partner labs & foundriesACTIVETalk to us