-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
installing openFAST binaries in windows 10 #463
Comments
Please provide more information. You can start by filling out this form: Bug description To Reproduce
Expected behavior Screenshots, if applicable OpenFAST Version
System Information (please complete the following information):
Additional context |
@tchatte3 when you attempt to install the executable, how are you doing this? The executables provided are not installation executables, but rather the full OpenFAST executables. These should be run through a command or powershell window one Windows 10. So if you double click on the executable file through the file explorer, it will briefly open a command window then exit since no input file name was given. |
@andrew-platt I understand that. OK, so that solves the problem, I closed the issue. |
Dear Andrew, |
Hi, I have also the tchatte3's problem. In AeroDyn standalone.
|
Dear @ArezooN, NREL has not provided a precompiled binary executable for the standalone AeroDyn driver, so, you must compile this from the source code and compile scripts that NREL has provided. If you are using Windows, I find Visual Studio + Intel Fortran the most straight forward. Documentation on compiling is found here: https://openfast.readthedocs.io/en/main/source/install/index.html. Once you've compiled the standalone AeroDyn driver, I agree that the executable can be run with the example files that you reference. Best regards, |
Hi openFAST team,
I have downloaded the openFAST binaries for windows 10. I have also installed the intel libraries, but when I try to install the executable, the command window briefly opens and then nothing happens. Any fixes for that ?
The text was updated successfully, but these errors were encountered: