You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Static input file format inhibits flexibility #140
The current input handling in the NWTC Library expects a mostly static input file format (I say "mostly" because at least one example of a dynamic input file format exists in beamdyn_driver). This means that any new feature which needs input will cause a breaking API change and, therefore, requires a new major version number according to the rules of semantic versioning.
It has been proposed to implement a more dynamic input system with a flexible syntax and default values where appropriate (something dictionary based, yaml, json, etc). This would allow backwards compatibility when new features are introduced and enable simpler restructuring of the input file.
While I am generally supportive of the proposal, we chose against it in the past due the large amount of work involved. Not only does the input-file processing within OpenFAST have to change, but all of the scripts that run batch simulations of OpenFAST must change. Of course, such an endeavor does not have to done at one time, but can be tacked on a module-by-module basis.
Currently, I am struggling with stand-alone BeamDyn input files( Dvr_5MW_static.inp, Static_BeamDyn_input_5MW.inp, 5MW_Blade_IEC.inp). I wonder if you could help me to change the length of the blade in the input file and also I wanted to know the difference between nodes and number of key points on member(kp_total). because for instance I want to consider 6 nodes on the member and then applying load on each node.
Thank you for you response. the links that you sent were useful. now I am just wondering how is it possible to change some parameters such as length in addition to the stand-alone BeamDyn input files.
the driver input file for the stand-alone version only contains the parameters on how you want to load the blade and how the blade is oriented.
The BeamDyn Primary input file contains the parameters for the SFEM-solver and the reference axis of the blade. The blade length is defined by the length of the reference axis, set by the key points. The Blade input file contains the cross-sectional structural and mass properties of the blade.
Thank you for your time and consideration. actually I'm new to it and thank you in advance for your understanding.
I set 7 for both kp-total and station total but I faced with this error;
" BD_Init:BD_ValidateInputData:The last station_eta must be equal to 1.0 (tip)
BeamDyn Driver encountered simulation error level: FATAL ERROR "
The keypoints determine the (possiblu curved) reference axis of the blade. This blade cross-sectional properties are defined at stations along this reference axis. The distance along the reference axis from the root of the blade to each station is normalized between 0 and 1 (station_eta) in the BeamDyn blade input file.
Thank you for your good explanation.
The last station_eta is equal to 1 in the BeamDyn blade input file but why should I have this type of error that says "The last station_eta must be equal to 1.0(tip)" !
Or maybe something else should be changed in order to to solve this error which I don't know about that.
Hi Pouria, I could only see screenshots in the zip file, could you send the input file as a text file as well? Maybe the number of stations does not match. As a quick check you could try using only station_total=2 and then defining only eta=0 and eta=1 in the file.
with station_total=2 by defining only eta=0 and eta=1 in the input file this error occurred " Load may be too large, BeamDyn will attempt to solve with additional steps. Maximum number of load steps reached. "
---------------------- BLADE PARAMETERS --------------------------------------
2 station_total - Number of blade input stations (-)
1 damp_type - Damping type (switch): 0: no damping; 1: viscous damping
---------------------- DAMPING COEFFICIENT------------------------------------
mu1 mu2 mu3 mu4 mu5 mu6
(s) (s) (s) (s) (s) (s)
1.0E-03 1.0E-03 1.0E-03 1.0E-03 1.0E-03 1.0E-03
---------------------- DISTRIBUTED PROPERTIES---------------------------------
0.000000
9.729480E+08 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 9.729480E+08 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 9.729480E+09 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 1.811360E+10 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 1.811000E+10 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 5.564400E+09
I agree with @ebranlard that your original model likely has more than 14 stations where the distributed mass and stiffness data are defined even though your input file had station_total = 14 (but it is difficult to confirm without the text-based input).
When switching to station_total = 2, the trapezoidal quadrature you are using (quadrature = 2) is very coarse, causing the new issue you are seeing. When using station_total = 2 with quadrature = 2, you should set refine to a sufficiently large value to sufficiently resolve the blade (e.g., refine = 20).
As mentioned by Jason, I'd recommend checking the syntax of your previous input file that had 14 stations.
If you experience further problems, feel free to post another issue on github since we are side-tracking from the topic of the current thread. If you start another issue, please mention the version of BeamDyn (it seems you are using an older version of BeamDyn) and don't hesitate to send the full inputs files.
By the way, I have a new problem that is in the output file(.sum) of stand-alone BeamDyn where there is no displacement for the beam!
In Driver input file; I added concentrated moment at the tip along Y direction
In primary input file; I have one member with 14 kp_total and 5 order_elem
In Blade input file; I have 14 stations.
I run it with no problem but the main problem is in the output file and I'm wondering why in the section of initial displacement, initial rotation and initial velocity the values are 0.0!
This summary information was generated by BeamDyn (v1.01.04, 26-Jul-2016) on 17-Jun-2019 at 10:10:14.
Blade mass (kg) 3354.157
Blade length (m) 12.200
Blade center of mass:
3.65681E+00 0.00000E+00 0.00000E+00
Global position vector:
1.00000E+00 0.00000E+00 0.00000E+00
Global rotation tensor:
1.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.00000E+00
Gravity vector (m/s^2):
0.00000E+00 0.00000E+00 0.00000E+00
Analysis type: STATIC
Numerical damping parameter: 0.00000E+00
Time increment: 2.00000E-03
Maximum number of iterations in Newton-Ralphson solution: 10
Convergence parameter: 1.00000E-05
Factorization frequency in Newton-Ralphson solution: 5
Quadrature method: Trapezoidal quadrature
FE mesh refinement factor: 1
Number of elements: 1
Number of nodes: 6
Initial position vectors
Element number: 1
Node Global node
Could you attach your primary input file? It looks like your keypoints are defined with the the primary beam axis in the x-direction, but BeamDyn is expecting the the primary beam axis is in the z-direction along kp_zr. This is the IEC convention.
I noticed you are using a very old version of BeamDyn (v1.01.04, 26-Jul-2016). In the last 3 years BeamDyn has gone through a very extensive rewrite . I suggest you start with the latest version as we no longer support the older version.
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read t_initial.
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read InitInputData%gravity(1).
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
The input file on readthedocs.io is only for versions of BeamDyn in the last two releases of OpenFAST (https://github.com/OpenFAST/openfast/releases). We do not support or recommend any version of BeamDyn prior to the December 2018 release.
You will need to pull the latest version of OpenFAST and recompile before you use the new input files. I suggest you pull from the latest dev branch.
From: PouriaAmouzadrad <notifications@github.com>
Reply-To: OpenFAST/openfast <reply@reply.github.com>
Date: Tuesday, June 18, 2019 at 8:39 AM
To: OpenFAST/openfast <openfast@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [OpenFAST/openfast] Static input file format inhibits flexibility (#140)
Dear @andrew-platt<https://github.com/andrew-platt> ,
Yes you are right actually v1.00.02, 5-Apr-2016.
I have already changed the Input files considering the ones on this site: https://openfast.readthedocs.io/en/master/source/user/beamdyn/appendix.html#bd-input-files
But it is still running with the old version containing some errors:
Running BeamDyn Driver (v1.00.02, 5-Apr-2016)
linked with NWTC Subroutine Library (v2.09.00, 23-Jul-2016)
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read t_initial.
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read InitInputData%gravity(1).
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7faeceb9cd4a
#1<#1> 0x7faeceb9bf7d
#2<#2> 0x7faece0bb05f
#3<#3> 0x560ee9b04b4e
#4<#4> 0x560ee9a369a0
#5<#5> 0x560ee99e6a64
#6<#6> 0x560ee9a75f22
#7<#7> 0x560ee9a6ebed
#8<#8> 0x560ee9a7058b
#9<#9> 0x560ee9a76146
#10<#10> 0x7faece0a82e0
#11<#11> 0x560ee99b2f69
#12<#12> 0xffffffffffffffff
Erreur de segmentation
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#140?email_source=notifications&email_token=AAPSHBAN2GAWOQV6LWESKVTP3DXRVA5CNFSM4FFIVRP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX63F5I#issuecomment-503165685>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAPSHBEJ5EFW3ZIZYBIV7VLP3DXRVANCNFSM4FFIVRPQ>.
Activity
gantech commentedon Jun 15, 2018
Great. I totally support this idea.
jjonkman commentedon Jun 16, 2018
While I am generally supportive of the proposal, we chose against it in the past due the large amount of work involved. Not only does the input-file processing within OpenFAST have to change, but all of the scripts that run batch simulations of OpenFAST must change. Of course, such an endeavor does not have to done at one time, but can be tacked on a module-by-module basis.
Pouria-AZD commentedon May 21, 2019
Dear all,
Currently, I am struggling with stand-alone BeamDyn input files( Dvr_5MW_static.inp, Static_BeamDyn_input_5MW.inp, 5MW_Blade_IEC.inp). I wonder if you could help me to change the length of the blade in the input file and also I wanted to know the difference between nodes and number of key points on member(kp_total). because for instance I want to consider 6 nodes on the member and then applying load on each node.
Regards,
Pouria
JelmerPolman commentedon May 22, 2019
Dear Pouria,
I suggest you read the following threads that explains the differences between keypoints, FE nodes and quadrature points used in BeamDyn:
https://wind.nrel.gov/forum/wind/viewtopic.php?f=4&t=1525
https://wind.nrel.gov/forum/wind/viewtopic.php?f=4&t=2046&p=11114
Best Regards,
Jelmer Polman
Pouria-AZD commentedon May 23, 2019
Dear Jelmer,
Thank you for you response. the links that you sent were useful. now I am just wondering how is it possible to change some parameters such as length in addition to the stand-alone BeamDyn input files.
Kind regards,
Pouria
JelmerPolman commentedon May 23, 2019
Dear Pouria,
the driver input file for the stand-alone version only contains the parameters on how you want to load the blade and how the blade is oriented.
The BeamDyn Primary input file contains the parameters for the SFEM-solver and the reference axis of the blade. The blade length is defined by the length of the reference axis, set by the key points. The Blade input file contains the cross-sectional structural and mass properties of the blade.
https://openfast.readthedocs.io/en/latest/
Best regards,
Jelmer Polman
Pouria-AZD commentedon May 23, 2019
Dear Jelmer,
Thank you for your time and consideration. actually I'm new to it and thank you in advance for your understanding.
I set 7 for both kp-total and station total but I faced with this error;
" BD_Init:BD_ValidateInputData:The last station_eta must be equal to 1.0 (tip)
BeamDyn Driver encountered simulation error level: FATAL ERROR "
Actually, I don't understand this error.
Kind Regards,
Pouria Amouzadrad
jjonkman commentedon May 23, 2019
Dear Pouria,
The keypoints determine the (possiblu curved) reference axis of the blade. This blade cross-sectional properties are defined at stations along this reference axis. The distance along the reference axis from the root of the blade to each station is normalized between 0 and 1 (station_eta) in the BeamDyn blade input file.
The inputs to BeamDyn are documented in greater detail in the online BeamDyn User Guide and Theory Manual: https://openfast.readthedocs.io/en/master/source/user/beamdyn/index.html.
Best regards,
Pouria-AZD commentedon May 24, 2019
Dear Jason,
Thank you for your good explanation.
The last station_eta is equal to 1 in the BeamDyn blade input file but why should I have this type of error that says "The last station_eta must be equal to 1.0(tip)" !
Or maybe something else should be changed in order to to solve this error which I don't know about that.
Kind Regards,
Pouria Amouzadrad
jjonkman commentedon May 27, 2019
Dear @Pouria-AZD,
I think we'd need to see your input files to help debug the problem. It is difficult to guess what the problem might be. Please attach your files.
Best regards,
Pouria-AZD commentedon May 28, 2019
Dear @jjonkman,
Here are the Input files.
pamouzadra2018.zip
Kind regards,
Pouria Amouzadrad
ebranlard commentedon May 28, 2019
Hi Pouria, I could only see screenshots in the zip file, could you send the input file as a text file as well? Maybe the number of stations does not match. As a quick check you could try using only
station_total=2and then defining onlyeta=0andeta=1in the file.Pouria-AZD commentedon May 28, 2019
Hi @ebranlard ,
with station_total=2 by defining only eta=0 and eta=1 in the input file this error occurred " Load may be too large, BeamDyn will attempt to solve with additional steps. Maximum number of load steps reached. "
---------------------- BLADE PARAMETERS --------------------------------------
2 station_total - Number of blade input stations (-)
1 damp_type - Damping type (switch): 0: no damping; 1: viscous damping
---------------------- DAMPING COEFFICIENT------------------------------------
mu1 mu2 mu3 mu4 mu5 mu6
(s) (s) (s) (s) (s) (s)
1.0E-03 1.0E-03 1.0E-03 1.0E-03 1.0E-03 1.0E-03
---------------------- DISTRIBUTED PROPERTIES---------------------------------
0.000000
9.729480E+08 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 9.729480E+08 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 9.729480E+09 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 1.811360E+10 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 1.811000E+10 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 5.564400E+09
6.789350E+02 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 -1.154189E-01
0.000000E+00 6.789350E+02 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 6.789350E+02 1.154189E-01 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 1.154189E-01 9.730400E+02 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 9.728600E+02 0.000000E+00
-1.154189E-01 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 1.945900E+03
1.000000
3.530000E+05 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 3.530000E+05 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 3.530000E+06 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 5.010000E+06 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 1.700000E+05 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 1.900000E+05
1.031900E+01 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 -5.346274E-01
0.000000E+00 1.031900E+01 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 1.031900E+01 5.346274E-01 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 5.346274E-01 6.800000E-01 0.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 2.000000E-02 0.000000E+00
-5.346274E-01 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 7.000000E-01
jjonkman commentedon May 28, 2019
Dear @Pouria-AZD,
I agree with @ebranlard that your original model likely has more than 14 stations where the distributed mass and stiffness data are defined even though your input file had station_total = 14 (but it is difficult to confirm without the text-based input).
When switching to station_total = 2, the trapezoidal quadrature you are using (quadrature = 2) is very coarse, causing the new issue you are seeing. When using station_total = 2 with quadrature = 2, you should set refine to a sufficiently large value to sufficiently resolve the blade (e.g., refine = 20).
Best regards,
ebranlard commentedon May 28, 2019
Hi Pouria,
As mentioned by Jason, I'd recommend checking the syntax of your previous input file that had 14 stations.
If you experience further problems, feel free to post another issue on github since we are side-tracking from the topic of the current thread. If you start another issue, please mention the version of BeamDyn (it seems you are using an older version of BeamDyn) and don't hesitate to send the full inputs files.
Pouria-AZD commentedon Jun 17, 2019
Dear all,
Thanks for your helpful answers.
By the way, I have a new problem that is in the output file(.sum) of stand-alone BeamDyn where there is no displacement for the beam!
I run it with no problem but the main problem is in the output file and I'm wondering why in the section of initial displacement, initial rotation and initial velocity the values are 0.0!
This summary information was generated by BeamDyn (v1.01.04, 26-Jul-2016) on 17-Jun-2019 at 10:10:14.
Blade mass (kg) 3354.157
Blade length (m) 12.200
Blade center of mass:
3.65681E+00 0.00000E+00 0.00000E+00
Global position vector:
1.00000E+00 0.00000E+00 0.00000E+00
Global rotation tensor:
1.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.00000E+00
Gravity vector (m/s^2):
0.00000E+00 0.00000E+00 0.00000E+00
Analysis type: STATIC
Numerical damping parameter: 0.00000E+00
Time increment: 2.00000E-03
Maximum number of iterations in Newton-Ralphson solution: 10
Convergence parameter: 1.00000E-05
Factorization frequency in Newton-Ralphson solution: 5
Quadrature method: Trapezoidal quadrature
FE mesh refinement factor: 1
Number of elements: 1
Number of nodes: 6
Initial position vectors
Element number: 1
Node Global node
Initial rotation vectors
Element number: 1
Node Global node
Quadrature point position vectors
1 0.00000E+00 0.00000E+00 0.00000E+00
2 1.99875E-01 0.00000E+00 0.00000E+00
3 1.19986E+00 0.00000E+00 0.00000E+00
4 2.19985E+00 0.00000E+00 0.00000E+00
5 3.19984E+00 0.00000E+00 0.00000E+00
6 4.19984E+00 0.00000E+00 0.00000E+00
7 5.19982E+00 0.00000E+00 0.00000E+00
8 6.19982E+00 0.00000E+00 0.00000E+00
9 7.19980E+00 0.00000E+00 0.00000E+00
10 8.20102E+00 0.00000E+00 0.00000E+00
11 9.19979E+00 0.00000E+00 0.00000E+00
12 1.01998E+01 0.00000E+00 0.00000E+00
13 1.11998E+01 0.00000E+00 0.00000E+00
14 1.21998E+01 0.00000E+00 0.00000E+00
Sectional stiffness and mass matrices at quadrature points
Quadrature point number: 1
9.72948E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 9.72948E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 9.72948E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 5.56440E+09 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.81136E+10 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.81100E+10
Quadrature point number: 2
1.00672E+10 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.00672E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.00672E+09 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 4.99398E+09 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.94978E+10 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.74559E+10
Quadrature point number: 3
4.49395E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 4.49395E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 4.49395E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 1.57036E+09 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 8.06316E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.52836E+09
Quadrature point number: 4
4.08597E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 4.08597E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 4.08597E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 5.47490E+08 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 7.08170E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.38652E+09
Quadrature point number: 5
2.88262E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 2.88262E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 2.88262E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 2.91940E+08 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 4.80802E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.27199E+09
Quadrature point number: 6
2.35748E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 2.35748E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 2.35748E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 2.28820E+08 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 4.24407E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.82825E+09
Quadrature point number: 7
1.43240E+09 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.43240E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.43240E+08 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 1.19980E+08 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.13907E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 8.75800E+08
Quadrature point number: 8
7.60820E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 7.60820E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 7.60820E+07 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 4.59200E+07 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.82873E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.14540E+08
Quadrature point number: 9
5.31150E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 5.31150E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 5.31150E+07 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 2.09000E+07 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.18368E+09 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.26010E+08
Quadrature point number: 10
3.75750E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 3.75750E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 3.75750E+07 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 1.62800E+07 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 7.97810E+08 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 9.08800E+07
Quadrature point number: 11
1.81520E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.81520E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.81520E+07 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 7.08000E+06 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.95120E+08 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.93600E+07
Quadrature point number: 12
1.09230E+08 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 1.09230E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 1.09230E+07 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 5.75000E+06 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.04730E+08 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.04100E+07
Quadrature point number: 13
2.99200E+07 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 2.99200E+06 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 2.99200E+06 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 2.17000E+06 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 8.50700E+07 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 7.55000E+06
Quadrature point number: 14
3.53000E+06 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 3.53000E+05 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 3.53000E+05 0.00000E+00 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 1.90000E+05 0.00000E+00 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.01000E+06 0.00000E+00
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.70000E+05
Initial displacement
1 0.00000E+00 0.00000E+00 0.00000E+00
2 0.00000E+00 0.00000E+00 0.00000E+00
3 0.00000E+00 0.00000E+00 0.00000E+00
4 0.00000E+00 0.00000E+00 0.00000E+00
5 0.00000E+00 0.00000E+00 0.00000E+00
6 0.00000E+00 0.00000E+00 0.00000E+00
Initial rotation
1 0.00000E+00 0.00000E+00 0.00000E+00
2 0.00000E+00 0.00000E+00 0.00000E+00
3 0.00000E+00 0.00000E+00 0.00000E+00
4 0.00000E+00 0.00000E+00 0.00000E+00
5 0.00000E+00 0.00000E+00 0.00000E+00
6 0.00000E+00 0.00000E+00 0.00000E+00
Initial velocity
1 0.00000E+00 0.00000E+00 0.00000E+00
2 0.00000E+00 0.00000E+00 0.00000E+00
3 0.00000E+00 0.00000E+00 0.00000E+00
4 0.00000E+00 0.00000E+00 0.00000E+00
5 0.00000E+00 0.00000E+00 0.00000E+00
6 0.00000E+00 0.00000E+00 0.00000E+00
Initial angular velocity
1 0.00000E+00 0.00000E+00 0.00000E+00
2 0.00000E+00 0.00000E+00 0.00000E+00
3 0.00000E+00 0.00000E+00 0.00000E+00
4 0.00000E+00 0.00000E+00 0.00000E+00
5 0.00000E+00 0.00000E+00 0.00000E+00
6 0.00000E+00 0.00000E+00 0.00000E+00
andrew-platt commentedon Jun 17, 2019
Could you attach your primary input file? It looks like your keypoints are defined with the the primary beam axis in the x-direction, but BeamDyn is expecting the the primary beam axis is in the z-direction along
kp_zr. This is the IEC convention.Pouria-AZD commentedon Jun 18, 2019
Dear @andrew-platt ,
Data are defined along kp_zr , I don't know where the problem is.
False Echo - Echo input data to ".ech" (flag)
1 analysis_type - 1: Static analysis; 2: Dynamic analysis (switch)
0.0 rhoinf - Numerical Damping Parameter for Generalized-alpha integrator
2 quadrature - 1: Gauss; 2: Trapezoidal (switch)
DEFAULT refine - Refinement factor for quadrature 2 (-). DEFAULT = 1
DEFAULT n_fact - Factorization frequency (-). DEFAULT = 5
DEFAULT DTBeam - Time step size (s).
DEFAULT NRMax - Max number of iterations in Newton-Ralphson algorithm (-). DEFAULT = 10
DEFAULT stop_tol - Tolerance for stopping criterion (-)
---------------------- GEOMETRY PARAMETER --------------------------------------
1 member_total - Total number of members (-)
14 kp_total - Total number of key points (-)
1 14 - Member number; Number of key points in this member
kp_xr kp_yr kp_zr initial_twist
(m) (m) (m) (deg)
0.0000000E+00 0.0000000E+00 0.0000000E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 1.9987500E-01 1.3308000E+01
0.0000000E+00 0.0000000E+00 1.1998650E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 2.1998550E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 3.1998450E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 4.1998350E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 5.1998250E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 6.1998150E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 7.1998050E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 8.2010250E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 9.1997850E+00 1.3308000E+01
0.0000000E+00 0.0000000E+00 1.0199775E+01 1.3308000E+01
0.0000000E+00 0.0000000E+00 1.1199765E+01 1.3181000E+01
0.0000000E+00 0.0000000E+00 1.2199755E+01 1.2848000E+01
andrew-platt commentedon Jun 18, 2019
I noticed you are using a very old version of BeamDyn (v1.01.04, 26-Jul-2016). In the last 3 years BeamDyn has gone through a very extensive rewrite . I suggest you start with the latest version as we no longer support the older version.
Pouria-AZD commentedon Jun 18, 2019
Dear @andrew-platt ,
Yes you are right actually v1.00.02, 5-Apr-2016.
I have already changed the Input files considering the ones on this site: https://openfast.readthedocs.io/en/master/source/user/beamdyn/appendix.html#bd-input-files
But it is still running with the old version containing some errors:
Running BeamDyn Driver (v1.00.02, 5-Apr-2016)
linked with NWTC Subroutine Library (v2.09.00, 23-Jul-2016)
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read t_initial.
BD_ReadDvrFile:Invalid numerical input for file "Dvr_5MW_Static.inp" occurred while trying to
read InitInputData%gravity(1).
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7faeceb9cd4a
#1 0x7faeceb9bf7d
#2 0x7faece0bb05f
#3 0x560ee9b04b4e
#4 0x560ee9a369a0
#5 0x560ee99e6a64
#6 0x560ee9a75f22
#7 0x560ee9a6ebed
#8 0x560ee9a7058b
#9 0x560ee9a76146
#10 0x7faece0a82e0
#11 0x560ee99b2f69
#12 0xffffffffffffffff
Erreur de segmentation
andrew-platt commentedon Jun 18, 2019
The input file on
readthedocs.iois only for versions of BeamDyn in the last two releases of OpenFAST (https://github.com/OpenFAST/openfast/releases). We do not support or recommend any version of BeamDyn prior to the December 2018 release.michaelasprague commentedon Jun 18, 2019