Bug #4753
closedcreate gui for scheduled execution of sensor workflows on server
0%
Description
Provide a GUI to specify workflows to periodically run on a server. Configuration parameters include: the workflow xml, how often to run the workflow, etc. Note that the gui should provide a read-only view of the workflow: allow the user to see the workflow, but not edit it (this helps disambiguate the functionalities of engineering view and vanilla kepler). Additionally, include a template capability to allow the same workflow for multiple sensors.
See figures 6 and 7 in https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans
Related issues
Updated by Ilkay Altintas almost 15 years ago
This should have an option to run a workflow continuously.
Another idea is, can we change the frequency of a workflow execution based on sensor data? This might require adding a parameter for automatic management, e.g., if a value goes above a threshold, run x times faster.
Updated by Daniel Crawl over 14 years ago
This would be useful for any type of workflow, not just for the Engineering View.
Updated by Jing Tao about 14 years ago
Here are suggestions from Matt:
1)I in the scheduler, the list on the left should only show WF objects that can be scheduled.
2) Only being able to schedule wfs that have already been uploaded seems limiting. A better model would be to allow the user to schedule any wf (even local ones), but then prompt them that it will have to be uploaded to continue if its a local WF.
The third one - I make it as a new bug.
Updated by Jing Tao about 14 years ago
Item 1 on above was described in a new bug:
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5236
Item 2 on above was described in a new bug:
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5235
Updated by Jing Tao almost 14 years ago
This a general bug. The specific bugs have been created and fixed.
Updated by Derik Barseghian almost 14 years ago
changing bugs from REAP to Kepler product