Community
Participate
Working Groups
Text from Matthias Filter on the STEM newsgroup (http://www.eclipse.org/forums/index.php/mv/msg/423684/967553/#msg_967553) Motivation: For STEM users it would be great if they could use a disease model library comparable to the build-in model library. As disease model generation from scientific literature and historical epidemiological data is a highly complex and tricky issues it might be reasonable to create an open community repository where all STEM users could contribute (and describe) their models to. This idea could of course be extended to other scenario components later as well. As discussed today it is clear that such an eclipse-independent repository could provide resources in different levels of complexity (listed from easy to complex): 1. a simple repository of STEM scenarios (including meta data on the scenario) 2. a repository of parameterized standard disease models 3. a repository of other standard STEM modules (graphs, models, decorators, triggers etc.) 4. a repository of Code-Generator created disease model plug-ins - this would at minimum mean that a disease model integration via the update-site mechanisms need to be implemented into STEM I leave the question which implication each of the options have open to discussion
Some items I remember we discussed on the call a week ago: 1. Alex (correctly) pointed out that we cannot export a scenario right now, only the whole project. Exporting a scenario involved also exporting all models, graphs etc that's most likely located in separate files. This is a TODO. Should plugin resources also be exported? 2. Do we distribute new models of disease etc. via update sites? When a scenario contains a disease that's not distributed in the STEM binary download, it would be nice if we could point users to an update site containing the necessary plugins (maybe via a DC attribute?). We would need to provide instructions on how users would set up their own update site for STEM to share their models of disease. How does new disease plugins get published on the update sites? 3. Our current library of built-in scenarios is pretty useless. There's no reason why we couldn't allow users to distribute and share plugins that adds new scenarios to that view. If this is how we decide to share scenarios, the discussion under 2 becomes moot since plugin dependencies can be defined directly. Another thought about sharing scenarios is that it makes sense to share everything except the initial condition. If scenarios are validated to be realistic and useful, the only thing that varies between outbreaks is the initial condition. / Stefan
