[Pyarie-users] Current events

[John P. M. <pen...@on...>]

Two issues:

1: Possible merge with SimPy.
Klaus is on vacation for a month, but he's interested in possibly 
merging some of the Pyarie functionality in SimPy, or creating a module 
that is usable with SimPy. For this reason, I'm splitting the tree. 
There will be a base system, that can be used by programmers and used 
with SimPy, and there will be the "bells and whistles" version that I am 
working on for the long term. This way, the base system should be 
available within a few weeks, after cleaning it up and re-organizing a 
bit (such as naming conventions). I'll create some simple documentation 
and sample models. Nicolas, if you want to include a somewhat simple 
version of your complex case model, we could make that part of an 
examples directory.

2: Current state list
I've made a list in the base class called System.state. This way users 
can access all current calculations (time t instead of t-1) without 
first defining this. There is also System.update_state() method which 
will update the System.state list. There'll be some documentation needed 
for this. The quick and dirty is that you can ignore it if it's not 
needed. If you need it (see testmodel.py or the examples directory when 
it's built), use the Python copy module to copy Model.vars to 
system.state. Then before returning each state variables value, make a 
call to self.update_state(index, result). Then each equation has access 
to the current timestep's value (time t) through self.state[index]. 
Accessing x[index] then gives the value at timestep t-1.

I'll try to get a beta version for the base system up soon, and put it 
on this and pyarie-announce.

Cheers,
-j
-- 
John Metta (yes, my name has indeed changed...)
http://oregonstate.edu/~penningj/
"A computer without windows is like a dog
     without bricks tied to its head."