Dave, in our setup, we run Rserve on a completely separate host from WebWork's, so your idea wouldn’t have worked there. What we looked at instead was not that different, only adapted for accessing without a shared file system: 1. put the CSV file into the ‘html’ directory of the homework; and then 2. access it from R by giving ‘read.csv’ a HTTP URL to the file. (I think ‘read.csv’ is a better solution here than the lower-level ‘read.table’, btw.) I don’t remember if we used a programmatic way to construct the right URL, which would be the right thing to do, because in the end we weren’t able to go down that route because our WebWork server was configured to force ‘https’ even for static files and R can’t handle ‘https’ URLs without additional packages.
In the end, the simple solution was to embed the CSV in the body of the problem and send that to R as part of the ‘rserve_eval’, like this:
$csv = <<"DATA";Name,ValueFoo, 10Bar, 22DATA# expression "<<CODE" gets replaced with the string from the next# line to the line containing just the word "CODE"my ($remote_file, @problem_data) = rserve_eval(<<CODE);# this is R codemy_data <- read.csv(textConnection('$csv'))problem_data <- transform(my_data, Value = round(Value + rnorm(nrow(my_data))))problem_file <- tempfile(fileext = '.csv')write.csv(problem_data, problem_file)list(problem_file, problem_data)CODE# @problem_data is a one-element array, with $problem_data[0] being the# reference to an array of two columns of the R 'problem_data' data.frame# So $problem_data[0][1] is a reference to the second column of the data# frame, which is ‘Value'@values = @{$problem_data[0][1]};# this is to give the user the option to download the random CSV, as in the# example at the end of http://wiki.ubc.ca/Documentation:WeBWork/The_WeBWorKiR_Project:_Integrating_WeBWorK_with_R/Authoring_guidemy $local_file = rserve_get_file($remote_file);
I hope this helps. Let me know how you solve this in your setting — I’d like to include it as a recipe in our wiki.
Davor