> -----Original Message----- > From: Eitan Adler [mailto:[email protected]] > Sent: 02 October 2013 14:55 > To: Paulo Matos > Cc: [email protected] > Subject: Re: [creduce-dev] Increase of size during reduction process > > On Wed, Oct 2, 2013 at 5:41 AM, Paulo Matos <[email protected]> wrote: > > Hi, > > > Shouldn't size increase be dismissed? > > It is possible to get into local minimums which are not global minimums. > >
This testcase I am trying is driving me nuts. It's currently at (-3.3 %, 473260 bytes) Each time a pass_blank starts it increases the size more than it decreases during its process, therefore even though the testcase started with ===< pass_blank :: 0 >=== (0.0 %, 458340 bytes) it is now way larger. Is there a way to set a seed to creduce, so that I can try to avoid those local minimums? Maybe if I can set a seed, I can set up multiple parallel creduce and grab the one that generates the smallest example. Paulo Matos
