Bug in tuning.sh?

[Boris 'pi' Piwinger]

Greg Louis wrote:

> Ok, this looks much better.  24 is far too high a target for this data
> set, which is why all your cutoffs are 0.5.  Try setting a target of 6
> (there's a target= line early in the script).  The new bogotune will
> evaluate your data and set an appropriate target; tuning.sh requires
> that it be done manually.

This gives:

> 06/13 14:19:03 1e-1   0.450 fpos.. 2 at cutoff 0.500000, run0..  42  run1..  38  run2..  47  127
> 06/13 14:19:45 1e-1   0.475 fpos.. 2 at cutoff 0.500000, run0..  41  run1..  38  run2..  47  126
> 06/13 14:32:44 3.2e-2 0.450 fpos.. 2 at cutoff 0.500000, run0..  42  run1..  38  run2..  47  127
> 06/13 14:33:26 3.2e-2 0.475 fpos.. 2 at cutoff 0.500000, run0..  41  run1..  38  run2..  47  126
> 06/13 14:45:59 1e-2   0.450 fpos.. 2 at cutoff 0.500000, run0..  42  run1..  38  run2..  47  127
> 06/13 14:46:41 1e-2   0.475 fpos.. 2 at cutoff 0.500000, run0..  41  run1..  38  run2..  47  126
> 06/13 14:45:18 1e-2   0.425 fpos.. 2 at cutoff 0.501000, run0..  83  run1..  81  run2..  78  242
> 06/13 14:32:01 3.2e-2 0.425 fpos.. 2 at cutoff 0.506000, run0..  96  run1..  87  run2..  85  268
> 06/13 14:04:12 3.2e-1 0.450 fpos.. 2 at cutoff 0.594000, run0..  97  run1..  91  run2..  89  277
> 06/13 14:05:02 3.2e-1 0.475 fpos.. 2 at cutoff 0.569000, run0.. 104  run1..  85  run2..  89  278

Maybe I should use 3.

pi