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
There can be some complications while combining this with having a progress bar, but solutions can be found at tqdm/tqdm#484.
Alternatively, there is already parallel implementation in dscribe, but one needs to modify the call stack and group the calls to SOAP.create together.
The text was updated successfully, but these errors were encountered:
I prefer to do this at the asap level, as not all descriptors are parallelized, and this is really a trivial parrallelzation.
To do this properly, I'm thinking perhaps we first sort the frames according to sizes (as a proxy to the associated computing cost), and then start N processes for each N frames with similar sizes.
I agree. Sorting is probably not necessary as one can just use strides of the input frames? There might be some complications for avoiding using too much memory. For example, if the child process just inherent all the resources, the memory cost will increase N fold.
It may be better to use the joblib library, this is what dscribe uses.
It would be nice to use all those core of a PC.
At the moment ASAP is serial. It would be relatively easy to parallelise over the frames using
multiprocessing.Pool
in the following code:ASAP/asaplib/data/xyz.py
Lines 197 to 205 in 2ccd298
There can be some complications while combining this with having a progress bar, but solutions can be found at tqdm/tqdm#484.
Alternatively, there is already parallel implementation in
dscribe
, but one needs to modify the call stack and group the calls toSOAP.create
together.The text was updated successfully, but these errors were encountered: