Skip to content

Use of DoparParam #97

Description

@mtmorgan

(from @vjcitn) The BiocParallel vignette mentions foreach support and DoParParam ... but for package authors the steps of makeCluster, registerDo* and stopCluster the vignette should indicate what a package author foreach devotee would do to take advantage of BiocParallel

  1. leave registration and any cluster construction to the user outside
    of package code
  2. whatever cluster configuration is done is done using BiocParallel facilities,
    culminating in a DoParParam that the user manages and passes in
    via BPPARAM
  3. ensure that default behavior is to run in serial mode

Ultimately it seems that the effects of switching to BiocParallel are only to remove code and ensure that BPPARAM is present and used properly. So it is a gain for simplicity and maintainability, but old habits die hard

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions