-
Notifications
You must be signed in to change notification settings - Fork 524
Reasons for symmetric results of axial force and moments and well operated ElastoDyn simulation #3241
Replies: 2 comments · 14 replies
-
|
Dear @JongHoon-Jeong, Regarding (1), the sign change between the loads output at either end of a given element in SubDyn has been discussed in the following OpenFAST issue: #2781 and in the online SubDyn documentation on readthedocs: https://openfast.readthedocs.io/en/main/source/user/subdyn/theory.html#nodal-loads-calculation. The way SubDyn handles self weight and its implication on nodal load outputs has also been discussed in the following OpenFAST issue: #2325, along with a suggested workaround to improve the results. Regarding (2), when you say the "simulation runs fine", I assume you mean that both simulations are numerical stable, although the start-up transients differ. I would expect the use of initial conditions closer to the steady-state solution for a given set of conditions will have less start-up transients; is that what you are seeing? Using initial conditions that are far way from the steady-state solution will result in longer start-up transients, and may become unstable if, e.g., the controller gets confused by the state of the turbine and produces unreliable output. Best regards, |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
Dear Dr. Jonkman, ---------------------------- OUTPUT: SUMMARY & OUTFILE -------------------------------- (2) When comparing the case where initial conditions close to the steady-state solution are applied versus the case where initial conditions far from the steady-state solution are applied, the time required for the startup transient to settle is similar in both cases. While the Total Real Time is slightly shorter when using initial conditions closer to the steady-state solution (by approximately 0.01 hours), it is puzzling that both cases run successfully without significant differences. Thank you for your time and assistance. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
I give you ElastoDyn, SubDyn, fst with txt file, too. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Dear @JongHoon-Jeong, Regarding (1), I would expect increasing Regarding (2), can you quantitative results of what you are seeing, e.g., time series during the start-up transient? Best regards, |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Dear @JongHoon-Jeong, To @RBergua's point, does the solution of (1) change if you reduce Best regards, |
Beta Was this translation helpful? Give feedback.
All reactions
-
(1) SubDyn settings for NDiv = 2 (2) SubDyn settings for NDiv = 4 ------------------------- MEMBER OUTPUT LIST ------------------------------------------ Note that only a portion of the settings are shown here; the remaining parameters are configured with the same values as in (1).
For these simulations, WindType = 1 and WaveMod = 0 were applied, and the ElastoDyn settings are presented below.
All settings other than those described above were configured with the same values as in Case 1. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
To add one more note regarding 2., NDiv was set to 1 in SubDyn. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Dear @JongHoon-Jeong, Regarding (1), do the solutions eventually converge to similar answers for Regarding (2), does plotting the solution with Best regards, |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Dear Dr. Jonkman, I would like to wrap up our discussion on the issues I have been working on here. Regarding issue number 1, after speaking with my academic advisor, I came to understand that the answer to my question lies in structural analysis theory: when an external force is applied at one end of a beam, an equal force acts at the opposite end to maintain equilibrium. Regarding issue number 2, upon examining the graph results more carefully, I was able to see that a startup transient occurs at the very beginning. I believe it was not easy to notice because I was looking at approximately 3,600 seconds worth of data. I am currently enrolled as a master's degree student in graduate school. As I still lack knowledge in many areas, I am afraid I may have caused you inconvenience by asking such burdensome questions during your busy schedule, and I sincerely apologize for that. I am truly grateful for your consistent and kind responses throughout this discussion, and I sincerely hope that you remain in good health. Thank you very much. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
I am currently working with the example file '5MW_OC4Jckt_DLL_WTurb_WavesIrr_MGrowth' for a fixed offshore wind turbine in OpenFAST, and I have two questions regarding the results of two tasks I performed.
I extracted the time histories of axial forces and moments at the interface between the tower and the jacket. The axial forces at the bottom and top of the member — M1N1FMZe and M1N2FMZe — came out with the same magnitude but opposite signs (i.e., symmetric with respect to the time axis on a graph).
The same applies to M1N1MMZe and M1N2MMZe.
I previously read a post addressing a similar issue, which stated that although the force transmitted from the top to the bottom due to self-weight should theoretically make the axial forces and moments different, the weight is not directly used in the nodal output, so its effect is not reflected.
In that case, how can I get the axial forces and z-axis moments at the top and bottom nodes to come out asymmetrically (i.e., not mirror images of each other)?
The key SubDyn settings I used are as follows:
----------- SubDyn MultiMember Support Structure Input File ---------------------------
OC4 'Jacket' SubStructure Input File. The grouted connection is simulated with an equivalent tubular beam of enhanced properties. RRD 10/15/2013
-------------------------- SIMULATION CONTROL -----------------------------------------
False Echo - Echo input data to ".SD.ech" (flag)
"DEFAULT" SDdeltaT - Local Integration Step. If "default", the glue-code integration step will be used.
3 IntMethod - Integration Method [1/2/3/4 = RK4/AB4/ABM4/AM2].
True SttcSolve - Solve dynamics about static equilibrium point
-------------------- FEA and CRAIG-BAMPTON PARAMETERS ---------------------------------
3 FEMMod - FEM switch: element model in the FEM. [1= Euler-Bernoulli(E-B); 2=Tapered E-B (unavailable); 3= 2-node Timoshenko; 4= 2-node tapered Timoshenko (unavailable)]
2 NDiv - Number of sub-elements per member
8 Nmodes - Number of internal modes to retain. If Nmodes=0 --> Guyan Reduction. If Nmodes<0 --> retain all modes.
1 JDampings - Damping Ratios for each retained mode (% of critical) If Nmodes>0, list Nmodes structural damping ratios for each retained mode (% of critical), or a single damping ratio to be applied to all retained modes. (last entered value will be used for all remaining modes).
2 GuyanDampMod - Guyan damping {0=none, 1=Rayleigh Damping, 2=user specified 6x6 matrix}
0.000, 0.000 RayleighDamp - Mass and stiffness proportional damping coefficients (Rayleigh Damping) [only if GuyanDampMod=1]
6 GuyanDampSize - Guyan damping matrix (6x6) [only if GuyanDampMod=2]
0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00
0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00
0.0000e+00 0.0000e+00 1.066100e+06 0.0000e+00 0.0000e+00 0.0000e+00
0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00
0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00
0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00 0.0000e+00
---------------------------- OUTPUT: SUMMARY & OUTFILE --------------------------------
True SumPrint - Output a Summary File (flag)
0 OutCBModes - Output Guyan and Craig-Bampton modes {0: No output, 1: JSON output}, (flag)
0 OutFEMModes - Output first 30 FEM modes {0: No output, 1: JSON output} (flag)
False OutCOSM - Output cosine matrices with the selected output member forces (flag)
False OutAll - [T/F] Output all members' end forces
2 OutSwtch - [1/2/3] Output requested channels to: 1=.SD.out; 2=.out (generated by FAST); 3=both files.
True TabDelim - Generate a tab-delimited output in the .SD.out file
1 OutDec - Decimation of output in the .SD.out file
"F15.2" OutFmt - Output format for numerical results in the .SD.out file
"A11" OutSFmt - Output format for header strings in the .SD.out file
------------------------- MEMBER OUTPUT LIST ------------------------------------------
4 NMOutputs - Number of members whose forces/displacements/velocities/accelerations will be output (-) [Must be <= 99].
MemberID NOutCnt NodeCnt ![NOutCnt=how many nodes to get output for [< 10]; NodeCnt are local ordinal numbers from the start of the member, and must be >=1 and <= NDiv+1] If NMOutputs=0 leave blank as well.
(-) (-) (-)
101 2 1 2 ! M1
102 2 1 2 ! M2
103 2 1 2 ! M3
104 2 1 2 ! M4
------------------------- SDOutList: The next line(s) contains a list of output parameters that will be output in .SD.out or .out. ------
"M1N1FMZe, M1N2FMZe" - Leg1 dynamic forces
"M1N1MMXe, M1N1MMYe, M1N1MMZe, M1N2MMXe, M1N2MMYe, M1N2MMZe" - Leg1 dynamic moments
"M2N1FMZe, M2N2FMZe" - Leg1 dynamic forces
"M2N1MMXe, M2N1MMYe, M2N1MMZe, M2N2MMXe, M2N2MMYe, M2N2MMZe" - Leg1 dynamic moments
"M3N1FMZe, M3N2FMZe" - Leg1 dynamic forces
"M3N1MMXe, M3N1MMYe, M3N1MMZe, M3N2MMXe, M3N2MMYe, M3N2MMZe" - Leg1 dynamic moments
"M4N1FMZe, M4N2FMZe" - Leg1 dynamic forces
"M4N1MMXe, M4N1MMYe, M4N1MMZe, M4N2MMXe, M4N2MMYe, M4N2MMZe" - Leg1 dynamic moments
END of output channels and end of file. (the word "END" must appear in the first 3 columns of this line)
For this task, I tried to extract time histories of axial forces and moments at the top, middle, and bottom of the tower, and set the initial conditions in ElastoDyn accordingly. I ran the simulation multiple times with different settings, and what I found surprising is that the simulation runs fine whether I use setting (1) or setting (2) below.
Normally, to minimize startup transients that would arise from applying a large amount of simulation loading, and to ensure the controller operates from the correct initial values, one should use the values recommended in the NREL specification report for the ElastoDyn initial conditions.
(1)
---------------------- INITIAL CONDITIONS --------------------------------------
0 OoPDefl - Initial out-of-plane blade-tip displacement (meters)
0 IPDefl - Initial in-plane blade-tip deflection (meters)
0 BlPitch(1) - Blade 1 initial pitch (degrees)
0 BlPitch(2) - Blade 2 initial pitch (degrees)
0 BlPitch(3) - Blade 3 initial pitch (degrees) [unused for 2 blades]
0 TeetDefl - Initial or fixed teeter angle (degrees) [unused for 3 blades]
0 Azimuth - Initial azimuth angle for blade 1 (degrees)
12.1 RotSpeed - Initial or fixed rotor speed (rpm)
0 NacYaw - Initial or fixed nacelle-yaw angle (degrees)
0 TTDspFA - Initial fore-aft tower-top displacement (meters)
0 TTDspSS - Initial side-to-side tower-top displacement (meters)
0 PtfmSurge - Initial or fixed horizontal surge translational displacement of platform (meters)
0 PtfmSway - Initial or fixed horizontal sway translational displacement of platform (meters)
-0.00702 PtfmHeave - Initial or fixed vertical heave translational displacement of platform (meters)
0 PtfmRoll - Initial or fixed roll tilt rotational displacement of platform (degrees)
0 PtfmPitch - Initial or fixed pitch tilt rotational displacement of platform (degrees)
0 PtfmYaw - Initial or fixed yaw rotational displacement of platform (degrees)
(2)
---------------------- INITIAL CONDITIONS --------------------------------------
4.5 OoPDefl - Initial out-of-plane blade-tip displacement (meters)
-0.75 IPDefl - Initial in-plane blade-tip deflection (meters)
3.75 BlPitch(1) - Blade 1 initial pitch (degrees)
3.75 BlPitch(2) - Blade 2 initial pitch (degrees)
3.75 BlPitch(3) - Blade 3 initial pitch (degrees) [unused for 2 blades]
0 TeetDefl - Initial or fixed teeter angle (degrees) [unused for 3 blades]
0 Azimuth - Initial azimuth angle for blade 1 (degrees)
12.1 RotSpeed - Initial or fixed rotor speed (rpm)
0 NacYaw - Initial or fixed nacelle-yaw angle (degrees)
0.33 TTDspFA - Initial fore-aft tower-top displacement (meters)
-0.05 TTDspSS - Initial side-to-side tower-top displacement (meters)
0 PtfmSurge - Initial or fixed horizontal surge translational displacement of platform (meters)
0 PtfmSway - Initial or fixed horizontal sway translational displacement of platform (meters)
-0.00702 PtfmHeave - Initial or fixed vertical heave translational displacement of platform (meters)
0 PtfmRoll - Initial or fixed roll tilt rotational displacement of platform (degrees)
0 PtfmPitch - Initial or fixed pitch tilt rotational displacement of platform (degrees)
0 PtfmYaw - Initial or fixed yaw rotational displacement of platform (degrees)
Output parameters requested:
---------------------- OUTPUT --------------------------------------------------
True SumPrint - Print summary data to ".sum" (flag)
2 OutFile - Switch to determine where output will be placed: {1: in module output file only; 2: in glue code output file only; 3: both} (currently unused)
True TabDelim - Use tab delimiters in text tabular output file? (flag) (currently unused)
"F15.2" OutFmt - Format used for text tabular output (except time). Resulting field should be 10 characters. (quoted string) (currently unused)
30 TStart - Time to begin tabular output (s) (currently unused)
1 DecFact - Decimation factor for tabular output {1: output every time step} (-) (currently unused)
3 NTwGages - Number of tower nodes that have strain gages for output [0 to 9] (-)
1, 10, 20 TwrGagNd - List of tower nodes that have strain gages [1 to TwrNodes] (-) [unused if NTwGages=0]
0 NBlGages - Number of blade nodes that have strain gages for output [0 to 9] (-)
0 BldGagNd - List of blade nodes that have strain gages [1 to BldNodes] (-) [unused if NBlGages=0]
OutList - The next line(s) contains a list of output parameters. See OutListParameters.xlsx for a listing of available output channels, (-)
"TwHt1FLzt" - Local tower yaw (or torsional) force of tower gage 1
"TwHt1MLxt" - Local tower roll (or side-to-side) moment of tower gage 1
"TwHt1MLyt" - Local tower pitching (or fore-aft) moment of tower gage 1
"TwHt1MLzt" - Local tower yaw (or torsional) moment of tower gage 1
"TwHt2FLzt" - Local tower yaw (or torsional) force of tower gage 2
"TwHt2MLxt" - Local tower roll (or side-to-side) moment of tower gage 2
"TwHt2MLyt" - Local tower pitching (or fore-aft) moment of tower gage 2
"TwHt2MLzt" - Local tower yaw (or torsional) moment of tower gage 2
"TwHt3FLzt" - Local tower yaw (or torsional) force of tower gage 3
"TwHt3MLxt" - Local tower roll (or side-to-side) moment of tower gage 3
"TwHt3MLyt" - Local tower pitching (or fore-aft) moment of tower gage 3
"TwHt3MLzt" - Local tower yaw (or torsional) moment of tower gage 3
END of OutList section (the word "END" must appear in the first 3 columns of the last OutList line)
Beta Was this translation helpful? Give feedback.
All reactions