A fatal error occurred when parsing data from “…/InflowWind.dat”
The variable “FileName_Uni” was not found on line #17.
Aborting Fast.Farm.
I am using Turbsim binary file (Windtype =3) in the InflowWind.dat file. There is the standard filename entered in the Windtype 2 row, which I didn’t mess with. Any help would be appreciated in solving this issue.
Can I also get a copy of the Fast Farm manual and a version of the code that you’ve been sending to folks on the forum (assuming its a bit different than what’s on GitHub?). Thanks.
The version of FAST.Farm on github is the newest version. It is in the process of being reviewed in preparation for being merged into the dev branch of OpenFAST soon. I’ll send you the most up-to-date FAST.Farm documentation, which is also being reviewed before publication soon.
The error you are receiving seems to point to a formatting problem in your InflowWind input file. As with any such problem, I would enable the Echo option in InflowWind to debug.
I am trying to run FAST.Farm with OpenFAST v1.0 5MW files. Earlier I was able to run it for 100s but then when I try to run for more time. I get the following error message.
This error could be caused with the old near-wake correction model of FAST.Farm when running a wind turbine in a high thrust condition (C_T > 24/25). In the most recent version of FAST.Farm available in the pull request (github.com/OpenFAST/openfast/pull/584), we’ve introduced an improved near-wake correction model that is valid for both low- and high thrust conditions. So, upgrading to the most recent version should solve the problem.
Alternatively, you could change your set up to avoid simulating under high thrust conditions. Considering that you are receiving this error 174 s into the simulation for the the 3rd turbine (T3), I would guess the error is triggered when wakes from an upstream turbine are impinging on a downstream wind turbine. Reducing the rotor speed on the 3rd turbine (resulting in a lower TSR and lower thrust) could solve the problem as well.
Thank you Dr.Jonkman for your swift response. I have downloaded the updated version and while building solution in VS I get the following mitigation report
I am using VS2015 community edition and Intel FORTRAN compiler 2017. Also I have been successful earlier with these combo to build solutions for openFAST v2.3 and v2.4. Not sure why suddenly they became incompatible.
Otherwise I was able to successfully run for a case(a little longer now 500s) in which the turbines are parked and feathered (all of the turbines were pitched 90deg and rotspeed zero) with ambient wind.
This error sounds like Fortran is not installed properly. Perhaps you upgraded or reinstalled something since you last compiled OpenFAST? Can you still compile OpenFAST?
I tried to download FAST.Farm according to the latest FARM guide file, but I did not find the corresponding file in Open-fast, i mean the file FAST-Farm.sln. Would you please share the latest or pre-release version of the FAST.Farm software package just as others requested earlier?
And i wanna know that after I compiled fast.sln through VS and IFM,has OpenFast been fully installed? Do I need to compile the same sln files of other corresponding files (submodules)?
The FAST.Farm Visual Studio solution, FAST-Farm.sln, is included in the vs-build/FAST-farm directory of the branch of OpenFAST available in the active pull request: github.com/OpenFAST/openfast/pull/584. Once you download this branch of OpenFAST, you can compile FAST.Farm with this solution file. No other compilation is necessary.
You were right earlier I wasn’t able to compile now even though I was able to do it earlier. I was using VS community edition 2015 and Intel Fortran compiler 2017 edition. I tried to uninstall and reinstall both several times but unable to compile the same files which I did before.
As the error now seems to be related to the compiler. I am trying to download another version of it but unable to locate the file.
Would you recommend a compatible version of the compiler and the link to download it from.All my search leads to Intel API toolkit link.
Hi Jason,
Thank you for your previous suggestions. I downloaded the name “openfast-947292b79b6c676949cfac1dae4038691083ec57” from the active pull request: github.com/OpenFAST/openfast/pull/584. and successfully completed the compilation.
I also met the analogous problem when running the Fast.Farm(compiled from the latest version on github), and the error is:
[code]FAST.Farm-Unversioned from 947292b79b6c676949cfac1dae4038691083ec57
Compile Info:
Compiler: Intel(R) Fortran Compiler 2021
Architecture: 64 bit
Precision: single
OpenMP: Yes, number of threads: 64/64
Date: Feb 24 2021
Time: 12:11:28
Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running InflowWind.
Farm_Initialize:Farm_ValidateInput:OutFmt produces a column width of 10 instead of 20 characters.
Farm_Initialize:AWAE_Init:InflowWind_Init:InflowWind_ParseInputFileInfo:ParseSiVarDefault:ParseChV
ar:
A fatal error occurred when parsing data from “.\InflowWind.dat”.
The variable “VFlowAng” was not found on line #7.
InflowWind_ParseInputFileInfo:ParseSiVarDefault:ParseChVar:
A fatal error occurred when parsing data from “.\InflowWind.dat”.
The variable “VFlowAng” was not found on line #7.
Aborting FAST.Farm.[/code]
it seems that error occurred when reading data from ‘’.\InflowWind.dat’’ , but i didn’t met this problem when running the Pre-release version Fast.Farm. Any help would be appreciated in solving this issue.
[size=150]I think I solved the above problem by adding “VFlowAng” to the 7th line of the input file, but the same problem as Mr. Raghu occurred when I ran it again, and I don’t know how to solve it, because the latest openfast guide file does not Mention this flag. Hope to get your help[/size]
Well, it sounds like your FAST.Farm input file is not formatted properly. Do you have 10 lines in the wind turbine table? As with any input file processing error, I suggest that you enable the Echo option to debug.
I am trying to simulate wind farms using a row of 3 WTs separated 5D from each other to study aerodynamic wake interaction among wind turbines. I have reduced the value of C_NearWake from the default one to 1.1 with HWindSpeed=8m/s, but wake deflection is unobservable under the noticeable yaw misalignment with 25°/40°/0°, as the figure shown below. I’m confused why wake steering doesn’t occur under yaw conditions. I would be very appreciative if you can give me any hint on why this happens.
There is not really a way to disable wake deflection from turbine yawing in FAST.Farm; it is intrinsic to the calculation. I would guess that there is a small of amount of wake deflection that is occurring, it is just hard to see. You could review the wake center position outputs (WkPos#dT#D#) at various downstream distances, which when time averaged (to average out the wake meandering) should quantify the amount of wake deflection.
I also don’t see much (if any) wake meandering in your simulation. Are you using DEFAULT values for the wake parameters? Is your wake plane diameter (determined by dr and NumRadii) about 3 times the diameter of the rotor?
Thank you so much for the quick reply. During my simulation, I set dr=5.0, NumRadii=40, the rotor radius TipRad=63m, so the diameter of each wake plane, 2(NumRadii–1)dr, is about 3 times the rotor diameter. However, I did not use the DEFAULT value for C_NearWake, which is one of the wake parameters, because I would get the following error when C_NearWake= DEFAULT:
T2:FARM_UpdateStates:NearWakeCorrection:Local induction is high enough to invalidate the near-wake correction, i.e., m%a(i) >= 1.0_ReKi / p%C_NearWake.
I guess, the wake expand just before the near-wake correction error is displayed, which makes no physical sense, so I dropped the value of C_NearWake from the DEFAULT one, as discussed in the previous post. Other wake parameters are set as DEFAULT values. What confuses me is there’s no (little) wake meandering can be seen under obvious yaw conditions after the C_NearWake dropping. I wonder if you know how to explain or solve this problem.
Those settings sound OK, except for much lower than expected value of C_NearWake. To avoid the near-wake correction error, I recommend recompiling the newest version of FAST.Farm. This version includes an improved near-wake correction model that is valid under high-thrust conditions such that you should not need to drop C_NearWake.
Regardless, I’m still not sure how to explain the small amount of wake deflection or wake meandering in your case. Again, I suggest reviewing the wake center position outputs (WkPos#dT#D#) at various downstream distances to quantify how much deflection and meandering there are.
Rencently I runned the FAT.Farm example which has ten wind turbines in the same line, and the distance between every two turbines is 8 diameter. The wind files were produced by Turbsim and the wind speeds are 6m/s, 8m/s, 10m/s, 11.4m/s, 12m/s, 20m/s. When the wind speed was more than 10m/s, the FAST.Farm example could run normally, but the wind speed is 6m/s and 8m/s, the example can’t run and will occur the problem as the picture.
In the command, the information about the T8, T9 and T10 and the error message couldn’t be shown, so I can’t look over the error message. I don’t know this reason.
Finally, I want to know whether having a FAST.Farm example that includes the super control? And I hope to use that in my study.
