I like the way the tactical mode is implemented now ie to use allocated threads.
All or some very nice feature ,I have installed on engine with 50% cores to tactical and 50% to normal run this engine on a position send to IDEA project and use IA in aquarium if any thing looks interesting i then load the normal all cores Houdini see if anything different then if so load a full all cores Tactical to see if it was a tactical solution, then send to IDEA again later run IDEA with Komodo 11.2.2 check any interesting results with SF development and then enter into my own tuned book for Playchess.com it's added a new feature thanks Robert.
Just wondering, did Robert get this idea from Ed's "Speculative Move Principle" in Prodeo 2.2 SMP (which also dedicated one core to the Q3 tactical engine) which essentially does the same thing?
The objectively highest level of play is achieved without contempt, i.e. Contempt value 0.
1 - do you urge usage of zero rather than default value when facing SF Dev. Maybe default contempt value is adequate when facing Komodo 11.2.2
2 - Is it wise to allocate one core out of eight for tactical mode during analysis, i.e 7 in normal mode and remaining allocated for tactical mode.
1) Against opponents that are close in strength, contempt zero provides the best result. The difference is small, leaving the default contempt on should cost less than 10 Elo.
2) It will reduce the strength somewhat (also less than 10 Elo), and find slightly faster the tactical solutions. Not a big deal over-all.
BrendanJNorman wrote:Just wondering, did Robert get this idea from Ed's "Speculative Move Principle" in Prodeo 2.2 SMP (which also dedicated one core to the Q3 tactical engine) which essentially does the same thing?
Not saying it's bad, just very curious.
No, I didn't know about Prodeo 2.2 SMP (apparently from last year).
The Tactical Mode exists since Houdini 3 in 2012, so it's quite an old idea.
Leo wrote:It looks like the learning feature is gone. One of my favorite features.
I've removed the learning feature last year, in Houdini 5.
I wasn't really happy with its implementation and results in Houdini 2/3/4. I may revisit this in the future.