Projects: Difference between revisions

Jump to navigation Jump to search

Projects (edit)

Revision as of 08:48, 3 February 2016

1,441 bytes removed ,  3 February 2016
→‎Interface to Electronic Circuit Simulator: removed for now, Iproposed this, but no longer have time to mentor
(→‎Interface to Electronic Circuit Simulator: removed for now, Iproposed this, but no longer have time to mentor)
Line 110: Line 110:


When tuning a SISO feedback system it is very helpful to be able to grab a pole or a zero and move them by dragging them with the mouse. As they are moving the software must update all the plotted lines. There should be the ability to display various graphs rlocuse, bode, step, impulse etc. and have them all change dynamically as the mouse is moving. The parameters of the compensator must be displayed and updated.
When tuning a SISO feedback system it is very helpful to be able to grab a pole or a zero and move them by dragging them with the mouse. As they are moving the software must update all the plotted lines. There should be the ability to display various graphs rlocuse, bode, step, impulse etc. and have them all change dynamically as the mouse is moving. The parameters of the compensator must be displayed and updated.
== Interface to Electronic Circuit Simulator ==
[http://sourceforge.net/projects/qucs/ Qucs] is a C++ based circuit simulation package. This project aims to improve the interface to the Qucs algorithms to allow the transient, i.e. time series, simulation of circuits in Octave within a larger ODE system simulation driven by Octave. Other possible goals would be to make other analysis types available directly from Octave. There is an existing C++ interface which is based on handle class syntax available in the development version of Octave. The Qucs interface is intended to have two modes, synchronous and asynchronous. The asynchronous mode uses qucs to solve a circuit between two given time steps (internally taking as many smaller time steps as required), returning only the final result. This method is well developed. The alternative synchronous mode is intended to give full control of the time steps to Octave, and it is this mode which requires more work. A simple synchronous interface exists which can be built upon.
'''Main Goals'''
* Improve the functionality of the transient solver interface by implementing a robust synchronous simulation mode that integrates well with Octave ode solvers, particularly those from the odepkg package from OctaveForge.
* Create interface to other analysis types (AC, DC, S-Parameter and Harmonic Balance)
* Packaging the interface for Octave, to make it available through OctaveForge


=Sparse Matrices=
=Sparse Matrices=
Crobar
39

edits

Retrieved from "https://wiki.octave.org/Special:MobileDiff/7666"

Navigation menu