[Bioc-devel] BiocFileCache for developers

Shepherd, Lori Lori.Shepherd at RoswellPark.org
Fri Dec 1 16:46:42 CET 2017

If you are using it as a helper function that may be too much exposure and you may just want it running behind the scenes in default location;  but it could be given as an option to the user. I guess a coding preference. If the user specified directory is used, they will have to remember to input that each time they use your package or it will redownload.

There shouldn't be a concern of overwriting files in the default cache location, as files added to the cache get a random identifier to try to avoid overwriting and to allow for essentially duplicate entries.

You can always get the cache location of a bfc object by calling bfccache(bfc) in case a user specific directory is used.

Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Michael Love <michaelisaiahlove at gmail.com>
Sent: Friday, December 1, 2017 10:28:48 AM
To: bioc-devel at r-project.org
Subject: [Bioc-devel] BiocFileCache for developers


I'm writing a function which currently uses BiocFileCache to store a
small data.frame and one or more TxDb objects, so that these objects
are persistent and available across sessions (or possible available to
multiple users).

In the simplest case, I would call

bfc <- BiocFileCache()

inside my function, which will check the default location:

user_cache_dir(appname = "BiocFileCache")

In general, should developers also support the user specifying a
specific location for the BiocFileCache? So functions using
BiocFileCache should have an argument that overrides the above


Bioc-devel at r-project.org mailing list

This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list