GeneticTS / docsProject documentation

Reference

Target Constraints and Reconfiguration

Look up syntax, contracts, layouts, algorithms, and exact behavior.

The target is constrained so the search problem remains valid and the controls remain usable. Its x coordinate must stay to the right of the launcher by a fixed minimum, its radius must fit inside the stage, and it must avoid the wind panel region so the draggable target does not overlap UI instrumentation.

x∈[max⁡(q0x+120,inset+r),  W−inset−r],y∈[inset+r,  H−inset−r]x \in [\max(q_{0x}+120, inset+r),\; W-inset-r],\quad y \in [inset+r,\; H-inset-r]
Target domain. The target domain is the stage rectangle shrunk by radius and safe inset, with an additional x-distance constraint from the launch point.
control change or drag
  |
  v
copy ranked genomes from previous summary
  |
  v
resize population to new populationSize
  |
  v
clamp target to legal bounds
  |
  v
evaluate immediately under new config
  |
  v
reset solved streak
Reconfiguration path. Interactive changes preserve useful genetic material where possible while invalidating solved-state history.

Population resizing is rank-preserving. If the population shrinks, the highest-ranked genomes survive. If it grows, new random genomes are appended. That gives configuration changes continuity without pretending old convergence statistics still apply.

Continue exploring

Tutorials →How-to guides →Explanation →Source repository →