OpenFAST / openfast

Main repository for the NREL-supported OpenFAST whole-turbine and FAST.Farm wind farm simulation codes.
http://openfast.readthedocs.io
Apache License 2.0
654 stars 447 forks source link

About how ad_VerticalAxis_OLAF is calculated and parameterized #1508

Closed engineerYuXN closed 11 months ago

engineerYuXN commented 1 year ago

Dear all @ebranlard @jjonkman I have some questions I would like to ask you about the r-test/modules/aerodyn/ad_VerticalAxis_OLAF 1.How should I calculate this model directly using aerodyn? 2.The relevant parameters of the tag in the following figure, such as the environment parameters, can modify the labeled area according to the requirements? image 3.Where can I find literature or reports about the model 4.Is it possible to visualize the aerodynamic calculations of the model by means of post-processing software? 5.If I want to compare this model with my CFD calculations, do you have some suggestions? 6.How should I determine the model parameters in that module? Since I have no previous relevant experience, my question may not be very good, I hope you can give relevant advice.

Thank you so much!

jjonkman commented 1 year ago

Dear @engineerYuXN,

Have you already reviewed the AeroDyn and OLAF documentation? If not, I would start there as I would expect that to answer most of your questions: https://openfast.readthedocs.io/en/main/source/user/aerodyn/index.html# https://openfast.readthedocs.io/en/main/source/user/aerodyn-olaf/index.html

Our related journal paper may also be insightful for you: https://wes.copernicus.org/articles/7/455/2022/.

Best regards,

engineerYuXN commented 1 year ago

Dear developer, I have encountered the following problem when running ad_VerticalAxis_OLAF, and I don't know how to solve it

微信截图_20230408201543

@ebranlard@jjonkman

ebranlard commented 1 year ago

Dear @engineerYuXN

It looks like you are using an old executable for the aerodyn driver, and you are calling that executable with an AeroDyn file. You would need to compile your own driver executable and call the executable using an aerodyn driver input file (diffrent from an AeroDyn file). You can find more information about the compilation and the driver input file here: https://openfast.readthedocs.io/en/dev/source/user/aerodyn/driver.html If you use the main branch of the OpenFAST repository to compile, make sure you use example files from the r-test repository that are also in the main to ensure that the inputs are compatible with the executable. I hope that helps!

engineerYuXN commented 1 year ago

Thank you for answering my question I have another small question about OutListParameters

1.I selected the output parameters in OutListParameters, but in the calculation results, the output was all zero. I don't know where the problem occurred

2 1

2.The second problem is that I selected the torque output of the following three coordinate axes in the output parameters, but the torque value is very small compared to the CFD result, and I don't know why.

1

3.There is also a question about blade parameters, I extended the blade height in the AD_blade.dat, but did not modify the relative position of the blade in ad_driver.dvr, I want to determine the sweep radius by the above operation, but I found that the blade relative position is unchanged, increase the blade height, RtArea will become larger, but the calculated radius is different, I want to consult the developer, for adVerticalAxis Where the model sweep radius in OLAF should be defined.

2 1

@ebranlard@jjonkman

jjonkman commented 1 year ago

Dear @engineerYuXN,

I'm not sure I can answer your questions, but here are a few responses:

  1. To better understand your problem setup, can you share your full AeroDyn input file? What wind conditions are you simulating?
  2. Can you clarify the level of differences you are seeing or share a plot? Do both results have the same units?
  3. I'm not sure I understand your question.

Best regards,

engineerYuXN commented 1 year ago

Thanks for your reply @jjonkman 1.I'm doing a simulation with steady wind, and here are the relevant settings for my aerodyn input file,I don't know why TSR, Cp are 0.

1 2

2.Since I am currently unable to determine the wind wheel parameters of VAWT, I still need to confirm this issue

(This problem has been solved)3.I would like to consult whether to change the blade extension and chord length (blue line) by changing the parameters in the AD_blade.dat, and if I want to change the diameter of the wind wheel to change the ad_driver relative position of the blade in .dvr (red line), I don't know if the above idea is correct. If not, please tell me where I should modify the blade spread, chord length and rotor diameter

4 3

4.If I want to use inflow wind to generate turbulent wind and compare it with the flow field generated by the SST k-ω turbulence model in CFD, do you have any good suggestions or references? Thank you very much

ebranlard commented 1 year ago

Hi @engineerYuXN

When using vertical axis turbine (HAWTProjection=False), AeroDyn doesn't know the rotor area or typical radius, which is why the Rotor area, tip speed ratio, power coefficient, thrust coefficients, etc. are zero. You'll have to compute these quantities from your own knowledge of the geometry and using quantities such as RtAeroPwr, RtAeroMxg or RtAeroMxh.

You can use VTK outputs (WrVTK) to double check your change of geometry.

I would recommend looking at the aerodyn driver documentation and the sketch therein to get familiar with the coordinate systems. This can help you set up the geometry of the turbine. If you want the blades to be further away from the tower, you'll have to change the coordinate of the origin of the blades in the hub coordinate system (BldOrigin_h).

To generate turbulent wind that approximatively matches the ones from a CFD calculation you'll want to find the average shear profile, power spectrum, and coherence in your CFD simulation, and try to set the TurbSim inputs so that they approximate these values in a stastisical sense. You can also constraint the turbulence box (using TurbModel=TIMESR) to match some time series from CFD at given points.

If you have the flow field from CFD (without wind turbine disturbances), you can extract the flow field at a given plane of your CFD simulation for all time steps, and write it into the BTS format using pyFAST (you can start with this example to get familiar with it)

I hope that helps.

Emmanuel

engineerYuXN commented 1 year ago

Hello dear developers! Thank you for answering the above question! I currently use the CFD software Star-ccm+ to simulate a vertical axis wind turbine and compare it with OLAF using a steady-state model. I compared the Z-axis torque calculated by the two methods and obtained the following figure. I don't know why there is such a big difference.

1

Below are all my settings for OLAF, and I hope you can give me some questions or suggestions about why the simulation results are so different.

AD.dat

2 3

ad-driver.dvr

4 5

OLAF.dat

6

AD-blade.dat

7

@ebranlard@jjonkman Best regards,

shipors commented 1 year ago

@engineerYuXN 可以加个联系方式交流下吗?

engineerYuXN commented 1 year ago

@engineerYuXN 可以加个联系方式交流下吗?

你好,你可以把你的微信发到我的邮箱中,我来加你(我的邮箱:yuxiaonan@hrbeu.edu.cn) @shipors