[Computer-go] Are 4 'easy to avoid errors' common to all MC programs?

[Jonathan Chetwynd]

Are 4 'easy to avoid errors' common to all MC programs?

peepo.com now offers a browser-based front-end to Fuego, currently  
19x19 only.
and whilst debugging a number of trivial errors commonly  played by  
Fuego became apparent:

1	when behind (even slightly), Fuego appears to collapse and play  
rubbish, in my experience this is most easily perceived in the late/ 
middle game.

2	Fuego plays out ladders, which it cannot capture.

3	snapback, but see 1

4	preserve 2 eyes, again see 1

Are these common to all MC type Go programs?

There is a small set of game data building on  the site, if anyone is  
interested to study, let me know...

regards

Jonathan Chetwynd
http://www.peepo.com