From b.rowlingson at lancaster.ac.uk  Sat Jul 20 08:58:56 2013
From: b.rowlingson at lancaster.ac.uk (Barry Rowlingson)
Date: Sat, 20 Jul 2013 07:58:56 +0100
Subject: [Rd] Problem with distributing data in package.
In-Reply-To: <40021026bf894a17a9db5f6c883ba0f6@EX-1-HT0.lancs.local>
References: <40021026bf894a17a9db5f6c883ba0f6@EX-1-HT0.lancs.local>
Message-ID: <CANVKczMVQjiY2LL2CsJvbYX4=jjDCXC9V-L28hqtyD9YKvy_PQ@mail.gmail.com>

On Fri, Jul 19, 2013 at 10:33 AM, Simon Knapp <sleepingwell at gmail.com> wrote:
> Hi List,
>
> I am building a package for a client to help them create and perform
> analyses against netcdf files which contain 'a temporal stack' of
> grids.
>
> For my examples and test cases, I create an example dataset in code
> (as this is a lot more space efficient than providing raw data). The
> code creates a netcdf file in tempdir() and an object of class 'ncdf'
> in the global namespace. I have placed the code in a .R file in the
> data directory of my package and 'load' it with a call to data().

 Why not just put the function that generates the data file into the
usual place (/R/ folder) and document it so that the user knows to run
'sampledata=makeSampleNCDF()' before doing things that need it?

 Trying to put executable code into the data folder does seem a bit perverse!

Barry



[Rd] Problem with distributing data in package.
Barry Rowlingson