Parent Directory
| 
Revision Log
| Sticky Revision: |
Finally fixed the SolverReporter problems. Thanks Marcelo!
Fixed the SolveReporter functionality so that it works from Python
Added wrapping of slv_status_t (SolverStatus) for bug #138. Improved 'About...' box.
Fixed bug #227
Added ability to output structural singularity analysis.
Fixable vars added to interface (outputs to console) Added 'next big' and 'prev big' to move between 'big blocks' in the diagnose window.
Added cursor to report mouse-over variable and residual
Colours fixed, zooming works, active block focussed by default.
Added reporting of divergent relation names. Found more convergent form of LMTD heat-exchanger equation
Improved behaviour of incidence matrix when you mouseover points outside the matrix Stopped emitting exception for Block out of range (why does it happen?)
Made it so that fixed variables never get an icon.
Adding preliminary support for showing variable solve-status in browser view
Added reporting of unconverged variables to the console
Implemented editable 'active' row in observer Move focus of to active row when new row added and observer tab already focussed
Incidence matrix now reports the mouseover-ed variable on the console
Something resembling an incidence matrix returned via SWIG...
Solverparameters GUI code split into separate file. Help launcher started, will need more work. Corrected wrong cpu_elapsed values in GUI by direct use of tm_cpu_time() Added 'about' box. Fixed 'auto' menu option.
Added const-ness to 2nd parameter of slv_set_char_parameter. Implemented setting of int, real and string parameters via PyGTK interface.
Added menu bar at top of PyGTK interface. 'Preferences' menu currently just outputs the number of solver parameters in use. Plan is to allow the parameters to be viewed and edited via the GUI.
Added ability to output expressions from PyGTK interface. Expressions are output to the console using WriteRelationString. You must right-click on a relation an hit 'properties'.
Improved status reporting for solvers. When a solver is going slowly, you'll get a fair bit of output. If it's going fast there shouldn't be much input at all. Todo: use some kind of callback technique to get this information back to the GUI.
- Simplifying many 'error_reporter' calls with new macros:
ERROR_REPORTER_NOLINE and ERROR_REPORTER_HERE
- Adding some cygwin cases in the PyGTK build.
Added wait-cursor during compile/build, started working on correct destruction of Simulation objects.
Removing debug output, adding self_test to iapws95.
Fixing bug #178.
Working on a test case for bug #178
Committed changes to C++ solver class to accommodate new slv_lookup_client. Still seeing bug #178 though.
Adding the PyGTK interface to CMU repository. Whaddyareckon?
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| john.pye@anu.edu.au | ViewVC Help |
| Powered by ViewVC 1.1.22 |