We don't have code that represents an individual component. That's because a component often doesn't have a distinct input and a distinct output. A resistor for example has two equal ends and the current that flows through it can go either way, depending on the voltages present on each side.fluffy_little_something wrote:So you model the overall output of the component so to speak, not the individual factors that lead to that output?
What we do have is a set of equations that describe the current over each component based on the voltages around them, and a matrix that connects these in nodes. It's really all about dealing with the relation of voltages and currents in the circuit as a whole - every component can have an effect on any other, hence it has to be looked at as a whole, not as a set of components.
Most filters in DSP literature otoh are based either on the abstract concept of poles and zeros, or they are a set of formulas working on the rather concrete concpet of "sample values" fed into components with distinct imputs and outputs. Former take capacitor impedance into account, latter don't. Former can't model non-linear behavior, but latter can. The method we use (which is similar to the way SPICE works) can do both and is thus closer to the reality of analogue behaviour than either of the standard methods.
Well, we're a dozen people. We need to access our stuff from wherever we are. That said, if anyone gets hold of the source code they'll still have a hard time understanding how it's doneYou have your development stuff on an online computer?! Well, the good thing is that you always have a backup copy in Utah
