Adams Basic Package > Adams View > Adams View > Dialog box - F1 help > E - I > Import - Adams Solver Analysis Files

Import - Adams Solver Analysis Files

File Import Adams Solver Analysis, Adams Graphics, Adams Request, or Adams Results Shared Dialog Box
Imports Adams Solver analysis files, which are a set of output files that Adams Solver generates during a single Simulation. The files include:
You can import multiple files if you associate and store the files with a model. Adams View reads and creates all analyses under the specified model. If you do not provide a model name, Adams View reads each analysis into its own model. For request files, when you specify multiple files, the Request IDs button only displays the requests from the first file listed. The list of IDs will, however, be applied to all files.
If you select to associate the files with a particular simulation, you can only import one set of output files generated from the same Adams Solver simulation. Adams View uses the time-date stamp placed at the beginning of each output file to determine if the files were generated by the same simulation run.
If you have very large request files that you want to import, Adams View lets you read in only a subset of the request file to conserve memory use. You can specify to read in only the request IDs in which you are interested and skip time steps. Note that this is only available when reading in a single request file, not when reading in an entire set of analysis files.
 
Notes:  
Importing an entire set of analysis files works even if you have only one of the three files included in the analysis set as explained below.
If Adams View cannot find any of the three files, it issues a message. The most common reasons that Adams View cannot find one or more of the files are that the path to the files is incorrect or you do not have permission to read the file. You can either:
Import the files again using the correct path name.
Move the files into the directory from which you are running Adams View and check the file permission. Then, import the files again. You do not need to specify the file locations.
 
For the option:
Do the following:
File Type
To import sets of analysis files, select Adams Solver Analysis Files.
To import individual analysis files one at a time, select Graphics, Request, or Results.
Note: When you import only a graphics file, you can select to display the graphics and choose to store the data on your disk drive and not in the Adams Modeling database. Then when Adams View or Adams PostProcessor animates the model, it references the data on disk. By saving the data on disk and not in the Adams database you can save substantial amounts of memory, especially if the files are large (containing 20,000 output steps or more). Note that storing the data on disk results in slightly longer animation time.
File(s) to Read
Enter the base name of the file or set of files. You do not need to enter their extension.
Model/Analysis
Enter either the model or analysis name under which you want to store the analysis files in the modeling database. You can enter multiple files if you select to store them under a model.
View
(Adams PostProcessor only)
Enter the viewport in which to display the data.
Display Model After Completion
(Graphics file only)
Select if you want to display the final results of the import.
Keep Results Data On Disk
Select if you want to avoid reading the entire contents of the graphics, request, or results data (XML only) into the database. Adams View references the data only when needed for animations or xy plotting. Storing the data on disk reduces the memory footprint and improves performance for very large simulations, for example, those containing durability results. Learn more about storing results files in XML format with Results (.res) Options dialog box help.
If you selected to import a results file, the following two options appear:
Time Step Skip
Specifies whether or not to skip time steps by specifying a pattern of time steps to skip in the result file. This should be greater than or equal to 0. For XRF style result files only.

If you have a large result file with unnecessarily fine time resolution, specifying Time Skip Step can significantly reduce the amount of memory used to store the data as well as reduce the reading time.

If the this is not specified or if the value is 1 then the entire result file is read as usual. If this is for example 3, for a result file with the name test.res, then every 3rd step (not including initialCondition, input and contact step is included in the new results file with the name test_3.res. This file, after shrinking, is read into Adams View instead of the original file. This file is stored in the same location as the original result file. This can be combined with a Contact Step Skip specification (two suffixes would be added to the filename in that case).
Contact Step Skip
Specifies whether or not to skip contact steps by specifying a pattern of contact steps to skip in the result file. This should be greater than or equal to 0. For XRF style result files only.

If you have a large result file with unnecessarily fine resolution and employing contacts, specifying Contact Skip Step can significantly reduce the amount of memory used to store the data as well as reduce the reading time.

If the this is not specified or if the value is 1 then the entire result file is read as usual. If this is for example 4, for a result file with the name test.res, then every 4th step (not including initialCondition, input and contact step is included in the new results file with the name test_4.res. This file, after shrinking, is read into Adams View instead of the original file. This file is stored in the same location as the original result file. This can be combined with a Time Step Skip specification (two suffixes would be added to the filename in that case).
If you selected to import a request file, the following two options appear:
Request IDs
Enter the IDs of the requests in which you are interested and want read into the Adams View database. Select the More tool to select from a list of all the requests and their IDs in the specified request file.
Time Step Skip
Enter whether or not to skip time steps by specifying a pattern of time steps to skip. If you have a large request file with unnecessarily fine time resolution, this can significantly reduce the amount of memory used to store the data. For example, enter 1 to have Adams View store only the following time steps in the database: 1st, 3rd, 5th, and so on. Enter 2 to store only the 1st, 4th, 7th, and so on.