Replace TRANSFER Function in FAST Registry-Generated Pack/Unpack Routines #99
Labels
Comments
bjonkman
added a commit
to bjonkman/openfast
that referenced
this issue
Jul 19, 2019
- updated C2F copy routines to allow for skipping the pointers (in case of module initially defining the pointers in Fortran code in instead of C/C++ code) - updated pack/unpack routines to avoid putting entire arrays on the stack (OpenFAST#99) - updated extrap/interp routines to account for values that have a period of 2pi. This change requires additional routines in NWTC_Num.f90. - this also includes changes that were introduces in a not-yet-merged pull request for 2D airfoil interpolation
bjonkman
added a commit
to bjonkman/openfast
that referenced
this issue
Nov 15, 2019
- Use less stack space in interpolation/extrapolation, pack, and unpack routines (fixes OpenFAST#99). - update auto-generated types files - update interp/extrap routines work on angles (over 2pi boundaries); this requires Angles_ExtrapInterp routines added to NWTC Library - NWTC Library + when reading real variables from file, check that they aren't Inf or NaN + remove unused code + add error handling to VTK read routines + check that size of scalars matches between meshes in transfer of data + add an (optional) reference node to mesh data structures
|
This was completed in #373, which is now merged into 'dev', so I think this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The TRANSFER function puts data on the stack, so pack and unpack routines generated by the FAST Registry can cause stack overflow errors when run on large data sets (e.g., large wind files or large offshore models).
The text was updated successfully, but these errors were encountered: