[WIP/WORKING TREE] V1.2.0 #11
Merged
Merged
Conversation
…development trajectory
…ional for python too.
…bility and extensibility. Make sure feature gating for all backends works right, that CI excercises that too; Improvement to RateBackend development DRYness.
This comment was marked as resolved.
This comment was marked as resolved.
…xecution onto validated compiled plans instead of raw wrapper specs, tightened tests and CI around that boundary.
… feature combinations. Improve CI coverage breadth for tests. Make sure everything works across different feature combinations
This comment was marked as resolved.
This comment was marked as resolved.
- Removed the hidden lifecycle methods/types from the public OnlineBytePredictor trait in crates/infotheory/src/mixture.rs. Internal rate-backend experts now use a private ExpertPredictor wrapper so compact lifecycle rollback stays available without leaking into the public trait. - Removed the dead FAC-CTW predict_update_byte_msb wrapper and its test from crates/infotheory/src/backends/ctw.rs. - Made RatePdfPredictor::from_compiled test-only in crates/infotheory/src/compression/mod.rs. - Removed the no-op ZPAQ release function and all surviving call sites across crates/infotheory/src/backends/zpaq_rate.rs, crates/infotheory/src/lib.rs, crates/infotheory/src/spec.rs, and crates/infotheory/ src/aixi/common.rs. - Documented lifecycle snapshot allocation cost for CTW/FAC-CTW and added justifications for the relevant too_many_arguments suppressions, including the switching-mixture helper that also appeared in the branch diff. - Removed redundant debug_assert! checks in crates/infotheory/src/prediction.rs; the runtime contract panic remains.
… parallel_uct cloned rollouts - Improves memory efficiency and parallel_uct performance (in theory...)
…ope hooks; update some docs for clarification.
- Added support for native bitwise RateBackends (previously CTW was this, but only conditionally for AIXI) Bitwiseness is no longer decided by the consumer(i.e. MC-AIXI), but by the predictor -- and we provide helpers for efficient byte-to-bit factorization for both MSB and LSB first. - bitwise consumption is now first class: Bitwise Arithmetic Coding, and AIXI usage is now correctly handled using the libraries conversion utilities, or native bitwiseness. - Make mixtures with native bitwise models inherit native bitwiseness recursively. - Fix confusing naming of Ctw -- which was previously AC-CTW in AIXI paths, but FAC-CTW in compression -- it's now just AC-CTW consistently, with FacCtw being the unambigous FAC-CTW path.
… return-law evaluation - Introduce planner_agent and planner_runtime as the execution layer for MC-AIXI, discounted AIQI, and aiqi_warmstart_exact_jh controllers. - Move planner-run and warmstart teacher CLI flows into dedicated modules and document the planner ownership boundary in developer-canonical-pipeline-invariants. - Add return_law for shared return-label trie evaluation, wire AIQI through it, and expand warmstart teacher contracts, JSONL ingest, deterministic merge, and task fingerprint binding. - Validate warm-start controller specs at canonicalize time and integrate trace refresh with the tuner bridge. - Use sha2 for warm-start task fingerprints on the aixi feature path.
…Criterion bench alignment
…ocument same_task_live_trace cost
…nd harden exact-return validation with NonZeroUsize
…ns via shared streaming descent instead of materializing distributions and cloning predictors per action
…estable without backend-ctw
Performance improvements, and improvements to the Warmstart agent architecture
…with aixi-gameengine feature
- Updated python/tests/test_aixi.py so non-power-of-two return_bins=3 is accepted, matching the Rust contract. - Bumped pyo3 from 0.28.2 to 0.29.0 in crates/infotheory_py/Cargo.toml. - Updated Cargo.lock for the PyO3 package family only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Begin refactor for maintainability and extensibility in the expected development trajectory.
Done already: