Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Personalised compilation settings for running in Julia vs PySR #363

Open
MilesCranmer opened this issue Oct 27, 2024 · 1 comment
Open
Assignees
Labels
feature (importance: mid) Mid-importance feature

Comments

@MilesCranmer
Copy link
Owner

It would be nice to have the precompilation settings vary by intended user - whether it be PySR users or Julia users.

For example, the Julia users probably want the MLJ interface precompiled.
And the PySR would only want the equation_search interface precompiled, since that's what PySR calls.

For a future issue: it would also be nice if we could precompile some of the Python->Julia calls in PythonCall.jl so speed up startup time.

@MilesCranmer MilesCranmer added the feature (importance: mid) Mid-importance feature label Oct 27, 2024
@MilesCranmer MilesCranmer self-assigned this Oct 27, 2024
@ATOMSLab
Copy link

ATOMSLab commented Nov 5, 2024

This looks like a much-needed fix for us! Thanks for looking into it!

In Issue #358 , we were never certain if the saved_state was importing correctly, because the method we were using to test this (setting most mutation weights to zero, so expression length would never change) doesn't work. We now think this is because precompiling is interfering with our wish to set most mutation weights to zero.

This is also reflected in Issue #361 , where turning off precompilation leads to Type errors since we're trying to use modified Node structures with frozen metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature (importance: mid) Mid-importance feature
Projects
None yet
Development

No branches or pull requests

2 participants