Looks like I've managed to get Uniform into some sort of infinite loop
now. Not exactly sure how, or where it's happening... might just
proceed without it.
Will let you know if I get the chance to look into it.
On 28/11/2008, at 8:44 AM, Sean Luke wrote:
> Sending them to this list is fine, or you can send them directly to
> me or to [log in to unmask] (either way) to avoid torturing
> Michael Hart wrote:
>> Indeed, bugs in Uniform...
>> So far, they've been ArrayOutOfBoundsExceptions - I suspect mainly
>> due to the fact that I'm using some GPNodes in more than one
>> function set... or something like that.
>> I've patched a few of the array exceptions - at least so that they
>> don't appear, no idea if the code is doing what it's supposed to.
>> I've also attached a patch for the InterPopulationExchange
>> serialization, just in case it falls through the cracks (haven't
>> noticed it in CVS yet).
>> (if there's a better place to be bug reporting and sending patches,
>> let me know)
>> On 26/11/2008, at 2:33 AM, Sean Luke wrote:
>>> Hmmm, I'll have to figure out what to do there with regard to
>>> warnings in Uniform.
>>> And now a warning: you're using typed GP with Uniform. The type
>>> extensions to Uniform are my own, not those of the original
>>> authors of the paper. And they've not been well tested (or really
>>> tested at all). Expect the possibility of some bugs.
>>> Michael Hart wrote:
>>>> Thanks Sean - I'll steer clear for now. It just looked so meaty,
>>>> I figured it had to be doing something interesting :-)
>>>> Now, in terms of Uniform, I had to make UniformGPNodeStorage
>>>> implement Serializable to allow for checkpointing. I also ran
>>>> into an ArrayOutOfBoundsException on line 432 of Uniform.java
>>>> which took me ages to track down. Turns out that it was due to
>>>> some GPTypes specified in my params that I hadn't used yet in any
>>>> of my GPNodeConstraints. It might be nice to be able to catch
>>>> this or warn about it.
>>>> Apart from that, smooth sailing again.