Configuring the Execution Properties | ||
| ||
Select the component whose properties you want to edit, and click the Properties
button on the Component Title Bar.
From the Properties dialog box, click the Execution tab.
Set the following options under General Options, as desired:
Option Description Delay before execution Set a length of time that the component will wait before it executes. This is commonly used for demonstrations where you want some delay to occur to allow for discussion as the model executes. Timeout Set a limit for when execution of the component will stop. Typically, you would set this property only if you are concerned that the component could encounter problems during execution that would not allow it to complete. If you set this limit, you must set it to a time much longer than the expected standard time for execution so that the component is not terminated incorrectly. If set to 0, no timeout limit is enforced. Maximum number of retries For application components, enter the number of times that you want Isight to attempt to execute a component if it fails. This is useful for scenarios in which a component requires a license or other computer resources that might not be available at the current time but might be available upon subsequent attempts. If the model is executed in a SIMULIA Execution Engine environment, the SIMULIA Execution Engine attempts to execute the component on a different station if one is available.
Maximum parallel batch size For process components, use this option to set the maximum number of design points (subflow executions) that a process component can submit simultaneously if it supports parallel execution. If you select Automatic (the recommended setting), Isight automatically determines the best number of executions to run in parallel. If you do not select Automatic, you must enter the maximum number of design points to be run in parallel. The value must be greater than or equal to 1.
Note: Some process components may run fewer subflows than the maximum; some may run only a single subflow at a time. For details on parallel execution options, see the component-specific sections in this guide.
Estimated subflow runs For process components, select Automatic to allow process components to estimate the number of times the component will run a subflow. Process components that execute their subflow numerous times can provide an estimate of the number of times they will run that subflow based on the details of how they are configured. These estimates can be used to track the progress of the execution toward completion. Typically, this number is accurate, especially for components that are configured to run an explicit number of design points (subflow runs). However, because the estimates are sometimes based on simple rules using the values of configuration options, it is possible they could be far from what you know is accurate. If you do not select Automatic, you can override the estimate so that the simulation process flow progress can be monitored more accurately.
Use fast-flow execution tier For process components, select this option to improve performance for this component and any submodel components. This option can be used only with the SIMULIA Execution Engine. When your design driver component contains very fast (sub-second) executing process components in its subflow, selecting this option improves performance by executing the entire submodel on a single SIMULIA Execution Engine station. The submodel consists of this (root) component and any underlying subflow components. Executing the submodel on a single station greatly reduces the amount of data that must travel over the network during standard, fully distributed execution in the SIMULIA Execution Engine. If any component below this component does not execute in less than one second, this option is not useful and is not likely to improve performance.
Exclusive Execution For application components, select this option to run only this component on a SIMULIA Execution Engine station during execution. This option can be useful because application components are often used to drive commercial or proprietary application programs that require a large amount of main storage. Occasionally, these programs require so much storage that it is not feasible to execute more than one component at a time on any given SIMULIA Execution Engine station. When a selected component is run on a station, no other component will run on that station, giving the component's application program maximum access to the station's resources.
This option is used only in the SIMULIA Execution Engine environment. It is ignored when using Isight in standalone mode.
Choose the following options for the Runtime Folder:
Option Description Folder is generated or Folder is entered here Enter a specific location where you want the component to run by selecting Folder is entered here and typing or browsing to the desired directory in the text field. You can use variable substitution expressions in this field. If you want Isight to create a separate, temporary working directory to execute this component, select Folder is generated. If you chose to set a model directory but not to save per-component subdirectories (in the Models Properties editor), Folder is model property (see Setting Model Properties in the Isight User’s Guide) is selected. For example, if a single component in your model is executed multiple times (e.g., loop), each individual execution of that component is executed in its own temporary working directory. This structure allows for complete and safe parallel execution of the component so that it can be executed multiple times simultaneously, avoiding file collisions. However, there are times when a component must run in a specific directory on a computer. If you set a specific location, any attempt to execute this component in parallel can lead to errors related to file collisions (if files are used or produced by that component). Parallel execution can occur through configuration of process components or through construction of parallel simulation process flows, in any combination.
Keep after execution? Determine if you want the temporary directory retained after execution. When a component executes, Isight creates a temporary directory to manage the files required for and produced by the execution. Typically, the directory and files are deleted automatically following execution. However, you can select if the temporary directory and files are Always retained, Never retained, or retained only when a run fails (On Run Failure). If you have defined a specific directory in which to execute the component (see the Runtime folder option above), Isight always keeps that folder regardless of this setting. Isight detects any files (including subfolders) that are added under that folder during execution and either keeps or deletes these files as determined by this setting.
Set the following options under Result Options, as desired:
Option Description Prevent saving this components’s results to the database Normally Isight saves the component run results to the database. You can select this option to prevent the saving of result data, which may increase the model’s execution speed. However, you will not have the saved data that may later be needed for postprocessing or future re-execution using database lookup. For more information about saving parameters to the database, see Setting Gateway Preferences in the Isight User’s Guide. Prevent saving this components’s subflow history to the database For process components, you can select this option to prevent Isight from saving result (history) data for subflow runs. This option may increase the model’s execution speed; however, you will not have the saved data that may later be needed for postprocessing or future re-execution using database lookup. For more information about the Save to Database option, see Setting Local Results Database Preferences in the Isight User’s Guide. Prevent saving results for any components descending from this component For process components, you can select this option to prevent Isight from saving individual results of subcomponents below this component. This may improve performance by reducing the amount of data stored during execution. Selecting this option overrides all other parameter save options for all components that descend from this component, by preventing those subcomponents from saving run result data to the database. Click OK to save your changes and to close the Properties dialog box.