Tools for developing functions for parallel execution in distributed memory
bpvalidate interrogates the function environment and search path
to locate undefined symbols.
bpvalidate(fun)
fun |
The function to be checked. |
bpvalidate tests if a function can be run in a distributed memory
environment (e.g., SOCK clusters, Windows machines). bpvalidate looks
in the environment of fun, in the NAMESPACE exports of libraries
loaded in fun, and along the search path to identify any symbols
outside the scope of fun.
bpvalidate can be used to check functions passed to the bp* family
of functions in BiocParallel or other packages that support parallel
evaluation on clusters such as snow, BatchJobs, Rmpi,
etc.
The environment of a function defined inside a package is the NAMESPACE of the package. It is important to test these functions as they will be called from within the package, with the appropriate environment. Specifically, do not copy/paste the function into the workspace; once this is done the GlobalEnv becomes the function environment.
To test a package function, load the package then call the function by name (myfun) or explicitly (mypkg:::myfun) if not exported.
The environment of a function defined in the workspace is the GlobalEnv. Because these functions do not have an associated package NAMESPACE, the functions and variables used in the body must be explicitly passed or defined. See examples.
Defining functions in the workspace is often done during development or testing. If the function is later moved inside a package, it can be rewritten in a more lightweight form by taking advantage of imported symbols in the package NAMESPACE.
NOTE: bpvalidate does not currently work on Generics.
A list of length 2 with named elements 'inPath' and 'unknown'.
inPath A named list of symbols and where they were found. These symbols were found on the search path instead of the function environment and should probably be imported in the NAMESPACE or otherwise defined in the package.
unknown A vector of symbols not found in the function environment or the search path.
Martin Morgan mailto:mtmorgan@fhcrc.org and Valerie Obenchain mailto:vobencha@fhcrc.org.
## ---------------------------------------------------------------------
## Testing package functions
## ---------------------------------------------------------------------
## Not run:
library(myPkg)
## Test exported functions by name or the double colon:
bpvalidate(myExportedFun)
bpvalidate(myPkg::myExportedFun)
## Non-exported functions are called with the triple colon:
bpvalidate(myPkg:::myInternalFun)
## End(Not run)
## ---------------------------------------------------------------------
## Testing workspace functions
## ---------------------------------------------------------------------
## Functions defined in the workspace have the .GlobalEnv as their
## environment. Often the symbols used inside the function body
## are not defined in .GlobalEnv and must be passed explicitly.
## Loading libraries:
## In 'fun1' countBam() is flagged as unknown:
fun1 <- function(fl, ...)
countBam(fl)
bpvalidate(fun1)
## countBam() is not defined in .GlobalEnv and must be passed as
## an argument or made available by loading the library.
fun2 <- function(fl, ...) {
library(Rsamtools)
countBam(fl)
}
bpvalidate(fun2)
## Passing arguments:
## 'param' is defined in the workspace but not passed to 'fun3'.
## bpvalidate() flags 'param' as being found 'inPath' which means
## it is not defined in the function environment or inside the function.
library(Rsamtools)
param <- ScanBamParam(flag=scanBamFlag(isMinusStrand=FALSE))
fun3 <- function(fl, ...) {
library(Rsamtools)
countBam(fl, param=param)
}
bpvalidate(fun3)
## 'param' is explicitly passed by adding it as a formal argument.
fun4 <- function(fl, ..., param) {
library(Rsamtools)
countBam(fl, param=param)
}
bpvalidate(fun4)
## The corresponding call to a bp* function includes 'param':
## Not run: bplapply(files, fun4, param=param, BPPARAM=SnowParam(2))Please choose more modern alternatives, such as Google Chrome or Mozilla Firefox.