|
|
|
|
Subject: RE: some questions
From: Hoekstra, J. (Jeljer) (jhoekstra@feweb.vu.nl)
Date: mer jan 09 2002 - 17:25:29 CET
Niek,
I also had your second problem and solved in the following way:
I created an empty init method
ninit
^nil
and added a method that changes all my parameters depending on n
ninit:n
init
" + something like"
parameter:= minvalue+(n*increment)
My nstep:times method has an extra line
nstep: t times: n
t = 0
ifTrue: [self ninit: n]
ifFalse:[self stepSynchronously: t].
As your initialisation method you choose ninit and as your evolution
method you choose nstep:times:
So whenever a new run starts it is pseudo-initialized by ninint:n, which
sets your parameter values depending on n.
A more elegant solution which I propose for cormas 2002 is to make it
possible to choose an init method that depends on n "when run ntimes" is
used.
cheers,
Jeljer Hoekstra
---------------------------------------------------------------------
Jeljer Hoekstra
Free University Amsterdam
Faculty of Economics
de Boelelaan 1105
1081 HV Amsterdam
tel. 020 4446168
fax. 020 4446004
---------------------------------------------------------------------
-----Original Message-----
From: Niek.Koning@Alg.AAE.WAU.NL [mailto:Niek.Koning@Alg.AAE.WAU.NL]
Sent: Wednesday, January 09, 2002 12:53 PM
To: cormas@cines.fr
Cc: Wiebe.Aans@Sg.OSA.WAU.NL; Annemarie.vanPaassen@Alg.VLK.WAU.NL
Subject: some questions
Happy new year,
I have worked further on the IronAge model that Wiebe Aans, Annemarie
van
Paassen and I constructed during the MAS-course in Wageningen. I now
have a
version which shows some interesting behaviour.
I now have a few questions:
1. When running an N-times simulation (with 'step: t nTimes: n') I only
get
graphs for the last run. I suppose something must be changed in the
updateCharts command, but what is it?
2. How can I systematically explore the model's behaviour for different
parameter values?
3. The model contains various stochastic elements and different
simulation
runs give quite different results. Nevertheless, there are certain
recurring
patterns, depending on parameter values. But which features of the model
exactly lead to these patterns is not so easy to see. What is the best
way to
examine this?
Greetings,
Niek Koning