-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support for current dev version of qutip #46
base: main
Are you sure you want to change the base?
Conversation
Use packaging version 21.3 to avoid getting no attribute "LegacyVersion" since it was deprecated in newer versions
Use packaging version 21.3 to avoid getting no attribute "LegacyVersion" since it was deprecated in newer versions
machine_image update, trying to fix test jobs
Remove deprecated workflow parameter, adjust labels to contain cirun
Match runners by label
@@ -1,7 +1,7 @@ | |||
[build-system] | |||
requires = [ | |||
"setuptools>=36.6", | |||
"packaging", | |||
"packaging<=21.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can just replace the code in setup.py as was done in qutip/qutip@2fc35ba8c6 instead of pinning packaging.
@@ -7,22 +7,20 @@ runners: | |||
instance_type: g4dn.xlarge # Cheapest VM on AWS | |||
# Amazon AMI: Deep Learning AMI GPU CUDA 11.2.1 (Ubuntu 20.04) 20210625 | |||
# for eu-west-1 | |||
machine_image: ami-07b138161bedd526d | |||
machine_image: ami-00ac0c28c01352e53 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you find the name and region for the new AMI and update the comment above? Note that we need the AMI for eu-west-1 (I think).
count: 1 | ||
labels: | ||
- gpu | ||
- "cirun-gpu-runner" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did the label name change?
@@ -80,14 +80,14 @@ def is_cupydense(data): | |||
data.norm.max.add_specialisations([(CuPyDense, cdf.max_cupydense)]) | |||
data.norm.one.add_specialisations([(CuPyDense, cdf.one_cupydense)]) | |||
|
|||
data.inv.add_specialisations([(CuPyDense, linalg.inv_cupydense)]) | |||
data.inv.add_specialisations([(CuPyDense, CuPyDense, linalg.inv_cupydense)]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking a look. I left some questions and requests for changes, but the important fixes to the specializations look good.
As reported in issue #45 there were changes in QuTiPv5 that affected qutip-cupy
Pull requests introduces 2 changes:
Test was conducted on AWS GPU instance and basic check looks good but due to dated packages and qutip-cupy there is possibility for other issues to exist.