Quasi-Newton methods for partitioned simulation of fluid-structure interaction reviewed in the generalized Broyden framework: code and data

<p>These files accompany the publication</p><p>N. Delaissé, T. Demeester, R. Haelterman and J. Degroote. Quasi-Newton methods for partitioned simulation of fluid-structure interaction reviewed in the generalized Broyden framework.<i> Archives of Computational Methods in Engineering</i>, Vol.<strong> </strong>30, 3271-3300, 2023. doi: <a href="https://doi.org/10.1007/s11831-023-09907-y">10.1007/s11831-023-09907-y</a></p><p>In this work, the&nbsp;performance of multiple quasi-Newton methods are compared in terms of memory requirements and computational time. The results are generated for&nbsp;the well-known flexible tube example case, using the open-source code <a href="http://github.com/pyfsi/coconut">CoCoNuT</a>. This code, developed at Ghent University, is Python-based and has the capability to couple existing&nbsp;solvers, both open-source and commercial solvers.</p><p>This archive consists of the following files.</p><ul><li><strong>coconut.tar.gz:&nbsp;</strong>the specific CoCoNuT version used (sep-2022), including the Python flow and structure solvers for the flexible tube and modifications for monitoring memory requirements</li><li><strong>compare_coupling_algorithms.tar.gz:&nbsp;</strong>the scripts to set up the cases and perform the calculations and post-processing</li><li><strong>results.tar.gz:</strong>&nbsp;the generated result data</li></ul><p>For requirements to run CoCoNuT, refer to the <a href="http://pyfsi.github.io/coconut/">documentation</a>. Additionally, the Python package guppy3 is required for monitoring the memory use.&nbsp;In this work the data were generated with Andaconda3-2022.05 and the package guppy3-3.1.2.</p><p>Before running the provided scripts, make sure the parent directory of the "coconut" folder is&nbsp;added to the PYTHONPATH. The calculations can be started with "python run.py". For the cases which names contain&nbsp;"_m" followed by a number, e.g. "_m100", the number refers to the number of&nbsp;discretization points on the interface.&nbsp;The cases with suffix "_c" are distinct from those without, as they&nbsp;don't perform the time consuming memory monitoring and are therefore used for measuring computational time.</p>