Repository navigation
Conversation
Removed src/expirements from clippy Added default controucters for LambdaSoup, BTreeGen Implemented Rust Suggestions Renamed lambda module name to core Temporarily Suppressed dead code warning for FontanaGen
Fixed syntax error
Fix clippy warnings-
Added documentation for current issues, resolved problems, and remaining known issues in the README.
…dynamic version, tests
Merge changes from fontanagen to cherry-pick-bss-files Hopefully this brings the functional fontanagenerator into the `cherry-pick-bss-files` branch
This does not actually fix the clippy issues that we originally set out to resolve. However there are so many changes on this that we need, so we may as well merge into main.
…lliders (#8) - Store tuple as (expr, reductions, size) to align with collectors - Affects src/lambda/recursive.rs and src/lambda/core.rs
- Union = |A| + |B| - |A ∩ B| - Guard empty-empty case to return 1.0
Lots of changes, documentation, clippy, functionality, compilation issues.
Issue 8 9 collision jaccard
Seed python bindings fix
Add Supercollider reaction recording and integrate Fontana generator fixes
The reactor already supports a seed, but the Python bindings had no way to pass one in, so every soup picked a random seed and collisions were not reproducible from Python. Add an optional hex `seed` argument (same format as the generators). With no seed, behavior is unchanged.
When no seed is given, one is now chosen at construction and kept, and PySoup.seed, PyReactor.seed, PyBTreeGen.seed and PyFontanaGen.seed return it as a 64-char hex string (the encode_hex_py format). Passing that value back as `seed=` reproduces the run, so an unseeded run is no longer lost.
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
5 participants
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.
Fixed seed issue in rust
PySoup and PyReactor take an optional seed (64-char hex, the encode_hex_py / decode_hex_py format). The same seed produces identical runs.
When no seed is given, one is chosen at construction and kept. PySoup.seed, PyReactor.seed, PyBTreeGen.seed and PyFontanaGen.seed return it, so passing it back as seed= reproduces an unseeded run.
How I confirmed it works: created a soup without a seed, read .seed, and created a second soup with it. Both gave identical expressions after 500 collisions. Same for the BTree generator. In the dashboard, two experiments with seed 42 now produce identical graphs, and seed 43 differs.
Note: this is based on main. It should merge cleanly with refac/generator-abstraction, but both touch PySoup in src/python.rs.