howtos:debugging:model_debugging_in_samm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
howtos:debugging:model_debugging_in_samm [2011/06/24 13:48] chris.strashok |
howtos:debugging:model_debugging_in_samm [2011/06/24 17:54] (current) chris.strashok |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| Note that each of these options can be used alone or in combination with one another depending on your requirements. | Note that each of these options can be used alone or in combination with one another depending on your requirements. | ||
| - | ===== Using TOOL Code ===== | + | ===== TOOL Code ===== |
| + | |||
| + | You can also programatically incorporate debugging features in your Documeter code. This method is more flexible than setting the SAMM Preferences as you can pick and choose what code you want to debug. However you need to remember to when using this method you need to [[howtos:update_code_diagram|re-load any calculators that you have modified beck into SAMM]]. | ||
| + | |||
| + | ==== single step and display output objects ==== | ||
| + | |||
| + | You can activate the **single step** and **display output objects** debug features in your Documenter code by adding the following lines of code around the section you are interested in debugging. | ||
| - | You can also programatically activate the **single step** and **display output objects** debug features by adding the following lines of code in your Documeter code around the section of code you are interested in debugging. | ||
| <code> | <code> | ||
| $singleStep = on | $singleStep = on | ||
| Line 48: | Line 53: | ||
| Note: | Note: | ||
| - | * you need to ensure that the tool.links is properly configured to call Table or Graph as soon above. | + | * you need to ensure that the tool.links is properly configured to call Table or Graph as shown above. |
| * once you change the code in Documenter you will need to [[howtos:update_code_diagram|re-load the calculator into SAMM]] | * once you change the code in Documenter you will need to [[howtos:update_code_diagram|re-load the calculator into SAMM]] | ||
| - | ===== seeshape, table and display ===== | + | ==== seeshape, table and display ==== |
| - | In addition to these features outlined above there are a number of tools that are useful for debugging your model. | + | There are also a number of tools that are useful for debugging your model. |
| * **seeshape** - many of the model errors that occur are the result of objects that are misshaped (i.e. the object has to many dimensions, not enough dimensions, the dimensions are out of order, the units of measure is inconsistent and/or the data type is inconsistent). As the name implies the seeshape tool displays the shape of the specified object allowing you to see how the object has been defined and track down any inconsistencies. | * **seeshape** - many of the model errors that occur are the result of objects that are misshaped (i.e. the object has to many dimensions, not enough dimensions, the dimensions are out of order, the units of measure is inconsistent and/or the data type is inconsistent). As the name implies the seeshape tool displays the shape of the specified object allowing you to see how the object has been defined and track down any inconsistencies. | ||
howtos/debugging/model_debugging_in_samm.1308923294.txt.gz · Last modified: 2011/06/24 13:48 by chris.strashok
Page Tools
