trackObjs will not work together with mvbutils -- both use active
bindings to store objects on disk, and I would expect that trying to use
both together would cause all sort of nasty conflicts. I would think it
would be possible to fold the creation/modification time recording from
trackObjs into mvbutils, but it would probably be a significant amount
of work.
-- Tony Plate
On 05/31/2010 09:56 PM, Day, Roger S wrote:> Hello Colleagues,
>
> I've recently become a fan of Mark Bravington's mvbutils package
for organizing analysis projects in a tree.
> Using cd(), Save(), fixr(), mlazy() etcetera solves nicely some of the
nuisances that have worried or annoyed me and sometimes caused
> big problems over the years. Well thought out.
>
> Now one feature that would be fabulous would be automatic time-stamping of
objects.
> The trackObjs package from provides this, among other services.
>
> The question is, can the two packages work together peacefully?
>
> One curiosity: they have opposite ideas of the word "cache".
> In mvbutils, a cached object is one that is stored on disk, only retrieved
into memory when needed.
> In trackObjs, a cached object is one that is stored in memory as well as on
disk.
> More than a curiosity, also potentially a bad sign for compatibility
between the two packages.
>
> Anyone have experience with the two together, and care to share it?
> Thanks!
>
>
> Roger Day
> University of Pittsburgh Departments of Biomedical Informatics and
> Biostatistics
> University of Pittsburgh Cancer Institute
> University of Pittsburgh Molecular Medicine Institute
> -----------------------------------------------------
> Room 310, Suite 301
> Cancer Pavilion (CNPAV)
> 5150 Centre Ave.
> Pittsburgh, PA 15232
> e-mail: day01 at pitt.edu
> cell phone 412-609-3918
> assistant:
> Lucy Cafeo: (412) 623-2952
>
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>
>