#114 Octave link broken

0.0.18
closed-fixed
nobody
None
5
2014-05-16
2013-06-28
Guilherme
No

Mike Brinson reported:

Recent code changes to Qucs-0.0.17 and Qucs-0.0.18 appear to have caused the
link between Qucs and Octave post processing to become broken. The problem is
as follows: when using Octave linked to Qucs for post-simulation data processing
the link works correctly the first time a simulation is run. However, subsequent simulator
runs fail to complete ( ie stick!). The attached Qucs project file demonstrates the effect.

See attached example

1 Attachments

Related

Bugs: #114

Discussion

1 2 3 > >> (Page 1 of 3)
  • Guilherme
    Guilherme
    2013-06-28

    Somehow the octave window is blocking other processes. You can run the schematic multiple times as long as you 'exit' octave before running again.

    Issues:
    1) Octave still uses Q3Process, the qcusator is using QProcess;
    2) Octave is assumed to be on the path;
    3) How can I get it to read ~/.octaverc, where I setup 'setenv ("GNUTERM", "X11")'. This is needed to get it to plot on Mac OSX.

     
  • MikeBrinson
    MikeBrinson
    2013-06-28

    Hello Guilherme

    Thanks for confirming the Qucs-Octave link problem.
    Qucsstudio uses SendSignal to link with Octave.
    SendSignal could be worth looking at - however Qucsstudio still
    uses Qt3 so it might not help.

    Best wishes.

    Mike

    Mike Brinson

    mbrin72043@yahoo.co.uk

     
    Last edit: Guilherme 2013-06-28
  • Frans
    Frans
    2013-06-28

    This should be fixed right now, I think it was an incompatibility between Q3Process and QProcess
    I have ported most Q3Processes now (some are remaining) and it seems to work now

     
  • Frans
    Frans
    2013-06-28

    This should be fixed right now, I think it was an incompatibility
    between Q3Process and QProcess
    I have ported most Q3Processes now (some are remaining) and it seems to
    work now

     
  • Guilherme
    Guilherme
    2013-06-28

    I made some further tweaks to get it working on my box. It looks good here.

     
  • Guilherme
    Guilherme
    2013-06-28

    • status: open --> accepted
     
  • Frans
    Frans
    2013-06-29

    Hi Guilherme, Yesterday I committed some code to port the octave Q3Process, which fixed the bug that the simulation would not finish the second time if an octave script was involved.
    A few hours later you committed some code, now my octave (ubuntu) does not start anymore.

     
  • Guilherme
    Guilherme
    2013-06-29

    Sorry for that. I saw your commits, however they were not working on my side (Mac OSX).
    We have to provide the full path to octave. It also need to be aware of the location of gnuplot. I tried to make the path to octave portable, and also injected the QucsDir into the octave process environment (under the assumption that gnuplot is also on QucsDir, '/usr/local/bin' in my case).

     
  • Frans
    Frans
    2013-06-30

    Maybe we should add a path to octave to QucsConfig. It should not be QucsDir, maybe OCTAVEBINDIR (OCTAVEDIR) is already occupied.

     
  • Guilherme
    Guilherme
    2013-07-01

    I think it makes sense to have a path to Octave. Environment variables should be looked first. Perhaps we could even add another tab to the 'Application Settings' which lists the registered tools and allow users to point to the used tools (octave, iverilot,...).

     
1 2 3 > >> (Page 1 of 3)