|
This is version 18.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
The following are the Usecases the terrestrial working group discussed during the July 2007 REAP Requirements Workshop.
The group also conducted some informal ranking of these. First, usescases were given a 1-3 importance ranking, with 1 being most important. Second, of those cases ranked 1, group members voted for a few they felt were most important or should be implemented first.
1) Detached Execution Importance: 1, votes: 4
2) Smart Reruns Importance: 2
3) Optional archiving of intermediate derived datasets. Importance: 2
4) Archive a complete end to end run ("publication ready archive") Importance: 1, votes: 5
5) Database actor option: Snapshot? Importance: 2
6) Actor specific annotations (gui linked) Importance: 2
7) Actor for Data-Merge for specific product Importance: 1, votes: 2
8) Integrate database actors Importance: 2
9) Event Notification Monitoring system Importance: 1
10) Search through workflow for a certain type of actor Importance: 2
11) Different workflow view Importance: 3
12) Manage a group of model runs Importance: 1, votes: 1
13) Workflows need to accommodate sub-workflows that operate at different frequencies Importance: 1, votes: 1
14) Tutorial or Wizard for wrapping external programs Importance: 1, votes: 4
15) Easily create and share workflows and actors Importance: 1
16) Improve component search. Importance: 1
17) facilitate peer review process Importance: 3
18) Use Kepler as a teaching tool Importance: 3
19) Ecological Actors Importance: 3
20) FakeData Generator Actor(s) Importance: 2
21) 3d plots Importance: 3
Iterator wrapper actor
22) Markov Chain Monte Carlo (mcmc) Importance: 3
23) Breakpoints Importance: 2
24) Debugging Importance: 2
25) Improved error messages. Importance: 1
26) Disable actors Importance: 2
|
