execution.rst

Execution

Executing FloatingSE requires additional inputs beyond those of the geometry definition described above in Section geometry-label. Other user inputs for the metocean and loading environment, and the operational constraints, are required to evaluate the total mass, cost, and code compliance. These variables are also included in the WindIO effort or found in the floating-specific examples for standalone execution.

Simulation Flow

Once the input variables are completely specified, FloatingSE executes the analysis of the substructure. Conceptually, the simulation is organized by the flowchart in fig_floatingse.

Conceptual diagram of FloatingSE execution.

From a more technical perspective, FloatingSE is an OpenMDAO Group, so the analysis sequence is broken down by the sub-groups and sub-components in the order that they are listed in Table [tbl:exec]. In an OpenMDAO group, sub-groups and components are given prefixes to aid in referring to specific variables. The prefixes used in FloatingSE are also listed in tbl_exec.

	Prefix	Name	Description
1)	tow	TowerLeanSE	Discretization of tower geometry (but no analysis)
2)	main	Column	Discretization and API Bulletin 2U compliance of main.vertical column
3)	off	Column	Discretization and API Bulletin 2U compliance of offset columns
4)	sg	SubstructureGeometry	Geometrical constraints on substructure
5)	mm	MapMooring	Mooring system analysis via pyMAP
6)	load	FloatingLoading	Structural analysis of complete floating turbine load path via pyFrame3DD
7)	subs	Substructure	Static stability and final mass and cost summation for generic substructure

Outputs are accumulated in each sub-group or component, and they either become inputs to other components, become constraints for optimization problems, become design variables for optimization problems, or can simply be ignored. Currently, a single execution of FloatingSE takes only a handful of seconds on a modern laptop computer.

Examples

As mentioned previously floating-specific examples examples are provided. These files are encoded with default starting configurations (from OC3 and OC4, respectively), with some modifications. There is an additional spar example that also has a ready configurations for optimization with design variables, constraints, and solvers options. A visualization of the geometries described by these examples is shown in fig_initial-spar and fig_initial-semi.

Spar example in FloatingSE taken from OC3 OC3 project.

Semi example in FloatingSE taken from OC4 OC4 project.

../../references.bib