[Ktechlab-devel] Converting to Eigen - patch for revision, ver.1

[P Zoltan]

On Thu, 13 Aug 2009 16:33:39 +0200, Alan Grimes <agrimes at speakeasy.net>  
wrote:

> Zoltan Padrah wrote:
>> ok, tuning the simulator for strange cases should be done some day.
>> First, I'd like to create something like this for ktechlab's simulation
>> process, so the implementation could be verified against it:
>> http://zone.ni.com/devzone/jsp/largeImage.jsp?imagename=/cms/images/devzone/tut/5(2)-5818.jpg&language=en
>> <http://zone.ni.com/devzone/jsp/largeImage.jsp?imagename=/cms/images/devzone/tut/5(2)-5818.jpg&language=en>
>>  Probabily at the end of this week i'll come with a drawing like that,
>> so we could discuss the details.
>
> That's called a flow chart, there are a set of standard symbols that
> should always be used on flow charts. For example, decision boxes are
> always drawn as diamond-shaped.
>
>

  I know flowcharts for quite some time; on the linked pictures the inner  
workings of a circuit simulator are shown, that's what I want to clearly  
define.

  A flowcode (let's do things with style :D) made with ktechlab, attached,  
shows the current operations when one step in the simulation is done. It  
seem to me that it's too complicated and inefficient. It can be seen that  
in Simulator::step() there are quite a few loops, and in each loop  
ElementSet::doNonLinear also makes  internal iterations. That's not  
needed, as far I know.

  My goal now is to make the test circiut (also attached) to run decently,  
without 100% processor usage. The big question is how to do it?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ktechlab_simulator_step.flowcode.bz2
Type: application/bzip2
Size: 2574 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/ktechlab-devel/attachments/20090821/59f5edf4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test-perf-000.circuit.bz2
Type: application/bzip2
Size: 796 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/ktechlab-devel/attachments/20090821/59f5edf4/attachment-0001.bin>