I remember in the Cadence environment there was a full GUI setup for simulations. However what most ...
s
I remember in the Cadence environment there was a full GUI setup for simulations. However what most designers did was to just get the circuit netlist out of the tool, then get an existing testbench (a text file) , make the necessary modifications , include the new netlist and run the simulator in a terminal window. All this outside the Cadence framework, since doing all setups with the GUI, with dialog boxes, checkboxes, text entries, forced designers to repeat these 'point, click, type' actions even if the new design was slightly different from an old testbench.
h
… then you know different circuit designers than me, I guess I came with the GUI crowd 🙂 I agree, this topic has the potential of opening a can of worms with an unclear benefit in the end and too much restrictions, so people will anyway bypass it. Maybe needs more thinking if really worth the effort…
👍 1
People really like to script nowadays, so in this sense
xschem
will produce the netlist, and the rest driven from scripts. For repetitive tasks this is the way to go, for circuit exploration I like a GUI-based approach since I quickly change between different simulations normally.
👍 1