Quantum Control Software Engineer

Trapped-ion control software from pulse intent to measurable evidence.

Deterministic timing, hardware adapters, photon acquisition, and evidence-gated calibration.

01 · TIMING

Measurement-aware pulse validation

Specify what real captures must prove across pulse width, alignment, phase window and repeatability.

Width · alignment · phase · repeatability 02 · ARCHITECTURE

Registry and adapter-driven control

Keep device I/O, qubit growth and future transport or photonic links outside orchestration branches.

Maintainable · extensible · observable 03 · VERIFICATION

Software simulation + electrical emulation

Exercise the same contracts through deterministic simulation and TTL/photon hardware before any ion claim.

No-ion failure-path coverage 04 · FULL STACK

OpenQASM → hardware → PMT evidence

Preserve circuit identity through primitive compilation, backend execution, photon acquisition and analysis.

Traceable circuit-to-photon ownership

IMPLEMENTED Control contracts and verification

Python orchestration, primitive compilation, deterministic simulation, TTL/photon emulation and traceable outputs.

INTEGRATION TARGET Spectrum microwave backend

M4i.66xx AWG/DDS adapter, multi-tone carrier control, SSB upconversion and hardware-specific APIs.

EVIDENCE BOUNDARY Claims stop where evidence stops

No personal Spectrum operation, eleQtron proprietary topology or physical-ion gate-fidelity claim.

01 · Measurement-aware timing validation

A timing claim is not complete until the scope agrees.

The interactive trace is a literature-informed model of the intended sequence. It defines the signals, timing relationships and acceptance questions that a real capture would need to verify.

Published parameter MW Qubit 1 · Gate operation Ref [2] · PRX 15, 021079 (2025)

A / ΩAmplitude: Ω₁ / 2π = 94.8 kHz
f / ωFrequency: f_μw ≈ 12.6 GHz
τDuration: 313 µs
φPhase: φ(t) = 0.749 sin(2π · 94.8 kHz · t)

Notation: A amplitude · Ω/2π Rabi rate · f frequency · ω/2π angular-frequency form · τ duration · φ phase · Δ detuning

Each channel has a fixed color. Pulse height is an ON/OFF envelope unless a paper reports intensity or Rabi frequency; stage widths are visually compressed.

Evidence boundary: this is a composite literature model, not one experimental shot and not eleQtron proprietary calibration. Ref [1] reports the cooling sequence at an axial frequency of 117.48(11) kHz; Ref [2] reports the MAGIC gate in a different setup at 98.08 kHz. Unpublished hardware settings are shown as N/R (not reported).

References: [1] Sriarunothai et al., J. Mod. Opt. 65, 560–567 (2018) · [2] Nünnerich et al., Phys. Rev. X 15, 021079 (2025) · [3] eleQtron · MAGIC uses radio-frequency control

Public-evidence system study

The scope is an engineering sidecar—not the shot-loop data plane.

University of Siegen apparatus descriptions place deterministic sequencing, detector acquisition and state discrimination inside the experiment loop. Oscilloscopes observe selected electrical nodes through probes or splitters for commissioning, validation and debugging.

Main shot loop · published Siegen lineage

01 · SchedulePython or host software compiles the experiment; a real-time sequencer owns TTL triggers and deterministic I/O.

02 · DriveAOM/EOM channels prepare and detect; AWG/DDS plus microwave conversion deliver coherent control.

03 · Fluoresce369 nm emission passes collection optics, spatial filtering and a narrow-band optical filter.

04 · AcquireEMCCD, PMT or SPAD data enters a frame grabber, counter, TDC, ADC or FPGA for classification and feedback.

Engineering sidecar · diagnostic taps

Laser lockPhotodiode, cavity transmission and error signal.
RF / microwaveIF envelope, trigger, mixer or crystal-detector output.
Clock / triggerTTL fan-out, camera-ready and AWG trigger alignment, skew and jitter.
Detector front endPulse amplitude, noise, threshold, saturation and signal integrity.

Software boundary

Python/SCPI can configure the scope, acquire waveforms and emit commissioning, calibration or monitoring artifacts. The real-time controller still owns shot scheduling, while detector interfaces and analysis software own structured photon counts, frames, timestamps and bright/dark decisions.

Not claimed: eleQtron's current oscilloscope vendor, bandwidth, sample rate, channel count or installed topology are not public.

System-study references: [4] Piltz, 2016 · EMCCD/PMT triggering and ADwin sequencing · [5] Huber, 2024 · AWG hand-off and image feedback · [6] eleQtron · Python control software and programmatic device control · [7] DLR QSea II · SPAD and control-electronics integration direction

Capture integrity

Requested window, sample depth and scope readback must agree. A plausible trace from a shortened pre-trigger record is rejected.

Shot alignment

All channels must share one record length, and the expected dark window must prove that the capture contains the intended shot phase.

Reproducible consensus

Repeated captures must agree numerically. A conflicting capture stays a disagreement; it is never averaged into a green result.

02 · Maintainable quantum control software

Turn physics intent into contracts the software can safely evolve.

I first confirm the experiment sequence, tunable parameters, timing owner, required hardware capabilities and acceptance evidence with physicists. Only then do I choose registries, adapters and tests that keep later requirement changes local.

Requirements-led maintenance Scale targets remain evidence-bounded

PHYSICIST ↔ CONTROL SOFTWARE · WORKING CONTRACT

Confirm the physics semantics before choosing the software pattern.

Maintainability starts before code. I turn a physicist’s experimental objective into explicit parameters, timing ownership, hardware capabilities, acceptance evidence and failure policy—then keep that contract stable while adapters and implementations evolve.

PHYSICS OWNER · DEFINES MEANING

What must happen in the experiment?

Stage purpose and order; physical observable; tunable quantities such as A / Ω, f / Δ, τ and φ; safe ranges; calibration assumptions; and what result would be scientifically acceptable.

CONTROL SOFTWARE OWNER · MAKES IT ENFORCEABLE

How can the system execute and prove it safely?

Typed schemas and units; deterministic versus host-side ownership; device capabilities; preflight rules; adapter boundary; readback and timeout behavior; test cases; provenance; and an explicit statement of what the evidence does not prove.

01 · ELICIT

Start from the observable—not the instrument command.

Capture the scientific objective, stage dependency, scanned variables, required resolution and unacceptable physical states.

02 · CONTRACT

Translate meaning into a typed experiment boundary.

Agree on names, units, ranges, timing class, channel ownership, calibration source, acquisition window and capability requirements.

03 · VERIFY

Define the evidence before implementation.

Choose simulator assertions, TTL/scope measurements, readbacks, photon-count checks and rejection conditions for each claim level.

04 · REVIEW

Review semantics and enforceability together.

The physicist checks that the sequence still means the intended experiment; the control engineer checks that every condition is executable, observable and fail-closed.

EXAMPLE CHANGE REQUEST

“Add a sideband-cooling cycle with tunable red-sideband π durations.”

Clarify the phonon-index model, pulse order, optical-pump window, settle time, amplitude policy, termination condition and which measurements demonstrate cooling behavior.

QUESTIONS BEFORE CODE

Resolve ambiguity while it is still inexpensive.

Which observable is the experiment optimizing?
Which parameters are scanned, calibrated or fixed?
Which timing belongs on FPGA/AWG and which stays host-side?
Which missing or stale condition must reject the run?
What evidence is sufficient—and what does it not prove?

MAINTAINABLE DELTA

One registry entry, bounded adapter work and shared tests.

Add or revise a StageSpec, capability mapping, calibration record and contract tests. The scan orchestration, GUI/API consumers and evidence model remain unchanged unless the shared contract itself changes.

Shared acceptance rule: physics review owns experimental meaning; software review owns executable constraints and evidence integrity. A requirement is not ready when either side still relies on an unstated assumption.

REQUIREMENTS → ARCHITECTURE

Design from reviewed laboratory constraints—not pattern names.

After the physics handoff is agreed, I map each requirement to an owned boundary: what changes, what stays deterministic, which evidence proves success and which failure must stop execution. Patterns are selected only after those boundaries are explicit.

01 · HETEROGENEOUS I/OConnect instruments with different protocols and timing semantics.

Laser locks, AOM/EOM RF chains, FPGA/AWG, PMT/EMCCD and oscilloscopes expose different transports, units, state models and failure modes.

ADAPTER · DIP · REGISTRY · FACTORYNormalize capability—not vendor syntax.

DeviceDescriptor declares capability; RFAdapterBase owns vendor I/O; the registry and factory resolve implementations for orchestration.

NON-FUNCTIONAL RESULTMaintainability · OCP

Device-specific change stays local. Consumers depend on a stable control contract instead of accumulating transport branches.

EXAMPLEAdd a Spectrum backend at the seam.

Implement and register an adapter, then run the same contract tests. Spectrum remains a labelled integration target—not a shipped claim.

02 · QUBITS / ZONES ↑Scale topology without multiplying orchestration branches.

More qubits introduce pair selection, channel ownership, calibration scope, zones, transport hand-offs and possibly photonic module links.

DESCRIPTORS · COMPOSITE · NULL OBJECTMake topology and routing data-driven.

Typed qubit, pair and lane descriptors feed one interface; composite adapters aggregate routes while deliberate no-op modes preserve the contract.

NON-FUNCTIONAL RESULTExtensibility · scalability

Registry and topology grow while the scan loop remains closed to vendor-, zone- or qubit-count conditionals.

EXAMPLEAdd shuttling or a photonic lane.

Register a scheduled transport or heralded-readout capability with explicit hand-off evidence; do not add if qubits > N.

03 · DETERMINISTIC SHOTSProtect pulse timing from slow control and UI latency.

Amplitude, frequency, duration and phase must execute on a deterministic timeline while configuration, visualization and analysis remain host-side.

HOST / REAL-TIME SPLIT · IMMUTABLE PLANCompile intent before entering the shot.

Preflight resolves units, capabilities and stage ownership; the backend receives an admitted pulse plan rather than live GUI decisions.

NON-FUNCTIONAL RESULTReliability · repeatability

Shot behavior is insulated from network and presentation jitter, with explicit timing and readback ownership.

EXAMPLEPort ARTIQ intent to FPGA or AWG/DDS.

The backend changes scheduling mechanics; the admitted stage contract and evidence schema remain stable.

04 · VERIFY BEFORE IONSCatch logic and wiring failures before a physical-ion claim.

Software correctness, electrical timing and ion behavior are different evidence levels and must not be conflated.

STRATEGY · TEST DOUBLE · SHARED PORTExercise the same contract through independent lanes.

Deterministic simulation tests logic; TTL/photon emulation and scope captures test electrical/dataflow integration using the production-facing interface.

NON-FUNCTIONAL RESULTTestability · automation

Unsupported capability, stale mapping, all-dark counts and timing drift become repeatable failure cases instead of lab surprises.

EXAMPLEQualify each new adapter in stages.

Contract tests → simulator → electrical capture → separately authorized physical-ion validation. No lane upgrades another lane’s claim.

05 · SAFE, TRACEABLE RUNSStop incomplete operations and retain why a result was accepted.

Missing devices, stale health, timeouts, saturation or absent provenance must become terminal states—not silent warnings.

PREFLIGHT · DECORATOR · EVIDENCE BUNDLEWrap execution with health and admission.

HealthTrackingAdapter(inner) observes without rewriting drivers; run ID, configuration hash, readbacks and limitations travel with the result.

NON-FUNCTIONAL RESULTObservability · traceability · fail-closed safety

Operators and maintenance agents can locate the owner, reproduce the configuration and distinguish rejected from accepted evidence.

EXAMPLEAdd a sensor or collector independently.

Register its freshness and acceptance policy; preflight blocks the run when required evidence is missing, stale or invalid.

OCP EXTENSION PROTOCOL

One safe path from requirement to supported capability.

Each step has a named artifact, so a human or maintenance agent can extend the system without discovering architecture by trial and error.

01Declare capabilityUnits, timing class, stage ownership and evidence needs.

02Implement adapterKeep transport and vendor state inside the boundary.

03Register factoryResolve by descriptor; orchestration stays unchanged.

04Run contract testsSimulator and emulator exercise the same port.

05Attach evidenceReadback, health, provenance and failure collectors.

06Admit or rejectPreflight fails closed before deterministic execution.

Implemented evidence: scan_engine/device_plugins/, scan_engine/rf_adapters/, scripts/run_artiq/gateway.py, internal/registry.py and internal/obs/collectors.py. Spectrum, shuttling, photonic links and large-scale physical-qubit operation remain explicitly labelled extension targets.

Open/Closed Principle · implemented

Extend capabilities without rewriting orchestration.

OCP is the extension policy behind the system: hardware backends, fit models, compiler/simulator backends and observability sources enter through registered contracts. The scan loop and evidence pipeline consume the stable interface instead of accumulating vendor-specific branches.

OPEN FOR EXTENSION

Add a capability at an owned seam

Declare a DeviceDescriptor and hardware adapter.
Register a fitter, compiler, simulator or collector.
Add future Spectrum, shuttling or photonic-link adapters.

CLOSED FOR MODIFICATION

Keep the control core stable

Scan orchestration and stage sequencing.
GUI/API consumers derived from the registry.
Preflight, readback and evidence contracts.

stable core + registered extension + contract tests = new capability without an orchestration rewrite

Design patterns · verified in source

Architecture choices visible in code.

These are not decorative labels. Each pattern isolates one form of change so hardware growth, analysis extensions and test doubles remain independently maintainable.

PLUGIN / REGISTRY

Discover capabilities from declarations

DeviceDescriptor, BackendRegistry and fitter/collector registries make new implementations discoverable without editing each consumer.

ADAPTER + DIP

Depend on control contracts

RFAdapterBase and ArtiqGateway isolate vendor I/O. Orchestration depends on the interface; concrete drivers own transport details.

FACTORY

Resolve implementations centrally

create_rf_adapter() selects a registered backend, so callers never construct vendor-specific classes or duplicate selection logic.

DECORATOR

Add health telemetry by wrapping

HealthTrackingAdapter(inner) delegates the adapter contract while adding watchdog and failure-state observation without changing the driver.

STRATEGY

Swap algorithms behind one contract

Fitters, compilers and simulators are selected by name through registries, while execution code consumes a stable result and backend contract.

COMPOSITE + NULL OBJECT

Preserve one RF interface

CompositeRFAdapter routes mixed devices; NullRFAdapter provides deliberate no-op behavior. Both remain valid adapter implementations.

Code evidence: scan_engine/device_plugins/ · scan_engine/rf_adapters/ · scan_engine/fitting/registry.py · internal/registry.py · scripts/run_artiq/gateway.py · internal/obs/collectors.py. Spectrum M4i.66xx, shuttling and photonic links remain extension targets—not implemented hardware claims.

Agent maintenance loop

1 · Read contractLocate registry, dataset owner and evidence boundary.
2 · Add adapterKeep device-specific I/O outside orchestration.
3 · Run guardsCatch drift, stale mappings and unsupported paths.
4 · Emit evidenceRetain provenance, limitation and terminal outcome.

Laboratory boundary · engineering-domain lenses

Apply the same contracts across optics, control and measurement.

This apparatus view supports the software argument: choose a domain to expose its owned boundaries on the same optical table. Select a component to trace its signal path and inspect control, observation and fail-closed ownership.

FUNCTIONAL OPTICAL TABLE · NOT TO SCALE PD · LOCK TAP RF · ENVELOPE TAP FR / ISO HWP · PBS PM FIBER FR / ISO HWP · PBS FC · COLL FR / ISO HWP · PBS TELESCOPE QWP UHV VIEWPORT NA OBJECTIVE IRIS BP 369 BS BEAM PATHS · DIAGNOSTIC TAPS DASHED

MEASUREMENT BUS Observe without perturbing shot orchestration. Diagnostic sidecars and acquisition adapters retain independent evidence limits.

SYSTEM OVERVIEW · FUNCTIONAL MODEL · CALIBRATION N/R

Coupled laboratory control boundaries

Optical delivery, deterministic electrical control and measurement evidence remain separate contracts inside one shot.

CONTROL: Typed capabilities define amplitude, frequency, duration, phase, timing owner and acquisition window.
OBSERVE: Lock state, Scope timing, ADC/counter acquisition, detector readiness and run-scoped evidence are independently observed.
FAIL CLOSED: Does every requested operation resolve to a supported device contract with current evidence before execution?

OPTICAL COMPONENT LEDGER · ENGINEERING INTENT

Every optic owns a physical variable.

The control system does not treat a laser as one boolean channel. Frequency, optical power, polarization, spatial mode, pointing and readout collection each require a component, calibration owner and monitoring signal.

01 · SOURCE PROTECTION + LOCK

Faraday rotator / isolator · pick-off · reference cavity

Reject return light, expose a diagnostic fraction and stabilize laser frequency without placing the slow lock loop inside shot timing.

CONTROL: PZT, current and temperature setpoints
MONITOR: lock state, error signal, cavity transmission, optical pick-off

02 · POWER + POLARIZATION

HWP · QWP · PBS

HWP + PBS sets or splits linear-polarized power; the final QWP prepares the required σ/π polarization components relative to the quantization axis.

CALIBRATE: waveplate angle, extinction ratio, delivered polarization
MONITOR: power before/after PBS and polarization checks

03 · PULSE + FREQUENCY

AOM · EOM · RF driver

The AOM owns fast switching, envelope and frequency offset; the EOM generates sidebands. RF amplitude becomes diffraction efficiency or modulation index—not optical power by assumption.

CONTROL: A, f, τ, φ, blanking and settle time
VERIFY: RF envelope, diffraction order, sideband spectrum, residual light

04 · SPATIAL MODE + POINTING

PM fiber · fiber coupler · collimator · telescope

Fiber delivery suppresses source-pointing drift; collimators and a telescope set beam diameter, divergence and waist at the interaction region.

CALIBRATE: coupling efficiency, collimation, waist and focus
MONITOR: input/output power and pointing stability

05 · ROUTING + VACUUM INTERFACE

Mirror · dichroic · beam combiner · UHV viewport

Mirrors route one wavelength; dichroics combine or separate wavelengths; the viewport and focusing optics preserve alignment into the trap while stray UV on electrodes must be controlled.

OWNERSHIP: wavelength path, coating range, alignment reference
LIMIT: exact angles, coatings and installed geometry remain N/R

06 · FLUORESCENCE READOUT

NA objective · collimating/focus lens · iris · bandpass · beam splitter

Collection NA sets photon capture; apertures and the 369 nm filter reject scatter; PMT analog output can enter an ADC while TTL pulses enter a photon counter, and EMCCD remains the imaging lane.

CONTROL: sample/count clock, acquisition gate, exposure window and detector route
MONITOR: background, overrange, saturation, threshold margin and missing records

PROGRAMMABLEElectrical intentRF amplitude/frequency/phase, TTL gate, duration and trigger.

CALIBRATEDOptical consequencePower, modulation index, polarization, waist, focus and pointing.

OBSERVEDRuntime evidenceLock/readback, pick-offs, RF envelope, counts, frames and limitations.

Primary apparatus anchors: Sriarunothai’s Siegen thesis documents the 369 nm AOM branches, 935 nm EOM, HWP/PBS/QWP, polarization-maintaining fiber with collimators, reference resonator, collection lenses, blades/irises and PMT/EMCCD routing (§§3.5–3.8). A separate compact ¹⁷¹Yb⁺ laser-system paper demonstrates multi-wavelength fiber delivery (Mulholland et al.). These sources support component roles, not eleQtron’s installed table.

QUBIT COUNT ↑ Registry and topology grow—not orchestration branches.

Stability comes from typed capabilities, deterministic scheduling, readback, health collectors and evidence-aware admission. Large-scale physical-qubit operation remains an architecture target, not a demonstrated result.

Evidence boundary: this is a functional integration model built from implemented logical control contracts and cited ¹⁷¹Yb⁺ literature—not eleQtron’s proprietary optical-table layout. Beam geometry, polarization, optical power, modulation index and installed instrument models remain N/R unless independently evidenced. Spectrum M4i.66xx is shown only as a documented integration target.

03 · Timing verification system

Test the same contract through two independent realities.

A fast deterministic simulator checks logic and data contracts. An electrically live lane runs the production hardware-timed control core with real TTL/DDS envelopes and a controlled photon source—still without ions.

Verification lanes implemented

LANE A · SOFTWARE

Deterministic software simulation

Compile the exact primitive OpenQASM, execute synthetic counts and verify repeatable evidence without lab network access.

Same primitive circuit and execution contract
Deterministic replay and evidence hash
Freshness, all-dark and capability failures are injectable
Proves software behavior—not RTIO or wiring

LANE B · TTL / PHOTON EMULATION

Electrically live control path

The production control core runs on the test master; a scope observes physical 369/935 envelopes while controlled TTL photon pulses exercise the counter/readout chain.

Real FPGA-backed scheduling and deterministic timeline
Scope-visible DDS/TTL timing envelopes
Controlled photon counts through the acquisition boundary
Proves electrical/dataflow integration—not ion physics

Fail-closed evidence ladder: software-sim results cannot enter calibration; electrically live results cannot claim state preparation or gate fidelity; physical-ion verified capability remains explicitly separate.

04 · Circuit-to-photon full stack

Own every boundary from algorithm to evidence.

The system does not stop at compilation or pulse generation. It carries circuit identity through execution, photon acquisition, analysis and a claim that includes its own limitation.

OpenQASM → control contract → counts implemented Spectrum M4i.66xx AWG/DDS: integration target

The diagram distinguishes implemented software contracts from the publicly documented eleQtron microwave backend, which is presented as an integration target rather than personal hands-on evidence. Horizontal scrolling is available on narrow screens.

PUBLIC ELEQTRON QUBIT-CONTROL PATH · REF [4]

Python contract to microwave carrier.

Python / control services
↓
Spectrum M4i.66xx AWG + M4i.66xx-DDS
↓
SSB mixer + microwave LO
↓
f_μw ≈ 12.64 GHz → ¹⁷¹Yb⁺ MAGIC processor

Spectrum’s official eleQtron case study identifies the M4i.66xx series as the microwave qubit-control AWG family. The control-software and FPGA boundaries are consistent with eleQtron’s public engineering roles: Python APIs/data interfaces above hardware-specific I/O, and FPGA signal generation plus real-time feedback below.

f_kcarrier frequency φ_kcarrier phase A_kcarrier amplitude df_k/dtfrequency slope dA_k/dtamplitude slope

16 bit · up to 1.25 GS/sPCIe AWG family; one, two or four synchronous channels.

k = 1…20 carriers/outputEach carrier exposes f_k, φ_k, A_k, df_k/dt and dA_k/dt.

Δt_cmd ≈ 6.4 nsf_μw ≈ 12.64 GHz after SSB mixing; Δf_ion ≈ 3–5 MHz.

References: [4] Spectrum Instrumentation · DDS technology enables microwave ion control for quantum computing · [5] eleQtron · Senior Software Engineer—Python control software · [6] eleQtron · FPGA Engineer—Quantum Computing

Claim boundary: the public source confirms the M4i.66xx series, not an exact installed submodel. M4i.6631 appears in the article image caption only. No claim is made about eleQtron’s laser, camera, trap-DAC or laboratory-wide sequencer stack.

Selected research · application bridge

Translate application questions into executable quantum workflows.

Collaborations across quantum machine learning, generative chemistry and quantum chemistry gave me a working vocabulary on both sides of the interface: domain objectives and benchmarks on one side; circuits, simulators, hardware constraints and defensible evidence on the other. Google Scholar profile ↗

01 · ASKApplication objective & success metric

02 · MODELPhysics assumptions & algorithm choice

03 · EXECUTECircuit, backend & resource constraints

04 · EXPLAINEvidence, benchmark & limitations

QUANTUM MACHINE LEARNING · PREPRINT

Unentangled quantum reinforcement learning agents in the OpenAI Gym

First author · arXiv:2203.14348 · 2022

Application → experimentTurned standard reinforcement-learning tasks and metrics into a single-qubit variational workflow, classical post-processing and execution on real IBM quantum machines.

Read the arXiv preprint

GENERATIVE CHEMISTRY · JOURNAL

Exploring the Advantages of Quantum Generative Adversarial Networks in Generative Chemistry

Co-author · J. Chem. Inf. Model. 63, 3307–3318 · 2023

Domain objective → hybrid modelConnected small-molecule generation goals to hybrid quantum-classical GAN components, then compared physicochemical, goal-directed and validity trade-offs.

Read the ACS paper

QUANTUM CHEMISTRY · JOURNAL

Quantum simulation of preferred tautomeric state prediction

Co-author · npj Quantum Information 9, 102 · 2023

Scientific workflow → resource constraintsMapped a drug-discovery question through active-space selection, qubit-efficient encoding and VQE while retaining benchmark and hardware-resource limits.

Publisher-stated contribution: performed noiseless and noisy quantum simulations with Yu Shee.

Read the npj paper

These publications evidence cross-domain collaboration in quantum applications. They complement—but do not replace—the separately labelled software and electrical evidence for the trapped-ion control system above.