19.2. Specifying Analysis Project Pedigree (Inputs and Outputs)

You can specify the location of inputs and outputs (or “analysis pedigree”) for an Analysis Project folder using the Edit Pedigree action. When the simulation analysis is executed, EKM will use the information supplied in this dialog box to locate the inputs and outputs of the analysis and create the required dependencies. This information can also be predefined for custom analysis project folders. See Defining Custom Analysis Projects in the Administration Guide for details.

You can also specify upstream dependencies for a file contained within an Analysis Project folder. See Specifying File Dependencies.

To specify the pedigree (inputs and outputs) for an analysis project:

  1. Select the Analysis Project folder, then select   (Edit) > Pedigree. This will open the Edit Analysis Pedigree dialog box.

    Figure 19.2:  Specifying the Analysis Pedigree

    Specifying the Analysis Pedigree

  2. To specify the inputs:

    1. Click the Add input parameter link to add a row to the table.

    2. Move your cursor to the newly-added row and enter the relative path of your input files in the text box. Follow these rules for specifying the path:

      • All the inputs that are used by an analysis must be present within the analysis project. If the inputs are present outside the project, you can create a shortcut to them and place the shortcut within your analysis project. When creating shortcuts to files under version control, you can select a particular version of the file to use. When you select a file in the repository, the dependency diagram will indicate if the file has been modified (and the analysis is out-of-date). When you select a particular version of the file, it will be shown as modified only when a new version of the file exists, and the file contents of the new version have been modified.

      • The path is relative to the current analysis project. For example, specifying file.dat for the input location means that you want to use a file named file.dat at the top level of the analysis project folder as the input. Specifying an input location as inputs/file.dat means that the file named file.dat within the inputs folder in the analysis project folder should be taken as the input. You cannot use “..” to reference objects outside the current project.

      • You can specify either a file or a folder, or a shortcut to a file or folder as an Input location. If you specify a file, it will be taken as an input for the analysis. If you specify a folder, all files contained within that folder or its sub folders will be inputs. If you specify a shortcut to a file, that file will be an input. If you specify a shortcut to a folder, all files contained within that folder and its sub folders will be inputs.

      • If the input location points to a folder or a shortcut to a folder, and that folder contains shortcuts, then all those shortcuts will be traversed recursively and all files found will be taken as inputs.

      • You can specify wildcards * and ?. * denotes multiple occurrences of any character and ? denotes a single occurrence of any character. For example, file-?.dat will match file-1.dat, file-2.dat, and so on, but will not match file-12.dat. file-*.dat will match any relative path that starts with file- and ends with dat, for example, file-12.dat, file-abcd.dat, file-1/file-2.dat, and so on.

    3. Optionally click the Preview button next to the input table to display all the files that have been selected to be added as inputs. To remove any input, just click Remove next to the input that you want to remove.

  3. To specify outputs, follow the same procedure that is defined in Step 2 above, using the Add output parameter link instead. The rules for specifying the path location are the same for both inputs and outputs. Because the dependencies are updated only when the analysis is updated, you may specify files and folders as outputs, even if they do not currently exist.


Note:
  • Dependencies are updated only when you update the analysis using the Update Analysis action and not when you submit this dialog box. This is done to ensure that the dependency diagram displays only the dependencies that existed when the analysis was last updated. Consequently, the files that you see in the Inputs and Outputs table of this dialog box may not match the files that are displayed in the dependency diagram. See Updating an Analysis Project Folder for details.

  • If you attempt to update an analysis project that contains a process template that is in the draft stage, an error message appears because the process template is not executable. Right-click the process template and select Edit > Lifecycle > Promote to request promotion to the executable stage.



Release 18.2 - © ANSYS, Inc. All rights reserved.