[kepler-dev] test data

[Bertram Ludaescher]

How about this:

1. Move all data away
2. See which demos break because of this (can we automatically test this?)
3. Isolate those "large data dependent demos" in a separate module
("demos-with-big-data")

Bertram

On Wed, May 27, 2009 at 3:09 PM, ben leinfelder
<leinfelder at nceas.ucsb.edu>wrote:

> I noticed some of the R demos reference data stored in that directory. It
> would make sense to include the test data for those demos in the same place
> as the actual R demo workflow that uses it for demonstration purposes.
> I'd move the data (to the R module) if I were sure no other demos used it.
> -ben
>
>
> On May 27, 2009, at 2:45 PM, Chad Berkley wrote:
>
>  Hi,
>>
>> In common/lib/testdata, there is currently 53.4 MB of data that gets
>> checked out every time we do a checkout.  I'm guessing that much of this is
>> rarely/never used.  Some of it is referenced in the user manual, however,
>> for the demos and tutorials.  I was wondering what people would think of
>> moving this test data to a new module that would be optional (i.e. not in
>> the kepler suite).  I could then have installers for the release that
>> include or not include it based on user preference.  We could also just
>> point people to the SVN web interface if they want to download test
>> datasets.
>>
>> Comments, other ideas?
>>
>> thanks,
>> chad
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20090528/309a079d/attachment.html>