Put in this panel all variables that will be used by the Batch object itself but also by any other simulation objects. Typically, the Batch object contains various variables that change at each iteration, based on various user strategies or based on result of the past runs. Each new run might use the Batch variables to setup their initial values.
Part called as soon as the called scenario terminates.
Do here all the variable modification requested for the next scenario run.
Must return AGAIN if a new batch iteration is requested. Return DONE if the batch object must be left. Next connected Batch object will be activated. If none, batch mode is terminated.
Return QUIT if the batch mode must be terminated.
To check the number of iterations, use variable cIter() inside the code.
Put here the code that will be evaluated every second during the simulation run.
If code returns AGAIN, the Batch object remains active. If it returns DONE, the batch object stops the scenario the same way as using R:stop() into the code.
