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

Using Prophet with custom cmdstan install #2639

Open
justinessert opened this issue Nov 20, 2024 · 0 comments
Open

Using Prophet with custom cmdstan install #2639

justinessert opened this issue Nov 20, 2024 · 0 comments

Comments

@justinessert
Copy link

Hey Prophet team,

We are trying to use Prophet alongside other custom stan models that are not pre-compiled. We are installing cmdstan via Conda and would like to use that version for all of our models, including Prophet.

Your README implies that if we simply set export PROPHET_REPACKAGE_CMDSTAN=False prior to installing Prophet, then we can use our own version of cmdstan, but we are having issues with this.

Looking further into this, it looks like in your setup.py that export PROPHET_REPACKAGE_CMDSTAN=False is essentially just not calling cmdstanpy.install_cmdstan. But nonetheless, it's still looking for the exact same cmdstan version in the exact same location (eg. target_dir/cmdstan-2.33.1).

Furthermore, even if I install the same version of cmdstan locally already installed through conda, it looks like when you initialize a Prophet model, it's overriding the CMDSTAN env var to the location that it would be by default in Prophet.

Do y'all have compatibility with people installing cmdstan via other means?

@justinessert justinessert changed the title Using Prophet with custom cmdstan version Using Prophet with custom cmdstan install Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant