Keeping Track of ModelsĬhild models are kept track of in the extension with an id number, starting with 0, and all communication from parent to child is done by referencing this number, henceforth referred to as model-id. Interactive models are good if you run a small amount of models, if you are writing a LevelSpace model and need to be able to debug, or if you need access to widgets during runtime. Typically you will want to use headless models when you are running a large number of models, or if you simply want to run them faster.
#Ls child model marcia full
#Ls child model marcia code
Once this is done, a model will be able to load up other models using the LevelSpace primitives, run commands and reporters in them, and close them down when they are no longer needed.Īsking and reporting in LevelSpace is conceptually pretty straight forward: You pass blocks of code to child models, and the child models respond as if you had typed that code into their Command Center. LevelSpace must be loaded in a model using extensions at the top of your model.
In this documentation, we will refer to models that have loaded LevelSpace and have opened models as 'parents', and to the models they have opened as 'children' or 'child models'. LevelSpace models are hierarchical, in that models always belong hierarchically to another model.
LevelSpace is an extension for NetLogo that allows you to run several models concurrently and have them "talk" with each other.