We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
concurrent.futures.ProcessPoolExecutor
I notice that this module use concurrent.futures.ProcessPoolExecutor instead of joblib when generating random walk , according to https://joblib.readthedocs.io/en/latest/auto_examples/parallel_random_state.html#sphx-glr-download-auto-examples-parallel-random-state-py and https://stackoverflow.com/questions/49847794/child-processes-generating-same-random-numbers-as-parent-process , I'm not sure whether concurrent.futures.ProcessPoolExecutor may lead to wrong embedding ...... So I open this issue for discuss ......
joblib
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I notice that this module use
concurrent.futures.ProcessPoolExecutor
instead ofjoblib
when generating random walk , according to https://joblib.readthedocs.io/en/latest/auto_examples/parallel_random_state.html#sphx-glr-download-auto-examples-parallel-random-state-py and https://stackoverflow.com/questions/49847794/child-processes-generating-same-random-numbers-as-parent-process , I'm not sure whetherconcurrent.futures.ProcessPoolExecutor
may lead to wrong embedding ...... So I open this issue for discuss ......The text was updated successfully, but these errors were encountered: