<@U01819B63HP> <@U016EM8L91B> Do you have any thoughts on the above questions ?
s
@Stefan Schippers @Tim Edwards Do you have any thoughts on the above questions ?
s
Please do not mix too many things together. If you want to run simulations and save to different files it is just better to use xschem to generate the netlist without ngspice commands, Then create a small ngspice file
test1.cir
containing a
.include netlist.spice
generated from xschem, add the
.control
section with the
tran
and
write
instructions and the input voltage source, and run ngspice directly on this. The simulation file should look something like this:
Copy code
* test simulation
vvin vin 0 pwl
+ time1 value1
+ time2 value2
...
.control
  tran ....
  write results1.raw
.endc

.include /path/to/xschem/generated/netlist.spice
Of course the above small wrapper file can be generated with a script, you decide how to do that. The .include is at the end since xschem closes the netlist with
.end
. You run ngspice with:
ngspice -i test1.cir
In the above bash script I don't know exactly what you are doing, however I see you call xschem with the -l option that is a 'set debug file' option that should not be used unless you are debugging xschem itself. Also do not tag directly the people since many are very busy. Posts can be read and whoever has an answer will help.
Also as a suggestion don't make your life complicated using filenames/dirs that are sooooooo long and with spaces in between. Xschem handles filenames and dirs with spaces (because windows users LOVE to use spaces everywhere, so I had to cope with that) but it is MUCH better to avoid using spaces in filenames and directories if you don't want to cross the quoting hell event horizon. I think also ngspice handles correctly spaces, but my suggestion based on experience with various circuit-to-layout flows (commercial and open source) is to avoid them (use an underscore and shorter names).
t
"_the quoting hell event horizon"---_I'm going to have to remember that one!
😄 1