[drahnoel]

Ok.

There are some components, where one needs to use initialDC=yes, because they have no initial conditions fields. Example: Diode. (With initial DC=0, they always start with 0V at t=0)

However, I want to have different initial conditions as initialDC=yes calculates. So, what I do is to force the voltages to the desired initial conditions using a voltage source. To make the voltage source not affect transient simulation, I add a 1H inductance in series. This way I emulate the InitCond element of ADS.

This is the workaround I am successfully using at the moment.

[drahnoel]

I cannot edit anymore

[drahnoel]

Yes you are right, I will edit.

Let’s say we have variable “signal” depending on variable “frequency”.

With the proposed syntax, you could do something like:

(signal/frequency)[2:3]

or

signal[2:3]/frequency[2:3]

What I propose is:

s = signal[2:3]

s/get_dependencies(s, “frequency”)

Now, that I think about it, this does not seem too usefull, as long as the dependencies are always bound to variables.

[drahnoel]

I also miss this feature. There is yvalue(…). There is range(…) . And there is octave post processing. I uploaded a script for python post-processing

[drahnoel]

Qucs, Qucs-S and QucsStudio are differnt things. QucsStudio is closed, Windows only and developed by Michael Margraf AFAIK. Some people use wine.

[drahnoel]

I found, that Qucs 0.0.19 does not have the problem. The dat file for an equivalent schematic contains following lines:

<Qucs Dataset 0.0.19>

<indep VAR1 10>

…

<indep VAR2 10>

…

<dep VAR4 VAR2>

…

<dep VAR3 VAR1>

 

[drahnoel]

My file uploads were restricted for security reasons, I try again as archive

Attachments:

1. qucsStudio.7z

[Author]

Posts