Re: [Bug-gnubg] Set analysis limit

[Michael Petch]

longer applies and should be removed. Thanks for looking into it!
> 
> I have plenty of disk space, so I don't mind large files, but note that one
> possible use of "set analysis limit" is to reduce the size of saved .sgf
> files.  E.g. one can set analysis limit to a small number, analyze the
> match/session, and save the resulting analysis as a small .sgf file.  If
> this command is eliminated, gnubg will retain the analysis of every legal
> move (most of them at 0-ply, some at higher plies), resulting in a larger
> .sgf file.
> 

This seems rather plausible, given the comment on a CVS check in that Gary
Wong made on April 9th, 2001 to analysis.c:

analysis.c Revision 1.12 "Allow a limit to be specified on the number of
analysed moves recorded."

gnubg.c Revision 1.119 was also modified to support set limit (Same day).

I think the comment about "number of analyzed moves recorded" is a better
description of the intent of the command - likely referring to recording to
the SGF format.

But I wonder, does it really matter? I could argue that if you wish to store
SGF files it might be better to compress them. With people using terabytes
to store video and songs, not sure it'll make a difference that an SGF file
might be 1mb instead of 200k (Example).

No one has identified any issues until now, which makes me thing most people
had no idea there was a way to potentially reduce the output file size with
this feature. I am still with the "Lets remove it" position.