Feature #391
Implement instrumented OMF Application for GPS Support in GEC9 Demos
| Status: | Closed | Start date: | 06/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | 25/10/2010 | |
| Assignee: | Christoph Dwertmann | % Done: | 100% |
|
| Category: | OMF Software | |||
| Target version: | OMF 5.3.1 |
Description
Features for GEC9 Demos are described on this page.
Detailed description of this feature is available of this page.
The following new OMF instrumented application is required:
- F - GPS Support in OMF/OML for GEC9 Demo:
- use GPSD to make GPS information available to both local EC/RC (via OML) for local GPS-triggered events and remote OML server for overall experimental measurements
- create related documentation/tutorial to explain how to use this feature
Note: The developed code and related documentation in this issue should be part of the OML Application project, however we keep the issue under OMF to centralise in a unique "Target Version" all the issues related to GEC9 Demos. (i.e. Redmine seems not to allow tickets from one project to be associated to target versions of another)
History
Updated by Christoph Dwertmann over 1 year ago
- Status changed from New to Assigned
Capturing latitude, longitude, elevation, GPS supplied timestamp and data format.
Updated by Christoph Dwertmann over 1 year ago
- % Done changed from 0 to 50
The GPSlogger application has been finished and uploaded to the OML apps git.
Updated by Christoph Dwertmann over 1 year ago
- Status changed from Assigned to Resolved
- % Done changed from 50 to 100
GPSlogger has been tested with a sample GPS walk. Created an application definition and an experiment for it. Wrote a tutorial on how to use it.
Updated by Thierry Rakotoarivelo over 1 year ago
- Status changed from Resolved to Assigned
- % Done changed from 100 to 70
Hi Christoph,
Could you please update the tutorial as follow:
- cross-links to other tutorial (e.g. refer to how to access testbed, access result, use 3rd party application etc...)
- add more context, for example the current tutorial says: "add the gpslogger binary to a tar archive: tar cf gpslogger.tar gpslogger" but what are we suppose to do with that tar after? does it stay on the laptop? does it goes onto my EC machine? etc...
- run a real OMF experiment with that and describe results as collected by OML in the general case (i.e. through a database) rather than in a particular case of dump into file. Indeed, the database that we get from the result AM is different from the one we get from the file which is described in the tutorial
- chase Max to get the either his new visualisation for Maps or how to use the old one, either way the tutorial will be only complete with an OMF-based visualisation.
Examples of tutorials are:
- http://omf.mytestbed.net/projects/omf/wiki/OMLWrapperHowTo
- http://omf.mytestbed.net/projects/omf/wiki/BasicTutorialStage1-5-3
Updated by Thierry Rakotoarivelo over 1 year ago
Incidentally, although the gpslogger is part of "OML Application" repository, there is no mention or description of it within the corresponding wiki pages. Maybe we should have something there, or at list in the front-page list of available apps (and why it is different from the previous oml2 gps app)
Updated by Christoph Dwertmann over 1 year ago
- added cross link on how to run 3rd party apps. A link for how to access results was already there. A link on how to access a testbed is not needed here, since this scenario assumes that you have your own mobile node (e.g. car) instead of someone else's fixed testbed.
- you're not supposed to do anything with the tarball, just leave it where it is. Clarified that in the guide.
- replaced text results with result in SQLdump format. The data is the same, just the format is slightly different.
- added a page to OML apps that describes the GPS logger here
Updated by Thierry Rakotoarivelo 12 months ago
- Status changed from Assigned to Resolved
- % Done changed from 70 to 100
Updated by Christoph Dwertmann 12 months ago
- Target version changed from OMF 5.3.GEC9 to OMF 5.3.1
Updated by Thierry Rakotoarivelo 12 months ago
- Status changed from Resolved to Closed