Re: [Bug-gnubg] include 'MET used' in rollout results (export) ?

[Jim Segrave]

On Wed 20 Aug 2003 (01:11 +0200), Robert-Jan Veldhuizen wrote:
> At 23:32 8/14/2003 +0200, you wrote:
> >On Thu, 14 Aug 2003 06:43:39 +0000, Joern Thyssen wrote:
> >>
> >> This is somewhat difficult due to the flexibility gnubg allows. If you
> >> could only choose among a fixed set of METs then we just need to store
> >> the number of the one used, but gnubg allows you to choose an
> >> arbitrary MET. So in order to store which one used, we need to score the
> >> entire MET! Each MET is 1-10kb, so adding it to all moves will require
> >> either lots of work or lots of memory.
> >
> >What about hashing the known ones and saving a checksum only?
> 
> Something like that seems a good idea to me. Especially when comparing 
> rollout results with others, knowing which MET was used is sometimes 
> essential and I really miss that feature right now with GNUBG.

Why not do something like:
Generate a known hash/checksum/md5 sum or whatever for the distributed
METs. Keep a table of MET name and hashes

Store the hash of the MET as part of the analysis. When exporting, if
it matches a known MET, identify it, otherwise put something like
'Custom MET'. Frankly, since it's not a security issue, a 32 bit hash
is sufficient and that's not too costly on a per-move basis.


-- 
Jim Segrave           address@hidden