You are here

Role arrow

Interpretation

Role arrows join submodels that participate in some form of association, or where one is a satellite of the other. The following sections detail the mathematical methods invoked by the role arrow. In each case, a multi-dimensional matrix is created. The dimensions of the matrix depend on the number of role arrows used, and the different uses are therefore described in separate sections.

Condition

A condition model element is used to specify whether a submodel, or a potential instance of a multiple-instance submodel, actually exists.

How to add a Condition symbol

The condition symbol only has meaning inside a submodel. Therefore, you should make the submodel first, then add the condition symbol to it. This is not strictly necessary: you can add the condition symbol first, then construct a submodel around it, but it is better practice to construct the submodel first.

Reproduction

The reproduction symbol is used to specify the rate of creation of new instances of a population submodel by each existing instance. It thus differs from the migration symbol, which specifies the total rate of creation of new instances.

Migration

The Migration symbol is used to specify the creation of new instances of a population submodel during the course of a simulation. In contrast to the Reproduction symbol, which specifies this in per instance terms (i.e. the creation of new instances per existing member of the population), the Migration symbol determines the total number of new instances that are created.

Initialisation

The Initialisation symbol is used to specify the initial number of individuals in a population submodel.

Extermination

The mortality symbol is used to specify the conditions under which one instance of a population submodel is destroyed.

ECDF-MOLUSC notes and resouces

Child pages can be added using the link below.

Files can be attached to pages. See the Attachments section below the text edit field when editing a page.

 

Tags at the bottom of pages. They must be at the top.

Tags at the bottom of pages are not visible enough.

Reporter: 
jonathanm
Created: 
Tue, 15/04/2008 - 11:56
Updated: 
Sun, 04/05/2008 - 08:23

Find the version of glibc on your Linux installation

As of Simile version 5.0, glibc version 2.4 is required to run the Linux Simile build available from simulistics.com. (If you have an earlier version we may be able to build Simile for you. Let us know the version of glibc you have and other details of your Linux distribution.)

To find the version of glibc on most systems, including Debian, call the library as a program:

(uiserver)::~ > /lib/libc.so.6
GNU C Library stable release version 2.3.6, by Roland McGrath et al.

On Debian-based systems:

Page type: 

Undoing a mistake or unwanted automatic operation when editing a model diagram

Use undo/redo

When editing a model it can be easy (as is often the case with diagram editors) to make an addition or change you immediately wish you hadn't made. Returning the diagram to how it was before the change manually can be a nuisance involving several mouse manipulations and/or key clicks. Any change can be undone by using the undo button on the toolbar or pressing Ctrl z. You can undo changes incrementally by repeated undo operations and if you change your mind there is a redo button.

Page type: 

Pages

Subscribe to Simulistics RSS