Before you spend a fair amount of time on this, make sure the output you'll be creating will be as useful as you hope. Review the errors from a long session and add the gnuBG IDs to a file. The first thing that'll be different from a Python script is that you'll discard all obvious goofs.
Then enter the IDs into the bot one at a time and you'll see a few problems. Look at all four types of doubling errors and you'll see what I mean. Also, if you're going to record your opponent's errors, are you happy with how things look? And how will you handle positions that might benefit from a rollout? Will you need to save that information or is your machine so fast you'll just redo it? Finally, will you record your thoughts about the positions? There's a lot to think about. My approach has been to use saved positions but it's currently too time-consuming to recommend. On Sat, Dec 31, 2022 at 9:01 AM <bug-gnubg-requ...@gnu.org> wrote: > Send Bug-gnubg mailing list submissions to > bug-gnubg@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/bug-gnubg > or, via email, send a message with subject or body 'help' to > bug-gnubg-requ...@gnu.org > > You can reach the person managing the list at > bug-gnubg-ow...@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Bug-gnubg digest..." > > > Today's Topics: > > 1. Re: Bug-gnubg Digest, Vol 228, Issue 5 (Wayne Joseph) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 30 Dec 2022 23:20:19 +0000 > From: Wayne Joseph <waynejos...@gmail.com> > To: bug-gnubg@gnu.org > Subject: Re: Bug-gnubg Digest, Vol 228, Issue 5 > Message-ID: > <CAH= > l7pzdkzg5-et6qrzz4nm5m9v7oxu0xs+nuwt5twet93t...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Many thanks Ian, I am looking into this. Happy New Year to you! > > Wayne > > On Fri, 30 Dec 2022 at 17:00, <bug-gnubg-requ...@gnu.org> wrote: > > > Send Bug-gnubg mailing list submissions to > > bug-gnubg@gnu.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.gnu.org/mailman/listinfo/bug-gnubg > > or, via email, send a message with subject or body 'help' to > > bug-gnubg-requ...@gnu.org > > > > You can reach the person managing the list at > > bug-gnubg-ow...@gnu.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Bug-gnubg digest..." > > > > > > Today's Topics: > > > > 1. Re: A way to extract / collate all blunders from session(s) > > (Ian Shaw) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 29 Dec 2022 17:16:27 +0000 > > From: Ian Shaw <ian.s...@riverauto.co.uk> > > To: Wayne Joseph <waynejos...@gmail.com>, "bug-gnubg@gnu.org" > > <bug-gnubg@gnu.org> > > Subject: Re: A way to extract / collate all blunders from session(s) > > Message-ID: > > < > > > cwxp123mb57637cc458033fc30f9459acaa...@cwxp123mb5763.gbrp123.prod.outlook.com > > > > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi Wayne, > > > > There is nothing within gnubg itself for this. > > > > It would not be surprising if somebody has written some Python code to > > query the database, but I'm not aware of it. > > > > Good luck, > > Ian Shaw > > > > > > Regards, > > > > Ian Shaw > > > > Project Manager > > > > > > > > Email: ian.s...@riverauto.co.uk<mailto:ian.s...@riverauto.co.uk> > > > > Tel: +44 114 2555500<tel:+441142555500> > > > > Mob: +44 7949 021822<tel:+447949021822> > > > > Web: www.riverauto.co.uk<http://www.riverauto.co.uk/> > > > > > > Registered Office: 61 Wostenholm Road, Sheffield, S7 1LE< > > https://goo.gl/maps/ZB9CEjzVh3JMCMTo6> > > > > Registered in England and Wales No. 2736526.<tel:+442736526> > > > > > > ________________________________ > > From: bug-gnubg-bounces+ian.shaw=riverauto.co...@gnu.org > > <bug-gnubg-bounces+ian.shaw=riverauto.co...@gnu.org> on behalf of Wayne > > Joseph <waynejos...@gmail.com> > > Sent: Wednesday, December 28, 2022 12:11:20 PM > > To: bug-gnubg@gnu.org <bug-gnubg@gnu.org> > > Subject: A way to extract / collate all blunders from session(s) > > > > Season's Greetings! > > > > Is there a way in Gnubg to extract & collate all blunders from analysed > > session(s)? > > > > By this, I mean the various Position IDs. > > > > I think this would be very useful for training on personalised areas of > > weakness. > > > > I have devised a possible method and workflow on the back of an envelope, > > but before I start implementing, just want to check if something already > > exists. > > > > Thanks! > > > > -- Sent from my Android phone > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: < > > > https://lists.gnu.org/archive/html/bug-gnubg/attachments/20221229/a6972c42/attachment.htm > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Bug-gnubg mailing list > > Bug-gnubg@gnu.org > > https://lists.gnu.org/mailman/listinfo/bug-gnubg > > > > > > ------------------------------ > > > > End of Bug-gnubg Digest, Vol 228, Issue 5 > > ***************************************** > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.gnu.org/archive/html/bug-gnubg/attachments/20221230/20786e64/attachment.htm > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Bug-gnubg mailing list > Bug-gnubg@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-gnubg > > > ------------------------------ > > End of Bug-gnubg Digest, Vol 228, Issue 6 > ***************************************** >
