The phase angle corresponding to the surge RAO. The phase angle corresponding to the heave RAO.
![orcaflex wamit input orcaflex wamit input](https://www.open-ocean.org/wp-content/uploads/2021/04/image-23-1024x454.png)
The RAO in pitch, corresponding to the specified heading and frequency. The RAO in roll, corresponding to the specified heading and frequency. The RAO in yaw, corresponding to the specified heading and frequency. The RAO in sway, corresponding to the specified heading and frequency. The RAO in surge, corresponding to the specified heading and frequency. The RAO in heave, corresponding to the specified heading and frequency. The format of the RAO data, if an RAO conversion is being applied. The entire block of data can then be repeated to specify force RAO data for subsequent vessels if required. This concludes the specification for externally imported RAO data. This is followed by an optional line which indicates the units used in this RAO file. Program Name may be AQWA, WAMIT, MOSES or ORCAFLEX. The next two lines specify the name of the external program from which the RAO data originates and the path of the file containing the RAO data. The Vessel Name specified here must be defined under the *VESSEL keyword. This concludes the specification for explicitly specified RAO data. Flexcom automatically sorts the RAO data by heading and frequency. Note also that the order in which the lines of RAO data appear is not important. If the same wave heading is specified on all lines, then Flexcom assumes that the RAOs are independent of wave heading.
![orcaflex wamit input orcaflex wamit input](https://i1.rgstatic.net/publication/255247579_Investigation_of_a_FAST-OrcaFlex_Coupling_Module_for_Integrating_Turbine_and_Mooring_Dynamics_of_Offshore_Floating_Wind_Turbines_Preprint/links/559abd9008ae5d8f3937ed2c/largepreview.png)
So, for example, if RAOs were to be defined at three wave headings and ten frequencies per heading, then 30 lines of data would be required to specify the RAOs using the Line layout. As with the MCS layout, if RAOs are being defined at more than one incident wave heading, then they must also be defined at more than one frequency at each wave heading, and the number of frequencies at which the RAOs are defined is the same for each heading.
![orcaflex wamit input orcaflex wamit input](https://www.orcina.com/webhelp/OrcaFlex/Content/image/drawings/ImportWAMITVectors.png)
This line is repeated for every wave frequency and every wave heading for which RAOs are being defined. Sway RAO, Sway Phase, Yaw RAO, Yaw Phase, Roll RAO, Roll Phase, Pitch RAO, Wave Heading, Wave Frequency, Heave RAO, Heave Phase, Surge RAO, Surge Phase, Note that, for clarity, the data shown below is split over a number of lines, but is in reality specified on a single line of the RAO file. The Line layout is very similar to the standard MCS layout, with the exception that the RAO and phase data for a particular heading and frequency appear on a single line, the format of which is shown below. If the RAOs are independent of the incident wave heading, then the HEADING= line should be omitted. If RAOs are being defined for more than one incident wave heading, then they must also be defined for more than one frequency at each wave heading, and the number of frequencies at which the RAOs are defined is the same for each heading. To define RAOs at more incident wave headings, you simply repeat the HEADING= line for the new wave heading, and the RAO data for this wave heading is specified as before. The block of three lines specifying the incident wave frequency, RAOs and phases are repeated as often as necessary until the RAOs are defined over the required range of wave frequencies. Heave Phase, Surge Phase, Sway Phase, Yaw Phase, Roll Phase, Pitch Phase Heave RAO, Surge RAO, Sway RAO, Yaw RAO, Roll RAO, Pitch RAO
![orcaflex wamit input orcaflex wamit input](https://i1.rgstatic.net/publication/356610819_Modeling_the_TetraSpar_Floating_Offshore_Wind_Turbine_Foundation_as_a_Flexible_Structure_in_OrcaFlex_and_OpenFAST/links/61a5608eee3e086e3d3bf5d1/largepreview.png)
Note that entries shown below in italics should be replaced with their actual numeric values in the RAO file. This is followed by a block of three lines specifying the incident wave frequency and the relevant RAO amplitudes and phases for this heading and wave frequency, as shown below. The MCS layout begins with a single line defining the incident wave heading at which the RAOs are being defined. The next line can either specify a File Name (file path of a file containining the RAO data), or is the first of many lines defining RAO data in the keyword file directly.įlexcom supports two different schemes for laying out RAO data, namely the MCS layout and the Line layout. Layout Name can be either MCS or LINE, defaulting to MCS if omitted. Format Name cannot be MCS, AQWA, WAMIT, MOSES or ORCAFLEX – these are predefined formats. Data for any conversion format referenced here must be input under *RAO FORMAT. An optional line can be added on the second line, referencing an RAO conversion, and/or defining the layout of the RAO data. The Vessel Name specified must be defined under the *VESSEL keyword. The data may be explicitly defined, or imported from a file which is generated by an external program. Keyword Formatīlock of data consisting of a vessel name followed by RAO data. Refer to High Frequency RAO Motions for further information on this feature. To specify Response Amplitude Operators for a vessel.