JE et al 2015a - Revision history

Julio at 12:18, 4 January 2017

2017-01-04T12:18:40Z

Julio at 12:12, 4 January 2017

2017-01-04T12:12:38Z

Julio at 12:12, 4 January 2017

2017-01-04T12:12:24Z

Julio at 12:12, 4 January 2017

2017-01-04T12:12:04Z

Julio at 12:11, 4 January 2017

2017-01-04T12:11:59Z

Show changes

Julio at 12:07, 4 January 2017

2017-01-04T12:07:43Z

Julio at 12:06, 4 January 2017

2017-01-04T12:06:42Z

Julio at 12:06, 4 January 2017

2017-01-04T12:06:17Z

Julio at 12:05, 4 January 2017

2017-01-04T12:05:42Z

Julio at 12:04, 4 January 2017

2017-01-04T12:04:07Z

@@ Line 379: / Line 379: @@
 |[[Image:draft_Gutiérrez Romero_359737809-Fig_08a.png|400px|]]
 |[[Image:draft_Gutiérrez Romero_359737809-Fig_08b.png|400px|]]
-|-
+|[[Image:draft_Gutiérrez Romero_359737809-Fig_08c.png|400px|]]
-| colspan="2"|[[Image:draft_Gutiérrez Romero_359737809-Fig_08c.png|420px|Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.]]
 |- style="text-align: center; font-size: 75%;"
-| colspan="2" | '''Figure 8:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.
+| colspan="3" | '''Figure 8:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.
 |}
@@ Line 390: / Line 389: @@
 |[[Image:draft_Gutiérrez Romero_359737809-Fig_9a.png|400px|]]
 |[[Image:draft_Gutiérrez Romero_359737809-Fig_9b.png|400px|]]
-|-
+|[[Image:draft_Gutiérrez Romero_359737809-Fig_9c.png|400px|]]
-| colspan="2"|[[Image:draft_Gutiérrez Romero_359737809-Fig_9c.png|420px|Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.]]
 |- style="text-align: center; font-size: 75%;"
-| colspan="2" | '''Figure 9:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.
+| colspan="3" | '''Figure 9:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.
 |}
@@ Line 400: / Line 398: @@
 |-
 |[[Image:draft_Gutiérrez Romero_359737809-Fig_10a.png|400px|]]
-|[[Image:draft_Gutiérrez Romero_359737809-Fig_10b.png|400px|Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.]]
+|[[Image:draft_Gutiérrez Romero_359737809-Fig_10b.png|400px|]]
 |- style="text-align: center; font-size: 75%;"
 | colspan="2" | '''Figure 10:''' Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.

← Older revision		Revision as of 12:12, 4 January 2017
Line 472:		Line 472:

	Tracy C. 2007. Parametric design of floating wind turbines. M.S. Thesis. Boston (USA): Massachusetts Institute of Technology.		Tracy C. 2007. Parametric design of floating wind turbines. M.S. Thesis. Boston (USA): Massachusetts Institute of Technology.
−
−	~~==Captions for Figures==~~
−
−	~~Figure 1: Scheme showing the general approach of the software application.~~
−
−	~~Figure 2: Advanced capacities of ''Lognoter forms''. Screen example taken from ''MorisonForm'' GUI.~~
−
−	~~Figure 3: Screen showing the edit field option on ''Lognoter'' GUI.~~
−
−	~~Figure 4: MorisonForm GUI.~~
−
−	~~Figure 5: Page distribution of MorisonForm.~~
−
−	~~Figure 6: Preliminary idea of coupling with ''FASTLognoter''.~~
−
−	~~Figure 7: Different types of analysed platforms.~~
−
−	~~Figure 8: Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.~~
−
−	~~Figure 9: Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.~~
−
−	~~Figure 10: Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.~~

← Older revision		Revision as of 12:12, 4 January 2017
Line 472:		Line 472:

	Tracy C. 2007. Parametric design of floating wind turbines. M.S. Thesis. Boston (USA): Massachusetts Institute of Technology.		Tracy C. 2007. Parametric design of floating wind turbines. M.S. Thesis. Boston (USA): Massachusetts Institute of Technology.
−
−	~~==Captions for Tables==~~
−
−	~~Table 1: Properties of analysed platforms (Fig. 7).~~
−
−	~~Table 2: Natural frequencies of analyzed OWT devices, in rad/s (Fig. 7).~~

	==Captions for Figures==		==Captions for Figures==

← Older revision		Revision as of 12:12, 4 January 2017
Line 500:		Line 500:

	Figure 10: Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.		Figure 10: Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.
−
−	~~==Tables==~~
−
−
−	~~{\| class="wikitable" style="text-align: center; margin: 1em auto;"~~
−	~~\|+ <span id='table-1'></span>Table. 1 Properties of analysed platforms (Fig. 7).~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Platform characteristics~~
−	~~\| OC3~~
−	~~\| OC4~~
−	~~\| NREL/MIT TLP~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Diameter (m)~~
−	~~\| <math>6.5-9.4</math>~~
−	~~\| <math>47.54</math>~~
−	~~\| <math>18.0</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Draft (m)~~
−	~~\| <math>120</math>~~
−	~~\| <math>20</math>~~
−	~~\| <math>47.9</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Depth (m)~~
−	~~\| <math>320</math>~~
−	~~\| <math>200</math>~~
−	~~\| <math>200</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Water displacement (m<math display="inline">^{3}</math>)~~
−	~~\| <math>8029</math>~~
−	~~\| <math>13140</math>~~
−	~~\| <math>12180</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Mass, including ballast (kg)~~
−	~~\| <math>7.466\times 10^{7}</math>~~
−	~~\| <math>1.347\times 10^{7}</math>~~
−	~~\| <math>8.600\times 10^{6}</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| CM location below SWL<span id="fnc-2"></span>[[#fn-2\|<sup>1</sup>]] (m)~~
−	~~\| <math>-89.92</math>~~
−	~~\| <math>-13.46</math>~~
−	~~\| <math>-40.61</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Roll inertia about CM (kg.m<math display="inline">^{2}</math>)~~
−	~~\| <math>4.230\times 10^{9}</math>~~
−	~~\| <math>6.827\times 10^{9}</math>~~
−	~~\| <math>5.716\times 10^{9}</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Pitch inertia about CM (kg.m<math display="inline">^{2}</math>)~~
−	~~\| <math>4.230\times 10^{9}</math>~~
−	~~\| <math>6.827\times 10^{9}</math>~~
−	~~\| <math>5.716\times 10^{9}</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Yaw inertia about CM (kg.m<math display="inline">^{2}</math>)~~
−	~~\| <math>1.640\times 10^{8}</math>~~
−	~~\| <math>1.226\times 10^{10}</math>~~
−	~~\| <math>3.614\times 10^{9}</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Number of mooring lines~~
−	~~\| <math>3</math>~~
−	~~\| <math>3</math>~~
−	~~\| <math>8</math>(4 pairs)~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Unstretched line length (m)~~
−	~~\| <math>902.2</math>~~
−	~~\| <math>835.5</math>~~
−	~~\| <math>151.7</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Line diameter (m)~~
−	~~\| <math>0.09</math>~~
−	~~\| <math>0.077</math>~~
−	~~\| <math>0.127</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Line mass density (Kg.m<math display="inline">^{-1}</math>)~~
−	~~\| <math>77.71</math>~~
−	~~\| <math>113.4</math>~~
−	~~\| <math>116.0</math>~~
−	~~\|- style="border-top: 2px solid;border-bottom: 2px solid;"~~
−	~~\| style="text-align: left;" \| Line extensional stiffness (N)~~
−	~~\| <math>3.840\times 10^{8}</math>~~
−	~~\| <math>7.530\times 10^{8}</math>~~
−	~~\| <math>1.500\times 10^{9}</math>~~
−
−	\|}
−
−
−	~~{\| class="wikitable" style="text-align: center; margin: 1em auto;"~~
−	~~\|+ <span id='table-2'></span>Table. 2 Natural frequencies of analysed OWT devices, in rad/s (Fig. 7).~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Platform characteristics~~
−	~~\| OC3~~
−	~~\| OC4~~
−	~~\| NREL/MIT TLP~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Surge~~
−	~~\| <math>0.05051</math>~~
−	~~\| <math>0.05450</math>~~
−	~~\| <math>0.1037</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Sway~~
−	~~\| <math>0.05051</math>~~
−	~~\| <math>0.05450</math>~~
−	~~\| <math>0.1037</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Heave~~
−	~~\| <math>0.2026</math>~~
−	~~\| <math>0.3468</math>~~
−	~~\| <math>2.749</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Roll~~
−	~~\| <math>0.2149</math>~~
−	~~\| <math>0.1820</math>~~
−	~~\| <math>1.422</math>~~
−	~~\|- style="border-top: 2px solid;"~~
−	~~\| style="text-align: left;" \| Pitch~~
−	~~\| <math>0.2155</math>~~
−	~~\| <math>0.1820</math>~~
−	~~\| <math>1.389</math>~~
−	~~\|- style="border-top: 2px solid;border-bottom: 2px solid;"~~
−	~~\| style="text-align: left;" \| Yaw~~
−	~~\| <math>0.7603</math>~~
−	~~\| <math>0.1699</math>~~
−	~~\| <math>0.6107</math>~~
−
−	\|}
−
−	~~<span id="fn-2"></span>~~
−	~~<span style="text-align: center; font-size: 75%;">([[#fnc-2\|<sup>1</sup>]]) Still water level</span>~~

← Older revision		Revision as of 12:07, 4 January 2017
Line 473:		Line 473:
	<span id="fn-2"></span>		<span id="fn-2"></span>
	<span style="text-align: center; font-size: 75%;">([[#fnc-2\|<sup>1</sup>]]) Still water level</span>		<span style="text-align: center; font-size: 75%;">([[#fnc-2\|<sup>1</sup>]]) Still water level</span>
−
−	~~==FIGURES==~~
−
−	~~<div id='img-1'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_01.png\|600px\|Scheme showing the general approach of the software application.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 1:''' Scheme showing the general approach of the software application.~~
−	\|}
−
−	~~<div id='img-2'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_02.png\|600px\|Advanced capacities of ''Lognoter forms''. Screen example taken from ''MorisonForm'' GUI.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 2:''' Advanced capacities of ''Lognoter forms''. Screen example taken from ''MorisonForm'' GUI.~~
−	\|}
−
−	~~<div id='img-3'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_03.png\|600px\|Screen showing the edit field option on ''Lognoter'' GUI.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 3:''' Screen showing the edit field option on ''Lognoter'' GUI.~~
−	\|}
−
−	~~<div id='img-4'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_04.png\|600px\|MorisonForm GUI.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 4:''' MorisonForm GUI.~~
−	\|}
−
−	~~<div id='img-5'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_05.png\|600px\|Page distribution of MorisonForm.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 5:''' Page distribution of MorisonForm.~~
−	\|}
−
−	~~<div id='img-6'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_06.png\|600px\|Preliminary idea of coupling with ''FASTLognoter''.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 6:''' Preliminary idea of coupling with ''FASTLognoter''.~~
−	\|}
−
−	~~<div id='img-7'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_07.png\|600px\|Different types of analysed platforms.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="1" \| '''Figure 7:''' Different types of analysed platforms.~~
−	\|}
−
−	~~<div id='img-8'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_08a.png\|400px\|]]~~
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_08b.png\|400px\|]]~~
−	\|-
−	~~\| colspan="2"\|[[Image:draft_Gutiérrez Romero_359737809-Fig_08c.png\|420px\|Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="2" \| '''Figure 8:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a OC3 Spar-Hywind platform.~~
−	\|}
−
−	~~<div id='img-9'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_9a.png\|400px\|]]~~
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_9b.png\|400px\|]]~~
−	\|-
−	~~\| colspan="2"\|[[Image:draft_Gutiérrez Romero_359737809-Fig_9c.png\|420px\|Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="2" \| '''Figure 9:''' Response Amplitude Operators (RAOs) for a) surge, b) heave and c) pitch, for a TLP MIT/NREL platform.~~
−	\|}
−
−	~~<div id='img-10'></div>~~
−	~~{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"~~
−	\|-
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_10a.png\|400px\|]]~~
−	~~\|[[Image:draft_Gutiérrez Romero_359737809-Fig_10b.png\|400px\|Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.]]~~
−	~~\|- style="text-align: center; font-size: 75%;"~~
−	~~\| colspan="2" \| '''Figure 10:''' Response Amplitude Operators (RAOs) for a) surge and b) pitch, for a OC4 semisubmersible platform.~~
−	\|}

← Older revision		Revision as of 12:06, 4 January 2017
Line 234:		Line 234:

	In order to illustrate the use of the presented GUIs, a study of different types of OWT platform is chosen as a powerful application. The seakeeping analysis for three representative kinds of typical platform design (see Fig. 7) for FOWT (Flotating Offshore Wind Tubine) is carried out, assuming the marine wind turbines are under steady-state operating conditions. The study is mandatorily coupled, that is, both the aerodynamic and the hydrodynamic effects are included and linked. ''FASTLognoter'' (Gutiérrez, Zamora, et al. 2013) is employed for calculating the linear representation of a given wind turbine (''NREL baseline 5 MW'', Jonkman, Butterfield, et al. 2009), whereas WAMIT (www.wamit.com) or SeaFEM (www.compassis.com) are used to get the added mass and radiation terms of the FOWT. Typical results are the RAOs of the structures studied for different degrees of freedom, which leads to systematic comparisons between the behaviour of devices.		In order to illustrate the use of the presented GUIs, a study of different types of OWT platform is chosen as a powerful application. The seakeeping analysis for three representative kinds of typical platform design (see Fig. 7) for FOWT (Flotating Offshore Wind Tubine) is carried out, assuming the marine wind turbines are under steady-state operating conditions. The study is mandatorily coupled, that is, both the aerodynamic and the hydrodynamic effects are included and linked. ''FASTLognoter'' (Gutiérrez, Zamora, et al. 2013) is employed for calculating the linear representation of a given wind turbine (''NREL baseline 5 MW'', Jonkman, Butterfield, et al. 2009), whereas WAMIT (www.wamit.com) or SeaFEM (www.compassis.com) are used to get the added mass and radiation terms of the FOWT. Typical results are the RAOs of the structures studied for different degrees of freedom, which leads to systematic comparisons between the behaviour of devices.
		+
		+	<div id='img-7'></div>
		+	{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"
		+	\|-
		+	\|[[Image:draft_Gutiérrez Romero_359737809-Fig_07.png\|600px\|Different types of analysed platforms.]]
		+	\|- style="text-align: center; font-size: 75%;"
		+	\| colspan="1" \| '''Figure 7:''' Different types of analysed platforms.
		+	\|}

	===4.2 Dynamic analysis of FOWTs and validation===		===4.2 Dynamic analysis of FOWTs and validation===

← Older revision		Revision as of 12:06, 4 January 2017
Line 218:		Line 218:

	In order to analyze the dynamic behaviour of offshore structures, coupling between hydrodynamics, aerodynamics and mooring effects is required. Obviously, several complex effects can be found in OWT devices, and this fact makes it harder to do a complete study of marine structures. So, the aim of the ''MorisonForm'' development is to get a rough estimation of the dynamics of OWT, as previously explained. The preliminary idea concerning the coupling between the presented GUI and ''FASTLognoter'' is outlined in Fig. 6. ''FASTLognoter'' allows the linearization of the wind turbine, using FAST code, at the operation point. The results of the linearization are periodic state matrices, which can be added into ''MorisonForm'' GUI; then, the user can conduct an appropriate coupled analysis of the OWT in working operation.		In order to analyze the dynamic behaviour of offshore structures, coupling between hydrodynamics, aerodynamics and mooring effects is required. Obviously, several complex effects can be found in OWT devices, and this fact makes it harder to do a complete study of marine structures. So, the aim of the ''MorisonForm'' development is to get a rough estimation of the dynamics of OWT, as previously explained. The preliminary idea concerning the coupling between the presented GUI and ''FASTLognoter'' is outlined in Fig. 6. ''FASTLognoter'' allows the linearization of the wind turbine, using FAST code, at the operation point. The results of the linearization are periodic state matrices, which can be added into ''MorisonForm'' GUI; then, the user can conduct an appropriate coupled analysis of the OWT in working operation.
		+
		+	<div id='img-6'></div>
		+	{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"
		+	\|-
		+	\|[[Image:draft_Gutiérrez Romero_359737809-Fig_06.png\|600px\|Preliminary idea of coupling with ''FASTLognoter''.]]
		+	\|- style="text-align: center; font-size: 75%;"
		+	\| colspan="1" \| '''Figure 6:''' Preliminary idea of coupling with ''FASTLognoter''.
		+	\|}

	Most of the data may be estimated using the pre-processors added into ''FASTLognoter'' GUI. Thus, ''MorisonForm'' acts when the user has obtained the periodic state matrix. Finally, the user can calculate the forces and moments exerted by wave loads, and the transfer functions of the OWT device, i.e., Response Amplitude Operators (RAOs), which are key elements in the study of the behaviour of marine structures.		Most of the data may be estimated using the pre-processors added into ''FASTLognoter'' GUI. Thus, ''MorisonForm'' acts when the user has obtained the periodic state matrix. Finally, the user can calculate the forces and moments exerted by wave loads, and the transfer functions of the OWT device, i.e., Response Amplitude Operators (RAOs), which are key elements in the study of the behaviour of marine structures.

@@ Line 184: / Line 184: @@
 ''MorisonForm'' is developed using ''Lognoter'' and employing the advanced features of this tool; that is to say, Tcl/Tk, XML and a database such as SQlite computer programming. This allows the addition of a database with the tubular elements that form the structure. The tool can classify different types of project and sea conditions. To give the user more information about the software management, theory introduction and several explanations are included in an options tree, as well as dynamic help and adapted sight. The results can be exported to a compatible format with data processing programs, and can be plotted through Tk tool added into GUI (see Fig. 4).
 Regarding other features of the presented GUI, those exposed above for ''Lognoter forms'' can be underlined. The GUI is divided into pages related to specific parameters of the calculus (see Fig. 5). These pages are the following:
@@ Line 196: / Line 204: @@
 * ''Analysis''. Here, the buttons for carrying out the analysis and plotting the results are placed.
 * ''Wave analysis''. The variance of the motion for different spectral density of the ambient waves can be evaluated in this section.
 ''MorisonForm'' includes the capability of adding mooring effects into restoring terms. The user can insert catenary or taut lines, and also spread mooring lines. Note that these terms are static and only give the user a rough approximation about the effects into the behaviour of the OWT devices (Faltinsen 1990). In additon, use of presented GUI leads to obtaining the variance of the motion, using different spectral models, such as Pierson-Mostkowitz or JONSWAP (Gran 1992). Finally, one of the most advanced features of the GUIs is the capability of modifying, adding or removing code from the form. Therefore, the user can edit the form and add code easily. This fact achieves the feature improvement of the forms, making the GUI a powerful tool; besides, the tool can be adapted to several projects and subjects.

← Older revision		Revision as of 12:04, 4 January 2017
Line 42:		Line 42:

	One of the most useful advantages of using ''Lognoter forms'' is the XML format for editing the GUIs. XML programming is an open and flexible standard derived from SGML (''Standard Generalised Markup Language''). It was designed to transport and store data (with focus on what data is), constitutes a W3C recommendation (''World Wide Web Consortium'', www.w3.org) and is endorsed by software market leaders. In ''Lognoter forms'', the information is stored in plain text format. It can be viewed in all major browsers and is designed to be self-descriptive. The elements in a ''Lognoter'' GUI outline a ''tree-structure'', starting at the root and progressing towards the leaves, through the branches, with different relationships between the nested elements. The XML elements are defined using fixed ''tags'' and can have ''attributes'', which provide additional information about elements inserted into ''Lognoter form''. ''Lognoter'' GUI also allows the user to edit and create new forms using its tools, avoiding programming editions. Figure 3 shows the option edit field on ''Lognoter'' GUI.		One of the most useful advantages of using ''Lognoter forms'' is the XML format for editing the GUIs. XML programming is an open and flexible standard derived from SGML (''Standard Generalised Markup Language''). It was designed to transport and store data (with focus on what data is), constitutes a W3C recommendation (''World Wide Web Consortium'', www.w3.org) and is endorsed by software market leaders. In ''Lognoter forms'', the information is stored in plain text format. It can be viewed in all major browsers and is designed to be self-descriptive. The elements in a ''Lognoter'' GUI outline a ''tree-structure'', starting at the root and progressing towards the leaves, through the branches, with different relationships between the nested elements. The XML elements are defined using fixed ''tags'' and can have ''attributes'', which provide additional information about elements inserted into ''Lognoter form''. ''Lognoter'' GUI also allows the user to edit and create new forms using its tools, avoiding programming editions. Figure 3 shows the option edit field on ''Lognoter'' GUI.
		+
		+	<div id='img-2'></div>
		+	{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"
		+	\|-
		+	\|[[Image:draft_Gutiérrez Romero_359737809-Fig_02.png\|600px\|Advanced capacities of ''Lognoter forms''. Screen example taken from ''MorisonForm'' GUI.]]
		+	\|- style="text-align: center; font-size: 75%;"
		+	\| colspan="1" \| '''Figure 2:''' Advanced capacities of ''Lognoter forms''. Screen example taken from ''MorisonForm'' GUI.
		+	\|}
		+
		+	<div id='img-3'></div>
		+	{\| style="text-align: center; border: 1px solid #BBB; margin: 1em auto; width: 100%;max-width: 100%;"
		+	\|-
		+	\|[[Image:draft_Gutiérrez Romero_359737809-Fig_03.png\|600px\|Screen showing the edit field option on ''Lognoter'' GUI.]]
		+	\|- style="text-align: center; font-size: 75%;"
		+	\| colspan="1" \| '''Figure 3:''' Screen showing the edit field option on ''Lognoter'' GUI.
		+	\|}

	===2.3 Adding new functions and procedures using Tcl/Tk programming===		===2.3 Adding new functions and procedures using Tcl/Tk programming===