Re: [computer-go] Storing positions

[Don Dailey <drd@xxxxxxx>]

I store games in PGN format just like chess.  It's way easier to read
and easier to parse.

But this doesn't address storing positions.  Of course the standard is
SGF which is really ugly and hard to read.  It's probably at least as
bad as XML or even worse, because a move is represented in a different
format that you see in books.

You will have to have an SGF parser eventually if you want to load
games from external sources, that ugly format is the standard I'm
afraid and the computer GO community is very resistant and
conservative about any kind of change.

I think that what happens is the first person to come up with some
idea, if it fills a need, becomes the standard.  I'm not sure if there
is actually a standard way to store ONLY positions.  The experts here
will know better than I do.  Perhaps SGF does this too in it's ugly
way?

- Don


[Event "Autotest Sequence"]
[Site "Local Site"]
[Date "2005.06.02"]
[Round "1"]
[Black "V1"]
[BlackTime "00:27:21"]
[White "V2"]
[WhiteTime "00:27:12"]
[Boardsize "19x19"]
[Komi "6.5"]
[Rules "Chinese"]
[Final "206-155"]
[Result "1-0"]

1. d5 p18 2. d10 f8 3. l15 e5 4. e6 e11 5. j16 d6 
6. d7 f6 7. c6 d4 8. e4 f5 9. f7 g7 10. e7 f4 
11. e3 g8 12. f3 g6 13. g3 h3 14. d3 c4 15. c3 g4 
16. b4 h4 17. c5 q15 18. r10 h2 19. d12 d11 20. n3 p14 
21. c11 p4 22. r15 c12 23. e12 e10 24. q16 e9 25. c13 f12 
26. b12 o16 27. p15 o15 28. q14 q11 29. p13 o14 30. q13 o13 
31. o12 n12 32. n11 o11 33. p12 n13 34. p11 m11 35. o10 n17 
36. m10 d9 37. c9 c8 38. l11 c7 39. m12 c10 40. b14 b9 
41. l17 q17 42. r17 r18 43. p17 p16 44. q18 m13 45. l13 o17 
46. q17 m18 47. l14 q15 48. l18 o18 49. p15 m16 50. l16 q15 
51. p19 s17 52. p15 m19 53. q19 q15 54. r16 o19 55. r14 m15 
56. f13 g13 57. m14 n15 58. g12 f11 59. p3 q3 60. q4 f14 
61. e13 g14 62. e14 e15 63. d15 r4 64. q5 o3 65. r3 p2 
66. k12 p5 67. q6 p6 68. d14 q7 69. h12 d16 70. e16 e17 
71. f15 r6 72. j12 r5 73. f17 b6 74. f18 g2 75. b2 q10 
76. q9 p9 77. p10 r9 78. l19 q8 79. e18 n9 80. o9 o8 
81. m9 n8 82. m8 m7 83. r12 r11 84. s11 s10 85. l7 f2 
86. m6 n7 87. l8 l6 88. k6 l5 89. k5 l4 90. k7 s12 
91. k4 l3 92. k3 l2 93. s13 t11 94. k2 b5 95. a4 b7 
96. c4 t13 97. n10 e2 98. d2 d18 99. d17 d1 100. c1 l1 
101. t14 b11 102. t12 c12 103. s11 b17 104. c11 s12 105. c16 t13 
106. e1 c12 107. t12 c18 108. s11 b16 109. b15 s12 110. b18 t13 
111. c11 n18 112. b19 c12 113. t12 a13 114. s11 a14 115. a15 s12 
116. c11 t13 117. d6 c12 118. t12 a12 119. s11 b13 120. t10 t9 
121. c15 t11 122. s12 g11 123. h11 h10 124. j10 j9 125. k1 k10 
126. t10 j11 127. n2 t11 128. m5 m4 129. n4 n5 130. t10 n6 
131. j7 t11 132. k9 j8 133. t10 j10 134. h7 h8 135. a5 t11 
136. r19 l10 137. a6 a7 138. t10 h6 139. d1 t11 140. k8 f1 
141. t10 k11 142. j5 t11 143. p15 t10 144. j1 q15 145. h5 h1 
146. p15 q12 147. q15 d19 148. a18 d8 149. e8 n14 150. a17 g5 
151. a16 j4 152. j2 j6 153. j3 q1 154. s18 s2 155. r2 t7 
156. s4 t1 157. c17 r1 158. s3 t6 159. q2 s5 160. o2 m5 
161. o1 p3 162. p1 h13 163. k13 t2 164. s1 r1 165. q1 t3 
166. s1 t5 167. t4 t2 168. s2 o4 169. m17 m1 170. m2 m3 
171. n1 l9 172. k16 h16 173. j14 j17 174. j15 g16 175. b3 f16 
176. g18 h18 177. e17 k18 178. e15 s15 179. m11 g10 180. l12 o5 
181. t3 k19 182. t1 f10 183. c19 a9 184. e19 b8 185. s14 a11 
186. t15 h17 187. s16 r8 188. t17 t8 189. j18 j19 190. d18 o6 
191. j13 q4 192. t19 g9 193. h14 s8 194. g15 s7 195. a1 q5 
196. g13 k17 197. k15 p8 198. h15 b10 199. f14 h19 200. b17 p7 
201. a2 g19 202. f19 g17 203. j18 g16 204. f16 h17 205. h16 j17 
206. g17 h19 207. k17 j19 208. h18 k19 209. g19 h17 210. j17 pass 
211. k18 j19 212. k19 pass 213. h19 pass 214. pass 
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/