WISDEM / CCBlade

A blade element momentum method for analyzing wind turbine aerodynamic performance that is robust (guaranteed convergence), fast (superlinear convergence rate), and smooth (continuously differentiable).
Other
45 stars 40 forks source link

ImportError: DLL load failed while importing _precomp: The specified module could not be found. #32

Closed MuhammadSharjil closed 6 months ago

MuhammadSharjil commented 9 months ago

Hi I am getting the following error while executing test case.

ccblade

ccblade1

ccblade2

Kindly guide me on this. Thanks

Regards, Muhammad Sharjil

gbarter commented 9 months ago

Your WISDEM install did not succeed. The quickest resolution would be to just type conda install wisdem. If you need to install from source, then we'll have to see where things went awry using the installation instructions here.

MuhammadSharjil commented 9 months ago

hi @gbarter Thanks for the response. I have executed conda install wisdem

The response I am getting is conda_install_wisdem

I actually want to use CCBlade to generate Cp Ct Cq surface for IEA 15MW wind turbine with umaine platform.

Thanks

MuhammadSharjil commented 9 months ago

I am using python version 3.10.0

I am getting the following message while activating on windows power shell image

gbarter commented 9 months ago

You can try dropping the python=3.10 part of the command. That might be a bit outdated.

MuhammadSharjil commented 9 months ago

Hi @gbarter I tried your suggested command and then followed https://wisdem.readthedocs.io/en/master/installation.html#configure-anaconda-environment ccblade_2

ccblade_4

When I tried to execute cd test python test_all.py

I got following errors ccblade_3 Can you suggest me how to resolve this. Thanks

gbarter commented 9 months ago

This is very confusing. Precomp is clearly compiled and available but the code cannot find it. Also, WISDEM is not installing correctly because it labels the package as UNKNOWN, which is odd. This could be because the environment is corrupted. You have pasted the command to create a new environment, but have no used a unique name, so it keeps using the same one. I would suggest removing the WISDEM folder and the wisdem-env environment and starting fresh. To remove the environment do: conda remove --name wisdem-env --all

Are you behind any corporate firewall or security software that might be blocking use of some types of files or programs?

MuhammadSharjil commented 9 months ago

Hi @gbarter Thanks for the response. I will check this command and will share the outcome. I am using a university connection and as far as I know, my desktop computer is quite at freedom to install these utilities.

Regards, Muhammad Sharjil

MuhammadSharjil commented 9 months ago

hi @gbarter I have looked into it and I found that the python was trying to access WindowsApp folder for some kind of installation in C drive, which is not by default allowed by windows 10. I changed it to avoid the access. Now I am using Python 3.11.4 1

2

3

4

5

6

Can you guide me on this. Thanks

gbarter commented 9 months ago

@MuhammadSharjil : I'm really sorry, but I do not know what is wrong with your installation. I have not seen that problem before, nor can I recreate it on any of my computers. I am at a loss of what to suggest to you next and I'm really sorry about that.

Moving forward, it you are comfortable trying the WSL (windows subsystem linux) or have access to a Mac or Linux computer, that tends to be a bit more robust. I am also hopeful that future WISDEM releases on Windows will be smoother.

MuhammadSharjil commented 9 months ago

Hi @gbarter Thanks for a detailed response. I made some further attempt and finally digout the issue. I dont know why this was happening but it was somewhat causing the problem. mamba activate wisdem-env was not activating the wisdem-env I tried conda activate wisdem-env also but it didnt work. Even trying to delete the environment with conda remove --name wisdem-env --all was not deleting the wisdem-env. Afterwards executing conda env list was still showing wisdem-env I then used the absolute path in conda remove command to reference the environment . It removed the wisdem-env

I then made a a fresh attempt to go through WISDEM Installation. Now only using absolute path for environment activation is enabling the wisdem-env. I am able to execute _python testall.py I am now facing this issue that the 16GB ram windows 10 system is crashing in between the process.

ccblade1

Can you guide me on this. Thanks

Thanks Regards, Muhammad Sharjil

MuhammadSharjil commented 8 months ago

hi @gbarter I have managed to get the things going in the right direction fortunately. I am running the example.py file in 10_ccblade. I want to ask about the data source of r = np.array( I tried matching it with the data in 02_reference_turbines/nreal5mw.yaml components.blade.outer_shape_bem.reference_axis.&ref_axis_blade.z.values

ccblade

Can you guide me on this as to how to select the numbers used in example.py for "r" in comparison to the ones provided in nrel5mw.yaml

Thanks

Regards Muhammad Sharjil

gbarter commented 8 months ago

@MuhammadSharjil : I am a bit unclear what the question or concern is. You are correct in noticing that the values for chord and twist in the CCBlade example are taken from the NREL 5MW reference turbine profile. However, I don't understand why the chord and twist profiles have to be neatly aligned with the larger yaml-input file for full WISDEM simulation.? You'll notice that the nrel5mw.yaml file also has different input grids for the blade shape (the "reference axis") vs the chord and twist profile. Internal to WISDEM everything is interpolated to a common grid of interpolation points, but no such requirement is placed on the input.

In case it helps, the input grid in the yaml files is non-dimensionalized between 0-1. You can use these points and the reference axis curve to calculate the radial position. The CCBlade example species the radial points directly.

MuhammadSharjil commented 8 months ago

Hi @gbarter I got bit confused by the numbers and just wanted to be sure about the values as to where are these referenced from. I compared and found differences in the values and number of data points between BladeSpan, Blade Chord and Blade Twist as given in a. r-test/glue-codes/openfast/5MW_Baseline /NRELOffshrBsline5MW_AeroDyn_blade.dat b. WISDEM/examples/10_ccblade /example.py

Screenshot 2024-03-07 at 10 07 42 Screenshot 2024-03-07 at 10 09 58 Screenshot 2024-03-07 at 10 10 22

I actually want to use ccblade to get get Cp, Ct and Cq values for iea 15MW wind turbine. I wanted to be sure about the numbers to be inserted for 5MW Wind Turbine case. So that I can easily identify and plug in numbers from https://github.com/IEAWindTask37/IEA-15-240-RWT/blob/master/OpenFAST/IEA-15-240-RWT/IEA-15-240-RWT_AeroDyn15_blade.dat

Thanks

Regards, Muhammad Sharjil

gbarter commented 8 months ago

Why not use the file already provided in the same 15-MW repository for the coefficient values?

If you really want to use CCBlade to get those values from the AeroDyn file, you would set:

MuhammadSharjil commented 8 months ago

Hi @gbarter I used Aerodyn_driver and Openfast to get Cp, Ct and Cq for IEA 15MW. The numbers I got were not in comparison with the https://github.com/IEAWindTask37/IEA-15-240-RWT/blob/master/OpenFAST/IEA-15-240-RWT/Cp_Ct_Cq.IEA15MW.txt which used ccblade (https://wes.copernicus.org/articles/7/53/2022/wes-7-53-2022-discussion.html) I will try the numbers you have suggested to get some results.

Thanks Regards, Muhammad Sharjil

wodetouzi commented 8 months ago

Hi @gbarter Thanks for a detailed response. I made some further attempt and finally digout the issue. I dont know why this was happening but it was somewhat causing the problem. mamba activate wisdem-env was not activating the wisdem-env I tried conda activate wisdem-env also but it didnt work. Even trying to delete the environment with conda remove --name wisdem-env --all was not deleting the wisdem-env. Afterwards executing conda env list was still showing wisdem-env I then used the absolute path in conda remove command to reference the environment . It removed the wisdem-env

I then made a a fresh attempt to go through WISDEM Installation. Now only using absolute path for environment activation is enabling the wisdem-env. I am able to execute _python testall.py I am now facing this issue that the 16GB ram windows 10 system is crashing in between the process.

ccblade1

Can you guide me on this. Thanks

Thanks Regards, Muhammad Sharjil

Hi Muhammad, I am facing exactly the same problem as you were. Could you please explain more about how to remove the wisdem-env using an absolute path? Best regards, wodetouzi

gbarter commented 8 months ago

I believe if you type conda env list it will give you the full path to the environments, and then you can manually delete those directories. I think there is also a .conda/environments.txt file in your home directory that needs to be updated. Be wary that this manual approach might cause some issues and conda remove --name <envname> --all is best.

MuhammadSharjil commented 8 months ago

Hi @gbarter Thanks for a detailed response. I made some further attempt and finally digout the issue. I dont know why this was happening but it was somewhat causing the problem. mamba activate wisdem-env was not activating the wisdem-env I tried conda activate wisdem-env also but it didnt work. Even trying to delete the environment with conda remove --name wisdem-env --all was not deleting the wisdem-env. Afterwards executing conda env list was still showing wisdem-env I then used the absolute path in conda remove command to reference the environment . It removed the wisdem-env I then made a a fresh attempt to go through WISDEM Installation. Now only using absolute path for environment activation is enabling the wisdem-env. I am able to execute _python testall.py I am now facing this issue that the 16GB ram windows 10 system is crashing in between the process. ccblade1 Can you guide me on this. Thanks Thanks Regards, Muhammad Sharjil

Hi Muhammad, I am facing exactly the same problem as you were. Could you please explain more about how to remove the wisdem-env using an absolute path? Best regards, wodetouzi

@wodetouzi , conda info --envs This will give you the complete path of environments Then you can copy the full path of environment from the list which you want to remove conda remove --name -p --all i.e. conda remove --name -p C:\ProgramData\miniforge3\envs\wisdem-env --all conda

gbarter commented 6 months ago

This should be resolved in the latest version of WISDEM