Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Review hironx-nextageopen system component diagram for users #59

Closed
130s opened this Issue Mar 7, 2014 · 3 comments

Comments

Projects
None yet
2 participants
Member

130s commented Mar 7, 2014

Please review @k-okada, and anyone who's interested in I'll give edit right if you request against. You know I'm so bad at drawings.
https://docs.google.com/drawings/d/12jyX6fGuVDiIJpACxixHhZ_Z8IdO1yIcJhkkrJ7B0Pk/edit?usp=sharing

Doesn't have to be completely detailed but needs to be exhaustively and collectively descriptive for the robot users.

@130s 130s added the enhancement label Mar 7, 2014

Member

130s commented Mar 19, 2014

Diagram updated.

Owner

k-okada commented Mar 19, 2014

Sorry for late, that seems better,

  1. what's is the difference between Uses/Sends
  2. It may depends on how you interpret this diagram, but hrpsys(rtcd) does not run Ubuntu side, it is running on QNX side
  • use different shape for different concept / layer
    1. two main concept is QNX/Ubuntu hardware machine and ROS/OpenRTM communication world
    1. then we have package name layer (openrtm_aist, hrpsys, openhrp3, hironx_ros_bridge,,,,)
    1. then we have executable program or script file name layer
    1. we may have library layer between 2 and 3 (OpenHRP3 libraries, or using hironx_client.py as modules)
    1. we can create message layer that indicate what kind of messages are send between programs.
Member

130s commented Apr 15, 2014

Though not complete, I changed a lot. The image in the previous comment should reflect the change.

@130s 130s added the documentation label Apr 30, 2014

@k-okada k-okada closed this Jul 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment