Cannot install an R package through Runtime for R Console
I tried to install a package that's compressed in a zip file, but Spotfire is not letting me install it.
The command I used is the following:
> install.packages("C:\\LOCATION OF FILE\\FILENAME.tar.gz", repos = NULL)
I received the following error:
* checking MD5 checksums
* Package "PACKAGE NAME" at directory "DIRECTORY OF FILE" does not have an MD5 file, so integrity check was not done
COULD NOT CHECK MD5 CHECKSUMS
When I install this on my local version of R, this package installs perfectly... I'm only experiencing this issue in Spotfire.
The functions mentioned in the "function not yet implemented" warnings and the traceback() report are not part of base R, so I would not expect to find them in TERR, either.
The warnings could be generated by your colleague's package, or by another user-contributed R package.
Here is an example, in which I checked to see if open-source R 3.3.2 contained a function named makeCenv():
> find( "makeCenv" )
> exists( "makeCenv" )
 ".GlobalEnv" "package:stats" "package:graphics"
 "package:grDevices" "package:utils" "package:datasets"
 "package:methods" "Autoloads" "package:base"
You may find it helpful to consult your colleague about these "function not yet implemented" warnings.
Will do! Thank you so much for the help! Much appreciated.
You may find the following Spotfire knowledge base (KB) article helpful for using REvalute():
('How to use the "data" and "expr" arguments in the REvaluate() function from TERR's "RinR" package to send data and expressions out to an open source R session.')
Are you able to open this article using the URL?
REvaluate didn`t work, I followed the steps in the article. Please see the image below:
yes, thank you. I can open it. I will take a look at it.
What is the function call you have tried, along with the text of the error message it returns and the result from calling traceback() right after you receive the error?
Here is an example of what I am asking for, but using a built-in TERR command in a way that deliberately throws an error message, then calling traceback() to see how that command led to the error message:
> lm( Mileage ~ Weight, data = fuel.frame )
Error in model.frame.formula(formula = Mileage ~ Weight, data = fuel. : object "
fuel.frame" not found
3: eval(expr, envir, enclos)
2: eval(expr, envir, enclos)
1: lm(Mileage ~ Weight, data = fuel.frame)
Please see the above image for the error and traceback result. `mydata` is a dataframe with 162 obs. of 52 variables.
Just for added background - this analysis worked perfectly on R (before I tried this on TERR console runtime for R).
If it turns out that development of your colleague's R package did not include testing it for compatibility with TERR (or with the TERR version you are using), you could use the REvaluate() function in TERR's built-in "RinR" package to send data and expressions out for processing in an open-source R instance that has been installed on the same machine.
In a TERR Console session, the following command will open the help file for the REvaluate() function:
help( "REvaluate", try.all.packages = TRUE )
The following command will add the "RinR" package to your TERR Console session's search() path:
library( RinR )
It`s not clear to me how I can use REvaluate. I`m fairly new to Spotfire TERR scripting and R scripting..
Will this function check whether the functions in the package are compatible with TERR? Also, what arguments should I put in REvaluate?
Thanks so much for your help with this!