Move depth property

[trevoke]

Move depth property

[Trevoke]

Do you suggest that slices and enumerations be limited to the branch
on which you are, or that they include all the variations therein?
Imagine this:
0 1 2 3
2 3 4

slice = object[1..3]
Now.. Does slice mean
1 2 3
2 3

Or does it mean just
1 2 3

Or ... What does it mean?

The same question applies to enumeration. What do you suggest?

On Mon, Dec 5, 2011 at 02:43, Colin Noga
[email protected]
wrote:

The SGF format is move independent, but human logic is not. A move depth property shoudl be available for each node, specifying it’s depth from root. This is analogous to ‘move number’, as it is equivalent to the position if the node from the root (move 0).

Adding bonus properties like slices, or enumerations based on these would be delicious, delicious frosting on the cake of usability.

---

Reply to this email directly or view it on GitHub:
#12

[Tempus]

Slices should act in a ruby-like way, exactly as they do with strings or arrays. In a different issue, I suggested adding a third class to game and tree called branch, for a branch within a game (which I believe is possible, no?). See Issue #11

In that case, a slice of a GameBranch should return only that branch. A slice of a GameTree or SgfTree should return all branches, it seems. Likewise, SgfTree.main[slice] would return a single branch of the main branch.

For the sake of simplicity, we could also only allow slicing for a single branch, avoiding variation trouble. But the above scenario would be superior.

Use cases:
Imagine, for example, a users wanting to comprise an compilation of opening database from the first 50 moves of pro games. He could simply go... SgfTree[0,50] to grab it for each game. Now imagine someone checking if anyone ever played the 2-6 point as an opening move on the second move. This could be done with SgfTree[2], and magically you would have every node in all those games to iterate over, to check for your 2-6. Other uses might be checking for tags, such as the old clan system on KGS used -> in order for games to qualify, you needed to add a specific tag before a specific move. Slices would facilitate this.

[Trevoke]

Okay. Here's another question.

Imagine I have a game like this:

 0 1 2 3 4
   1 2 3 4 5
      2 3 4 5
      2 3
      2 3 4

Clearly, that's five branches.. Right? What would be inside those branches?

 0 1 2 3 4
    1 2 3 4 5
       2 3 4 5
       2 3
       2 3 4

Or would it create this:

0 1 2 3 4
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3
0 1 2 3 4

?

[Trevoke]

Poke @Tempus -- I think I can implement this but I would like some feedback from you on a previous comment on this issue :)

[Trevoke]

poke @Tempus so it doesn't matter that the resulting slices might be completely meaningless fragments of games, right?

[Trevoke]

Depth has been implemented.

Slicing has been at least partially implemented.