Analog Lab reference
Beta documentation
Start with the question, then choose the analysis.
A compact reference for the Analog Lab workflow, its five analysis modes, numerical limits, project JSON, and SPICE-like netlist export.
- 50
- components
- 25
- free components
- 8
- verified Beta starter examples 3 are public; none are formal lessons
- 5
- analysis modes
Mode selector
Five modes, five different questions
The rows come from the governed mode inventory; the explanations describe the intended question and the boundary of each result.
| Analysis | Use it to ask | Does not establish by itself |
|---|---|---|
| Operating point | Where do node voltages and branch currents settle in steady DC? | Startup, switching, or frequency behavior |
| Transient | How do voltages and currents change over time? | Small-signal frequency response |
| AC | How do small-signal magnitude and phase vary with frequency? | Large-signal time-domain distortion |
| DC sweep | How does a steady result vary while one DC value is swept? | Dynamic response to a time-varying event |
| Live | How does the modeled response change while I explore supported values? | A fully recorded, reproducible analysis setup |
Getting started
Build the smallest circuit that can answer the question
Place a reference node, source, and the components needed for one observable result. Check values and units, then solve the operating point before adding a more demanding analysis.
A practical first sequence is a resistive divider: predict the DC output, verify it, sweep the input, add a capacitor for a transient run, and then inspect the frequency response with AC analysis.
- Name the quantity and node or branch you intend to observe.
- Keep one reference node and a complete electrical path.
- Record the mode, range, step, and source values with the result.
- Compare the solver output with a hand estimate or limiting case.
Numerical boundary
A converged result is still a model
An analog solver searches for numerical solutions to component models. A floating circuit, incompatible values, a difficult nonlinear region, or unsuitable analysis settings can fail to converge or produce a misleading-looking graph.
Reduce a failing circuit, check the operating point, inspect units and references, and vary numerical settings deliberately. DigiSim does not replace manufacturer models, datasheets, tolerance or thermal analysis, safety review, or physical validation.
Files and handoff
Project JSON and a SPICE-like netlist serve different jobs
The versioned .analog.json project preserves a DigiSim Analog workspace. The .cir export is a text netlist for supported interoperability work; DigiSim Analog is not ngspice, and external SPICE tools can use different dialects and models.
Analog project and netlist exports are capability-gated by current plan policy. Guest work uses a single-browser draft, and the audited product state did not establish a public Analog share or embed surface.
Learning status
The formal Analog course has not started
The captured backend rows are simulation-verified Beta starter examples, not formal lessons. Use them to explore the current lab and analysis modes while course design is still pending; the published course totals exclude these examples.
Begin with a small, checkable circuit.
Open the Beta lab, solve one operating point, and record the question and settings before adding another analysis.