[kepler-dev] test data

[Chad Berkley]

agreed.  Maybe we should do an "outreach" module and include the demos, 
test data, additional documentation, etc in one module.

chad


ben leinfelder wrote:
> I think the approach sould be to include test/demo data along with the 
> demo that uses/relies on it.
> Perhaps this should be a "demos" module that is optional?
> I'm leery of giving people demo workflows in common/demos that will only 
> work if they have the foresight to include the optional "test data" module.
> -ben
> 
> On May 27, 2009, at 3:01 PM, David Welker wrote:
> 
>> Hi Chad,
>>
>> Thanks for catching this potential optimization. That is pretty major. 
>> This sounds like a great idea. Any objections?
>>
>> David
>>> 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
>