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

global running time setting error , with ti.init(random_seed=) #2333

Closed
spdcoding opened this issue May 12, 2021 · 3 comments
Closed

global running time setting error , with ti.init(random_seed=) #2333

spdcoding opened this issue May 12, 2021 · 3 comments
Assignees
Labels
potential bug Something that looks like a bug but not yet confirmed

Comments

@spdcoding
Copy link

spdcoding commented May 12, 2021

[Taichi] version 0.7.18, llvm 10.0.0, commit 9a31814, linux, python 3.6.7
It seems like that "random_seed" parameter has been deprecated in the newest version of taichi. Maybe, related documentation should be updated

reproduce:
python3 -c "import taichi as ti; ti.init(random_seed=1)"

result:
[Taichi] mode=release
[Taichi] preparing sandbox at /tmp/taichi-on5gm_8n
[Taichi] version 0.7.18, llvm 10.0.0, commit 9a31814, linux, python 3.6.7
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.6/dist-packages/taichi/lang/init.py", line 202, in init
f'Unrecognized keyword argument(s) for ti.init: {", ".join(unexpected_keys)}'
KeyError: 'Unrecognized keyword argument(s) for ti.init: random_seed'

@spdcoding spdcoding added the potential bug Something that looks like a bug but not yet confirmed label May 12, 2021
@BillXu2000
Copy link
Collaborator

Could you please make a clearer description about this bug?
A sample code or log, for example, will be helpful to reproduce and fix the bug.

@spdcoding
Copy link
Author

Could you please make a clearer description about this bug?
A sample code or log, for example, will be helpful to reproduce and fix the bug.

updated

@victoriacity
Copy link
Member

The random_seed argument is a feature added by #2297. I don't know why its documentation gets merged by 0.7.18 in advance. I tested with 0.7.19 and it should be working fine.

@k-ye k-ye closed this as completed May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug Something that looks like a bug but not yet confirmed
Projects
None yet
Development

No branches or pull requests

4 participants