Tommy, The current implementation of the R actor (RExpression) starts an entirely new R session (as though you'd quit and then re started R from the the command line) for every R actor in the workflow. As you know - this can get costly, and I'm afraid you won't be able to keep those libraries loaded across each actor. There has been some development with an alternative R actor implementation (RExpression2) that uses native Java-R bindings and a single R interpreter across actors. I'm still finding kinks in this "JRI" implementation (it can crash _hard_), but feel free to try it out - it may be just what you are looking for in terms of maintaining your environment. -ben
On Aug 14, 2009, at 3:29 PM, Tommy Stropp wrote: > I was wondering if there is any way to keep the same environment > going between R actors within the same workflow. I know I can save > the workspace, but that doesn't save the libraries I've loaded. I > have to load each one that I was using before again in the new R > actor, which is time consuming as some of them are quite large and > take a long time to load. > > - Tommy > > Attention all humans. We are your photos. Free us. > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
