This page presents an overview of all entities created and stored in the
database by the current user:
Hovering the mouse over the descriptive columns will bring up more
detailed information where applicable.
The last column in each table contains a number of action icons, which
are activated by clicking on the icons.
This action opens a pop-up window with a description of the selected
entity, and a summary of the input parameters used to generate it. Where
applicable, hyperlinks are provided to other entities used to generate
the entity being viewed (e.g., a link to the event list used to generate
a statistical model). File and plot links are available where applicable.
This action is a shortcut to the server page which was used to generate
the selected entity. When the page is opened, the stored parameters are
retrieved from the database so that the original input settings are
presented. The user can then repeat the run with modified parameters, or
repeat the run with the same parameter values when an input needed for
the run has changed (e.g. when a device geometry is updated, the effects
models that use it as an input need to be re-run).
This action deletes the selected entity from the database. The user has
to confirm the delete action. All entities depending on the selected
entity will be deleted as well!
Warning: this action is irreversible!
Users are encouraged to delete entities when they are no longer needed in order to free up space in the database.
As the models and tools on the server can be used in sequence, complex
dependencies can result. As an example, consider the following sequence
to generate a statistical model:
Suppose that the user then modifies the device geometry. This means that
all the downstream outputs (response function and statistical model in
this example) are no longer up to date with the device geometry.
- generate a device geometry;
- generate an effects response function;
- generate an event list (which in turn can use a response function);
- generate the statistical model.
These occurrences are flagged by the
icon. Hovering the mouse
over the icon will bring up a short description of where the dependency
chain is broken. The same information is also shown on the pop-up window
spawned by the action. On
the model and tool input pages, entities which are not up to date are
listed but are not selectable. It is the user's responsibility to
verify the consistency of the output chain by checking that no warning
icons are set.
Last modified on: 3 October 2011.