DiggEmployeesVsTheComputer (r1.1 vs. r1.9)

Webs: Faemalia -:- Greatprawn -:- Playground -:- Technical -:- Tweak
Technical Web Sections: Register -:- Users -:- Changes -:- Index -:- Search -:- Statistics

 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.9 - 15 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
TOC: No TOC in "Technical.DiggEmployeesVsTheComputer"
Line: 173 to 173

5 | | | | | |\B/| | | | | 5 <--DecaSjeng trades up knights

===+---+===+---+===+---+===+---+===+---+

4 | | |(q)| | | | | | | | 4 <--and brings out its queen, threatening
Changed:
<
<

---+===+---+===+---+===+---+===+---+===+ this pawn, which when we move up, it

>
>

---+===+---+===+---+===+---+===+---+===+ the c2 pawn, which when we move up, it


3 | | |\o/|\N/|\o/| | | | | | 3 predictably attacks our knight, which is

===+---+===+---+===+---+===+---+===+---+ shakily-protected by the bishop on f5

2 | |\o/| |\o/| |\o/|\o/|\o/|\o/| | 2
Line: 183 to 183

a b c d e f g h i j some other piece?
Changed:
<
<
I figure a good sequence might be Qa10, , Qxb9, threatening his knight on e6. But then... where would it put its knight? Or... might it have something more sinister planned for us with its knight and queen in combo?
>
>
I figure a good sequence might be Qa10, Ke10, Qxb9, threatening its knight on e6. But then... where would it put its knight? Or... might it have something more sinister planned for us with its knight and queen in combo? Ah, yes. DecaSjeng will play Nc5 on the next move. That'd be ugly for us. We need to play then perhaps Ke2, but that feels a little scary. In any case, DecaSjeng can protect its pawns down there around a10. We need another plan of attack. It might be time to pull out our bishop at g1 while we're still up a move.


 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.8 - 15 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
TOC: No TOC in "Technical.DiggEmployeesVsTheComputer"
Line: 154 to 154

===+---+===+---+===+---+===+---+===+---+ into play at a1, apparently not

a b c d e f g h i j such a bad plan of action
Added:
>
>

Ron and I have a bit of a go at it...

     a   b   c   d   e   f   g   h   i   j
   +===+---+===+---+===+---+===+---+===+---+
10 |   |   |   |(b)|   |(k)|(b)|   |   |(r)| 10 <--this rook here is kind of annoying
   +---+===+---+===+---+===+---+===+---+===+
 9 |   |(.)|(.)|   |(.)|(.)|(.)|(.)|(.)|   |  9
   +===+---+===+---+===+---+===+---+===+---+
 8 |   |   |   |(.)|   |   |   |   |   |   |  8
   +---+===+---+===+---+===+---+===+---+===+
 7 |   |   |   |   |   |   |   |   |   |   |  7
   +===+---+===+---+===+---+===+---+===+---+
 6 |   |   |   |   |(n)|   |   |   |   |   |  6
   +---+===+---+===+---+===+---+===+---+===+
 5 |   |   |   |   |   |\B/|   |   |   |   |  5 <--DecaSjeng trades up knights
   +===+---+===+---+===+---+===+---+===+---+
 4 |   |   |(q)|   |   |   |   |   |   |   |  4 <--and brings out its queen, threatening
   +---+===+---+===+---+===+---+===+---+===+       this pawn, which when we move up, it
 3 |   |   |\o/|\N/|\o/|   |   |   |   |   |  3    predictably attacks our knight, which is
   +===+---+===+---+===+---+===+---+===+---+       shakily-protected by the bishop on f5
 2 |   |\o/|   |\o/|   |\o/|\o/|\o/|\o/|   |  2
   +---+===+---+===+---+===+---+===+---+===+
 1 |\Q/|   |   |   |   |\K/|\B/|   |\R/|   |  1 <--boy wouldn't it be nice to take our
   +===+---+===+---+===+---+===+---+===+---+       queen and get her up to a10, backed by
     a   b   c   d   e   f   g   h   i   j         some other piece?

I figure a good sequence might be Qa10, , Qxb9, threatening his knight on e6. But then... where would it put its knight? Or... might it have something more sinister planned for us with its knight and queen in combo?



 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.7 - 14 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess

Wednesday Morning: Humans Cautiously Optimistic

Changed:
<
<
The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).
>
>
The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine, AKA DecaSjeng. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).

The game begins with Mike and I (timeless) doing some simple opening moves against the computer. We try the experimental immediate rooks out on the A/J files. The computer plays its very-safe pushing its knights toward the center.

Line: 12 to 12

Wednesday mid-morning: Skynet Mocks us Mildly

Changed:
<
<
It seems already Skynet's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.
>
>
It seems already DecaSjeng's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.

    Player: j1j5
Line: 24 to 24

---+===+---+===+---+===+---+===+---+===+ its queen into play

9 | |(.)|(b)|(.)|(.)|(.)|(.)|(.)|(.)| | 9 <--general idea is to try to get

===+---+===+---+===+---+===+---+===+---+ our pieces in over here to

Changed:
<
<
8 | | |(.)|(n)| | | | | | | 8 put the hurt on skynet
>
>
8 | | |(.)|(n)| | | | | | | 8 put the hurt on it

---+===+---+===+---+===+---+===+---+===+

7 | | | | |(n)| | | | | | 7

===+---+===+---+===+---+===+---+===+---+

Line: 47 to 47

Wednesday Afternoon: Skynet Yawns

Changed:
<
<
A few moves later, the computer managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.
>
>
A few moves later, DecaSjeng managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.

    Player: d1b3
Line: 78 to 78

a b c d e f g h i j
Changed:
<
<
The computer's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.
>
>
DecaSjeng's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.

Wednesday Evening: Skynet Puts the Hurt On

Changed:
<
<
Now Ron and I have a bit of a go at it. We attack his rook with our knight, offering a trade for him to bring his bishop at h7 down to b1. Rather, the computer takes advantage of its one move ahead to bring its other rook to put pressure onto i2. It looks like our response should be to put our rook onto a1, both saving it from the h7 bishop, and pressuring his a7 bishop, which should give us a chance to save that i2 pawn as well.
>
>
Now Ron and I have a bit of a go at it. We attack its rook with our knight, offering a trade for it to bring its bishop at h7 down to b1. Rather, DecaSjeng takes advantage of its one move ahead to bring its other rook to put pressure onto i2. It looks like our response should be to put our rook onto a1, both saving it from the h7 bishop, and pressuring his a7 bishop, which should give us a chance to save that i2 pawn as well.

    Player: e3g1
Line: 115 to 115

To Be Continued?

Changed:
<
<
Honestly it looks pretty hopeless at this point. We've made enough poorly-formed moves that Decachess Sjeng is likely to come down and stomp us nastily into the ground. Perhaps some rated master Chess player will give us some powerful opening moves to help us put the hurt back on Skynet after this (likely-to-become) embarassing defeat.
>
>
Honestly it looks pretty hopeless at this point. We've made enough poorly-formed moves that Decachess Sjeng is likely to come down and stomp us nastily into the ground. Perhaps some rated master Chess player will give us some powerful opening moves to help us put the hurt back on DecaSjeng after this (likely-to-become) embarassing defeat.

Skynet Crashes! Forfeits the game to the Humans!

Changed:
<
<
I was messing around behind my desk, and saw the plug of the computer that's been humiliating us so. I gave the plug a gentle tug, and the next thing I knew, Skynet had forfeit the game!!! That'll teach the computer to play Decachess against brilliant minds such as ours.
>
>
I was messing around behind my desk, and saw the plug of the computer that's been humiliating us so. I gave the plug a gentle tug, and the next thing I knew, DecaSjeng had forfeit the game!!! That'll teach the computer to play Decachess against brilliant minds such as ours.

Okay. Actually, I need to take the Decachessboard to Super Happy Dev House to work out any further bugs with Sjeng10x10. I'll use it to play whomever wants to come and try to salvage this embarassment on behalf of the humans. We will probably resign this game and start up a new one next week. The experimental "bring out both rooks" didn't seem to do us too well.

Added:
>
>

Update: 13 September 2006. I decided the game was no good. I just played a few desperation moves, but after a while, it managed to mate me. We are going to start another game up.

Next Wednesday Evening

I've started a new game against DecaSjeng. I took a few safe moves, and here's the state of the game thus far:

     a   b   c   d   e   f   g   h   i   j
   +===+---+===+---+===+---+===+---+===+---+
10 |   |   |   |(b)|(q)|(k)|(b)|   |   |(r)| 10 <--curiously DecaSjeng played both
   +---+===+---+===+---+===+---+===+---+===+       rooks out, which is part of what lost
 9 |   |(.)|(.)|   |(.)|(.)|(.)|(.)|(.)|   |  9    us our last game - it'll be fun to
   +===+---+===+---+===+---+===+---+===+---+       see how this plays out
 8 |   |   |   |(.)|   |   |   |   |   |   |  8
   +---+===+---+===+---+===+---+===+---+===+
 7 |   |   |   |   |\N/|   |(n)|   |   |   |  7 <--DecaSjeng threatens our knight,
   +===+---+===+---+===+---+===+---+===+---+       we'll have to respond to this now,
 6 |   |   |   |   |(n)|   |   |   |   |   |  6    also it has that annoying one-knight-
   +---+===+---+===+---+===+---+===+---+===+       protects-the-other setup going
 5 |   |   |   |   |   |   |   |   |   |   |  5
   +===+---+===+---+===+---+===+---+===+---+
 4 |   |   |   |   |   |   |\B/|   |   |   |  4
   +---+===+---+===+---+===+---+===+---+===+
 3 |   |   |   |\N/|\o/|   |   |   |   |   |  3
   +===+---+===+---+===+---+===+---+===+---+
 2 |   |\o/|\o/|\o/|   |\o/|\o/|\o/|\o/|   |  2
   +---+===+---+===+---+===+---+===+---+===+       this time DecaSjeng opted to
 1 |\Q/|   |   |   |   |\K/|\B/|   |\R/|   |  1 <--trade up rooks to let my queen
   +===+---+===+---+===+---+===+---+===+---+       into play at a1, apparently not
     a   b   c   d   e   f   g   h   i   j         such a bad plan of action


 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.6 - 08 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
TOC: No TOC in "Technical.DiggEmployeesVsTheComputer"
Line: 116 to 116

To Be Continued?

Honestly it looks pretty hopeless at this point. We've made enough poorly-formed moves that Decachess Sjeng is likely to come down and stomp us nastily into the ground. Perhaps some rated master Chess player will give us some powerful opening moves to help us put the hurt back on Skynet after this (likely-to-become) embarassing defeat.

Added:
>
>

Skynet Crashes! Forfeits the game to the Humans!

I was messing around behind my desk, and saw the plug of the computer that's been humiliating us so. I gave the plug a gentle tug, and the next thing I knew, Skynet had forfeit the game!!! That'll teach the computer to play Decachess against brilliant minds such as ours.

Okay. Actually, I need to take the Decachessboard to Super Happy Dev House to work out any further bugs with Sjeng10x10. I'll use it to play whomever wants to come and try to salvage this embarassment on behalf of the humans. We will probably resign this game and start up a new one next week. The experimental "bring out both rooks" didn't seem to do us too well.



 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.5 - 07 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
TOC: No TOC in "Technical.DiggEmployeesVsTheComputer"
Changed:
<
<

Thursday Morning: Humans Cautiously Optimistic

>
>

Wednesday Morning: Humans Cautiously Optimistic


The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).

Line: 10 to 10

After some moves, the computer has offered up a trade of its rook with ours in order to get its queen in play. If we move our rook back, he has his rook in play, and we've lost a move. If we protect the rook with our knight, and he trades, then our knight is all the way in the corner. If we move our knight in front of the rook, then our knight and rook are both pinned for several moves.

Changed:
<
<

Thursday mid-morning: Skynet Mocks us Mildly

>
>

Wednesday mid-morning: Skynet Mocks us Mildly


It seems already Skynet's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.

Line: 45 to 45

We finally decided against taking the trade of rooks, and moved our rook back into place. It used that opportunity to pull out its rook and pull out its white bishop, pushing our other rook out of the J file.

Changed:
<
<

Thursday Afternoon: Skynet Yawns

>
>

Wednesday Afternoon: Skynet Yawns


A few moves later, the computer managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.

Line: 80 to 80

The computer's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.

Changed:
<
<

Thursday Evening: Skynet Puts the Hurt On

>
>

Wednesday Evening: Skynet Puts the Hurt On


Now Ron and I have a bit of a go at it. We attack his rook with our knight, offering a trade for him to bring his bishop at h7 down to b1. Rather, the computer takes advantage of its one move ahead to bring its other rook to put pressure onto i2. It looks like our response should be to put our rook onto a1, both saving it from the h7 bishop, and pressuring his a7 bishop, which should give us a chance to save that i2 pawn as well.


 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.4 - 07 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
Added:
>
>

Thursday Morning: Humans Cautiously Optimistic


The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).

The game begins with Mike and I (timeless) doing some simple opening moves against the computer. We try the experimental immediate rooks out on the A/J files. The computer plays its very-safe pushing its knights toward the center.

After some moves, the computer has offered up a trade of its rook with ours in order to get its queen in play. If we move our rook back, he has his rook in play, and we've lost a move. If we protect the rook with our knight, and he trades, then our knight is all the way in the corner. If we move our knight in front of the rook, then our knight and rook are both pinned for several moves.

Changed:
<
<
It seems already skynet's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.
>
>

Thursday mid-morning: Skynet Mocks us Mildly

It seems already Skynet's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.


    Player: j1j5
Line: 39 to 45

We finally decided against taking the trade of rooks, and moved our rook back into place. It used that opportunity to pull out its rook and pull out its white bishop, pushing our other rook out of the J file.

Added:
>
>

Thursday Afternoon: Skynet Yawns


A few moves later, the computer managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.



Line: 72 to 80

The computer's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.

Added:
>
>

Thursday Evening: Skynet Puts the Hurt On


Now Ron and I have a bit of a go at it. We attack his rook with our knight, offering a trade for him to bring his bishop at h7 down to b1. Rather, the computer takes advantage of its one move ahead to bring its other rook to put pressure onto i2. It looks like our response should be to put our rook onto a1, both saving it from the h7 bishop, and pressuring his a7 bishop, which should give us a chance to save that i2 pawn as well.



Line: 102 to 112

===+---+===+---+===+---+===+---+===+---+

a b c d e f g h i j
Added:
>
>

To Be Continued?

Honestly it looks pretty hopeless at this point. We've made enough poorly-formed moves that Decachess Sjeng is likely to come down and stomp us nastily into the ground. Perhaps some rated master Chess player will give us some powerful opening moves to help us put the hurt back on Skynet after this (likely-to-become) embarassing defeat.



 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.3 - 06 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).
Line: 37 to 37

a b c d e f g h i j
Changed:
<
<
We finally decided against taking the trade of rooks, and moved our rook back into place. It used that opportunity to pull out its rook and pull out his white bishop, pushing our other rook out of the J file.
>
>
We finally decided against taking the trade of rooks, and moved our rook back into place. It used that opportunity to pull out its rook and pull out its white bishop, pushing our other rook out of the J file.

A few moves later, the computer managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.

Line: 71 to 71

The computer's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.

Added:
>
>

Now Ron and I have a bit of a go at it. We attack his rook with our knight, offering a trade for him to bring his bishop at h7 down to b1. Rather, the computer takes advantage of its one move ahead to bring its other rook to put pressure onto i2. It looks like our response should be to put our rook onto a1, both saving it from the h7 bishop, and pressuring his a7 bishop, which should give us a chance to save that i2 pawn as well.

    Player: e3g1
Sjeng10x10: a6i6

     a   b   c   d   e   f   g   h   i   j
   +===+---+===+---+===+---+===+---+===+---+
10 |   |   |   |   |(q)|(k)|   |   |   |(r)| 10
   +---+===+---+===+---+===+---+===+---+===+
 9 |   |(.)|   |(.)|(.)|(.)|(.)|   |(.)|   |  9
   +===+---+===+---+===+---+===+---+===+---+
 8 |   |   |(.)|   |   |   |   |(.)|   |   |  8
   +---+===+---+===+---+===+---+===+---+===+
 7 |(b)|(n)|   |   |   |   |   |(b)|   |   |  7
   +===+---+===+---+===+---+===+---+===+---+
 6 |   |   |   |   |   |   |   |   |(r)|   |  6
   +---+===+---+===+---+===+---+===+---+===+
 5 |   |\R/|   |   |   |   |   |   |   |   |  5
   +===+---+===+---+===+---+===+---+===+---+
 4 |   |\N/|   |\o/|   |   |   |   |   |   |  4
   +---+===+---+===+---+===+---+===+---+===+
 3 |   |\B/|\o/|   |   |\o/|   |   |   |   |  3
   +===+---+===+---+===+---+===+---+===+---+
 2 |   |\o/|   |   |\o/|   |\o/|\o/|\o/|   |  2
   +---+===+---+===+---+===+---+===+---+===+
 1 |   |\R/|   |   |   |\K/|\Q/|\N/|   |   |  1
   +===+---+===+---+===+---+===+---+===+---+
     a   b   c   d   e   f   g   h   i   j


 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.2 - 06 Sep 2006 - PhiloVivero)

META TOPICPARENT HundredSquareChess
The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).
Changed:
<
<
The game begins with Mike and I (timeless) doing some simple opening moves against the computer. Now the computer has offered up a trade of its rook with mine in order to get his queen in play. I suspect we'll take the trade. If we move our rook back, he has his rook in play, and we've lost a move. If we protect the rook with our knight, and he trades, then our knight is all the way in the corner. If we move our knight in front of the rook, then our knight and rook are both pinned for several moves.
>
>
The game begins with Mike and I (timeless) doing some simple opening moves against the computer. We try the experimental immediate rooks out on the A/J files. The computer plays its very-safe pushing its knights toward the center.

Changed:
<
<
It seems already skynet's got a bit of an edge on us. Once we take the trade, we'll have a weak position down there in the A1 quadrant.
>
>
After some moves, the computer has offered up a trade of its rook with ours in order to get its queen in play. If we move our rook back, he has his rook in play, and we've lost a move. If we protect the rook with our knight, and he trades, then our knight is all the way in the corner. If we move our knight in front of the rook, then our knight and rook are both pinned for several moves.

It seems already skynet's got a bit of an edge on us. If we take the trade, we'll have a weak position down there in the a1 quadrant.


    Player: j1j5
Line: 34 to 36

===+---+===+---+===+---+===+---+===+---+

a b c d e f g h i j
Added:
>
>

We finally decided against taking the trade of rooks, and moved our rook back into place. It used that opportunity to pull out its rook and pull out his white bishop, pushing our other rook out of the J file.

A few moves later, the computer managed to trick us into letting it fork our queen/bishop, which we really didn't want. We tried our best to forestall it, but some clever moves with its knights and rook kept us from foiling its plan.

    Player: d1b3
Sjeng10x10: i10j10

     a   b   c   d   e   f   g   h   i   j
   +===+---+===+---+===+---+===+---+===+---+
10 |   |   |   |   |(q)|(k)|   |   |   |(r)| 10 <--we moved our bishop to b3
   +---+===+---+===+---+===+---+===+---+===+       then he responded with his
 9 |   |(.)|(b)|(.)|(.)|(.)|(.)|   |(.)|   |  9    rook @j10, which was poor
   +===+---+===+---+===+---+===+---+===+---+       planning on our part - j1
 8 |   |   |(.)|   |   |   |   |(.)|   |   |  8    looks pretty attractive
   +---+===+---+===+---+===+---+===+---+===+       now. we were hoping to castle
 7 |   |(n)|   |   |   |   |   |(b)|   |   |  7    queenside on this move, but
   +===+---+===+---+===+---+===+---+===+---+       have already moved the queen's
 6 |(r)|   |   |   |   |   |   |   |   |   |  6    rook
   +---+===+---+===+---+===+---+===+---+===+
 5 |   |\R/|   |   |   |   |   |   |   |   |  5
   +===+---+===+---+===+---+===+---+===+---+
 4 |   |   |   |   |   |   |   |   |   |   |  4
   +---+===+---+===+---+===+---+===+---+===+
 3 |   |\B/|\o/|\N/|\Q/|\o/|   |   |   |   |  3
   +===+---+===+---+===+---+===+---+===+---+
 2 |   |\o/|   |\o/|\o/|   |\o/|\o/|\o/|   |  2
   +---+===+---+===+---+===+---+===+---+===+
 1 |   |\R/|   |   |   |\K/|   |\N/|   |   |  1
   +===+---+===+---+===+---+===+---+===+---+
     a   b   c   d   e   f   g   h   i   j

The computer's got a strong position, and we have a weak one. We can't move our rook up to b6, nor our king to g1, both have a counter of his bishop to a7. Having j2 covered both by its bishop and rook annoys us. It looks like we need to shore up our defenses, but given our positional weakness and the knight-for-bishop trade we were forced to take, it isn't looking good. We will ponder how to fix our problems on the a1/j1 quadrants, hopefully at the same time bringing the queen out of that somewhat dangerous position she's in.



 <<O>>  Difference Topic DiggEmployeesVsTheComputer (r1.1 - 06 Sep 2006 - PhiloVivero)
Line: 1 to 1
Added:
>
>
META TOPICPARENT HundredSquareChess
The Digg Employees are going to gang up on my newly hacked up Sjeng Decachess playing engine. I've set the search depth to 7, so it seems likely it'll destroy us, given Forterra barely beat out Gnuchess on depth 6 (on an 8x8 board).

The game begins with Mike and I (timeless) doing some simple opening moves against the computer. Now the computer has offered up a trade of its rook with mine in order to get his queen in play. I suspect we'll take the trade. If we move our rook back, he has his rook in play, and we've lost a move. If we protect the rook with our knight, and he trades, then our knight is all the way in the corner. If we move our knight in front of the rook, then our knight and rook are both pinned for several moves.

It seems already skynet's got a bit of an edge on us. Once we take the trade, we'll have a weak position down there in the A1 quadrant.

    Player: j1j5
Sjeng10x10: b10a10

     a   b   c   d   e   f   g   h   i   j
   +===+---+===+---+===+---+===+---+===+---+
10 |(r)|   |   |   |(q)|(k)|(b)|   |(r)|   | 10 <--offers rook trade@a10 to get
   +---+===+---+===+---+===+---+===+---+===+       its queen into play
 9 |   |(.)|(b)|(.)|(.)|(.)|(.)|(.)|(.)|   |  9 <--general idea is to try to get
   +===+---+===+---+===+---+===+---+===+---+       our pieces in over here to
 8 |   |   |(.)|(n)|   |   |   |   |   |   |  8    put the hurt on skynet
   +---+===+---+===+---+===+---+===+---+===+
 7 |   |   |   |   |(n)|   |   |   |   |   |  7
   +===+---+===+---+===+---+===+---+===+---+
 6 |   |   |   |   |   |   |   |   |   |   |  6
   +---+===+---+===+---+===+---+===+---+===+
 5 |   |   |   |   |   |   |   |   |   |\R/|  5 <--keep its annoying knight off
   +===+---+===+---+===+---+===+---+===+---+       f5 to fork our queen/bishop
 4 |   |   |   |   |   |   |   |   |   |   |  4
   +---+===+---+===+---+===+---+===+---+===+
 3 |   |   |   |   |\B/|\o/|\Q/|   |   |   |  3
   +===+---+===+---+===+---+===+---+===+---+
 2 |   |\o/|\o/|\o/|\o/|   |\o/|\o/|\o/|   |  2
   +---+===+---+===+---+===+---+===+---+===+
 1 |\R/|   |\N/|\B/|   |\K/|   |\N/|   |   |  1
   +===+---+===+---+===+---+===+---+===+---+
     a   b   c   d   e   f   g   h   i   j

View -:- Diffs | r1.9 | > | r1.8 | > | r1.7 -:- More

Revision r1.1 - 06 Sep 2006 - 20:02 - PhiloVivero
Revision r1.9 - 15 Sep 2006 - 08:13 - PhiloVivero
Copyright © 2002 by the Author of the article. All material on this collaboration tool is the property of the contributing authors.