0327 » History » Version 4
Ellon Paiva Mendes, 2018-03-27 19:13
| 1 | 2 | Ellon Paiva Mendes | h1. 03/27 : Yet Another PoM/Prism Discussion |
|---|---|---|---|
| 2 | 3 | Ellon Paiva Mendes | |
| 3 | *Participants*: |
||
| 4 | Andrea, Ellon, Pierre, Quentin |
||
| 5 | |||
| 6 | |||
| 7 | *Goal of the meeting*: Discuss implementation details of PoM/Prism and try to take a decision about how to proceed. |
||
| 8 | |||
| 9 | h2. Discussion |
||
| 10 | |||
| 11 | *1. About accessing the time* |
||
| 12 | |||
| 13 | * We agreed that we should have a core library managing the time. This library would be used by all DFNs and DFPCs that wanted to get the current time. |
||
| 14 | 1 | Ellon Paiva Mendes | * This is in opposition to have PoM/Prism publishing timestamps on topics that would be used by other modules. This simplifies the access to time, and removing some complexity of the system to be designed |
| 15 | 4 | Ellon Paiva Mendes | * If we will need time synchronized between multiple robots the time library would be updated with mechanisms allowing time synchronization. The interface with the modules would be the same. |
| 16 | 3 | Ellon Paiva Mendes | |
| 17 | *2. About interfaces* |
||
| 18 | |||
| 19 | * There was some discussion about how to design our code (in general, not only related to POM/Prism). |
||
| 20 | 4 | Ellon Paiva Mendes | * We agreed that we should design our code on layers, from core ASN.1-free libraries, to ASN.1 dependent layers (probably the DFNs and DFPCs) and up to the modules/nodes that relate with the middleware, more or less how it is shown in the figure below. |
| 21 | 3 | Ellon Paiva Mendes | |
| 22 | 1 | Ellon Paiva Mendes | * ADD FIGURE |
| 23 | 3 | Ellon Paiva Mendes | |
| 24 | 4 | Ellon Paiva Mendes | * There was no agreement if bitstreams should be included or not on the ASN.1 layers. Quentin and Pierre are mostly in favour of the addition, while Andrea and Ellon were against it. |
| 25 | * We agreed that this was not a big problem if interfaces for both ASN1 C-structs and ASN.1 bitstreams were implemented. |
||
| 26 | 3 | Ellon Paiva Mendes | |
| 27 | 1 | Ellon Paiva Mendes | |
| 28 | *3. About PoM/Prism design* |
||
| 29 | |||
| 30 | 4 | Ellon Paiva Mendes | * Recap of what we want for PoM: |
| 31 | ** PoM = Prism + Mighty Localizer |
||
| 32 | ** Prism |
||
| 33 | *** Maintain internal frames |
||
| 34 | *** Export frames (How? TBD) |
||
| 35 | *** Receives "Joint States" |
||
| 36 | ** Mighty Localizer |
||
| 37 | *** Receives robot poses at given times (from localization modules) |
||
| 38 | *** Responsible for fusion of poses |
||
| 39 | *** Exports the latest robot pose |
||
| 40 | *** Maintain/Manages past robot poses |
||
| 41 | |||
| 42 | * There were two main propositions, given that time access was simplified by assuming the existence of a time library. |
||
| 43 | * Proposition #1: |
||
| 44 | |||
| 45 | * ADD FIGURE |
||
| 46 | |||
| 47 | * Proposition #2: |
||
| 48 | |||
| 49 | * ADD FIGURE |
||
| 50 | |||
| 51 | |||
| 52 | |||
| 53 | |||
| 54 | 3 | Ellon Paiva Mendes | *4. About using genom-ros or only ROS* |
| 55 | |||
| 56 | |||
| 57 | 1 | Ellon Paiva Mendes | |
| 58 | |||
| 59 | h2. Open questions |
||
| 60 | 4 | Ellon Paiva Mendes | |
| 61 | |||
| 62 | * Where to put the interface between ASN.1 C-structs and ASN.1 bitstreams? |