How p-rer/invertersimulation works
Project type and purpose
• This is a domain-specific simulation tool (a SPICE-like inverter circuit simulator).
• Purpose: parse a netlist, build an in-memory circuit model of components (resistors, capacitors, inductors, transistors, sources, etc.), run nodal analysis or transient analysis, and report results.
File structure
• Top-level:
• main.py – entry point (CLI or script)
• README.md – high-level description
• Circuit/ – holds the Circuit class (graph, node management, etc.)
• CircuitElement/ – one file per element type: BJT, R, C, L, diode, voltage/current sources
• Simulator/ – core engine: NetlistParser.py and Simulator.py
Key insights from README
• “インバータ回路シミュレーション” (= inverter circuit simulation)
• “Spiceと同様の解析を行う” implies support for netlist parsing, component stamping, solver routines
Main components
a. CLI / User Interface
• main.py
b. Netlist Parser
• Simulator/NetlistParser.py
• Responsibility: read text netlist, produce component definitions and connectivity
c. Circuit Model
• Circuit/Circuit.py
• Holds nodes, element registry, adjacency, trimming, stamping hooks
d. Component Library
• CircuitElement/*.py
• Each subclass implements stamping into system matrices
e. Simulation Engine
• Simulator/Simulator.py
• Implements analysis (e.g., DC operating point, transient), matrix assembly, solver calls
f. (Optional) Output / Reporter
• Could be part of main.py or Simulator output routines
Architectural patterns and design principles
• Modular separation: parser, model, solver, and elements decoupled
• Strategy / polymorphism: each CircuitElement stamps its own contribution
• Single Responsibility: NetlistParser only parses; Circuit only manages structure; Simulator only runs analysis.
Technologies and libraries
• Another for “domain classes” (green)
• A third for “external libraries” or “utilities” (gray)
a. Sketch a central “Simulator App” boundary.
g. “External Solver Library” connected to “Simulation Engine”.