You are here

Using a submodel to extract a part of a model

For the model described above, you may want to see how the vegetation part behaves, assuming fixed inputs from the animal and soil sections that affect it. You draw a submodel envelope around the vegetation, open up a separate window for it, then use the File: Save command to save it to a file. You can then start up Simile again, and load just the saved vegetation submodel (which is now a model in its own right). You can now explore how it behaves by itself. This can be very useful for testing and debugging purposes.

Using a submodel for multiple views on a model

Once part of a model is made into a submodel, you can open up a separate window for it (by double-clicking on its boundary). This window can be kept on the screen while you scroll the main model diagram to some other part of the model. Also, you can change the zoom factor for each main model window or submodel window separately, enabling you to see part of the model in fine detail while maintaining an overview of the whole model at a coarser scale.

Using a submodel to show the main components of a complex model

You have constructed a model with a number of compartments and flows. Some relate to vegetation; some to the animals in the area; some to soil water and nutrients. By grouping the model-diagram elements for these different parts into submodels (called 'Vegetation', 'Animals' and 'Soil'), the gross structure of the model is immediately apparent.

Introduction

A submodel in Simile is a way of bundling up a number of model elements, including other submodels. This is done by either drawing a submodel envelope around a number of elements in the model diagram, or by creating an empty submodel and inserting model elements into it. However, the reasons for wanting to do this are many and varied, and it is important to appreciate that the submodel construct can be used for a range of modelling needs.

Add the Model Gallery

Use a nested Drupal book or just a wholesale copy?

I would prefer not to use a table for the for the index page. Drupal book would make it even easier to add more.

As Drupal book

 

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 18:43
Updated: 
Sun, 02/03/2008 - 16:24

Model examples index page added

Would it be better not being a a table - less regimented? The information is basically the same though.

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 18:38
Updated: 
Tue, 18/03/2008 - 13:23

Software pages

Could just copy the original pages across, initially.

Could later have a projects based set of pages as the Drupal download pages. Customers allowed to a Standard or Enterprise download.

The credit card page would act as a door keeper. Purchase would allow registration as a Standard or Enterprise user.

 I've copied /products/index htm The links need  checking. Some pages to be added.

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 18:28
Updated: 
Mon, 03/03/2008 - 20:06

Drupal version of model repository (catalogue)

JM added some lots more to do.

Model entries have their own content type and so have their own menu command in the Add content menu.

Having a seperate content type allows cataloguing entries using a view, examples/catalogue/index.html

We agreed at the meeting on Wed 27/2/08 that Mark would take over adding the entries. Also do cast an eye over the implementation. Call/email if you want to ask anything and if you have suggestions for improvements.

Required for the publishing of the site 2 April 2008.

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 17:57
Updated: 
Fri, 12/10/2012 - 09:23

Update the Guided tour

Rewrite as attractive introductory web material.

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 17:55
Updated: 
Fri, 12/10/2012 - 09:07

Update Applications section

We barely started this section and stopped while promising more.

Priority is relatively minor before the site is pubished 2 April 2008.

Reporter: 
jonathanm
Created: 
Mon, 10/12/2007 - 17:52
Updated: 
Fri, 12/10/2012 - 09:09

Pages

Subscribe to Simulistics RSS