Skip to content

Add Internal Iterative Reduction - #4

Draft
KnightStackSys wants to merge 9 commits into
mainfrom
internal-iterative-reduction
Draft

KnightStackSys wants to merge 9 commits into
mainfrom
internal-iterative-reduction

Conversation

@KnightStackSys

@KnightStackSys KnightStackSys commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

Adds a conservative Internal Iterative Reduction (IIR) baseline to IronPhoenix search for isolated Elo testing.

IIR policy

  • applies only at PV nodes
  • skips the root (ply > 0)
  • minimum depth 5
  • disabled while in check
  • only triggers when the transposition table provides no move
  • reduces depth by exactly one ply

Why conservative

IIR is primarily useful when a deep PV node lacks a TT move to guide move ordering. IronPhoenix already applies LMR to later quiet moves, so this first IIR version keeps the reduction to one ply and avoids stacking broader reductions onto non-PV nodes.

Scope

  • only src/search.cpp changes
  • existing SEE pruning, LMR, history, PVS, aspiration windows, TT cutoff behavior, comments, and move ordering remain intact

Please SPRT this branch against main by itself before combining it with Null Move Pruning or other search changes.

@KnightStackSys KnightStackSys self-assigned this Oct 9, 2026
@KnightStackSys KnightStackSys added the enhancement New feature or request label Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant