Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,44 @@ All notable changes to CableDyn are recorded in this file. The format follows
start with the same torques on every kernel, proportional to the pretwist.
- The "unresolved/kinked equilibrium" refusal names the element and the factor to refine its
section's `NumSegs` by.
- Console messages that said something untrue now say what happens:
- OpenFAST: "SeaState wave/current kinematics drive the mooring hydro" is printed only when the
deck's `WaterKin` policy takes a SeaState component (a `WaterKin` file with `WaveKinMod 0` and
`CurrentMod 0` gives still water and says so);
- the body/rod static start reports the largest turn of a body or rod and the move of every
point the objects carry, so a pinned rod that only rotated no longer reads "largest move
0.000E+00 m";
- a mixed or FAST.Farm deck refused for a deck current names the input that declares it (the
`CurrentMod 1` table of its `WaterKin` file, or the `current` OPTION), not always "the current
OPTION";
- the torsion note reports the line's total twist `Twist<L>` at the static state, beside the
imposed `Pretwist(B) - Pretwist(A)` and with the end frames' turn (a `PtfmInit` or `TURBINES`
rotation) and the shape's geometric twist, not the pretwist alone;
- in FAST.Farm the time-step messages name the farm's `DT_Mooring`, not a "glue DT".
- A standalone `TURBINES` deck that mixes `EI = 0` lines and finite-EI cables (a power cable
shared by two turbines beside their chain legs, the usual farm deck) runs. It stopped with the
internal message `no farm init was given (pass n_turbines + turbine_ref_pos)`: the mixed route
did not take the `TURBINES` rows. It now places the `Turbine<J>` points from them and moves the
points and turns the cable end frames with the per-turbine `motionFile` records, as the decks of
the cables alone and of the `EI = 0` lines alone do. The IEA 15 MW two-turbine deck (a 1530 m
cable restrained in torsion and four chains, 60 s of FAST.Farm platform motion) reproduces those
two decks to 3.2e-6 of the channel maxima and the FAST.Farm `Mod_SharedMooring = 5` run to
2.3e-5. On a two-turbine test deck whose turbines heave and roll, the chains match their deck
bit for bit and the cable, marched with the single-cable route's Newton controls, matches its
deck to 0.44 of the last printed digit. A `Turbine<J>` point in a run without a farm
(single-turbine OpenFAST, the C API) is now refused by point, naming FAST.Farm and the
`TURBINES` section.
- A coupled deck with both bodies and rods stopped at init with `a coupled deck mixing RODs and
Rigid6/point3 bodies is not supported (the aggregate marches one body/rod family per step)`,
a limit the OpenFAST and capability pages did not state. The message now says what the coupled
route takes (bodies or rods, a rod fixed to a body counting as a rod) and where such a deck runs
(MoorDyn `CompMooring = 3`, the standalone driver); the OpenFAST, capability and troubleshooting
pages state the limit, and the Python validator (`caller_driven=True`) refuses the deck.
- `FAST.Farm.exe` built through the CMake route of `integration/openfast` with the GNU compilers
on Windows stopped at start with `0xC00000FD` (stack overflow) while initialising the first
turbine: MinGW links it with a 2 MiB stack. The new patch `0022` gives `openfast.exe` and
`FAST.Farm.exe` a 256 MiB stack reserve on that toolchain, and the shared-mooring farm (two IEA
15 MW turbines) runs to normal termination.
- A rod numbered as a body no longer joins the body's attachment points. A `Rod<N>A/B` end point
keeps its rod's id where a `Body<N>` point keeps its body's, and the body's point list took
every point with its id: a rod end POINT row listed before the body's points became the body's
Expand Down
11 changes: 10 additions & 1 deletion CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -2388,6 +2388,10 @@ add_executable(test_mixed_route_torsion tests/test_mixed_route_torsion.f90)
target_link_libraries(test_mixed_route_torsion PRIVATE cabledyn_core)
add_test(NAME mixed_route_torsion COMMAND test_mixed_route_torsion $<TARGET_FILE:cabledyn>)
set_tests_properties(mixed_route_torsion PROPERTIES LABELS "fortran;driver;integration;dynamic")
# A standalone TURBINES deck of a finite-EI cable between two turbines and chain legs on the mixed
# route, against its cable-only and legs-only decks (gate 9).
add_test(NAME mixed_route_turbines COMMAND test_mixed_route_torsion $<TARGET_FILE:cabledyn> turbines)
set_tests_properties(mixed_route_turbines PROPERTIES LABELS "fortran;driver;integration;dynamic")

# Deck currents on the standalone mixed route (the aggregate samples the deck current at every
# node before each step): OPTION uniform and profile and MoorDyn-C Currents 1/2/5 against the
Expand Down Expand Up @@ -2623,7 +2627,7 @@ set_tests_properties(driver_cli_mixed_nmodes PROPERTIES LABELS "fortran;driver;c
add_test(NAME driver_cli_torsion_nmodes
COMMAND ${CMAKE_COMMAND} -DDRIVER=$<TARGET_FILE:cabledyn> -DEXPECT_RC=0
"-DARGS=${CMAKE_CURRENT_SOURCE_DIR}/tests/data/torsion_lazy_wave_modes.dat|${CMAKE_CURRENT_BINARY_DIR}/driver_cli_torsion_nmodes"
"-DMUST_MATCH=torsion solved, imposed twist 7.20000E\\+02 deg;converged run written"
"-DMUST_MATCH=torsion solved, total twist Twist1 =;imposed Pretwist.B. - Pretwist.A. = +7.20000E\\+02 deg;converged run written"
-P ${CMAKE_CURRENT_SOURCE_DIR}/tests/check_driver_output.cmake)
set_tests_properties(driver_cli_torsion_nmodes PROPERTIES LABELS "fortran;driver;cli")
# Non-ASCII, reserved-device, input-clobbering, and concurrently used output paths.
Expand Down Expand Up @@ -2898,6 +2902,11 @@ cabledyn_msg_test(mixed_waves msg_mixed_waves.dat 1
cabledyn_msg_test(mixed_connect_coupled_cable msg_mixed_connect_coupled_cable.dat 1
"finite-EI LINE 3: a Coupled/Vessel End A .POINT 1. would need motionFile coupling to drive it;remove the Connect/Free points;held still .that route takes no motionFile either."
"is driven by a motionFile")
# A Pinned rod that its line turns at the static start: the completion line reports the move of its
# End B and its turn, not the zero translation of its pin.
cabledyn_msg_test(pinned_rod_turn msg_pinned_rod_turn.dat 0
"body/rod static equilibrium .1 object.s., largest move [1-9].[0-9]+E[-+][0-9]+ m, largest turn [1-9]"
"largest move 0.000E\\+00")
# The standalone mixed route warns about a coarse section and notes a static strain above maxStrain.
cabledyn_msg_test(mixed_coarse_strain msg_mixed_coarse_strain.dat 0
"WARNING: LINE 1 section of type \"chain\" .150.00 m in 1 segment.s.. has segments of 150.00 m, 17.6 %;Note: LINE 1 is stretched to a static strain of;above 1.00E-02 % .OPTION maxStrain."
Expand Down
7 changes: 4 additions & 3 deletions NOTICE
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,10 @@ OpenFAST (Apache License, Version 2.0)
https://github.com/OpenFAST/openfast

* integration/openfast/patches/ contains patches that MODIFY OpenFAST source
files (the root, openfast-library, and version CMakeLists.txt;
FAST_AeroMap.f90, FAST_Funcs.f90, FAST_Mapping.f90, FAST_ModGlue.f90,
FAST_Registry.txt, FAST_Solver.f90, FAST_Subs.f90, and FAST_Types.f90 in
files (the root, openfast-library, version, glue-codes/openfast and
glue-codes/fast-farm CMakeLists.txt; FAST_AeroMap.f90, FAST_Funcs.f90,
FAST_Mapping.f90, FAST_ModGlue.f90, FAST_Registry.txt, FAST_Solver.f90,
FAST_Subs.f90, and FAST_Types.f90 in
modules/openfast-library/src; FAST_Farm_IO.f90, FAST_Farm_Registry.txt,
FAST_Farm_Subs.f90, and FAST_Farm_Types.f90 in glue-codes/fast-farm/src).
The modified files remain under the Apache License, Version 2.0, and
Expand Down
7 changes: 5 additions & 2 deletions app/cabledyn.f90
Original file line number Diff line number Diff line change
Expand Up @@ -533,10 +533,13 @@ SUBROUTINE run_mixed_held_deck(deck, root, dt, has_dt, run_time, has_run_time, h
! name instead of silently holding zero fluid. The deck's own current is the aggregate's
! (deck_current), sampled at the nodes before every step at the step's t_committed. The
! driver holds the line end frames or turns them with the deck's vesselMotion table
! (host_orientation), and marches the deck's prescribed motion (prescribed_motion).
! (host_orientation), and marches the deck's prescribed motion (prescribed_motion). A
! TURBINES section places the Turbine<J> points and its records move and turn them
! (deck_turbines), as on the single-route decks.
CALL CD_AGG_Init_From_Deck(aggregate, deck, step_dt, es, em, forbid_deck_ambient=.TRUE., &
run_tmax=MAX(CD_ZERO, run_time), range_files=.TRUE., host_orientation=.TRUE., &
prescribed_motion=has_motion, static_run=nstep == 0, deck_current=.TRUE.)
prescribed_motion=has_motion, static_run=nstep == 0, deck_current=.TRUE., &
deck_turbines=.TRUE.)
IF (es /= CD_AGG_OK) THEN
CALL set_aggregate_error(es, em, run_stat, run_msg)
EXIT mixed_run
Expand Down
4 changes: 3 additions & 1 deletion doc/capabilities.rst
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,9 @@ rigid rods. In OpenFAST, ``Coupled``/``Vessel`` bodies and rods are platform-bor
return a force and a moment, ``CoupledPinned``/``VesselPinned`` rods turn about a platform-borne
node that takes the platform position only and returns a force with zero moment, as do
``CoupledPinned``/``VesselPinned`` bodies about a node at their reference point, and ``Pinned``
rods turn about a fixed End A. The C API and Python
rods turn about a fixed End A. A coupled deck (OpenFAST, the C API and Python) carries bodies or
rods, not both, a rod fixed to a body counting as a rod; the standalone driver's multibody march
takes both, as does MoorDyn (``CompMooring = 3``). The C API and Python
run free, fixed and pinned rods and free bodies in still water. The coupled body/rod routes carry
checkpoint state and SeaState drag, Froude–Krylov, and added mass.
``Rigid6`` also carries the documented hydrostatic restoring terms. Consult :doc:`driver_format`
Expand Down
1 change: 1 addition & 0 deletions doc/coupling.rst
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ is their zero-frequency reduction ``D − C A⁻¹ B``, not a derivative CableDy
command outside MoorDyn-F's bounds or one that would make a controlled segment
non-positive, and ``CONTROL`` of a finite-EI cable under ``False alpha_force_blend``,
- coupled ``Rigid6`` bodies and rods in a FAST.Farm deck,
- a deck with both bodies (Rigid6 or Point3) and rods, a rod fixed to a body included,
- deck ``waves``/``wavetrain`` OPTIONS (the host SeaState supplies the waves), and a deck
``current`` except as a steady current on a single-turbine, pure ``EI = 0`` deck without
Rigid6 bodies or rods in a SeaState without waves or current (a WaterKin ``CurrentMod 1``
Expand Down
7 changes: 5 additions & 2 deletions doc/driver_format.md
Original file line number Diff line number Diff line change
Expand Up @@ -596,8 +596,11 @@ follows `x + R(q) p`, with the rigid-body velocity and acceleration. A finite-EI
`Turbine<J>` point takes its `END CONNECTIONS` direction `Ez` and torsion normal `Nx` in that
turbine's axes: turned by the `PtfmInit` rotation at the static start and by `R(q)`, with the
row's angular velocity and acceleration, in the run (End A and End B alike), as the FAST.Farm
host's orientations turn them. In FAST.Farm the host supplies the turbine positions and the
section is not used.
host's orientations turn them. A `TURBINES` deck that mixes `EI = 0` lines and finite-EI cables (a
power cable shared by two turbines beside their chain legs) runs on the standalone mixed route,
the aggregate of FAST.Farm, with the same placement, records and end frames as the decks of its
cables alone and of its `EI = 0` lines alone. In FAST.Farm the host supplies the turbine positions
and the section is not used.

### ROD TYPES + RODS (rigid cylindrical rods)

Expand Down
12 changes: 10 additions & 2 deletions doc/openfast.rst
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,9 @@ solves once per that many glue steps, which is faster. Between commits the coupl
extrapolated from the last two commits (deck ``OPTIONS predictLoads``, the default) or, with
``predictLoads False``, held at the last commit, which delays them (see the note below). The
console reports the result, for
example ``CableDyn time step dtM = 2.50000E-02 s (1 x glue DT; deck dtM)``. A deck ``dtM``
example ``CableDyn time step dtM = 2.50000E-02 s (1 x glue DT; deck dtM)``; in FAST.Farm the
coupling step is the farm's mooring step ``DT_Mooring``, and the line reads ``1 x FAST.Farm
DT_Mooring``. A deck ``dtM``
larger than ``DT`` but not a whole multiple of it is never coarsened: CableDyn uses the largest
multiple of ``DT`` that does not exceed it and reports a warning with both values (``dtM = 0.025``
with ``DT = 0.01`` runs at 0.02 s), matching MoorDyn, which only ever shortens its step to fit the
Expand Down Expand Up @@ -427,7 +429,13 @@ without an auxiliary process:
held fluid stay those of the committed step). ``PtfmInit`` moves and turns such a rod with
the platform before the static solve balances it about its pin. ``Pinned`` rods turn about a
fixed End A. ``Coupled``/``Vessel`` bodies are platform-borne the same way as ``Coupled`` rods,
with the node at the body reference point, and may share a deck with ``Free`` bodies.
with the node at the body reference point, and may share a deck with ``Free`` bodies. A deck
carries bodies (Rigid6 or Point3) or rods, not both: the coupled march advances one of the two
families, and a rod fixed to a body (``RODS`` type ``Body<N>`` or ``Body<N>Pinned``) counts as a
rod, so such a deck stops at init (``a coupled deck with both BODIES and RODS is not
supported``). MoorDyn (``CompMooring = 3``) in the same binary runs it, and so does the
standalone driver's multibody march when the deck has no ``CoupledPinned`` objects (those run in
OpenFAST only).
``CoupledPinned``/``VesselPinned`` bodies are pinned to the platform like ``CoupledPinned`` rods:
the node at the body reference point follows the platform position only, the body turns about
it with its own three rotations (its inertia about the node, its weight and buoyancy at the
Expand Down
4 changes: 4 additions & 0 deletions doc/standalone_driver.rst
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,10 @@ formerly NREL) and advances the objects atomically. Every ``Coupled``/``Vessel``
at its initialised position, or follows the deck's ``motionFile`` or ``vesselMotion`` (a vessel
turns the end connection and torsion frames of the power cables on its points, and the
``motionFile`` roll column twists a cable restrained in torsion, as on the single-cable route).
A ``TURBINES`` deck (:doc:`driver_format`) places its ``Turbine<J>`` points from the section, and
its per-turbine ``motionFile`` records move them and turn the frames of the cable ends on them
with their turbine, so a FAST.Farm shared-mooring deck of power cables and chain legs runs here
as a whole.
A mixed deck that also has bodies, rods or ``Connect``/``Free`` points runs on the multibody
march instead (:doc:`driver_format`), which accepts deck waves and current. ``examples/iea15mw_umaine_mixed_cabledyn.dat`` is the maintained four-line
example; its ``TMax = 0`` setting writes the common static configuration. Give a positive ``TMax``
Expand Down
20 changes: 15 additions & 5 deletions doc/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -681,11 +681,15 @@ Warnings and notes that do not stop a run
torque–tension coupling (``GJ|K``) its stretch twists it by
:math:`-\sum (K/GJ)(l - L)`, so a free End B turns by :math:`+x` and a free End A by
:math:`-x` about the End A → End B tangent.
* - ``Note: line <L>: torsion solved, imposed twist ... deg, torque ... N m (<n> twist
stage(s), <m> buckling descent(s))``
- the static twist stage of a torsional line. A non-zero descent count means the straight or
untwisted branch was unstable at the imposed twist and the solve moved to a buckled shape;
check the shape and the ``Twist<L>`` channel.
* - ``Note: line <L>: torsion solved, total twist Twist<L> = ... deg (imposed Pretwist(B) -
Pretwist(A) = ... deg, with the end frames' turn and the shape's geometric twist), torque
... N m (<n> twist stage(s), <m> buckling descent(s))``
- the static twist stage of a torsional line. The total twist is the ``Twist<L>`` channel at
the static state: the imposed pretwist difference plus the turn of the end frames (a
``PtfmInit`` or ``TURBINES`` rotation of a parent turns its end) less the geometric twist the
line takes up by its shape; the torque follows from it. A non-zero descent count means the
straight or untwisted branch was unstable at the imposed twist and the solve moved to a
buckled shape; check the shape and the ``Twist<L>`` channel.
* - ``WARNING: CableDyn mooring module: <n> of the <N> CableDyn sampling nodes in the water
lie outside the SeaState wave-kinematics grid at t = ... s (warned once)`` (OpenFAST)
- the SeaState grid (``X_HalfWidth``, ``Y_HalfWidth``, ``Z_Depth``) does not cover the
Expand Down Expand Up @@ -901,6 +905,12 @@ aborts with a CableDyn fatal error, check whether the deck uses one of these com
* - a finite-EI cable in the same deck as Rigid6 bodies, rods, or ``Connect``/``Free`` points
- model the cable and the body/point system in separate decks or use the supported
combinations in :doc:`capabilities`
* - ``a coupled deck with both BODIES and RODS is not supported``: bodies (Rigid6 or Point3)
and rods in one deck, a rod fixed to a body (``Body<N>``, ``Body<N>Pinned``) included
- the coupled march advances the bodies or the rods of a deck, not both (also in the C API and
Python). Run the deck with stock MoorDyn (``CompMooring = 3``) in the same binary, or, without
``CoupledPinned`` objects, with the standalone driver, whose multibody march takes both; a
deck with only bodies or only rods runs coupled
* - OpenFAST linearisation of a cable with a ``Rigid`` ``END CONNECTIONS`` row (``formal
OpenFAST linearization of a cable with a rigid end connection is not supported``), of a deck
with ``Free`` or ``Connect`` points or a line with VIV (``Cl > 0``), or with a ``CONTROL``
Expand Down
8 changes: 7 additions & 1 deletion integration/openfast/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,13 @@ check the build:
```

The script fails unless `openfast.exe` builds, the smoke case initialises the CableDyn module, and
the output is finite to the last row. An `openfast.exe` built through CMake does not embed the
the output is finite to the last row. Configure with `-DBUILD_FASTFARM=ON` to build `FAST.Farm`
as well (target `FAST.Farm`); the release does not ship it, so FAST.Farm users take this route.
On Windows with the GNU compilers, patch `0022` links `openfast.exe` and `FAST.Farm.exe` with a
256 MiB stack reserve (`-Wl,--stack,268435456`, as the CableDyn driver): with the MinGW default
of 2 MiB, `FAST.Farm.exe` stops with `0xC00000FD` (stack overflow) while it initialises the
turbines of a farm, before any output. The reserve is address space, not committed memory; the
Visual Studio projects of the release set their own. An `openfast.exe` built through CMake does not embed the
UTF-8 active-code-page manifest, so on Windows it may not open input files in folders whose names
the system code page cannot spell; the static release build embeds it.

Expand Down
Loading
Loading