Bug in tuning.sh?

[Boris 'pi' Piwinger]

Greg Louis <glouis at dynamicro.on.ca> wrote:

>> getco $md 0.10 $rs r0.ns.mc r1.ns.mc r2.ns.mc
>
>Good catch.  That should be
>getco $md,$rs 0.1 r0.ns.mc r1.ns.mc r2.ns.mc
>with current bogofilter.

Great. I knew something was wrong. With my fixed explained
below my tuning results now are really showing something:

>06/12 17:42:03 3.2e-2 0.450 fpos.. 0 at cutoff 0.797000, run0.. 111  run1.. 100  run2.. 103  314
>06/12 17:29:34 1e-1   0.450 fpos.. 0 at cutoff 0.797000, run0.. 125  run1.. 113  run2.. 116  354
>06/12 17:54:31 1e-2   0.450 fpos.. 0 at cutoff 0.797000, run0.. 132  run1.. 106  run2.. 120  358
>06/12 17:17:06 3.2e-1 0.450 fpos.. 0 at cutoff 0.797000, run0.. 132  run1.. 116  run2.. 124  372
>06/12 17:04:38 1      0.450 fpos.. 0 at cutoff 0.797000, run0.. 147  run1.. 133  run2.. 149  429
>06/12 17:28:55 1e-1   0.425 fpos.. 0 at cutoff 0.946100, run0.. 162  run1.. 146  run2.. 154  462
>06/12 17:41:24 3.2e-2 0.425 fpos.. 0 at cutoff 0.946100, run0.. 178  run1.. 154  run2.. 166  498
>06/12 17:53:52 1e-2   0.425 fpos.. 0 at cutoff 0.946100, run0.. 188  run1.. 165  run2.. 173  526
>06/12 17:16:26 3.2e-1 0.425 fpos.. 0 at cutoff 0.946100, run0.. 184  run1.. 177  run2.. 174  535
>06/12 17:28:16 1e-1   0.400 fpos.. 0 at cutoff 0.962300, run0.. 175  run1.. 186  run2.. 181  542

What we do see: robs is significant no:-)) What is still
strange: the cutoff which is displayed is not affected,
which I cannot believe. So there will be something else
wrong.

>> So there is a fixed 0.10! I would expects both optional
>> values next to each other.
>
>The purpose of getco is to get the cutoff required for a given target
>number of false positives.

Which seems to fail above. At least for what is displayed.

>That would work too (leaving the 3 shifts) but the other is, I think,
>more readable.

I agree. I'll try tomorrow. If someone solves the problem
described above in the meantime that would be great.

pi