On 4 November 2013 at 14:31, Murray Stokely wrote:
| Most operating systems have tools which allow you to audit the resources
| used by a running process, for example the 'lsof' (list open files) command
| on Unix and MacOS X. Or, for more complex dynamic tracing, the DTrace
| framework again on
Most operating systems have tools which allow you to audit the resources
used by a running process, for example the 'lsof' (list open files) command
on Unix and MacOS X. Or, for more complex dynamic tracing, the DTrace
framework again on MacOS X or BSD Unix.
Not sure what the Windows equivalent w
If you have the code in a parseable form then CodeDepends will try to do
this:
> library(CodeDepends)
> code
[1] "w = rnorm(10); t = read.csv('mycsv.csv'); lm(y~x, data = t)"
> scr = readScript("dummy", type = "R", txt = code)
> inp = getInputs(scr)
> length(inp)
[1] 3
> inp[[2]]@files
[1] "mycsv.
I am not sure R can do what you want (others may), but have a look at
?history
for R's history mechanism, which keeps a record of all commands that
you have entered and so might satisfy your needs.
Note that there are various 3rd party GUI's/IDE's (e.g. RStudio) that
might be more to your likin
I'm using R in a regulated environment and one of the requirements is to
be able to trace how a result is arrived at. I would like to be able to
determine which files are opened in read or write mode by an R session,
for example when a program uses source, sink, file, open, read.table,
write.ta
