.. _understand_output: Understanding output files ========================== The automatic analysis performed by the FloorTools software generates several output files. This list of files made available depends on the type of analysis performed (Standard analysis = validation against OEM allowable / Non Standard analysis = comparative FE analysis with validated reference floor loading). Output files are accessible under the pull down menu **Deliverables** of the result page. .. _fig_deliverables-dropdown: .. figure:: ./_static/deliverables-dropdown.png :align: center :width: 350pt :alt: Ftools Screenshot deliverables dropdown list :figclass: align-center Screenshot of FtoolsV3 deliverables drop-down list Single Archive Download ----------------------- Item ``(1)`` of :numref:`fig_deliverables-dropdown` allows to download **all deliverables** as a single archive. Analysis Assets --------------- item ``(2)`` of :numref:`fig_deliverables-dropdown` features *general* assets (*ie.* not AC zone relative). .. _nastran_bdf: Checked FE Model ################ The FE model of the floor structure loaded with user defined IFL is written in NASTRAN bulk data file. It can be imported in standard FE pre-processor like MSC PATRAN or SIEMENS FEMAP to perform spot check on user applied loading. Additionally the file can be run on NASTRAN FE solver and then some more checks could be done on critical FE results. .. _fig_fea_nas: .. figure:: ./_static/fea_nas.png :align: center :width: 350pt :alt: NASTRAN bdf :figclass: align-center NASTRAN Bulk Data File of Checked FE model FEMAP neutral File ################## This asset is aimed to be loaded in FEMAP. It brings groups of nodes and eventually elements of miscellaneous items for an easier check of LOPA loading. PATRAN neutral File ################### The same as FEMAP neutral export, but for PATRAN. Substantiation Report ##################### The main output of the FTools software is the complete Structural Substantiation report in Word format. This report is automatically generated by the FloorTools based on customer stylesheet for the document rendering and with some customized templates to control the output. As the report generated is in WORD format it can be freely modified and completed by the end user. For the end user of the FTools it is important to understand that this report is made of **static** and **dynamic** text, pictures and tables coded in the templates. A static text is a text that is written in the report template and won't be change by the software. A dynamic text is a text that will be "adapted" by the software to match some input / output data. It becomes a contextual text. Similarly a static image is stored in the report environment and will be incorporated in the SSR has it stands. In contrary a dynamic picture is automatically generated by the FTools to reflect FEM properties or FEM output. Here is an example of static figure: .. _fig_static-figure: .. figure:: ./_static/example_static-figure.png :align: center :width: 450pt :alt: report static figure :figclass: align-center Example of SSR static figure Here is an example of dynamic figure: .. _fig_dynamic-figure: .. figure:: ./_static/example_dynamic-figure.png :align: center :width: 450pt :alt: report dynamic figure :figclass: align-center Example of SSR dynamic figure Same is valid for report table. Some tables are stored in the report template and are not modified by the FTools. Some other tables are automatically generated by the FTools based on FE properties and output. Here is an example of static table: .. _fig_static-table: .. figure:: ./_static/example_static-table.png :align: center :width: 350pt :alt: report static table :figclass: align-center Example of SSR static table Here is an example of dynamic table: .. _fig_dynamic-table: .. figure:: ./_static/example_dynamic-table.png :align: center :width: 450pt :alt: report dynamic table :figclass: align-center Example of SSR dynamic table .. note:: As the report is based on stylesheet and templates, it is fully customizable and can be updated on request to numeric-GmbH. User Supplied Loading File ########################## The file uploaded by the FTools user is linked to the analysis for traceability purpose and can be downloaded at any time. .. _std_allowable_selection: Standard allowable selection ############################ This spreadsheet presents the data tables used for the automatic association of standard allowable to each seat. This spreadsheet should be read in association with the "Standard seat allowable" report. For standard seat analysis 16 different seating arrangements have been recorded. Each of them leads to different seat interface load allowable. Additionally, individual seat weight and seat row weight depend on those 16 different seating arrangements combined with a seat pitch. This combination generates 76 different seat and seat row weight possible allowable. In this "std_allowable_selection" spreadsheet the logic behind the automatic association of a seat IFL allowable and seat weight allowable is recorded. Reading output spreadsheets --------------------------- Item ``(3)`` of :numref:`fig_deliverables-dropdown` allows to download individual checkers' :term:`trace`. The FTools analysis output spreadsheets present a large amount of data in order to keep trace of all calculation steps leading to the margins of safety. Data dumped in those spreadsheets are reflecting the different tables computed internally by the software. They are not all formatted and structured to be easily readable by a end user. However, all of them have some commonalities in their structure and data presentation. A logical way to read the different xls sheets within an output spreadsheet is to go from the left to the right. Leftmost sheets are gathering input data necessary for the analysis whereas rightmost sheets are presenting final Margins of safety. Most of the sheets are generated from a Pandas DataFrame, which is a standard Python data manipulation module and one of the most popular tools used in data science and analysis tasks. In each sheet, the data in bold represents the column headers and row indices. Sometimes, rows may have duplicate values in the row indices, leading to merged row indices. Excel's data filter may not work correctly with such merged row indices. To overcome this limitation, the row labels (or row identifiers) are usually repeated at the end of the presented data, in the last columns, without any row merging. A detailed presentation of the spreadsheet / Sheet / field is detailed in the following chapters. ------- .. include:: .understand_outputs2.inc