Data Storage Files |
 
|
Data Storage Files |
|
Various options are provided to specify the type and level of output produced by a time domain analysis run for subsequent postprocessing. The relevant data falls into two main categories, reflecting the fact that two (time domain) postprocessing modules are available in Flexcom, namely the Database Postprocessor and Timetrace Postprocessor, respectively. The differences between two output file types, and their relative advantages and disadvantages, are described in the following sections on Database Files and Timetrace Files.
The vast majority of Flexcom users tend to use database files to store program outputs. Timetrace output is essentially a legacy feature which continues to be supported for backward compatibility reasons. It's traditional advantages have since been counteracted by the ever-increasing functionality available for database files...
•Small size and quick access times have been replicated by customisable database files.
•Ability to produce a text-based output (rather than binary) has been replicated by the ability to produce spreadsheet based output.
No options are provided regarding control of output produced by a frequency domain analysis run for subsequent postprocessing. The reason for this is that a frequency domain analysis is relatively concise by comparison with that of a corresponding time domain simulation, and all of the relevant output data is stored automatically in a frequency domain database file.
•$DATABASE POSTPROCESSING corresponds to the database postprocessing facility, which generally represents the most comprehensive postprocessing resource. Refer to Database Postprocessing for further details.
•$Timetrace Postprocessing corresponds to the timetrace postprocessing facility, which is mainly used in the area of time domain fatigue analysis. Refer to Timetrace Postprocessing for further details.