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.

Please or Register to create posts and topics.

Qblade Turbine Simulation issue across different computers

Hi!!

There’s a few issues we have when we try to run simulations with different computers.

For example, when we re-run the same simulation in another computer, we get different outputs, especially for coefficient of power and Aerodynamic torque values which was our main focus.

We’ve also seen that whether we utilize GPU or CPU, the results sometimes differ as well.

This happens inconsistently (i.e. sometimes there’s no difference in results, sometimes running even in the same computer and same CPU but at different time periods, provides different results).

Thanks in advance for any help!!

Hi,

Thanks for reporting this.

What you describe would be highly unusual. In QBlade, results are generally deterministic apart from very small floating-point deviations, for example from wake integration. These should normally be barely noticeable.

Also, after every commit we run automated test cases and compare result time series across different machines to ensure deterministic behavior and track effects of updates and model improvements.

The sporadic behavior you describe points more towards a bug, for example an uninitialized variable or another source of non-deterministic behavior. That would also be consistent with differences appearing only sometimes, even on the same machine.

If possible, please send us the QBlade version number and a minimal test case where this happens. Then we can look into it in more detail.

Best regards,

David

Scroll to Top