| Line 273 was replaced by line 273 |
| - Users would typically like this kind of system to run automatically and periodically on a cron or cron-like system that easy to setup. |
| + Users would typically like these kinds of workflows to run automatically and periodically on a cron or cron-like system that easy to setup. |
| Line 303 was replaced by lines 303-304 |
| - ----\\__Use Case Name__: Manage a group of model runs |
| + ---- |
| + \\__Use Case Name__: Manage a group of model runs |
| Line 307 was replaced by line 308 |
| - Users would like to be able to design a workflow that allows for the management of running a group of model runs. |
| + Users would like to be able to design a workflow that allows for the management a group of model runs. |
| Line 310 was replaced by line 311 |
| - * allowing user to redefine the parameter sweep partway through execution |
| + * allowing user to change course by redefining the parameter sweep part-way through execution |
| Line 312 was replaced by line 313 |
| - * groups sets of products produced in an understandable way (eg legend of params used on each graph, listed in metadata of products produced) |
| + * grouping sets of products produced in an understandable way (eg legend of params used on each graph, listed in metadata of products produced, output files grouped by name or directories, etc) |
| Line 325 was replaced by lines 326-327 |
| - User develops workflow that includes a parameter sweep component. parameter sweep actor's input port(s) are connected to parameters or parameter source(s). |
| + User develops workflow that includes a Parameter Sweep component. The input port(s) of this component are connected to parameters or parameter source(s) like a text file. |
| + |
| Line 328 was replaced by line 330 |
| - User designs a workflow that uses and changes parameter components. |
| + User designs a workflow that uses and changes (existing) Parameter components. |
| Line 339 was replaced by lines 341-342 |
| - ----\\__Use Case Name__: Instruction set for wrapping external program |
| + ---- |
| + \\__Use Case Name__: Tutorial or Wizard for wrapping external programs |
| Line 343 was replaced by line 346 |
| - Users would like to easily wrap an external program in Kepler. By "wrap" we mean create a simple workflow that consists of being able to run an external program that has already been developed, eg a C or fortran program. |
| + Users would like to easily wrap an external program in Kepler. By "wrap" we mean create a simple workflow that consists of being able to run an external program that has already been developed, eg a C or Fortran program. |
| Line 359 was replaced by line 362 |
| - User executes wizard inside Kepler, points it at their external program, configures any required settings via the wizard. |
| + User executes wizard inside Kepler, points it at their external program, and configures any required settings via the wizard. |
| Line 363 was replaced by line 366 |
| - User reads tutorial that explains how to "wrap" external programs |
| + User reads tutorial that explains how to "wrap" external programs and builds the workflow. |
| Line 375 was replaced by lines 378-379 |
| - ----\\__Use Case Name__: Easily create and share workflows and actors |
| + ---- |
| + \\__Use Case Name__: Easily create and share workflows and actors |
| Line 379 was replaced by line 383 |
| - Users want an easy way to create and share workflows with others. This means making sure exporting, emailing, and importing workflows is painless, or the submission of workflows/actors to a repository that others can access is painless. |
| + Users want an easy way to create and share workflows with others. This means making sure exporting, emailing, and importing workflows is painless, or the submission of workflows/actors to a repository that others can import from is painless. |
| Line 386 was replaced by line 390 |
| - # User1 exports or publishes component of workflow. |
| + # User1 exports or publishes component or workflow. |
| Line 399 was replaced by lines 403-404 |
| - ----\\__Use Case Name__: facilitate peer review process |
| + ---- |
| + \\__Use Case Name__: facilitate peer review process |
| Line 417 was replaced by lines 422-423 |
| - ----\\__Use Case Name__: use Kepler as a teaching tool |
| + ---- |
| + \\__Use Case Name__: Use Kepler as a teaching tool |
| Line 432 was replaced by line 438 |
| - \\__Notes:__ |
| + \\__Notes:__ There was a lock of discussion on how to "lock" things. with ideas ranging from simply changing the icon or color of the component to signify the user should not touch it, to more difficult to circumvent restrictions like a password. |
| Line 438 was replaced by lines 444-445 |
| - ----\\__Use Case Name__: Ecological Actors |
| + ---- |
| + \\__Use Case Name__: Ecological Actors |
| Line 451 was replaced by line 458 |
| - User makes use of new ecological components in library. |
| + User makes use of new ecological components in library as they would any other. |
| Line 462 was replaced by lines 469-470 |
| - ----\\__Use Case Name__: FakeData Generator Actors |
| + ---- |
| + \\__Use Case Name__: FakeData Generator Actor(s) |
| Line 466 was replaced by line 474 |
| - Users would like a set of FakeData Generator Actors appropriate to the REAP Case Studies. A FakeData actor should produce data in the same way a real data source would. For example, a "FakeData_CR800_Temperature" Actor might produce a datastream of temperature data at 1 "sample" per minute. The actual data in the datastream should be indecipherable from a real temperature datastream coming out of a Campbell CR800 datalogger deployed in the field. Somewhere in the metadata however, a FakeData Generator Actor should clearly identify itself (as being fake). |
| + Users would like a set of FakeData Generator Actors appropriate to the REAP Case Studies. A FakeData actor should produce data in the same way a real data source would. For example, a "FakeData_CR800_Temperature" Actor might produce a datastream of temperature data at 1 "sample" per minute. The actual data in the datastream should be indecipherable from a real temperature stream coming out of a Campbell CR800 datalogger deployed in the field. Somewhere in the metadata however, a FakeData Generator Actor should clearly identify itself (as being fake). |
| At line 468 added 3 lines. |
| + |
| + Depending on how exactly we wish to simulate certain datalogger datastreams, these specs need to be available during the development of this/these actor(s). |
| + |
| Line 484 was replaced by lines 495-496 |
| - ----\\__Use Case Name__: 3d plots |
| + ---- |
| + \\__Use Case Name__: 3d plots |
| At line 491 added 3 lines. |
| + |
| + 3d visualization software is installed on user's machine. |
| + |
| Line 503 was replaced by lines 518-519 |
| - ----\\__Use Case Name__: iterator wrapper actor |
| + ---- |
| + \\__Use Case Name__: Iterator wrapper actor |
| Line 523 was replaced by lines 539-540 |
| - ----\\__Use Case Name__: markov chain monte carlo (mcmc) |
| + ---- |
| + \\__Use Case Name__: Markov Chain Monte Carlo (mcmc) |
| Line 527 was replaced by line 544 |
| - Allow this different technique for running the model. Can not use if model is stochastic. |
| + Allow this different technique for running models. Can not use if model is stochastic. |
| At line 529 added 3 lines. |
| + |
| + An understanding of mcmc. :) |
| + |
| Line 540 was replaced by lines 560-561 |
| - ----\\__Use Case Name__: breakpoints |
| + ---- |
| + \\__Use Case Name__: Breakpoints |
| Line 544 was replaced by line 565 |
| - Users would like to be able to add breakpoints in a workflow. When a breakpoint is reached, workflow execution is paused or stopped. Users would also like breakpoints to be conditional, eg a breakpoint might only pause or stop execution once a certain condition (eg equilibrium) has been reached. |
| + Users would like to be able to add breakpoints in a workflow. When a breakpoint is reached, workflow execution is paused or stopped. Users would also like breakpoints to be conditional, eg a breakpoint might only pause or stop execution once a certain condition (like equilibrium) has been reached. |
| Line 557 was replaced by lines 578-579 |
| - ----\\__Use Case Name__: debugging |
| + ---- |
| + \\__Use Case Name__: Debugging |
| Line 561 was replaced by line 583 |
| - Users would like an easy way to debug workflows. Some ideas on this: a special debug output port on all actors, a specific debug actor (most workflow developers make extensive use of the display actor to verify output after each step as they build workflows--new users might not think of this, an actor named or tagged Debug might be of use) |
| + Users would like an easy way to debug workflows. Some ideas on this: a special debug output port on all actors; or a specific debug actor (most workflow developers make extensive use of the display actor to verify output after each step as they build workflows--new users might not think of this, an actor named or tagged Debug might be of use) |
