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
Firstly, thanks for developing a really nice package!
When trying to parse a list of Structure objects with M3GNetStructure(n_jobs=4).transform (to then perform DIRECT sampling), using the n_jobs argument to run this command in parallel (to speed up parsing as suggested in the example notebook), the following error is obtained, stating that the parsing functions are not pickle-able and thus unable to be used in parallel:
When I tried to instead run the transform function in parallel using multiprocessing (Pool.imap_unordered()) rather than joblib's Parallel, I get a similar error about pickle-ability:
For now, I can get around this by manually dividing up my dataset and running separate python jobs to parse these individual chunks, but it would be much easier for users if parallel processing was possible, as it can take quite a while.
Email (Optional)
No response
Version
v2023.9.9
Which OS(es) are you using?
What happened?
Firstly, thanks for developing a really nice package!
When trying to parse a list of
Structure
objects withM3GNetStructure(n_jobs=4).transform
(to then perform DIRECT sampling), using then_jobs
argument to run this command in parallel (to speed up parsing as suggested in the example notebook), the following error is obtained, stating that the parsing functions are not pickle-able and thus unable to be used in parallel:When I tried to instead run the
transform
function in parallel usingmultiprocessing
(Pool.imap_unordered()
) rather thanjoblib
'sParallel
, I get a similar error about pickle-ability:For now, I can get around this by manually dividing up my dataset and running separate python jobs to parse these individual chunks, but it would be much easier for users if parallel processing was possible, as it can take quite a while.
Code snippet
Log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: