Does anyone know how to disable the pop-up terminals that appear every time a sim kicks off? I am running PVT analysis and the screen gets littered with these terminals. E.g. In the below pic I am running 17 corners, hence creating 17 pop up terminals. Thanks.

I don't think there is a non xterm fork mode. But use of

exit

at the end of the spice scripts might cleanup the left over debris.

use "quit 0" at the end of your control block in the sim (you can set that up in xschem)

Maybe just

quit

without the 0 is better ? You surely don't want it to stomp over a valid error code when an error did occur. The main point I was making, with 17 copies of spice running, you ideally want to know (or having indication of) all 17 exited with 0 that ran in the same batch.

Great inputs! Thanks guys. I'll get around to trying this later and get back to you. Cheers

It is a convention in many opererating systems that a ZERO process exit status indicates success to the parent process that has visibility of that exit status. There is one kind of success and many kinds of failures ( but this isn't the place for my life story ). So the non-zero values provide a range to convey the reason for failure with a numeric course grained diagnostic code. When not explicitly providing the number after the

exit

directive you would hope ngspice will relay the status of the last operation that occured. Like a command shell does. This means when the ngspice script failed, it can terminates early, like half way though the script usually with error message. As the failed command is the last command that failure gets indicated via the status. If you provide the number after the

exit

then you are forcing what that exit status will be regardless for how successful the script was. Ideally maybe its possible to do something like

# this is pseudo code I don't grok ngspice
# enough to know if this is even possible

if exit_status == 0 {
  exit
}

This will only close the windows on scripts that successfully completed without error . This would provide you with UI feedback that everything was successful (because all the windows auto closed, those that remained open should have error reason visible at end of output). This is because it is unclear how to differentiate a successful batch of 17 runs to have all completed to a successful conclusion via any other means when run from xschem.

@Diarmuid Collins just replace the ngspice invocation command, removing $terminal (Simulation-> COnfigure simulators and tools):

@dlmiles Thanks for that great explanation. Clears things up for me that the safest way to close is with "quit 0". Cheers