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

module 'taichi' has no attribute 'gpu' #865

Closed
GeoffreyPlitt opened this issue Apr 25, 2020 · 4 comments
Closed

module 'taichi' has no attribute 'gpu' #865

GeoffreyPlitt opened this issue Apr 25, 2020 · 4 comments
Labels
discussion Welcome discussion! potential bug Something that looks like a bug but not yet confirmed

Comments

@GeoffreyPlitt
Copy link

Running on Mac 10.15.4 / Python 3.7.7
19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64

fractal.py 
[Taichi] mode=release
[Taichi] version 0.5.14, supported archs: [cpu, metal], commit 9a3bb30b, python 3.7.7
Traceback (most recent call last):
  File "fractal.py", line 3, in <module>
    ti.init(arch=ti.gpu)
AttributeError: module 'taichi' has no attribute 'gpu'

How do I troubleshoot this?

@GeoffreyPlitt GeoffreyPlitt added the potential bug Something that looks like a bug but not yet confirmed label Apr 25, 2020
@archibate
Copy link
Collaborator

archibate commented Apr 25, 2020

For now please use ti.metal instead of ti.gpu. Sorry about the confuse!

Recently we added the ti.gpu feature (#843) and updated documentions for that feature. However, we haven't released that yet (will be soon in v0.5.15).
@yuanming-hu Maybe we should update taichi.readthedocs.io only after release? So that users won't get confused by not-released-yet features.

@GeoffreyPlitt
Copy link
Author

Do you guys have a stable branch that excludes unreleased features?

@archibate
Copy link
Collaborator

No, we don't have a stable branch yet. Thanks for the idea! Currently master serves as the developing branch. And we use tags for stable release instead.

My suggestions:

  1. Create a stable branch.
  2. Contributor PRs compares from contributor:patch-xxx to master, squash before merge.
  3. When release, make a PR compares from master to stable, squash before merge.
  4. And the stable commit history should looks like:
[release] v0.5.15 (#1002)
[release] v0.5.14 (#1001)
[release] v0.5.13 (#1000)
...

Should be helpful when tracking bugs. What do you think?

@archibate archibate added the discussion Welcome discussion! label Apr 25, 2020
@GeoffreyPlitt
Copy link
Author

Sounds great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Welcome discussion! potential bug Something that looks like a bug but not yet confirmed
Projects
None yet
Development

No branches or pull requests

2 participants