Commands
Operate on histories.
Each history records and stores a single scalar value during cycling. The interval is controlled by the history interval
command. Histories are created using the history keyword applied to a specific data type (for example zone history
or ball history
).
Please note that the history logic is not intended for the purpose of taking a very large number of histories. While the code will not stop you from taking tens of thousands of histories every step (or even more), the amount of data stored will quickly become unmanageable and might even fill up a hard drive.
History data is stored in a temporary file while the model is open, and this data is transferred to the save file when the model is saved.
History Commands
Was this helpful? ... | Itasca Software © 2024, Itasca | Updated: Dec 19, 2024 |