[Shannon Williams 2011.09.28 11:30 CST]
FYI - I am taking a course on writing iOS Apps for the iPhone and
iPad. My first iteration of the App will not use PCT. It will
operate as follows: based on initial conditions, Money from
individuals in society will flow to other individuals (and companies)
based on statistics that are configured for the App. In subsequent
versions, it will flow based on choices which are selected based on
statistics that are configured for the App. In the final versions, it
will flow based choices which are selected based on goals, where the
goals are determined by the environment available to each individual.
···
[From Adam Matić 2011.08.19.1045 CET]
Bill Powers (2011.08.17.0410 MDT)
This may be an opportunity to try Lazarus, which is (almost) a clone of
Delphi. It's free (GNU) and eventually will have full functionality.AM:
Sounds good. I'll try it out.BP:
The actor's control loop looks fine. Every control loop requires one
integrator in it for stability (and no more than one), which is a much
simplified version of stability requirements but it works. In your code the
control system shows up in this loop:step = cs.Step(a_goodx).round(2)
a_goodx = (a_goodx + step).round(2)... with the required integration in the second statement. I assume that
"round(2)" limits the variable to 2 decimal places of accuracy?? The control
system is defined in the method "Step", containing perceptual signal,
reference signal, gain, and output quantity.AM:
So I added an integrator without knowing what it is. Good.BP:
I suggest that you go on developing the actor further before adding more
shops. Give the actor an income, which adds to a_money on every iteration
(or 7th or 30th if pay arrives intermittently). Give the actor an assortment
of goods to want. Assign different loop gains to the consumer's control of
different goods, and different reference levels, as well as different
prices. Add a rate of use or depreciation for the goods, so they gradually
disappear from a_goodx and have to be replaced. This will allow the program
to iterate continuously instead of stopping, so you can print out the values
of variables and watch them change with time.AM:
Great, that'll be the be the next step. I had this idea of having to make a
large, table-sized, detailed blueprint of every loop and item that will go
in the model, before any programming could be done. This one step at a time
process made things start moving. Thank you for the suggestion.
I'll get back with the next version.
Best
Adam