Executing SeaFEM solver ======================= Automatically executing SeaFEM ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SeaFEM solver can be comfortably started through Tdyn preprocessing environment **Calculate** menu. Once the analyzed problem is defined (i.e. the geometry is created) the boundary conditions assigned, and the mesh is generated, the *Start* button in the **Calculate** menu (or the Calculate icon) can be pressed. :guilabel:`Calculate > Calculate window` Then the calculation is started and creates a number of output files (see section *Output files* for a brief description of the files generated during the execution) Manually executing SeaFEM ^^^^^^^^^^^^^^^^^^^^^^^^^ Sometimes it can be interesting to run the Tdyn executable (tdyn.exe) manually (without using the graphic user interface of the software) in order to run SeaFEM analysis. The necessary steps are described here. From here in advance, the following notation will be employed for description purposes: * **$gidpath** : root directory of the installed program. It contains, among others, the gid.exe executable file called to run the GiD custom GUI. * **$CompassFEM_version** : CompassFEM problemtype version name. * **$inputpath** : directory that contains the input data file associated to the SeaFEM model under analysis. * **$modelname** : name of the input data file. First, the input data file required by the Tdyn executable must be generated before execution. To this aim, the corresponding SeaFEM model must be loaded to the GiD custom interface. Next, the input data file must be exported, assuming that the model setup has been finished successfully (applying material properties and boundary conditions) and that the mesh has been already generated. In order to export the input file, the following menu sequence must be used: :guilabel:`Files > Export > Calculation file...` By doing this, the user will be asked for a file name (*$modelname*) and location (*$inputpath*). By default, .dat extension will be used to export de input file. If desired, .flavia extension can be also specified for instance, trying to mimic the file name convention used when running SeaFEM solver automatically. Before execution, you must ensure that the tdyn.exe process is able to find a password.txt file containing a valid tdyn password. You can create such a text file manually and copying the password inside. Alternatively, the password.txt file can be copied from the directory **$gidpath\\problemtypes\\$CompassFEM_version\\compassfem.gid**, where it is automatically saved if tdyn passwords have been previously registered through the GiD custom GUI. For manual execution of the solver, the password file must be located either next to the tdyn.exe executable (this is on the previously mentioned **$gidpath\\problemtypes\\$CompassFEM_version\\compassfem.gid\\exec** directory) or next to the input file. After exporting the input file and copying a valid password.txt file, everything is ready to launch tdyn.exe manually. To this aim, open a command shell and move to the location of the tdyn.exe executable. Such a location will be typically of the form: **$gidpath\\problemtypes\\$CompassFEM_version\\compassfem.gid\\exec** Note that tdyn.exe may be also executed from an arbitrary location if the directory path above is conveniently added to the environment system variable PATH. Finally, launch tdyn by using the following command line: .. code-block:: C\:> tdyn.exe -name "$inputpath\$modelname" -SeaWaves Output files generated during process execution ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ **The output files described in the following section concern to the global analysis** +----------------------------+-------------------------------------------------------------------------------+ | Output files | Description | +============================+===============================================================================+ | | Text file containing global information as well as process information |br| | | ProblemName.flavia.inf | information for each time step. The content of this file can also |br| | | | be accessed during calculation through the GUI by using the menu |br| | | | option *Calculate > View process info*. | +----------------------------+-------------------------------------------------------------------------------+ | | | | ProblemName.flavia.out | Text file containing iterations and convergence history. | | | | +----------------------------+-------------------------------------------------------------------------------+ | | XML file that contains a timetable in XML format giving information on |br| | | ProblemName.flavia.tim | the CPU time consumption of the process. The timetable contains a |br| | | | report of the execution time used by different parts of the problem. |br| | | | This file is only available after complete successful calculation |br| | | | of a problem. | +----------------------------+-------------------------------------------------------------------------------+ | | Text file containing error messages |br| | | ProblemName.flavia.err | (file created only if tdyn.exe exits with an error). | | | | +----------------------------+-------------------------------------------------------------------------------+ | | Main results file that contains all field valued results. |br| | | ProblemName.flavia.res | When pressing **Postprocess** in *Custom GiD*, this file is loaded, |br| | | | and the results it contains can be visualized in the |br| | | | post-processing module. Also note that each calculation will | +----------------------------+-------------------------------------------------------------------------------+ | | | | ProblemName.flavia.ram.msh | Mesh for structural analysis using Ram-Series. | | | | +----------------------------+-------------------------------------------------------------------------------+ **The output files described in the following section concern to the results of the mooring system.** +-----------------------------+------------------------------------------------------------------------------+ | Output files | Description | +=============================+==============================================================================+ | | Mesh file containing the nodes coordinates of the mooring |br| | | MooringResults.msh | segments mesh for the initial configuration. For |br| | | | post-process animation,the coordinates of the initial |br| | | | mesh are updated according to the displacement results |br| | | | saved in MooringResults.res during calculation. | +-----------------------------+------------------------------------------------------------------------------+ | | Text file containing time evolution data of the tension |br| | | ProblemName.MooringData.res | force on both ends of each mooring segment. | | | | +-----------------------------+------------------------------------------------------------------------------+ | | Text file that contains displacement results (components |br| | | MooringResults.res | and module) at mooring mesh nodes. This results are necessary |br| | | | for animation of the mooring lines in the postprocess. | +-----------------------------+------------------------------------------------------------------------------+ **The output files described in the following section concern to time evolution results on bodies.** Results contained in these files can be visualized using the SeaFEM graphs utility in the SeaFEM Postprocess (see for instance section Results visualization) +--------------------------------+---------------------------------------------------------------------------+ | Output files | Description | +================================+===========================================================================+ | | Text file containing time history data of body movements, |br| | | ProblemName.BodyKinematics.res | velocities and accelerations of all bodies under analysis. |br| | | | The complete set of data (all those kinematic results selected |br| | | | for output in the data tree) is written first for the first |br| | | | body defined in the GUI. The rest of bodies data results are |br| | | | written following the order the bodies are defined in the GUI. | +--------------------------------+---------------------------------------------------------------------------+ | | Text file containing time history data of body loads and |br| | | ProblemName.BodyLoads.res | moments acting over all bodies under analysis. |br| | | | The complete set of data (all those kinematic results |br| | | | selected for output in the data tree) |br| | | | is written first for the first body defined in the GUI. |br| | | | The rest of bodies data results are written following |br| | | | the order the bodies are defined in the GUI. |br| | | | Different components of forces and moments are written |br| | | | separately. Hence, total forces, reactions, hydrostatic |br| | | | pressure forces and dynamic pressure forces can be assessed |br| | | | separately. | +--------------------------------+---------------------------------------------------------------------------+ | | Text file containing time evolution data of the user defined |br| | | ProblemName.Outputs.res | results. (Up to 10 custom results can be defined by the user |br| | | | in the *User defined* data tree entry). | +--------------------------------+---------------------------------------------------------------------------+ | | Text file containing time evolution data of |br| | | MooringLoads.res | the mooring loads acting on bodies. | | | | +--------------------------------+---------------------------------------------------------------------------+ **The output files described in the following section concern the body animation results** Results contained in these files can be used to setup body animations within the Postprocessor (see for instance section Results visualization). +------------------------------------------+-----------------------------------------------------------------+ | Output files | Description | +==========================================+=================================================================+ | ProblemName.BodyMovements_animations.res | Text file containing time history data of the |br| | | | movements of the first body defined in the GUI |br| | | | of SeaFEM (referred to the global frame of reference |br| | | | located at the origin 0,0,0). | +------------------------------------------+-----------------------------------------------------------------+ | BodyMovements_animations_#.res | # stands for an integer index that identifies |br| | | | the body to which the file under consideration |br| | | | refers. These are text files similar to the |br| | | | previous one and concerning the remaining bodies |br| | | | defined in the analysis. | +------------------------------------------+-----------------------------------------------------------------+ .. |br| raw:: html