-
|
What to do about R errors such as: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This is likely caused by conflicting package versions across multiple R libraries. R checks both your personal and the system-wide shared library. You can get namespace conflicts if different versions of the same package exists in both. Even if you recently haven't changed anything in your personal library, HPC admins may update packages in the global library, creating a mismatch. To confirm that the problem is with R, load the relevant R module, launch R, and try loading the problematic package. To diagnose the problem, start R and run: .libPaths()
find.package("packagename")
packageVersion("packagename")The If you don't need specific versions in your personal library, you can remove the conflicting packages from there. Navigate to your personal path in the terminal and you will see all the libraries installed there. You can delete the directory corresponding to the offending package. If you prefer to be cautious, you can simply rename the directories to hide them from R and R will fall back to the system library versions. |
Beta Was this translation helpful? Give feedback.
This is likely caused by conflicting package versions across multiple R libraries. R checks both your personal and the system-wide shared library. You can get namespace conflicts if different versions of the same package exists in both. Even if you recently haven't changed anything in your personal library, HPC admins may update packages in the global library, creating a mismatch.
To confirm that the problem is with R, load the relevant R module, launch R, and try loading the problematic package.
To diagnose the problem, start R and run:
The
.libPaths()command typically returns two paths: the shared one starts with/gp…