I've added an example chezzz.cfg in my downloads area:
http://chezzz.elektronhjerne.dk/downloads/chezzz.cfg
/David
Hi Matthias,Use default values that won't kill the computer of "the normal user".I've added an example chezzz.cfg in my downloads area:
http://chezzz.elektronhjerne.dk/downloads/chezzz.cfg
/David
288 MB means you expect user's RAM to exceed 576 MB (2x288). Unrealistic !
Total hash = 32 MB is the norm.
Regards,
Matthias.
These are not default values, this is an example file.Use default values that won't kill the computer of "the normal user".I've added an example chezzz.cfg in my downloads area:
http://chezzz.elektronhjerne.dk/downloads/chezzz.cfg
/David
288 MB means you expect user's RAM to exceed 576 MB (2x288). Unrealistic !
Total hash = 32 MB is the norm.
YeahHello David,
At least your engine - and its configuration - is generating lots of comment!
I know other authors who wish they had some feedback, any feedback.
It can be a tough crowd here but they are generally good at heart.
Be happy, at this rate you will be able to release a much stronger engine
once the inevitable bug reports pour in.
The 32 MB norm is really an accepted tradition following from well established
sources such as Leo's detail pages. Several persons use that setting as a
reasonable setting given the typical user's ram capacity - around 128 to 256.
More hash size is better - to a certain diminishing limit - but 32 MB gets the
job done for most WB engines.
Your 700+ monster may very well be the norm now I suppose but I assure you,
it is way outside the reach of the typical user on this forum.
It is an example file and really, I am lazy but all I need is a
config file and I will do the tinkering. Set it to 500 MB if you like. I
will pare it down to a size that makes sense for my equipment.
Thanks for Chezzz.
Hi Matthias,Use default values that won't kill the computer of "the normal user".I've added an example chezzz.cfg in my downloads area:
http://chezzz.elektronhjerne.dk/downloads/chezzz.cfg
/David
288 MB means you expect user's RAM to exceed 576 MB (2x288). Unrealistic !
Total hash = 32 MB is the norm.
Regards,
Matthias.
This is an example file, the values in it are not default values. Default (if there is no cfg file) is 8 MB and 4 MB respectively for the two hash tables.
Best regards,
Gábor
Lack of memory doesn't harm our system as suchHi Gabor,
default values are the values a program uses if the user does not modify anything.
If I simply download chezzz.cfg and run a test match without changing anything,
it should not harm my system.
That is the meaning of "working config file".
Lack of memory doesn't harm our system as such.
These are not default values, this is an example file.Use default values that won't kill the computer of "the normal user".I've added an example chezzz.cfg in my downloads area:
http://chezzz.elektronhjerne.dk/downloads/chezzz.cfg
/David
288 MB means you expect user's RAM to exceed 576 MB (2x288). Unrealistic !
Total hash = 32 MB is the norm.
First of all, I wrote 256M, not 288. Secondly, the number given is _total_. That is, the engine will decide how to use this RAM for the transposition table. So the 256M is total.
Thirdly, whether it's unrealistic or not, I don't know. I have 768 MB RAM myself. And again, it's an example file.
Whose norm?
/David
I dunno, I'm very happy I don't see many complaints about my engine.At least your engine - and its configuration - is generating lots of comment!
I know other authors who wish they had some feedback, any feedback.
If it ships with Cheezzz (which supposedly it will in the next version), it should not be set too high. I'm guessing a large percentage of people dont borther to change the config files.To be fair to David his post was titled "Example Chezzz.cfg". Not default. To write a config file from scratch when I am not aware of what parameters are used by the chess engine is one thing. Editing a config file is quite another and I would suggest that all users would want to do that anyway.
I have to agree with Matthius here. If you provide a file with your engine it is by default the default file no matter what you would like to call it.
If I donwloaded your engine the first thing I would do is start it up and see how it ran and I have 128Mbytes total in my system. If you have 768 Mbytes of RAM then you have more than 95% of other users out there.
I'm happy about the feedback. Very little of it is complaints, most of it is useful commenting. The discussions about cfg files and about SAN notation that have been generated here, are important discussions and not complaints about my engine as I see it.I dunno, I'm very happy I don't see many complaints about my engine.At least your engine - and its configuration - is generating lots of comment!
I know other authors who wish they had some feedback, any feedback.
-Marcus
No one said this was a working config file. This is an _example_ file. If I made an example file with really small tables, the same critique could be said of that: That it wasn't suited for use by users just downloading it and using it. It's really not that hard to understand. And if it harms your system, you should consider changing operating systems.Hi Gabor,
default values are the values a program uses if the user does not modify anything.
If I simply download chezzz.cfg and run a test match without changing anything,
it should not harm my system.
That is the meaning of "working config file".
How?Lack of memory doesn't harm our system as such.
When swapping slows down my system considerably, it IS harmful.
I don't provide the file with my engine. People can view or download it separately from the page, and it is clearly stated that it is an example file.I have to agree with Matthius here. If you provide a file with your engine it is by default the default file no matter what you would like to call it.
If I donwloaded your engine the first thing I would do is start it up and see how it ran
and I have 128Mbytes total in my system. If you have 768 Mbytes of RAM then you have more than 95% of other users out there.
-Marcus
I actually agree with his statement. But first of all, I think Chezzz _is_ easy to use. And secondly, providing an _example_ config file with, say, 32M hash, is not my idea of userfriendlyness, since that file will have to be edited anyway for EGTBs etc. Userfriendlyness in this case would be to _ask_ the user about these things that the engine cannot know on it's own, like EGTB path and hash settings. The microsoft version of userfriendlyness in this case would be to search the users entire system for hours (on my harddisk it might be fast, but 95% of all people here might have slower disks) for EGTBs, thereby setting the path itself. What if you have several directories with EGTBs? I have. Also, the microsoft version would also be to determine the amount of physical memory that is unused at the moment, and make a decision based on that about how much to use. That would make tournaments on the same machine hard to do etc.If you want people to use your engine first you need to make it easy for people to use.
I disagree - but I do understand your point. Users will first of all be far
I'm not sure about that. It's available now on the download page. Maybe I will change my scheme altogether and generate a cfg file on startup if necesary, maybe after asking the user some questions. Or I will ship an example file where every line will have a '#' at the beginning, meaning a comment in the Chezzz cfg format.If it ships with Cheezzz (which supposedly it will in the next version), itTo be fair to David his post was titled "Example Chezzz.cfg". Not default. To write a config file from scratch when I am not aware of what parameters are used by the chess engine is one thing. Editing a config file is quite another and I would suggest that all users would want to do that anyway.
Return to Archive (Old Parsimony Forum)
Users browsing this forum: No registered users and 21 guests