- summary: 'u_del' selector not intuitive; rounding issues --> delivery selectors unintuitive
"Thomas Johnson" <tjohnNO11111SPAM@aol.com> wrote
in message
news:brnl2k$mni$1@home.itg.ti.com...
>
> "Markus Armbruster" <armbru@pond.sub.org> wrote in
message
> news:86he00vcow.fsf@snapper.pond.sub.org...
> > "Thomas Johnson" <tjohnNO11111SPAM@aol.com>
writes:
> >
> > > I am using delivery to manage uws. I tried to list
the sectors
> > > with a specific cutoff and the command failed. I
tried:
> > >
> > > Command: cut * ?u_del=296
> > > Tue Dec 16 20:00:58 2003
> > > *: No sector(s)
> > > command failed
> > >
> > > Then I used the '<' and '>' signs and it worked:
> > >
> > > Command: cut * ?u_del>290&u_del<300
> > > Tue Dec 16 20:00:40 2003
> > > DELIVERY CUTOFF LEVELS
> > > sect cmufsgpidbolhr civ mil uw food sh gun
pet irn dst bar oil
lcm
> hcm
> > > rad
> > > x,y k ..j........... 0 0 296 0 0 0 0 0
0 0 0 0
> 0
> > > 0
> > > .
> > > .
> > > .
> > > 39 sectors
> > >
> > > Is this a bug?
> >
> > Works as misdesigned.
> >
> > As you know, cutoff is rounded down to a multiple of
eight. Direction
> > is encoded as 1..6 (see include/path.h). The game
stores the sum of
> > the two, and the u_del selector works with that
sum. Try ?udel=298.
>
> Well, then the info page 'Selector' needs to state this.
>
> Tom
>
>
Actually, after pondering this, I do feel this should
be handled as a bug with the 'u_del' selector. These
things must be as intuitive as possible. Use of the
'u_del' selector must work on the implied and
displayed cutoff level. Therefore, the 'u_del'
selector should return sectors with the value
rounded down to a multiple of 8. This then
matches the return value from the 'delivery'
command and the result of the 'cutoff' command.
Tom
(Ski)