Re: [Qucs-devel] asco and qucs

[asco d. <as...@gm...>]

Hello Stefan,

Please find below my comments to your questions.


On 8/24/06, Stefan Jahn <st...@gr...> wrote:
> Dear Jo=E3o,
>
>   in the upcoming release of Qucs 0.0.10 there will be an optimization
> component including the appropiate dialog for setting it up.  It won't be
> fully functional, yet.  When simulating a schematic where this optimizati=
on
> component is placed everything works as ususal except that the asco
> configuration file "asco.cfg" will be created in the ~/.qucs/ directory.
> Also the appropiate ~/.qucs/extract/ directory is created and the
> extraction set files for the goal variables are created there.

The ASCO optimizer does not require a file called asco.cfg. Is has to
have the same name of the netlist to be optimized.


>
>   With this functionality it will be easy to setup optimization.  You
> can then
>
>   $ cd ~/.qucs
>   $ cp asco.cfg netlist.cfg
>   $ asco -qucs netlist.txt
>
> and see what's happening.
>
>   Anyway.  I already wrote 1 or 2 mails to you where I request certain
> improvements in the optimizer usability.  If you are going to work on
> this we can continue implementing the optimization flow in Qucs using
> ASCO.

Still concerning the naming in ASCO, I have just remembered that the
input file is pre-processed into a file with 'tmp' for extension. This
file is then read, edited where still required and simulated
<hostname>.txt.

Step 1: read netlist.txt
Step 2: file from step 1 is pre-processed into <hostname>.tmp
Step 3: simulate <hostname>.txt, the result from the previous steps.

As you can see, the file in step 3 is different from the one in step
1. For consistency, all other files also have the <hostname> with the
appropriate extension. So, simply redefining where ASCO outputs its
results requires multiple inputs and not just one for $filename.dat as
you have suggested in a previous email.


>
> Cheers, Stefan.


Regards,
Jo=E3o Ramos