Skip to content

Home > Introduction > Input & Output Files > User Interface Input & Output Files

User Interface Input & Output Files

The graphical user interface may handle several types of files. Each file type is given a particular extension. The main types of files that can be opened or created with the GUI are presented below.

  • Model files (*.DSK) : these files contain all the objects and analyses of your model. They are the basic files with which you build the complete model. You can add/delete objects, analyses within these files. The model files are binary files. They can be created or opened with the GUI only.

    Note

    The model files are naturally project oriented files as one model file may naturally contain all the components of your model and the definition of several analyses at the same time. This ensures consistency between your various analyses and efficient management of all multiple analyses. The QA Information attached with the model file also helps you in this task.

  • Simulation results files (*.DSS): these files are for post-processing the results of a given analysis. Each simulation results file is associated with one of the analysis previously defined within a Model file. The model components are displayed in the 3D view window in their default position, and depending on the requested analysis, in their static position (with animation on the various steps), in their dynamic position (with time-dependant animation) or per mode (modal animation). Plots and Windows AVI animation files can be created and exported in various formats. All previous data requests on the specific analysis are stored and accessible from that file (both graphs and statistics). If further new post-treatment is required, the binary database created by the solver must be available. Requested data are extracted and computed from the database files. Graphs and data can then be exported in MS Excel format with a single click.

  • RAO viewer files (*.DSO): these files are for viewing RAO data computed from the GUI only. The RAO must have been previously computed using the RAO tab from one or several simulation results files. Compared to these latter files, the RAO viewer files may gather RAO results from several analyses.

  • Fatigue results files (*.DSF): these files are for post-processing results from fatigue analyses previously defined within a Model file.

  • Pipe Properties Library files (*.DPL) : These files are binary files used to store sets of pipe segment mechanical properties, i.e. segments types. The advantage of these library files is that they facilitate multiple model build-up based on standard pipe properties. The segment types containing in the DPL files can then be accessed and transferred to any DSK model by opening the DPL file and using the Import/Export feature.

  • Zones Study post-processing files (*.ZS): These files are binary files used to store the various requests and results for zone study post-processing tasks. These files may be prepared by the GUI and run in batch mode and are somewhat similar to DSS files, expect that they gather results from multiple analyses and that results variables are restricted to lines related variables.

  • Login history file (*.TXT): A text file named LOG_History.txt will be automatically updated as you open any file with the GUI or ask for the GUI to extract any type of results. The information in this file is file contains a brief description of what you have done. When running batch post-processing, all the error messages are written in this file instead of being displayed on the screen.

  • Batch processing queue files (*.DBQ): These files are text files used to define predefined list of batch jobs (batch jobs queue) to be processed within the Batch Jobs processing form. These files may be generated either with the GUI or with any text editor.

  • Clearance check post-processing files (*.CLC) : These files are binary files used to define clearance post-processing requests to be processed within the Clearance Check processing form. These files also include the results from the clearance analysis when it is completed.

  • Code check processing files (*.DSC): post-processing code check studies previously defined within a Model file.

  • Code Check results files (.CSV, .LST, *.PUN): CSV file containing code check ratios, listing of the code check computation (.LST), details results of the code check computation (.PUN).

Note

As the Open file dialog displays, you must change the filter associated with the file type to access the .DSS, .DSO and .DSF files.

Tip

Use the drag and drop facility to open your files. You can launch the GUI and then select from Windows explorer one or several files name you want to open, and then just drag and drop them in the interface, which is a convenient way to open several files without using the Open file dialog.