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
Following #115 , we can go further in parallelizing PyAF computations. One can :
The text was updated successfully, but these errors were encountered:
impact of the APIs :
One can now use a list iSignals as an argument for Engine.Train, while keeping a strict backward compatibility (a single iSignal is still supported).
Sorry, something went wrong.
More Parallelization Efforts #145
ba9f5bd
Allow using multiple signals in the same engine (multiple signals sharing the same CPUs) Added some tests
f7b5810
Use one engine to train all nodes of a hierarchy (point 2).
2a25998
Allow using multiple signals in the same engine (multiple signals sharing the same CPUs) Allow custom settings for each signal
antoinecarme
No branches or pull requests
Following #115 , we can go further in parallelizing PyAF computations. One can :
The text was updated successfully, but these errors were encountered: