How to Determine Loaded Package Versions in R

Introduction

Package version management is a common yet critical aspect of R language development and usage. Particularly in multi-version R environments or cluster computing scenarios, accurately identifying loaded package versions is essential for debugging compatibility issues and ensuring code reproducibility.

Core Function Analysis

The sessionInfo() function provides the most comprehensive overview of session information. Its output consists of three main sections: R version details, platform architecture, and attached base packages along with other packages.

> sessionInfo()
R version 2.15.0 (2012-03-30)
Platform: x86_64-pc-linux-gnu (64-bit)

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C              
 [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8    
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8   
 [7] LC_PAPER=C                 LC_NAME=C                 
 [9] LC_ADDRESS=C               LC_TELEPHONE=C            
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       

attached base packages:
[1] graphics  grDevices utils     datasets  stats     grid      methods   base     

other attached packages:
[1] ggplot2_0.9.0  reshape2_1.2.1 plyr_1.7.1    

loaded via a namespace (and not attached):
 [1] colorspace_1.1-1   dichromat_1.2-4    digest_0.5.2       MASS_7.3-18       
 [5] memoise_0.1        munsell_0.3        proto_0.3-9.2      RColorBrewer_1.0-5
 [9] scales_0.2.0       stringr_0.6       

In the output, the underscore and numbers following package names (e.g., ggplot2_0.9.0) clearly indicate version information. This representation intuitively shows the correspondence between package names and their versions.

Targeted Version Checking

For specific package version queries, the packageVersion() function offers a more direct solution:

> packageVersion("snow")
[1] ‘0.3.9’

This function directly returns the version number of the specified package in a clear format suitable for programmatic processing. Note that the package must have a valid DESCRIPTION file containing a legitimate Version field to be properly recognized.

Package Loading Status Verification

In certain scenarios, it's necessary to confirm whether a specific package has been loaded into the current namespace:

> "Rmpi" %in% loadedNamespaces()
[1] TRUE

This approach is useful for complex scripts requiring dynamic checking of package dependencies, particularly in parallel computing or package development contexts.

Practical Application Case Study

Consider a typical multi-version R environment issue: a user's system has both R 2.11 and R 2.14.2 installed, encountering version compatibility errors when using MPI and snow packages.

Problem code:

library(snow)
library(Rmpi)
cl <- makeMPIcluster(mpi.universe.size()-1)
stopCluster(cl)
mpi.quit()

Error messages indicate that the snow package requires R version ≥2.12.1, but the loaded package corresponds to R 2.11.1. Even with correct library path settings via .libPaths(), version conflicts persist.

Solution strategies include:

1. Using sessionInfo() to confirm current R version and loaded packages
2. Verifying specific package versions with packageVersion("snow")
3. Checking .libPaths() priority to ensure loading correct package versions
4. Ensuring MPI commands point to the correct R executable in cluster environments

Extended Functionality and Best Practices

Beyond basic version checking, R provides additional related functions:

# Get package release date
packageDate("ggplot2")

# View complete package description
packageDescription("ggplot2")

Development best practices recommend:

• Recording sessionInfo() output at script initiation to ensure reproducibility
• Using packageVersion() for version conditional checks
• Explicitly setting library path priorities in multi-user environments
• Regularly updating package versions and testing compatibility

Conclusion

Accurate identification of R package versions forms the foundation for ensuring code stability and reproducibility. By appropriately combining functions like sessionInfo(), packageVersion(), and loadedNamespaces(), developers can effectively manage package dependencies and resolve version conflicts, particularly in complex computational environments.