I am a trimmed-down version of the RLC_Finder from rlc-04.py, Part 4 of the RLC Tutorial. The stuff required for parameter finding is omitted for clarity in this example file. However, as it does no harm to leave in, you would almost always to just put your subcircuit below a fully functional subclass of param.ParameterFinder in the same module as you used to do the parameter finding.

Method setup Undocumented

Inherited from ParameterFinder:

Class Variable Setups A subclass of Setups that you define to specify parameter names, analyzers, independent vectors, goal points, etc.
Instance Variable s An instance that I construct of the Setups subclass referenced in your subclass of me.
Method __init__

There are two different call patterns. One is for using Differential Evolution to find parameter values:

Method __getattr__ Looks to my subcircuit "parent" and then my Setups object s for attributes that I lack.
Method tableSources Called by analyzerPrep for each setup ID to possibly generate one or more TABLE sources.
Method analyzerPrep Call this with a setup ID to provide what the Analyzer for that setup will need when it is activated.
Method __call__ Call this to find best-fit alterable values for the circuit you've defined with your setup override method.
Method setupTestCircuit You must override this to define test circuitry for one or more setups.
Class _EmptySetups Undocumented
Method __init_pf My constructor calls this to do the full initialization in paramfinding mode, when no parameters are supplied.
def setup(self, f):
API Documentation for pingspice, generated by pydoctor at 2021-09-18 08:41:11.