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 as ASCII file
Hello David
I use the SIL Interface to write (a substantial amount of) .qpr files. I want .txt files for post-processing, so until now I have used the ‘Export Current TurbineSimulation Results as ASCII’ in the QBlade GUI.
The problem I am facing is that now that I am working with a lot of large files, it takes a lot of time to open them with the QBlade GUI and export them as ASCII. Is there a way to export to this file format directly in the Python code?
Thanks in advance!
Jelle
Hi Jelle,
the main purpose of the SIL interface is to provide full control of the simulation loopand to allow for couplings with other tools.
For batch processing, QBlade-EE includes the CLI interface, which can evaluate a large number of jobs efficiently and supports batch export of the results.
To export data from the SIL interfaceyou can use the following functions
- double getCustomData_at_num(char *str, double pos, int num);
- double getCustomSimulationData(char *str);
These functions allow you to request simulation data, which you can call multiple times as needed. You can then aggregate and store this data in a custom format. Exporting this data to a file using Python or MATLAB is straightforward.
BR,
David
Hi David,
Thank you for the explanation.
I can get the CLI interface to work on Windows, but I was wondering if the CLI interface also works on Linux?
Thanks in advance!
Jelle
Hi Jelle,
there is no difference between the Windows and Linux versions, so all features are available on both operating systems.
BR,
David
Hi David,
Thank you for the quick response. I asked the question because I keep running into the same error on Linux:
./QBladeEE_2.0.8.6: error while loading shared libraries: libQGLViewer.so.2: cannot open shared object file: No such file or directory
Do you have any idea why? It all works fine with the .sh scripts provided in the downloads and on windows as well.
Thanks in advance!
Jelle
Hi Jelle,
to ensure the libraries are found at runtime, you need to add the /Libraries folder to the LD_LIBRARY_PATH environment variable.
In the shell script, the following lines do exactly that:
This appends the Libraries subdirectory (located in the current working directory) to the existing LD_LIBRARY_PATH and then exports the updated variable. This ensures that any binaries or child processes started from this shell session can locate and use the required shared libraries.
BR,
David
