Optimisation issues with CCBlade

[zsacfder]

Hello，I would like to use CCBlade as a tool for blade optimization, but optimizing the entire blade at once seems to be quite resource-intensive. May I ask if it is possible to optimize each blade element individually using CCBlade? How should I go about doing that? I would like to evaluate the power output, but I noticed that both the source code and the output results sum the power of each blade element, making it difficult for me to assess the power of each individual element. If possible, I would prefer to calculate the aerodynamic performance of specific blade elements one at a time.

[gbarter]

"Resource intensive" is probably a relative term. For us, CCBlade is a very efficient and rapid approach to blade performance optimization compared to higher levels of fidelity.

For examples of blade design, see CCBlade's use in WISDEM in this example:
https://github.com/WISDEM/WISDEM/tree/master/examples/03_blade
https://wisdem.readthedocs.io/en/master/examples/03_blade/tutorial.html

I'm not sure I perfectly understand what you would like to do by tackling design one segment at a time, especially as the chord and twist profiles will need to be continuous along the blade span. Either way, I don't have a ready-made example for you here and it will require some development on your part using CCBlade and OpenMDAO (or other optimization libraries). You can see a more focused CCBlade example here if it helps.