More sophisticated relationships between annotations (v0.2)

[corot]

Following discussions on #1, why not to arrange annotations in a tree (following the Scene Graph concept)? (or other sophisticated configurations)

[corot]

From @jihoonl

Reference
Scene Graph : http://en.wikipedia.org/wiki/Scene_graph

While thinking about the relation between annotation and data, I am questioned the following. These are not for v0.1 development but for long-term view discussion.

Is Room annotatable?

For example, assumes that annotating the Inno Room where has Marcus's Desk, * Daniel's Desk* and Vending Machine. How the current design should represent this?

Can World Canvas represent the relation between two annotations?

Robot is located at Inno room in RnD Office in Namsung Plaza 6th floor. It need to go to KC's office in Yujin Headquarter in Namsung Plaza 12th floor. Can World Canvas represent relation between Inno room and KC's office? Something like the following.

This will allow to generate "global global" path plan something like

Marcus's Desk -> Inno Room -> Rnd Office entrance -> 6th Elevator -> 12th Elevator -> Yujin Headquarter Entrance -> KC's Office -> KC's desk.

Would it be feasible? Or too ambitious?

[jihoonl]

It would be hard to imagine without real examples. How about extracting models or descriptors out from usecase or examples as we need?

We have three usecases of World Canvas at the moment.

• Navigation Points
• AR Marker based Localization
• Virtual Obstacle

I will add up examples and some ideas as I come up with.

[jihoonl]

Navigation Example from #14

Robot navigates Marcus’s Desk to KC’s Desk. Robot stays at Inno room. Task storyline is the following.

1. Robot Wake up from docking station in inno room.
2. Goto Daniel’s Desk’s approach point.
3. Get document
4. Goto Inno room entrance’s approach point.
5. Interact with door.
6. Get to the another approach point.
7. Go to Yujin Rnd’s entrance’s approach point.
8. Interact with door.
9. Get to the another approach point.
10. Go to Elevator Approach point
11. Interact with elevator
12. Get into the elevator
13. Elevator go to 12th floor.
14. Get out from the elavator and goto elevator approach point.
15. Goto Headquarter’s door’s Approach point.
16. Interact with door
17. Get to the approach point inside the headquarter
18. Goto KC’s Office Approach point
19. Interact with KC’s office door
20. Get into the KC’s office approach point
21. Navigate to KC’s desk approach point
22. Chirp on him.

How should we model the locations to navigate the building?

[jihoonl]

This is annotation modeled Namsung Plaza I have in mind.

[jihoonl]

With this annotation tree.

This model have four different types of annotations.

Meta Location

• Inno Room - includes Daniel's desk, Marcus's desk, and Entrance in
• SW Team - includes Jihoon's Desk
• Yujin Rnd Office - Inno Room Entrance, SW Team, and Rnd Office Entrance In.
• 6th floor - Rnd Room entrance, Elevator Approach

Location

• Daniel's desk, Marcus's desk, and Jihoon's desk

Transitional Location

• Inno room Entrance - Shares map but requires door transition

Map transitional Location

• Rnd Office entrance
• Elevator Approach

where (map) transitional location requires transition method. With assumption that robot can move between children of same parent, it generates path like

Daniel's Desk -> Inno Entrance IN -- (transition) -- inno Entrance -> Rnd Entrance In -- (transition) -- (switch map to 6th floor) -- Rnd Entrance -> Elevator Approach -- (transition) -- Elevator -- .....

[jihoonl]

The other use cases are simple compare to navigation example.

Localization

Marker(or object) based Localization

It is annotating an existing object’s pose on the map. A pose message would be sufficient for its purpose.

Virtual Obstacle

To determine prohibited area where robot cannot visit.

• Regional prohibit zone - (Meta) Location from navigation example could also be representation of prohibited zone
• Column
• Wall
• Polygon
• ...

I have not thought about data model design which fits all these use cases yet though. I will come back when I get an idea..

[stonier]

@jihoonl Nice example for shaping thoughts, thanks.