Add pickle and unpickle support. #75
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Picklable objects for multithreading support.
Sometime we have a list of queries to run where each query is independent of each other. In such case, we can create a thread pool and copy the same environment in each thread to run queries in parallel. The following code gives an example of doing this:
However, objects like
fcl.BVHModel
,fcl.CollisionObject
are ==unpicklable==, making it unable to serialize them, and de-serialize them in threads:My solution to address this issue is to derive subclasses from those
Cython
class, add__init__
method to cache input arguments and__reduce__
method to return the cached data for pickling.Currently only support
fcl.Transform
,fcl.BVHModel
,fcl.CollisionObject
, with this commit and a simple magic import:from fcl import fcl2 as fcl
, the above example script can run in parallel.