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

Import Error using Azure DataBricks #1107

Closed
sennettleung opened this issue Sep 1, 2022 · 5 comments
Closed

Import Error using Azure DataBricks #1107

sennettleung opened this issue Sep 1, 2022 · 5 comments
Assignees
Labels
in progress upstream issue Resolution depends on upstream fixes

Comments

@sennettleung
Copy link

sennettleung commented Sep 1, 2022

Hi there,

I am trying to use ax-client to find the best hyperparameters for my neural network model, and I encountered this import error as shown in the link below. I used to be able to access the package okay, but it's not working now. I have installed all the dependency libraries onto the cluster, so am unsure why I'm still running into this error, using the pip install bleeding edge version of the package also didn't help resolve the issue. Any help is much appreciated, thank you!

Screenshot of the dependencies I have installed:
image

Screenshot of the error I encountered whilst trying to import the package (both lines output the same error message):
image

@saitcakmak
Copy link
Contributor

Hi @sennettleung! I assume you're using gpytorch 1.9.0 here? That is currently not supported in Ax/BoTorch (will be supported in next release). If you downgrade to GPyTorch 1.8.1 things should work again.

@Balandat
Copy link
Contributor

Balandat commented Sep 1, 2022

Related botorch issue: pytorch/botorch#1370

I am planning to release a version early next week to to fix this.

@sennettleung
Copy link
Author

Hi both,

That's great, downgrading seemed to have worked, thank you for the update and workaround! :)

@lena-kashtelyan lena-kashtelyan added upstream issue Resolution depends on upstream fixes in progress labels Sep 13, 2022
@lena-kashtelyan lena-kashtelyan self-assigned this Sep 13, 2022
@lena-kashtelyan
Copy link
Contributor

We're looking into cutting new version now, which should address this.

@saitcakmak
Copy link
Contributor

This should be resolved in the just-released 0.2.7 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress upstream issue Resolution depends on upstream fixes
Projects
None yet
Development

No branches or pull requests

4 participants