On 7/26/19 11:25 AM, Przemek Klosowski wrote:
> On 7/26/19 4:09 AM, Dr. K. nick wrote:
>> Dear octave maintainers,
Having said that, I do support gnucap/Qucs/ngspice. I personally have
been using LTspice because once Mike Engelhardt made it run well on
Linux, it worked well for me in spite of the fact that I barely know
what I'm doing; the other tools assume more domain knowledge than I had
at the time.
Nowadays, with Kicad integration, I should probably try them
again---especially since LT is no longer independent and who knows how
the LTspice project will fare in the long term, e.g. if Mike retires.
The FOSS alternatives have the community development model working for
them, so in principle they should have a better long-term outlook.
for me, it came down to the fact that in LTSpice I can specify a nonlinear capacitor via a charge definition (Q = ...) rather than a capacitance definition (C = ...), and it has an undocumented bus feature that made convergence studies easy. I'm also lazy and like a built-in schematic entry tool. :)
I currently do a post simulation text export and then cut/paste into a spreadsheet or read into Octave depending on how involved the post processing will be. There are (closed source & proprietary, it seems) tricks you can play within LTSpice to force it to export time-aligned data, etc, but it would be nice to work on this outside of the program from uncompressed waveform data. I've also done some Octave driven scripting of schematic & netlist files for crude parametric analysis.