GroIMP wiki

a part of grogra.de

User Tools

Site Tools

Trace:
You are here: GroIMP documentation » Platform documentation » Visual modeling » RGG modeling » XL-Console
01_user_documentation:04_modeling:03_rgg_modeling:02_console

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
01_user_documentation:04_modeling:03_rgg_modeling:02_console [2025/05/28 16:23] – sophiewachtel01_user_documentation:04_modeling:03_rgg_modeling:02_console [2025/08/19 14:46] (current) – gaetan
Line 1: Line 1:
 ~~NOTOC~~ ~~NOTOC~~
-====== Console ====== 
- 
-The XL-Console is used to run RGG commands on the model without recompiling it, which can be helpful for analyzing or manipulating the model during a simulation. Try to type ((*Model.A*)), that will list you all A's in your simulation. If you press the run button in the RGG toolbar(1) and run the command in the console again there will be more output. On the right you can see a history of the last commands you used. Why can't we simply write ((*A*))? Try it, and you will see an error message. In fact, the XL console is outside of the Model (which is an RGG class), so we need to tell GroIMP that we want to access the module A that only exists in Model.rgg.  
- 
 ==== XL-Console ==== ==== XL-Console ====
  
 The **XL-Console** in GroIMP provides a way to interact directly with the RGG model during runtime. It allows the evaluation of expressions without recompiling the entire model,  which can be helpful for analyzing or manipulating the model during a simulation. The **XL-Console** in GroIMP provides a way to interact directly with the RGG model during runtime. It allows the evaluation of expressions without recompiling the entire model,  which can be helpful for analyzing or manipulating the model during a simulation.
 +
 +
 +====== ======
 +
 +{{:01_user_documentation:03_interacting_with_groimp:02_panels:02_rgg:xl_console.png?400|}}
  
 Commands entered in the XL-Console are evaluated in the context of the currently loaded model. However, the console operates *outside* of the RGG class structure, meaning it does not have implicit access to members defined within the 'Model' class. For example, accessing a module 'A' requires the fully qualified form 'Model.A'. Attempting to access 'A' without the class prefix results in an error, as the console cannot resolve it in its own scope. Commands entered in the XL-Console are evaluated in the context of the currently loaded model. However, the console operates *outside* of the RGG class structure, meaning it does not have implicit access to members defined within the 'Model' class. For example, accessing a module 'A' requires the fully qualified form 'Model.A'. Attempting to access 'A' without the class prefix results in an error, as the console cannot resolve it in its own scope.
Line 14: Line 15:
 The XL-Console is tightly coupled with the runtime state of the model. When a public method from the RGG toolbar is executed, the resulting changes to the model are immediately reflected in subsequent console evaluations. The XL-Console is tightly coupled with the runtime state of the model. When a public method from the RGG toolbar is executed, the resulting changes to the model are immediately reflected in subsequent console evaluations.
  
-====== ====== 
  
01_user_documentation/04_modeling/03_rgg_modeling/02_console.1748442233.txt.gz · Last modified: 2025/05/28 16:23 by sophiewachtel