MilesCranmer/PySR: v0.18.0
Authors/Creators
- Miles Cranmer1
- Dhananjay Ashok
- T Coxon2
- William Booth-Clibborn3
- Johann Brehmer4
- William Booth-Clibborn3
- Mark Kittisopikul5
- foxtran
- Saurav Maheshkar6
- Shah Mahdi Hasan
- Arthur Grundner
- DeepSource Bot7
- Hongyu Wang8
- Jay Wadekar9
- Raúl Peralta Lozada
- Tanner Mengel10
- Tom Jelen11
- William Thompson
- Zehao Jin12
- chris-soelistyo
- 1. University of Cambridge
- 2. AAE @ Loughborough University
- 3. Scott Logic
- 4. Qualcomm AI Research
- 5. @JaneliaSciComp
- 6. @ml-gde
- 7. @deepsourcelabs
- 8. Beihang University
- 9. New York University
- 10. University of Tennessee, Knoxville
- 11. Abzu
- 12. New York University Abu Dhabi
Description
Frontend changes
- fix TypeError when a variable name matches a builtin python function by @tomjelen in https://github.com/MilesCranmer/PySR/pull/558
- Update to backend: v0.24.0 by @MilesCranmer in https://github.com/MilesCranmer/PySR/pull/564
- Fix extensions not being added to package env by @MilesCranmer in https://github.com/MilesCranmer/PySR/pull/579
- Bump backend version and switch to GitHub-based registry by @MilesCranmer in https://github.com/MilesCranmer/PySR/pull/580
Backend changes
Filtered to only include relevant ones for frontend. Also note that not all backend features, like graph-based expressions/program synthesis, are supported yet, so I don't mention those changes yet... Will add later.
BREAKING: The
swap_operandsmutation contributed by @foxtran now has a default weight of 0.1 rather than 0.0.BREAKING: The Dataset struct has had many of its field declared immutable, as a safety precaution.
- If you had relied on the mutability of the struct to set parameters after initializing it, or had changed any properties of the dataset within a loss function (which actually would break assumptions outside the loss function anyways), you will need to modify your code. Note you can always copy fields of the dataset to variables and then modify those variables
LoopVectorization.jl has been moved to a package extension. PySR will install automatically at first use of
turbo=Truerather than by default, which means faster install time and startup time.- Note that LoopVectorization will no longer result in improved performance in Julia 1.11 and thus
turbo=Truewill have no effect on that version (due to internal changes in Julia), which is why I have instead done the following:
- Note that LoopVectorization will no longer result in improved performance in Julia 1.11 and thus
Bumper.jl support added. Passing
bumper=trueto Options() will result in faster performance.- Uses bump allocation (see rust package bumpalo for a good explanation) in the expression evaluation which can get speeds equivalent to LoopVectorization and sometimes even better due to better management of allocations rather than relying on garbage collection. Seems like a pretty good alternative, and doesn't rely on manipulating Julia internals for performance (https://github.com/MilesCranmer/SymbolicRegression.jl/pull/287)
Various fixes to distributed compute; Slurm support seems to work again!
- Maybe from https://github.com/MilesCranmer/SymbolicRegression.jl/pull/297 - ensures ClusterManagers.jl is loaded on workers
Now prefer to use new keyword-based constructors for nodes:
Node{T}(feature=...) # leaf referencing a particular feature column Node{T}(val=...) # constant value leaf Node{T}(op=1, l=x1) # operator unary node, using the 1st unary operator Node{T}(op=1, l=x1, r=1.5) # binary unary node, using the 1st binary operatorrather than the previous constructors Node(op, l, r) and Node(T; val=...) (though those will still work; just with a depwarn). If you did any construction of nodes manually, note the new syntax. (Old syntax will still work though)
Formatting overhaul of backend (https://github.com/MilesCranmer/SymbolicRegression.jl/pull/278)
Upgraded Optim to 1.9
Upgraded DynamicQuantities to 0.13
Upgraded DynamicExpressions to 0.16
The main search loop in the backend has been greatly refactored for readability and improved type inference. It now looks like this (down from a monolithic ~1000 line function)
function _equation_search( datasets::Vector{D}, ropt::RuntimeOptions, options::Options, saved_state ) where {D<:Dataset} _validate_options(datasets, ropt, options) state = _create_workers(datasets, ropt, options) _initialize_search!(state, datasets, ropt, options, saved_state) _warmup_search!(state, datasets, ropt, options) _main_search_loop!(state, datasets, ropt, options) _tear_down!(state, ropt, options) return _format_output(state, ropt) end
Backend changes: https://github.com/MilesCranmer/SymbolicRegression.jl/compare/v0.23.1...v0.24.1
New Contributors
- @tomjelen made their first contribution in https://github.com/MilesCranmer/PySR/pull/558
Full Changelog: https://github.com/MilesCranmer/PySR/compare/v0.17.4...v0.18.0
Files
MilesCranmer/PySR-v0.18.0.zip
Files
(2.4 MB)
| Name | Size | Download all |
|---|---|---|
|
md5:0fa0495a3149d5fb4e910a1c83b53d2f
|
2.4 MB | Preview Download |
Additional details
Related works
- Is supplement to
- Software: https://github.com/MilesCranmer/PySR/tree/v0.18.0 (URL)