Get a change or a problem reviewed

This repository is maintained by Mehmet Onur Keskin. Its current scope is a Python modernization of the article framework, with a headless experiment workflow and an optional inspection GUI.

Use the existing issue templates for a reproducible bug or experiment question. Include the software commit/version, command, minimal scenario, effective settings, expected/observed behavior and sanitized logs. Keep private rosters, credentials and unpublished research data out of an issue. There is no promised response time or support SLA.

A useful bug report distinguishes physical/contract violations, infrastructure failures, bounded search exhaustion and scientific differences. A lower success rate alone does not identify a bug. Avoid repeatedly launching a failing large batch; reduce the case while retaining its input and attempt identities.

The supported path is local CPU execution with Python 3.12/3.13 qualification. GUI, analysis, docs and resource monitoring are optional extras. Native paper baselines require their explicitly built, identified binaries. Propose substantial extensions in an issue with their intended behavior and validation plan.

The current version is alpha software. Report the exact version and commit when opening a problem; a software release is not a claim of complete article reproduction.

Next: choose a scoped starting task, then follow the contribution checks.