Fix issue with strand_specific code #2
As the parmap author I have been contacting parmap users to make sure they can smoothly update to the minor API changes I had to make in
Unfortunately, I have found an issue in your usage of parmap that may have lead to some incorrect results. Until parmap 1.5.0,
If you want to check the impact of this bug on your results, please make sure you have the latest parmap version installed (which does support keyword arguments, you can use
parmap 1.5.0 introduced support for passing keyword arguments to mapped functions, as keyword arguments were not supported before. The drawback of this new feature is that a consistent naming of parmap arguments is needed in order to prevent conflicts between parmap arguments and user-defined arguments. The new parmap convention is to prefix all its arguments with "pm_" (for parmap) as documented http://parmap.readthedocs.io/en/latest/ This commit updates the cll-chromatin parmap calls to use the new API, removing the deprecation warnings that appear with parmap==1.5.1 (the parmap version used).