BEAMST operates on the files produced by a preceding ASAS, RESPONSE or LOCO analysis and hence these files must physically be present in the user’s working directory for the program to run successfully. In all cases the project file must exist which contains information about all other files in the current set of analyses. The name of this file is derived from the four character Project Name defined on all the PROJECT commands in the set. (For example, if the Project Name is PRKZ, then the Project File will be PRKZ1O).
For each ASAS, RESPONSE and LOCO analysis preceding this run with a ‘SAVE BEAMST FILES’ command in its preliminary data block, there will be a physical file containing forces and moments from that analysis. Again the physical file names are derived from the four character name defined on the FILES command. Typically, if the names used were STVK, SQSY and TBSS then the physical files would be STVK35, SQSY35 and TBSS35. The information stored in each file will depend on the form of the run producing the output. The forces and moments may relate to the analysis of a structure or to the results associated with the elements at any level in a sub-structured analysis. Provided that the user has the requisite files in their working directory the program will handle them in a transparent manner.
The preceding analysis must have run to completion. If the run did not complete either because of a failure or because the user terminated the run deliberately with a RESTART command, BEAMST may error because some files may not exist.