Database Files |
 
|
Database Files |
|
Flexcom can produce two database files, referred to as the motion database file and the force database file. Together, these can contain a detailed description of the analysis solution at all or selected solution times. These files are unformatted random access files, so you cannot type, print or edit them. The motion database file can contain information on the position, velocity and acceleration of all or selected nodes in the model (including runtime generated statistics of motion). The force database file can contain information on:
(i)Restoring forces in all or selected elements
(ii)Reactions at all restraints
(iii)Statistics of restoring forces generated during runtime
Restoring forces in this context may include axial forces, effective tensions, shears, bending moments relative to both local 
and 
axes, and curvatures relative to these same local axes. A number of further outputs may optionally be added to these parameters.
The database files provide a very detailed picture of the structure response. However, this is often obtained at a cost. For large models, or in long simulations with a large number of database outputs, the database files can become quite large. This is frequently an unavoidable overhead, particularly in the early stages of a job, when you are trying to develop a stable, efficient model or examine the effect of a number of design options. The size of the database files may be reduced, however, by customising the contents to suit your own requirements.
Another point of note is that the Summary Postprocessing facility (which allows you to extract pertinent results in succinct tabular format) is also based on database output, so if wish to avail of this facility, the presence of database files is a fundamental prerequisite.
You may also use customised Database Access Routines to access the data stored in the database files. This feature is intended for advanced users of the software, and facilitates the development of specialised postprocessing tools tailored to meet the specific requirements of individual clients. This feature is discussed in detail in Database Access Routines.
•*DATABASE is used to specify the frequency of database output.
•*DATABASE CONTENT is used to customise the contents of the database output files.
If you would like to see an example of how these keywords are used in practice, refer to A01 - Deepwater Drilling Riser or B01 - Steel Catenary Riser.