-
Notifications
You must be signed in to change notification settings - Fork 40
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
Automatic writing of various DLC input files #183
Comments
Hi Karthik, Yes, in the If you uncomment this line it should run DLC 1.1 from cut-in to cut-out, with 6 seeds each. You can also select certain wind speeds and number of seeds. I hope this helps. Best, Dan |
Hi Dan, Thanks a lot for getting back, this really helps. I am not that great with programming and hence pardon me for my naïve questions. The *.yaml files, are they Python scripts that I can run in Anaconda etc. and can I use the script to run a Open fast model that I have. Best, |
Hi Karthik, You run python scripts with The |
Hi Dan, So, can I run the python script 'weis_driver_loads.py' in Python as is separately & if so is it so that I have to point to the path of .yaml file in the Python script. Again, excuse me for my naive queries in coding. Best, |
Yes, right around here:
|
Thanks a lot Dan. I will git a shot and update. Best, |
Hi Dan, Do I need to install WEIS to run this script for a Onshore Wind turbine. Is there a similar file for Onshore turbines. Regards, |
Hi Karthik, Yes, you need to install WEIS to run scripts that Here is an onshore example. Note that it does not have platform or mooring geometry options, and the floating DOFs are set to Best, Dan |
Hi Dan, Thanks a lot for the reply. Is there a way to create one .fst file that will have the wind speeds from cut-in to cut-out or separete .fst files are needed for running simulations from cut-in to cut-out. For example from 3m/s to 25 m/s, do I need to create 23 .fst files? Best regards, |
Each .fst file will need to point to a different InflowWind file that will specify each wind speed. I'd recommend a full set of OpenFAST inputs for each case. That is our regular practice. Running this example will set up the cases, generate the wind inputs, and run the simulations. You will need to edit the DLCs in the modeling options. The DLCs in this example are close to what you are looking for, if you set |
Hi Dan, Probably a dumb question. If I want to run https://github.com/WISDEM/WEIS/blob/develop/examples/02_control_opt/modeling_options_loads.yaml, (will set up the cases, generate the wind inputs, and run the simulations.)does that mean that I have to run WEIS so that it generates all the .fst files and the corresponding inputs, for example like. -dat files etc. needed to run an OpenFast Aeroelastic simulation? If so, can you help me find the instructions on how to run WEIS so that those inputs will be created. Best regards, |
Yes, you will need to run WEIS. I added some documentation here: https://github.com/WISDEM/WEIS/tree/develop/examples/02_control_opt Running the weis_driver.py files will load modeling, geometry, and analysis options to run WEIS. More info can be found here: https://github.com/WISDEM/WEIS/blob/develop/docs/how_weis_works.rst |
Hi @dzalkind , I got the below error while trying to run WEIS with the command python weis_driver.py When I first installed WEIS, I used the instructions mentioned here https://github.com/WISDEM/WEIS |
It looks like WEIS isn't installed in the |
I will try that out. Should I clone the develop branch or the main would suffice? |
Aim for the |
I followed the instructions (as well as tried python setup.py develop in your Users\prakakar\source\WEIS directory.) https://github.com/WISDEM/WEIS/tree/develop (base) C:>cd C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt (base) C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt>conda activate weis-env (weis-env) C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt>python weis_driver.py (weis-env) C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt>python weis_driver.py (weis-env) C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt>python weis_driver.py (weis-env) C:\Users\prakakar\source\WIES_Develop\WEIS\examples\02_control_opt> |
The installation is failing in some way. Please post the results of the install instructions you followed. Also note that WEIS does not run on Windows unless you are running in the Windows Subsystem Linux |
I don't have Linux installed and is using only Windows. Is there any possibility to run it on Windows. I followed the below commands: ``conda env create --name weis-env -f https://raw.githubusercontent.com/WISDEM/WEIS/develop/environment.yml python=3.9 git clone https://github.com/WISDEM/WEIS.git |
You posted the commands you are using for the install, but not the output on the terminal. Regardless, the install is likely failing because you are using regular Windows. We have some ideas to make Windows better supported in the future using conda, but that has not been implemented yet. For now, I would suggest using the Windows Ubuntu Subsystem Linux or installing a virtual machine. |
Sorry for the mess, this was the output of commands conda env create --name weis-env -f https://raw.githubusercontent.com/WISDEM/WEIS/develop/environment.yml python=3.9 conda activate weis-env git clone https://github.com/WISDEM/WEIS.git git checkout branch_name python setup.py develop (weis-env) C:\Users\prakakar\source\WEIS_Develop_Rev2\WEIS>python setup.py develop
from numpy.distutils.command.build_ext import build_ext INFO: building 'wisdem.ccblade._bem' extension Installed c:\users\prakakar\source\weis_develop_rev2\weis\rosco Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Installed c:\users\prakakar\source\weis_develop_rev2\weis\pcrunch Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Installed c:\users\prakakar\source\weis_develop_rev2\weis\pyhams Installed c:\users\prakakar\source\weis_develop_rev2\weis\moorpy Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Installed c:\users\prakakar\source\weis_develop_rev2\weis\raft Installed c:\users\prakakar\source\weis_develop_rev2\weis\dtqpy Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages\mat4py-0.5.0-py3.8.egg Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages Using c:\users\prakakar\anaconda3\envs\weis-env\lib\site-packages CMake suite maintained and supported by Kitware (kitware.com/cmake). CPU baseline : CPU dispatch : CPU baseline : CPU dispatch : (weis-env) C:\Users\prakakar\source\WEIS_Develop_Rev2\WEIS> |
The terminal doesn't clearly say the word, "error", which is both surprising and annoying, but the install is not working. You can use standard Windows, sorry. |
Hi @gbarter Thanks a lot for getting back. I tried the installation all over again and its still the same error. (weis-env) C:\Users\prakakar\source\WEIS_Develop_Rev2\WEIS\examples\02_control_opt>python weis_driver.py (weis-env) C:\Users\prakakar\source\WEIS_Develop_Rev2\WEIS\examples\02_control_opt> |
Hi @gbarter I read the new Readme, https://github.com/WISDEM/WEIS/tree/develop in and saw the following updated comment Can you help me when I should use this command during installation. Will the above lines help in fixing the issue of module missing. |
Karthik, Sorry if I wasn't clear before. You keep trying to install WEIS on Windows, but it will not work, no matter what conda commands you use. There is nothing I can do to fix this. Cheers, |
Hi Garrett, Thanks for the response. If I understand correctly, I have to install Windows Ubuntu Subsystem Linux in a virtual machine? Best regards, |
You would have to use either the Windows Ubuntu Subsystem Linux or a virtual machine (not both). VMWare Workstation Player would be one virtual machine option. |
Got it. So, I can use a VMWare virtual machine and install Linux (or Ubuntu) in the Virtual |
Yes |
Is there another way of automatically writing the inputs for the simulation for various DLC's (eg .fst files, .dat files etc) and obtaining the inputs other than WEIS. |
Hi, If I understand correctly, then if If I want to run from 3 m/s to 25 m/s with 6 seeds for each wind speeds, then should I need to create 23 x 1 (wind direction 0 degree only) x 6 (seeds) = 138 .*fst files? |
WEIS is our preferred tool for this. The OpenFAST team has some toolboxes to make batch editing easier that you can explore: |
Description of feature
Already, Is there any Python based script available that can be used to run a set of DLC's at one shot. For example, a script that can run NTM simulations from 3m/s to 25 m/s (basically create the input files for such a simulation) along with the cases like idling, idling above cut out etc.
Potential solution
A Python script that can create multiple input files or point to various files like controllers, brakes etc. for each of the simulations.
Best,
Karthik
The text was updated successfully, but these errors were encountered: