You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The processing of each of the realizations created in the ensemble should be fairly easy to run in parallel. This could improve the performance of the code considerable. Shouldn't be high on the priority list, but at some point down the road...
The text was updated successfully, but these errors were encountered:
- Used pathos multiprocessing beacause of problem with pickling if using the "normal" multiprocess module.
- added parallization for ensemble class; fixes#67
- Fixing logger issue for multiprocessing(closed pools after usage)
- fixed random seeds for each thread
- Used pathos multiprocessing beacause of problem with pickling if using the "normal" multiprocess module.
- added parallization for ensemble class; fixes#67
- Fixing logger issue for multiprocessing(closed pools after usage)
- fixed random seeds for each thread
- Used pathos multiprocessing beacause of problem with pickling if using the "normal" multiprocess module.
- added parallization for ensemble class; fixes#67
- Fixing logger issue for multiprocessing(closed pools after usage)
- fixed random seeds for each thread
- Used pathos multiprocessing beacause of problem with pickling if using the "normal" multiprocess module.
- added parallization for ensemble class; fixes#67
- Fixing logger issue for multiprocessing(closed pools after usage)
- fixed random seeds for each thread
The processing of each of the realizations created in the ensemble should be fairly easy to run in parallel. This could improve the performance of the code considerable. Shouldn't be high on the priority list, but at some point down the road...
The text was updated successfully, but these errors were encountered: