Another idea for null move pruning solution

[Uri Blass]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

[Henk]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

What's wrong with null move pruning ?

[ZirconiumX]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

What's wrong with null move pruning ?

Zugzwang is the problem. I don't think this is the solution.

Matthew:out

[mvk]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

Yes. What is your own experience with this?

[Uri Blass]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

Yes. What is your own experience with this?

My own experience is that I did not test it.

[lucasart]

I wonder if people tried simply not to do null move pruning only in the first iterations during games so the program is going to use null move pruning in big majority of the cases.

It can be done based on iteration(the program use null move pruning only from iteration 10).

It can be done also based on the target time(if the program did not use at least 0.4% of the target time do not use null move pruning,later use null move pruning).

Yes. What is your own experience with this?

My own experience is that I did not test it.

So it's always the same story with you.

[BBauer]

I do
// Step 8. Null move search with verification search (is omitted in PV nodes)
int piecesCnt;
piecesCnt = RootPos.total_piece_count();

if ( !PvNode
&& !ss->skipNullMove
&& depth >= (2 + (32-piecesCnt)/2) * ONE_PLY
&& eval >= beta
&& abs(beta) < VALUE_MATE_IN_MAX_PLY
&& pos.non_pawn_material(pos.side_to_move()))
{

My experiences are good. But I do no game play, only analysis.

Kind regards
Bernhard