[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] The match and game data structure
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] The match and game data structure |
Date: |
Mon, 3 Jul 2006 08:48:35 +0200 |
User-agent: |
Mutt/1.4.2.1i |
On Sun 02 Jul 2006 (22:01 +0200), Philippe Michel wrote:
> On Fri, 30 Jun 2006, Jim Segrave wrote:
>
> >By nature, a match or session should form a tree. The match/session is
> >the root, with leaves being game trees. A game is a tree with leaves
> >left to right representing moves/cube actions.
>
> Is the leaf node really a move/cube action, or rather a position ? If the
> latter, the same tree can just as well represent book/chapters/positions
> but the leaves would need enough context to be unrelated to each other.
>
> It would be nice if an entire book (positions, analysis, comments) could
> be packaged as a sgf file and browsed within gnubg.
You could take the leaves of games as being positions and hang
individual analysis of move choices off those leaves. Each position
where the cube is in play would have a double leaf and
leaves for each of the possible chequer moves. Analysis would be
packed into these leaves. This makes storing hint data particularly
easy. It also would give the structure to make it easy to save the
evaluations used by gnubg when it is playing one of the positions
--
Jim Segrave address@hidden