It's a correctly Axelised take (so I took) but Isight wrongly finds an
easy take.
The other methods [...] seem to understand the position much better.
So I don't like pure Axelisation here, despite the answer being
correct from a binary standpoint.
The solution? With so much play left in the position, there is no
need to penalise for crossovers and gaps here.
Alternatively, perhaps use one of the above two methods for this type
of long-distance race (sorry, Axel)?
"peps...@gmail.com" <peps...@gmail.com> writes:
It's a correctly Axelised take (so I took) but Isight wrongly finds anSee below ...
easy take.
The other methods [...] seem to understand the position much better.
Paul, please. A method does not understand a position.
So I don't like pure Axelisation here, despite the answer being(From above) It seems you are being here even more picky than usual
correct from a binary standpoint.
(-;
Now not even a correct solution is sufficient for you, because it does
not pinpoint the position in the doubling window perfectly ...
The solution? With so much play left in the position, there is noI get your point, but then you need to define "so much play left". You
need to penalise for crossovers and gaps here.
know that I do not like this kind of hand-waving, but rather prefer to
stay algorithmic.
Alternatively, perhaps use one of the above two methods for this typeThe last page of my article mentions an extension of my method for long
of long-distance race (sorry, Axel)?
races like this (which are much rarer than most people think, see figure
14). With it, you will get
74 - 96/5 + 2*(107 - 96) = 76.8 < 78
compared to my standard method's result of
80 - 96/3 + 2*(107 - 96) = 70 < 76
Does this make you happier?
Best regards
Axel
So maybe my previous posting could have been framed differently.
Rather than a framing of [This is a problem with Isight] which may be
unfair and may have annoyed you, the framing probably should have been "Here's a way in which a strong player might (and probably would [if
they use Isight at all]) use Isight as a base but adjust for improved results." So, it's just a framing issue. Sorry, if my post annoyed
you.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 117:40:27 |
Calls: | 6,854 |
Files: | 12,355 |
Messages: | 5,416,827 |