Forum
Important Notice for New User Registrations
To combat an increasing number of spam and bot registrations, we now manually approve all new user registrations. While this may cause a delay until your account is approved, this step is essential to ensure the quality and security of this forum.
To help us verify your registration as legitimate, please use a clear name as user name or an official email address (such as a work, university, or similar address). If you’re concerned that we may not recognize your registration as non-spam, feel free to email us at with a request to approve your username.
Export Aerodynamic Blade Graph for multiple timesteps
Quote from Shubham on 20. March 2023, 16:53Hello,
I am performing simulations for Vertical Axis Wind Turbines using LLFVW. I need the data for the spanwise variation of normal blade forces for a complete rotation. There are 120 timesteps (each timestep is for 0.00090792 secs) for a single rotation and therefore, manually it is not possible to store for every timestep. Can you please tell me how can I automate this process? For eg. I can specify the first and last timestep (or exact time in secs) which I want to store and it will export the data to text files in the folder specified. I have attached the image for a single timestep.
Thank you.
Regards
Shubham
Hello,
I am performing simulations for Vertical Axis Wind Turbines using LLFVW. I need the data for the spanwise variation of normal blade forces for a complete rotation. There are 120 timesteps (each timestep is for 0.00090792 secs) for a single rotation and therefore, manually it is not possible to store for every timestep. Can you please tell me how can I automate this process? For eg. I can specify the first and last timestep (or exact time in secs) which I want to store and it will export the data to text files in the folder specified. I have attached the image for a single timestep.
Thank you.
Regards
Shubham
Uploaded files:- You need to login to have access to uploads.
Quote from David on 20. March 2023, 18:30Hi Shubam,
to get this data exported you can export the simulation data to a text file through the menu:
- Turbine Simulation -> Export Data -> Export Current Simulation Data as ASCII
In the (very large) file that is created the local blade data is then stored for each blade panel and for each timestep. The normal force can be found in the columns:
- Normal Force Blade 1 PAN 1 [N/m]
where PAN goes from 1 -X where X is the total number of blade panels.
BR,
David
Hi Shubam,
to get this data exported you can export the simulation data to a text file through the menu:
- Turbine Simulation -> Export Data -> Export Current Simulation Data as ASCII
In the (very large) file that is created the local blade data is then stored for each blade panel and for each timestep. The normal force can be found in the columns:
- Normal Force Blade 1 PAN 1 [N/m]
where PAN goes from 1 -X where X is the total number of blade panels.
BR,
David
Quote from Shubham on 21. March 2023, 12:30Hello David,
Thank you for your reply. This one works. Meanwhile, I also found a way of doing the same using the SIL interface using Python code. I can extract the “Normal Force (at section) Blade 1 [N/m]” using getCustomData_at_num and at every timestep, I can extract data at every blade panel (“at section”). Although in this case, I need to run the SIL simulation again so more time taking. Also for future use cases, maybe you can specify in “QBlade Docs” how to extract “Aerodynamic Blade Graph” variables directly using the SIL interface. I was unable to figure that out. Another good add-on for SIL: extract simulation data directly from a converged LLFVW simulation (using a .qpr file) and no need to run the simulation again (maybe it’s already possible but I am not sure).
Regards
Shubham
Hello David,
Thank you for your reply. This one works. Meanwhile, I also found a way of doing the same using the SIL interface using Python code. I can extract the “Normal Force (at section) Blade 1 [N/m]” using getCustomData_at_num and at every timestep, I can extract data at every blade panel (“at section”). Although in this case, I need to run the SIL simulation again so more time taking. Also for future use cases, maybe you can specify in “QBlade Docs” how to extract “Aerodynamic Blade Graph” variables directly using the SIL interface. I was unable to figure that out. Another good add-on for SIL: extract simulation data directly from a converged LLFVW simulation (using a .qpr file) and no need to run the simulation again (maybe it’s already possible but I am not sure).
Regards
Shubham
Quote from David on 21. March 2023, 15:49Hi Shubam,
data from the “Blade Graph” can’t be directly exported using the getCustomData_at_num SIL function,. However, all data thats included in the “Blade Graph” is also available as an “…(at section)” variable in the “Aerodynamic Time Graph”. Regarding the export – this can be done from the GUI with a single click. We also have this feature in the CLI (command line) version thats part of the enterprise edition but have not planned to add it to the SIL interface.
BR,
David
Hi Shubam,
data from the “Blade Graph” can’t be directly exported using the getCustomData_at_num SIL function,. However, all data thats included in the “Blade Graph” is also available as an “…(at section)” variable in the “Aerodynamic Time Graph”. Regarding the export – this can be done from the GUI with a single click. We also have this feature in the CLI (command line) version thats part of the enterprise edition but have not planned to add it to the SIL interface.
BR,
David