Sections
Getting Started
  • Work through the tutorial available on the downloads page.
  • Read and/or subscribe to the support forums.
  • Peruse some images of the software in action.
Commercial Version
A commercial version of openWind is planned for clients who require:
  • authenticated reports
  • authenticated binaries
  • custom development
  • support contracts
Licensing
Please contact the openWind team regarding:
  • developing products from the openWind codebase
  • developing plugins to the openWind codebase
Document Actions
  • Send this page to somebody
  • Print this page

Crash when optimizing two lay-outs

Up to Bug Reporting

Crash when optimizing two lay-outs

Posted by Joan Miquel Angles at February 26. 2010

Hi Nick,


I've been optimizing two lay-outs, one of them is the father of the other one, so that I can set a parent validity for it and make them be separated a certain distance.


Everything works fine and I can see how the two layouts are modified since using this criteria and it actually leaves the space required.


However, I wanted to go a step further and use the optimizer options to let OpenWind introduce new turbines if the factor capacity and array loses are correct.


I start with a couple of turbines in each lay-out and it starts to introduce new turbines but when I reach a quantity of around 15 turbines in total it crashes. Sometimes it shows a Windows error saying something related to memory that wasn't able to be read.


If you could keep an eye on this bug and fix it for the next release it would be great. I guess this will be helpful aswell for the comercial version that you're planing to launch.


Thanks!




Re: Crash when optimizing two lay-outs

Posted by nick at February 28. 2010
Hi Joan,

That is a configuration that I haven't really tested. It should work and I will try to fix it but I don't think its necessary to do it this way.

When it comes to optimising wind-farms, I take a few liberties with the openWind rules. What you're doing is very correct and I am impressed but you don't need to do it in order to maintain separation distances. The legality checks look at all turbines in the workbook when it comes to seperation distance. This is because the alternative could result in some very complicated layer hierarchies. We have workbooks with dozens of site layers which are then optimised and grown simultaneously. If we followed the openWind rules strictly in this regard these workbooks would send people insane.

A addendum to the openWind rules might go something like this: the rules are the rules by default when it comes to finding information and establishing validity - however, individual models and operations can bend (or add to) the rules if it makes sense to :)

The optimiser and energy capture routines look at all the turbines in the workbook when assessing legality so you can have your site layers as siblings rather then parent-child.

Hope this helps (if you can, I would appreciate you letting me look at your workbook)

Nick


Powered by Ploneboard