|
Difference between
version 24
and
version 3:
| Lines 1-2 were replaced by lines 1-2 |
| - There currently exist two prototype actors and a few workflows that use them. |
| - We will merge these actors, as well as continue to add functionality to them in the future. |
| + There currently exist two prototype Kepler actors that retrieve and output data from RBNB servers, and a few workflows that use them. |
| + We will likely merge these actors into one, as well as continue to add functionality to them in the future. |
| Line 6 was replaced by lines 6-13 |
| - RBNBToKepler operates on a timeslice of data from an RBNB server. The user points it at the server, specifies a time range, and optionally specifies channels to ignore (ie not download). |
| + RBNBToKepler2 operates on a timeslice of data from an RBNB server. The user specifies server, time range, and optionally channels to ignore, and the actor then retrieves and outputs data and associated timestamps through multiports. |
| + |
| + There are two demonstration workflows that use the RBNBToKepler2 actor that you can try from the [CVS version|http://kepler-project.org/Wiki.jsp?page=DevelopmentForKepler] of Kepler: |
| + * workflows/neon/RBNBToKeplerDisplay4SDF.xml (Creates plots) |
| + * workflows/reap/TerrestrialRBNB_QAQC.xml (Emails alerts) |
| + |
| + |
| + Attached below are some plots from the RBNBToKepler2 actor, results of sensor data being pulled from an RBNB server and plotted. For more details please see the [Terrestrial UseCase Hardware page|TerrestrialUseCaseHardware] |
Back to RBNB Sink Actor Design And API,
or to the Page History.
|
