[Welcome to Sensei's Library!]

StartingPoints
ReferenceSection
About


Sub-pages (up)
Discussion
Sandbox

 

Axd/CandidateSLPages
Sub-page of Axd

This is a scratch space for candidate SL pages...

Table of contents


Reviewing guidelines?

As far as I know, there is no formal description of how to review a game. Also, the SGF format has only limited support for reviewing.

  • reviewers introduce themselve in the first node(s) (as well as in the reviewer properties); each comment should be preceded by the reviewer's nick/initials, enclosed in brackets.
  • be aware of difference between child/sibling variation styles
  • SGF: hyperlinking references to board position: currently, several ways exist to refer to board positions from within comments: coordinates, markers, variation labels, node names. Often, variations are labelled automatically, referring to them risks breaking the link when variations are reshuffled/added/deleted. Using coordinates avoids this problem, but it is more hard to follow (well, I guess one gets used to coordinates after a while...).

1001 Uses for a Dead Go Stone?

Based on [ext] http://www.msoworld.com/mindzine/news/orient/go/special/gostone.html

  1. key chain
  2. physics experiment: in vacuum, a Go stone will drop as fast as a feather
  3. attach to the next interstellar bound space probe, as a message from Earth to the aliens

phpwiki URLs

(useful) SL phpwiki URLs (such as those that can be used in the user bookmarks): (*) means this is already explained somewhere

  • Page history|phpwiki:?info=_referrer_
  • page info and history | phpwiki:?Info=MessagesToPeopleCurrentlyPresentInTheLibrar?
  • Latest page diff|phpwiki:?diff=_referrer_
  • version 61|phpwiki:?diff=EnglishGoTerms&new=61&old=60
  • diff|phpwiki:?diff=ContinueWhileDozensOfPointsBehind
  • 2004-04-15 | phpwiki:?CoffeeMachine:v513 (*)
  • Introductory|phpwiki:?header=difficulty&term=Introductory
  • Search for pages | phpwiki:?full=%22request%20for%20deletion%22
  • phpwiki:?search=A
  • Download sltxt2png|phpwiki:files/sltxt2png.php.txt
  • Edit page|phpwiki:?edit=HowDiagramsWork
  • RandomPage?|phpwiki:?random=1(*)
  • random joseki page|phpwiki:?random=keywords&term=Joseki
  • random beginner page | phpwiki:?random=difficulty&term=beginner


Go Variants scratchpad

(Not yet sure if this is worth adding to the related pages, so I put it here first)

  • intersections receive a weight. a question could be whether this weight should also be transferred to prisoners taken from those intersections, or maybe a parallel grid should exist for prisoner weight.
  • add-on to the "fog of war" concept in PhantomGo: each side divides the complete goban into arbitrary sectors, each allocated to a team member responsible for it. moves and inter-member communication is time-delayed by the server.
  • a client might restrict the view of the board to a part of it, there would be no way to move or play outside the view set by the client. The view might be determined as the area within N manhattandistance from the last played move.
  • extension of the toroidal board idea: tile an (NxM) goban to produce a toroidal playing space. Then, introduce a "shear" by sliding two adjacent tiles X points along a common edge in one direction. The resulting tiling gets a sheared appearance. Now apply a second shear operation of Y points along the other edge: a XxY sized "gap" will appear and serves as a secondary goban.
% please correct term "sheared" if necessary
  • when playing on-line on mobius/toroidal boards, the board would re-centre every time on the played move, requiring the player to adapt to the shifted board situation all the time: especially difficult in blitz games.
  • a radical variant (using a server) would be to have both players play simultaneous moves instead of in turn; each conflict would be resolved by bidding prisoners, the winner (who invested most prisoners) occupying the conflict intersection, the loser receiving a compensation in the form of prisoners:
    • each player secretly selects a number of prisoners, or
    • each player bets an increasing number of prisoners; then,
    • prisoners are exchanged, or
    • loser receives the difference in prisoners from the winner
    • see also BidGo

ComputerAssistedGo?

(cyberGo, ...)

This page would serve for discussing and collecting tools and concepts to be used during analysis as well as during play and to discuss ethics, future and possibilities of this extension to the human mind (Go playing using assistance software, not to replace human decision making - the borderline is very fuzzy, yes).

Although technically already feasible (and in some extent already in use), I think in the future a separate type of online playing might exist, where consenting players are assisted by software while playing.

My approach might tell more about my lack of Go knowledge (or a naive view of things) rather than introduce new ideas: do I underestimate the possibilities of such software, will it never really be useful? Maybe I will change my mind as I dig deeper into Go, only to find how foolish I was to reflect on this matter? Comments about this are welcome as well.

Some question to debate over:

  • is this (ethically) permitted?
  • What will be impact on the game of Go?
  • Does it make sense to advocate against computer assistance during play?
  • The borderline with true Go-playing software, where the move decision is taken by software, is very thin here; how do we subdivide this domain into "acceptable" tools and "not acceptable" (in this context, as the use of any tool is already unacceptable in the "classic" sense); what tools are available?
  • can advances in technology (processing speed, memory...) make this cyberGo unacceptable (i.e. it should never be acceptable that of two people playing cyberGo, the one with the better machine would have the edge - maybe a weak argument...)

Related pages

Some notes:

  • manual features (Player decides on values)
    • persistent concepts (are not linked to a move, cannot be stored in current SGF versions):
      • persistent concepts are stored in their layers that can be switched on/off
      • symbols can be added and deleted
      • (visual representation of) status of groups; alive-dead-weak-strong groups
      • confirmed territory - points (help counting during the game) - neutral - undecided
      • allow to classify potential playing points with a prio and/or value; drag the label to another classified point to reshuffle priorities; supported by special variant to variations concept aimed at evaluating the value of a point (what if Black plays first/what if White playes first => resulting value)
    • automatic replies
    • manually built game tree to explore variations
      • current move sequence highlighted in other branches, to find recurring patterns (Directed Acyclic Graph, Transposition ?)
      • allows to indicate preferred responses; allow automatic replies based on the currently built game tree;
  • automatic features (mainly counting stuff)
    • automatic ladder detection, life & death of groups? - probably not acceptable
    • present groups with 1-2-N liberties left -> ko threats, atari, double atari threats; Benson's Algorithm
    • strength and liberties of friend/foe contact groups, in relation with own group status
    • influence function - [ext] voronoi?
    • Adjusted Length Analysis
    • QARTS
    • ModularThinking support
    • manually indicating a shaded area (as in Kombiloo) for local evaluations: can be automated by taking the smallest involved area over all subbranches
  • databases, dictionnaries of any kind are not acceptable?
  • window tracking: the cyberGo application monitors and mirrors the current user board (presented in another application window). the idea is to be able to use this app together with any Go client.
  • Speculation

SLWishlist?

  • extend the footnote concept to true HTML bookmarks (URL#bookmark) to provide the possibility to point into a particular spot in a page
  • The way to specify headings seems wrong: ! should be 1st level, !! second, etc...
  • possibility to search in page histories/deltas (as long as this is still available), not only in current pages

DesigningAGoClient?

(features that should be present in a Go client software)

  • variations, SGF merge of different reviews of the same game
  • ko indication
  • playback features
    • highlight a square (as in Kombilo), show move history only inside/near that square
  • options
    • possibility to switch between SGF sibling style and children style


This is a copy of the living page "Axd/CandidateSLPages" at Sensei's Library.
(OC) 2004 the Authors, published under the OpenContent License V1.0.