Page 9 - Upgrading to ExtendSim 10
P. 9

 It is best to convert all your models to ES10 at the same time and to use the same libraries. If that isn’t possible or practical, save copies of whichever libraries you used to convert models and “freeze” those copies without making changes. Then use the “frozen” libraries when you later convert prior-release models. Using libraries that are as close as possible to what was used to build the models will give the best conversion results.
 If you have saved a hierarchical block (HBlock) in a library, and the HBlock contains blocks from releases prior to 7, put the HBlock on the ES10 model worksheet and force it to recompile before opening models that use that block. To force the recompile, open the structure and make an insignificant change. Then close the structure and choose Also Save to Library.
Verifying Models: Automating the Process
ExtendSim 10 ships with an automated test environment so you can verify models between releases and between changes you make to your models. There are two components to the test environment. They are used differently depending on whether you want to test several models at a time or only one model:
 The Compare Results application located at Program Files/ExtendSim10 is for testing multiple models
 The Model Compare block (Utilities library) is useful for testing a single model These tools help identify any differences in two situations:


Verifying that models will generate the same results when there is a new release of ExtendSim. The test environment
simplifies the process of comparing simulation results between two ExtendSim releases – looking for any differences
between models that were saved in a previous release and the same models run in the new release.
Determining if changes made to a model affect the results. In the same manner as verifying between releases, you can
compare copies of the model saved before and after you’ve made changes.
For complete information on how to use these tools for model verification, see the section “Automated test environment” in the
User Reference.
7


































































































   7   8   9   10   11