Open Tommi1198 opened 2 years ago
Dear @Tommi1198,
Have you generated your turbulent wind data file using TurbSim following the modeling guidance documentation: https://openfast.readthedocs.io/en/main/source/user/fast.farm/ModelGuidance.html#inflow-wind-generation? Is the turbulent wind data periodic as recommended? I would not expect that you'd receive an error regarding
FF wind array was exhausted
if the wind data is periodic.
Best regards,
Dear @jjonkman , this is my input file for the wind:
Dear @Tommi1198,
I don't see any issue with this InflowWind input file. The issue is likely with the TurbSim wind data file you are using, _90m_12mpstwr.bts.
How did you generate this file from TurbSim and is it periodic, i.e., is TurbSim input UsableTime
set to "ALL"?
Best regards,
Dear @jjonkman, I took this file from the library in GitHub; in addition, I donìt know how to open this file so that I can check if TurbSim input UsableTime set to "ALL". What can I do? Thank you
Dear @Tommi1198,
Presumably you obtained the file _90m_12mpstwr.bts from here: https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_Baseline/Wind; is that correct? The TurbSim input file used to generate this wind data file is available in the same directory, _90m_12mpstwr.inp. In this file, UsableTime
is set to 60 s, not "ALL". And there are other input parameters in this TurbSim input file that also do not follow the modeling guidance for TurbSim specified in the FAST.Farm documentation.
The TurbSim input file, _90m_08mps.inp, found in the following example more closely follows the modeling guidance for TurbSim specified in the FAST.Farm documentation: https://github.com/OpenFAST/r-test/tree/main/glue-codes/fast-farm/TSinflow. I would start with this example.
Best regards,
Dear @jjonkman, I changed the wind file using _90m_08mps.bts as bts file for TurbSim, but another error came out:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4980, 4980, 345) in wind-file coordinates]: FF wind array boundaries violated: Grid too small in Y direction. Y=4980; Y boundaries = [-500, 500]
Aborting FAST.Farm.
How can I change the Y boundaries?
This is my input file for the wind:
@Tommi1198
Your turbine is too far out of the bounds of the wind field. About 5 km away from the center based on [position=(4980, 4980, 345)
. Is that the correct position for the turbine?
Dear @andrew-platt, my turbine is in this position:
WT_X WT_Y WT_Z
(m) (m) (m)
100.0 180.0 0.0
This is a bit puzzling. What is asking for wind 5 km away at position=(4980, 4980, 345)
?
I don't really know...
Dear @Tommi1198,
My guess is your low- or high-resolution domains defined in your FAST.Farm input file have points that are outside the domain of your TurbSim wind data file.
Best regards,
Dear @jjonkman, how can I see if I have some points outside the TurbSim domain? Because I tried to extend the resolution of the turbine but nothing changed
Dear @Tommi1198,
You specify the X-Y-Z extent of the low- and high-resolution domains used by FAST.Farm in the FAST.Farm input file. And you specify the Y-Z extent of the TurbSim domain(s) used by the InflowWind module of FAST.Farm in the TurbSim input file (due to its periodicity, the X-extent of the TurbSim domain is infinite when UsableTime = "ALL"). The low- and high-resolution domains of FAST.Farm must lie within the TurbSim domain (and preferably align with the TurbSim domain to avoid extra interpolation) as discussed in the Modeling Guidance section of the online FAST.Farm documentation: https://openfast.readthedocs.io/en/main/source/user/fast.farm/ModelGuidance.html.
Best regards,
Dear @jjonkman, I have no idea how to open the .bts file to change the domain of the TurbSim input file...I tried to open it with a program found on the internet, but it didn't work
Dear @Tommi1198,
You shouldn't edit the binary wind data file manually. The TurbSim domain (and other wind conditions) is specified in the TurbSim input file. The TurbSim output file can then be generated by rerunning TurbSim.
Best regards,
Dear @jjonkman, the following error continued to show:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4975, 9950, 340) in wind-file coordinates]: FF wind array boundaries violated: Grid too small in Y direction. Y=9950; Y boundaries = [-500, 500]
Aborting FAST.Farm.
So, I enlarged the grid in Y direction and the following error came out:
forrtl: severe (157): Program Exception - access violationiod of 200 seconds). Image PC Routine Line Source FAST.Farm_x64.exe 00007FF7A16BBF97 Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A16B9F2B Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A169E7ED Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A0A2C0C5 Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A070C725 Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A08E3521 Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A08CCEAE Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A07013EE Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A2F23B62 Unknown Unknown Unknown FAST.Farm_x64.exe 00007FF7A341F934 Unknown Unknown Unknown KERNEL32.DLL 00007FF9D2E754E0 Unknown Unknown Unknown ntdll.dll 00007FF9D3A6485B Unknown Unknown Unknown
What can I do? Thanks a lot!
Dear @Tommi1198,
Can you clarify what you mean when you say that you "enlarged the grid in Y direction"?
Best regards,
Dear @jjonkman, I mean that, when I had the first error, I read on the guide that the problem was regarding the low-resolution domain, so I enlarged it; then, the second error described above came out
Dear @Tommi1198,
Can you share your FAST.Farm input file, InflowWind input file, and TurbSim input file?
Best regards,
Input file.zip Dear @jjonkman, here what you asked for, thanks a lot!
Dear @Tommi1198,
I'm still not sure what is resulting in the access violation error, but perhaps that is the same issue discussed previously: https://github.com/OpenFAST/openfast/issues/1044?
Regardless, I still see that you are not setting up your FAST.Farm discretizations correctly. Just a few comments:
dY_Low
spacing is large.dr
spacing of the wake planes (radial finite-difference grid) is way to large.Can you explain why you are setting up your model this way?
By now, you've asked a series of FAST.Farm questions, but you have not followed our recommendations, i.e., to set up your model following the documented modeling guidance and provided Python scripts. I'm not sure how to help if you don't follow our recommendations.
Best regards,
@jjonkman @Tommi1198 @andrew-platt @sayerhs @itd
respected sir,sir i am a student and doing my academic project on OWT but i can't understand,how to use this software, how to download it ? is matlab necessary to run this software? i seek your atteention for help. as a new member ,kindly help me so that i can contribute in this in future.
@jyotrimaya1993,
I recommend starting with the documentation here: https://openfast.readthedocs.io/en/main/index.html
@jyotrimaya1993,
I recommend starting with the documentation here: https://openfast.readthedocs.io/en/main/index.html
sir, this installation process is old,and after following also i am unable to install the software
Dear @jyotrimaya1993,
What is your operating system, which approach from the documentation are you trying to use to install OpenFAST, and which step in the process is not working for you?
Best regards,
sir, windows os in step 1 -i download visual studio community 2019 step 2 -i download fortran compiler with math library step 3- i download the zip file from openFAST git hub step 4 -i download all the assets except that 2 last source code zip file step 5-unzip all the downloaded file step 6-while running in powershell through the .exe code following that fst file... it is not running.... it only show that path only
Dear @jyotrimaya1993,
In Windows, the precompiled binary executables have been provided. So, unless you intend to modify the source code, requiring a recompile, you can likely skip steps 1-3.
To run the precompiled OpenFAST executable from a Windows command prompt, see, e.g., https://github.com/OpenFAST/openfast/issues/463.
Best regards,
this thingh i got error
OpenFAST
Copyright (C) 2022 National Renewable Energy Laboratory Copyright (C) 2022 Envision Energy USA LTD
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY. See the "LICENSE" file distributed with this software for details.
OpenFAST-v3.1.0 Compile Info:
OpenFAST input file heading: FAST Certification Test #22: NREL 5.0 MW Baseline Wind Turbine with ITI Barge Configuration, for use in offshore analysis
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running AeroDyn14. WARNING: AeroDyn 14 is deprecated and will be removed in a future release. Running InflowWind.
Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on 07-Jan-2014 at 12:50:45.
Processed 1442 time steps of 20-Hz full-field data (72.05 seconds). Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name ".../5MW_Baseline/HydroData/Barge". Computing radiation impulse response functions and wave diffraction forces.
Using SS_Radiation Module, with 30 of 30 radiation states
MAP++ environment properties (set externally)... Gravity constant [m/s^2] : 9.81 Sea density [kg/m^3] : 1025.00 Water depth [m] : 150.00 Vessel reference position [m] : 0.00 , 0.00 , 0.00
Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
FAST_InitializeAll:SrvD_Init:BladedInterface_Init:The dynamic library .../5MW_Baseline/ServoData/DISCON_ITIBarge.dll could not be loaded. Check that the file exists in the specified location and that it is compiled for 64-bit applications.
OpenFAST encountered an error during module initialization. Simulation error level: FATAL ERROR
Aborting OpenFAST.
Dear @jyotrimaya1993,
See a similar question asked and answered here: https://github.com/OpenFAST/openfast/discussions/1114.
Best regards
@rafmudaf kindly guide me to solve my issue(Aerodyn is an issue or it will under development)
OpenFAST-v3.1.0 Compile Info:
OpenFAST input file heading: FAST Certification Test #22: NREL 5.0 MW Baseline Wind Turbine with ITI Barge Configuration, for use in offshore analysis
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running AeroDyn14. WARNING: AeroDyn 14 is deprecated and will be removed in a future release. Running InflowWind.
Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on 07-Jan-2014 at 12:50:45.
Processed 1442 time steps of 20-Hz full-field data (72.05 seconds). Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name ".../5MW_Baseline/HydroData/Barge". Computing radiation impulse response functions and wave diffraction forces.
Using SS_Radiation Module, with 30 of 30 radiation states
MAP++ environment properties (set externally)... Gravity constant [m/s^2] : 9.81 Sea density [kg/m^3] : 1025.00 Water depth [m] : 150.00 Vessel reference position [m] : 0.00 , 0.00 , 0.00
Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). Using legacy Bladed DLL interface.
Total Real Time: 8.498 seconds Total CPU Time: 8.4219 seconds Simulation CPU Time: 7.8438 seconds Simulated Time: 60 seconds Time Ratio (Sim/CPU): 7.6494
OpenFAST terminated normally.
PS C:\openfast\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\glue-codes\openfast\5MW_ITIBarge_DLL_WTurb_WavesIrr>
Dear @jyotrimaya1993,
You received the message "OpenFAST terminated normally". So, there is no issue to be solved.
The warning about the deprecation of AeroDyn v14 is suggesting that you consider upgrading from AeroDyn v14 (CompAero
= 1) to AeroDyn v15 (CompAero
= 2) because we intend to eliminate AeroDyn v14 from OpenFAST in a future release (expected to happen soon). I'm not sure if you've modified the r-test input files in any way, but when we deprecate AeroDyn v14, we will upgrade all of the r-test cases that use AeroDyn v14 to use AeroDyn v15.
Best regards,
@jjonkman thank you sir,for your co-operation ,being new to this ,somehow i feel difficulty in installing ,but due to your help ,successfully i installed it ,Hopefully in near future you may help me in same manner
@jjonkman i am not getting the vtk files folder in my reg glue code. and this type of error is coming..
OpenFAST-v3.1.0 Compile Info:
OpenFAST input file heading: FAST Certification Test #25: NREL 5.0 MW Baseline Wind Turbine with OC4-DeepCwind semi configuration, for use in offshore analysis
FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:1/VTK_fps is not an integer multiple of DT. FAST will output VTK information at 16 fps, the closest rate possible. FAST_Init:ValidateInputData:Tmax is less than the last linearization time. Linearization analysis will not be performed after TMax. ValidateInputData:Linearization is not implemented for the OpenFOAM coupling. ValidateInputData:Linearization is not implemented for the FEAMooring or MoorDyn mooring modules. ValidateInputData:DT_out must be an integer multiple of DT.
OpenFAST encountered an error during module initialization. Simulation error level: FATAL ERROR
Aborting OpenFAST.
PS C:\openfast\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\glue-codes\openfast\5MW_OC4Semi_Linear>
Dear @jyotrimaya1993,
It appears that your OpenFAST model has several errors that that need to be resolved before you can run the simulation. These are the errors reported that are preventing the simulation from running:
ValidateInputData:Linearization is not implemented for the OpenFOAM coupling.
<-- To solve this error, either disable linearization (Linearize
= False) or use InflowWind instead of OpenFOAM (CompInflow
= 1).
ValidateInputData:Linearization is not implemented for the FEAMooring or MoorDyn mooring modules.
<-- To solve this error, either disable linearization (Linearize
= False) or use MAP++ instead of FEAMooring or MoorDyn (CompMooring
= 1).
ValidateInputData:DT_out must be an integer multiple of DT.
<-- To solve this error, set DT_Out
to be an integer multiple of DT
.
Best regards,
Dear @jjonkman ,
I am facing a similar problem while running the FAST.Farm_x64_OMP.exe. I got the following info and the software just stop running, could you please specify how shall I solve this?
....... Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). Using legacy Bladed DLL interface.
FAST_InitializeAll:FAST_Init:FAST_ReadPrimaryFile:1/VTK_fps is not an integer multiple of DT. FAST will output VTK information at 14.545 fps, the closest rate possible.
It didn't show 'aborting ...' but it seemed just stop running and no outb file was generated.
Thank you in advance.
Yours sincerely, Yuan
Dear @yuangao0916,
The warning about VTK_fps is just a warning, it will not cause the simulation to abort.
Can you share the full output from the Windows command prompt when you attempt to run FAST.Farm?
Best regards,
@jjonkman why it is showing "Nodal outputs section of ElastoDyn input file not found or improperly formatted."(below result)
OpenFAST
Copyright (C) 2022 National Renewable Energy Laboratory Copyright (C) 2022 Envision Energy USA LTD
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY. See the "LICENSE" file distributed with this software for details.
OpenFAST-v3.1.0 Compile Info:
OpenFAST input file heading: FAST Certification Test #22: NREL 5.0 MW Baseline Wind Turbine with ITI Barge Configuration, for use in offshore analysis
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running InflowWind.
Reading a 31x31 grid (145 m wide, 17.5 m to 162.5 m above ground) with a characteristic wind speed of 12 m/s. This full-field file was generated by TurbSim (v1.06.00, 21-Sep-2012) on 07-Jan-2014 at 12:50:45.
Processed 1442 time steps of 20-Hz full-field data (72.05 seconds). Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name ".../5MW_Baseline/HydroData/Barge". Computing radiation impulse response functions and wave diffraction forces.
Using SS_Radiation Module, with 30 of 30 radiation states
MAP++ environment properties (set externally)... Gravity constant [m/s^2] : 9.81 Sea density [kg/m^3] : 1025.00 Water depth [m] : 200.00 Vessel reference position [m] : 0.00 , 0.00 , 0.00
FAST_InitializeAll:SetVTKParameters:Cannot do surface visualization without using AeroDyn.
OpenFAST encountered an error during module initialization. Simulation error level: FATAL ERROR
Aborting OpenFAST.
PS C:\jb\r-test-061441958a2eef7f494d69ee097f8ec050d5a129\glue-codes\openfast\5MW_ITIBarge_DLL_WTurb_WavesIrr>
Dear @jyotrimaya1993,
The "nodal outputs" warnings are just warnings and will not effect the simulation results; you can ignore the warnings. A similar question was asked and answered before--see #573.
OpenFAST is aborting because surface visualization is only possible when AeroDyn v15 is enabled (CompAero
= 2). The ITI Barge r-test you are using makes use of AeroDyn v14 (CompAero
= 1). Either switch from AeroDyn v14 to AeroDyn v15 or disable surface visualization by not setting VTK_type
= 1.
Best regards,
Dear @jjonkman,
Sorry for the late reply, the following is the full outputs. I am confused as it does not say '...aborting' (although it did abort) and it just stops.
FAST.Farm-v3.1.0 Compile Info:
Time: 11:13:50-0700
Heading of the FAST.Farm input file: Sample FAST.Farm input file Running AWAE. Running InflowWind. Running WakeDynamics. Running FASTWrapper. Running OpenFAST. OpenFAST input file heading: FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore)
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running AeroDyn. AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. Skipping nodal outputs. Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 3) Running InflowWind. Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name "C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating../5MW_Baseline/HydroData/m arin_semi". Computing radiation impulse response functions and wave diffraction forces. Calculating second order difference-frequency force using the full quadratic transfer function. Calculating second order sum-frequency force using the full quadratic transfer function. Running MoorDyn. MD_Init: Opening MoorDyn input file: C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating\NRELOffshrBsline5MW_OC4Deep CwindSemi_MoorDyn.dat Creating mooring system. 3 fairleads, 3 anchors, 0 connects. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Finalizing ICs using dynamic relaxation. t=88 FairTen 1: 2.70557E+05, 2.70000E+05, 2.69018E+05 Fairlead tensions converged to 1% after 88 seconds. Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). Using legacy Bladed DLL interface. Running OpenFAST. OpenFAST input file heading: FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore)
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running AeroDyn. AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. Skipping nodal outputs. Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 3) Running InflowWind. Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name "C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating../5MW_Baseline/HydroData/m arin_semi". Computing radiation impulse response functions and wave diffraction forces. Calculating second order difference-frequency force using the full quadratic transfer function. Calculating second order sum-frequency force using the full quadratic transfer function. Running MoorDyn. MD_Init: Opening MoorDyn input file: C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating\NRELOffshrBsline5MW_OC4Deep CwindSemi_MoorDyn.dat Creating mooring system. 3 fairleads, 3 anchors, 0 connects. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Finalizing ICs using dynamic relaxation. t=88 FairTen 1: 2.70557E+05, 2.70000E+05, 2.69018E+05 Fairlead tensions converged to 1% after 88 seconds. Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). Using legacy Bladed DLL interface. Running OpenFAST. OpenFAST input file heading: FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore)
Running ElastoDyn. Nodal outputs section of ElastoDyn input file not found or improperly formatted. Running AeroDyn. AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. Skipping nodal outputs. Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 1) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 2) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 1, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 2, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 3, blade 3) Warning: Turning off Unsteady Aerodynamics because UA parameters are not included in airfoil (airfoil has likely has constant polars). (node 4, blade 3) Running InflowWind. Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name "C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating../5MW_Baseline/HydroData/m arin_semi". Computing radiation impulse response functions and wave diffraction forces. Calculating second order difference-frequency force using the full quadratic transfer function. Calculating second order sum-frequency force using the full quadratic transfer function. Running MoorDyn. MD_Init: Opening MoorDyn input file: C:\Users\Gary\Desktop\test3_modified\FastFarm\TestTemplates\Floating\NRELOffshrBsline5MW_OC4Deep CwindSemi_MoorDyn.dat Creating mooring system. 3 fairleads, 3 anchors, 0 connects. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Catenary solver failed for one or more lines. Using linear node spacing. Finalizing ICs using dynamic relaxation. t=88 FairTen 1: 2.70557E+05, 2.70000E+05, 2.69018E+05 Fairlead tensions converged to 1% after 88 seconds. Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). Using legacy Bladed DLL interface. C:\Users\Gary\Desktop\test3_modified\FastFarm\newbin2>
Dear @yuangao0916,
I'm not sure what would cause FAST.Farm to abort without an error. Can you share your full set of input files so that I can see if I can reproduce the error?
Best regards,
Dear @jjonkman,
I am quite confused about this because it works ok with my non-parallel version (it just run the simulation to the end), but once I change to this _OMP.exe file, it abort like this..
The following is my .fstf input file:
FAST.Farm v1.00.* INPUT FILE
Sample FAST.Farm input file
--- SIMULATION CONTROL ---
True Echo Echo input data to
@jjonkman and @yuangao0916
This may be a bug with opening files for reading and writing. When run in parrallel, I have occasionally seen issues with a unit number for file writing getting issued by GetNewUnit
, and another process getting issued the same unit number before either actually opens the file. I think this occasionally leads to strange crashes from the conflicting unit numbers. This should be caught internally and the program should gracefully end, but given the state of error handling in some of the modules (HD, AWAE for example) I shouldn't be surprised it isn't. If this is the cause, we need a long term solution for it.
Andy
Possibly related:
Dear @andrew-platt
Thanks for the information.
I think this might be the cause, but I haven't gotten it successfully run in the parallel case even once. - I used the same input files and controllers which was ok for the non-parallel cases.
For now, I will focus on the non-parallel once then.
Thank you again.
Yours sincerely, Yuan
Thanks, @andrew-platt, for the suggestion.
@yuangao0916 -- Can you confirm that you are running the precompiled Windows binary version of FAST.Farm provided by NREL (_FAST.Farm_x64OMP.exe, available from here: https://github.com/OpenFAST/openfast/releases) and that you have installed the Intel Fortran redistributable package and running from the Intel command prompt that loads the Intel libraries?
Best regards,
Dear @jjonkman ,
Yes, that is what I did.
Yours sincerely, Yuan
Hello everyone, I'm trying to run a simulation in FAST.Farm using the NREL5MW wind turbine, but the following error occured:
Farm_Initialize:InflowWind_CalcOutput:CalcOutput:IfW_FFWind_CalcOutput [position=(4980, 4980, 345) in wind-file coordinates]: Error: FF wind array was exhausted at 2 seconds (trying to access data at -406.96 seconds).
Aborting FAST.Farm.
How can I fix it? Thanks a lot!