[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnucap-devel] [Qucs-devel] Qucs, Gnucap, and Google Summer of Code

From: al davis
Subject: Re: [Gnucap-devel] [Qucs-devel] Qucs, Gnucap, and Google Summer of Code
Date: Fri, 24 Mar 2017 21:12:50 -0400

On Fri, 24 Mar 2017 09:01:39 +0000
Richard Crozier <address@hidden> wrote:
> The Qucs solvers can be used as a shared library, qucsator is actually 
> just a thin wrapper for this library now. With special elements in your 
> circuit you can externally control voltage sources etc. at every time 
> step. This can run either 'synchronously' i.e., you set voltages etc. on 
> every single time step, or 'asynchronously', where you set voltages in 
> between multiple steps and they are interpolated at the next steps.
> Is it possible to do the same or similar with gnucap?

The short answer is yes, but what if it wasn't?

If that were the case, it would be a feature I would classify as part
of what we would use from qucsator in a joint project, one of the
reasons we all gain by working together.

Going the other way, I see recent emails asking about PLECS style
fast linearized solver and models, and also about adding a memristor
model. Does Qucs have a mechanism for this to happen?  Does Xyce???

That's what plugins are for.  Anyone can make plugins.  You don't need
permission.  Then they can be made available for everyone who wants
them, without rebuilding or reinstalling.

> Based on the above I also created a matlab/octave interface based on mex 
> files for direct data communication with the simulation during 
> simulation execution from these languages to allow joining to larger 
> simulations.

Mex files are plugins for octave.  Circuit simulators need plugins

reply via email to

[Prev in Thread] Current Thread [Next in Thread]