Update HRIM structure

[ibaiape]

No description provided.

[hannibalhuang]

would be nice to have an overview description of the re-structure ?

[ibaiape]

@hannibalhuang

would be nice to have an overview description of the re-structure ?

Sure!

We are currently passing from a ROS 2 implementation of HRIM to an implementation generator. We are using XML to represent the models in a platform-independent machine-readable way and python for the tooling.

• The models directory holds all XML files: module models, common package definitions (i.e. generic to generate our ROS 2 hrim_generic_msgs), etc.
• The scripts directory holds function-specific python scripts.
• The templates directory holds plain text templates to generate needed files (CMakeLists.txt, package.xml for now)
• hrim.py is the main script and the one a user would interact with.

For more information you can look at our page or our docs. The script usage is available at our README.md. Do keep in mind this is a work in progress, every and any feedback is welcome!

[hannibalhuang]

@hannibalhuang

would be nice to have an overview description of the re-structure ?

Sure!

We are currently passing from a ROS 2 implementation of HRIM to an implementation generator. We are using XML to represent the models in a platform-independent machine-readable way and python for the tooling.

• The models directory holds all XML files: module models, common package definitions (i.e. generic to generate our ROS 2 hrim_generic_msgs), etc.
• The scripts directory holds function-specific python scripts.
• The templates directory holds plain text templates to generate needed files (CMakeLists.txt, package.xml for now)
• hrim.py is the main script and the one a user would interact with.

For more information you can look at our page or our docs. The script usage is available at our README.md. Do keep in mind this is a work in progress, every and any feedback is welcome!

Sounds awesome ! BTW I remember the doc mentioned there is also ongoing work with OMG regarding HRIM, do you have any pointers for that ?

[ibaiape]

@hannibalhuang

Sounds awesome ! BTW I remember the doc mentioned there is also ongoing work with OMG regarding HRIM, do you have any pointers for that ?

Nothing publicly disclosable yet, I'm afraid.

[hannibalhuang]

@hannibalhuang

Sounds awesome ! BTW I remember the doc mentioned there is also ongoing work with OMG regarding HRIM, do you have any pointers for that ?

Nothing publicly disclosable yet, I'm afraid.

any timeline for that ? It will be an open standard right ?

[vmayoral]

It will certainly be open. any timeline for that ? It will be an open standard right ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABT8DgZkbnQ6H9M5gjnyspFwjx-FaNKGks5u7H8_gaJpZM4Yqsei> .

-- *Víctor Mayoral Vilches* CTO & Co-Founder *Erle Robotics* erlerobotics.com | victor@erlerobot.com +34 616151561 *skype*: v.mayoral

[hannibalhuang]

It will certainly be open. any timeline for that ? It will be an open standard right ?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABT8DgZkbnQ6H9M5gjnyspFwjx-FaNKGks5u7H8_gaJpZM4Yqsei .
-- Víctor Mayoral Vilches CTO & Co-Founder Erle Robotics erlerobotics.com | victor@erlerobot.com +34 616151561 skype: v.mayoral

Great ! Anyways I'm interested in the effort and would like to be involved along the process if possible :)

[vmayoral]

@ahcorde, @ibaiape , let's please merge this ASAP. I'd like the XML version of HRIM to be in master branch.

[ahcorde]

Let's try to make smaller PR in the future please