Results Tab Best Practice

<< Click to Display Table of Contents >>

Navigation:  PipeLay > Software Components & Operation > Analysis & Postprocessing > Analysis Component > Results Tab >

Results Tab Best Practice

Previous page Next page

1.Use visual results such as animations and plots to quickly review analysis predictions. These visuals will highlight any unwanted behaviour (e.g. extreme deformation) quickly as well as possible reasons for the behaviour. They also give a sense of scale to motion/loads and can help pinpoint possible causes of convergence problems. Obviously, if there is unwanted behaviour then you should avoid delving into/using the actual number based reports and instead you should refactor your model/analysis before running again.

2.Once you are happy that the solution results/behaviour is appropriate you can then use the various number based reports. Reports from summary post-processing and code checking contain governing results across all stages and so should be used as much as possible. On the other hand, tabular output and analysis reports are local to individual stages and so take longer to go through and should be referred to only if needs be. The same applies to the detailed output file and in fact this file is very much FE orientated, which makes it more awkward to follow.

3.Using Excel version (CSV output) for many of the reports makes data extraction/adaption easier to achieve.

4.In addition to using results generated by PipeLay itself, you can also avail of the Excel Add-In capability that allows you to directly generate results in Excel spreadsheets using dedicated extraction functions which interrogate the analysis databases independently of the PipeLay application. This Excel Add-In is license free and can be installed separately to PipeLay. There are also a set of template spreadsheets provided for reference. For more information on the Excel Add-In please refer to a separate article or contact Wood Group.