Dear @KumaraRaja.Eedara
Thanks a lot for the response and the files. A very naive question, what is the difference between .dat and .inp file. My assumption was that the input file (.inp) was the the input to create wind files via TurbSim.
Please correct me if I am wrong.
Best regards,
Karthik
Dear @Karthik.Prakash
Your understanding about *.inp is correct, it is input for TurbSim.
I canāt understand which *.dat you are talking about. If it is about the *.dat file in line22 in the python code, then it is the input file required for running OpenFAST. It is basically name of the inflow wind file in *.fst. i.e the variable InflowFile in *fst file when CompInflow is set to 1.
Regards,
Kumara
Dear @KumaraRaja.Eedara
Thanks a lot for the reply. I meant the same .dat file that you mentioned.
- Where my confusion lies is, what is the difference between the .inp and .dat (InFlow) file?
- Is only .inp used to create wind files?
- What is the connection of .dat (Inflow) to Wind creation or use. I have seen .dat files referring to .bts file.
- I am also a bit confused about the difference between InflowWind and TurbSim.
Best regards,
Karthik
Dear @Karthik.Prakash
Here is how the code works:
To perform OpenFAST simulation, you need to specify āEDFileā, āInflowFileā,āAeroFileā,āServoFileāā¦etc. Right? and note that these are all *.dat files.
The code assumes you already have list of *bts files created from āTurbSimā already. Note that the line33 in the code creates a python list (wind_files) with all the *bts files names as entries.
Now, inorder to perform simulations automatically, corresponding to each of the
wind files (*bts) in the folder, all that needs be changed between two runs is,
the name of the wind file i.e variable name āFileName_BTSā in āInflowFile.datā. Agreed?
That is precisely what the code does.
For each run, the code opens āInflowWind.templateā and replaces the āFileName_BTSā variable
value with the new *bts file name and saves it as InflowWind_01.dat.
Then āOpenFASTā is called and results are saved.
Again, the process repeats for the new *bts file automatically.
Hope this helps!
Regards,
Kumara
1 Like
Hi @KumaraRaja.Eedara
This really helps. Can you help me understand a bit more about the fundamental difference b/w InflowWind and Turbsim. If I understood it correctly, Turbsim via the inputs from .inp creates .bts files and these .bts files are referred in the .dat (InflowWind) file. But, I am trying to understand are they both 2 different things.
Best regards,
Karthik
Hi @KumaraRaja.Eedara
I got the following error while running the simulations. I am trying to understand what line 40 is doing, can you help me understand why we need to rename openFAST_output_file_name as āSim_01.outā and why is the renaming from .bts to .out done in line 37 as the .out file was seen not used anywhere. Please correct me if I understood wrong.
Dear @Karthik.Prakash
The line40 simply renames the OpenFAST output file (*.out) with the name same as *bts file name. In my case after OpenFAST file the name of the output file created is āSim_01.outā. In your case if it is different (say xyz.out) replace āSim_01.outā in the line40 with āxyz.outā. If renaming is not done, the OpenFAST output file gets over written after each run. Make sure the directory is consistent.
Regards,
Kumara
Dear @Karthik.Prakash,
Iāll just clarify that InflowWind is a module of OpenFAST that enables other modules of OpenFAST (e.g., AeroDyn) to access ambient wind information. InflowWind is set up such that other modules can request wind data at a specific point and time and InflowWind will provide that data to OpenFAST. InflowWind supports many wind data types, including steady uniforum, unsteady uniform, and full-field turbulence. The latter can be computed by TurbSim and its output file can be listed in the InflowWind input file. TurbSim is a preprocessor for generating ambient wind data that varies in time and space (full-field turbulence).
Some files have specific extensions (such as *.bts files generated by TurbSim). The primary input files of modules of OpenFAST (including InflowWind) donāt require specific file extensions, but we tend to use *.dat as the file extension.
Best regards,
Dear @Jason.Jonkman ,
The explanation really helps and clarified one of my fundamental doubts.
Best regards,
Karthik
Dear KumaraRaja.Eedara
Thanks a lot. You can share it to windhy0415@gmail.com
Best regards
Yuan
Dear Yuan Hu,
I donāt understand what exactly you are looking for. Iāve emailed the files for automating wind file generation using TurbSim. Thanks.
Regards,
Kumara
Dear KumaraRaja.Eedaraļ¼
Can you emailed āthe files for automating wind file generation using TurbSimā to 1252996175@qq.com.
Best regards,
jia