Tool for making a graph of the IMC communication

[Kristoffer Gryte]

Hi,

I think a great tool for the LSTS toolchain would be something that could display the different tasks in DUNE and how they communicate with the different IMC messages, similar to the rqt_graph in ROS (http://wiki.ros.org/rqt_graph). This would be a great resource for people that are new to DUNE (e.g. master students). I have started using/recommending Sourcetrail (https://www.sourcetrail.com/) for getting a quick overview of "new" parts of the DUNE code, but often find two questions unanswered: "Who receives this IMC message?" and "Where does this message come from?".

I once started on a simple script based on sed and grep (non of which I am fluent in), but I did not quite succeed. 

My questions are:

1) Does there exist something like this already that I'm not aware of? 

2) Do you think that a sed/grep-based approach is the best way forward? I assume that I'm not the only one that struggles a bit with this problem from time to time, so perhaps someone has found a solution that is a lot smarter. Obviously the challenge with the sed/grep -approach is to find the type of the variables that are dispatched.

I imagine that visualization can be easily achieved by e.g. graphviz.

Appreciate any inputs on this :)

[José Braga]

Hi,

José Pinto wrote: https://github.com/zepinto/DuneInspector

Which shall help you

Kind Regards,

José Braga

--
www.github.com/LSTS/
www.lsts.pt
---
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchain+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/ced58957-8a90-4ac6-a855-82d5e5dde9b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristoffer Gryte]

Wow, great! :)

Thanks alot!

Kristoffer

fredag 26. januar 2018 17.51.56 UTC+1 skrev José Braga følgende:

Hi,

José Pinto wrote: https://github.com/zepinto/DuneInspector

Which shall help you

Kind Regards,

José Braga

2018-01-25 22:45 GMT+00:00 Kristoffer Gryte <kristoff...@gmail.com>:

Hi,

I think a great tool for the LSTS toolchain would be something that could display the different tasks in DUNE and how they communicate with the different IMC messages, similar to the rqt_graph in ROS (http://wiki.ros.org/rqt_graph). This would be a great resource for people that are new to DUNE (e.g. master students). I have started using/recommending Sourcetrail (https://www.sourcetrail.com/) for getting a quick overview of "new" parts of the DUNE code, but often find two questions unanswered: "Who receives this IMC message?" and "Where does this message come from?".

I once started on a simple script based on sed and grep (non of which I am fluent in), but I did not quite succeed. 

My questions are:

1) Does there exist something like this already that I'm not aware of? 

2) Do you think that a sed/grep-based approach is the best way forward? I assume that I'm not the only one that struggles a bit with this problem from time to time, so perhaps someone has found a solution that is a lot smarter. Obviously the challenge with the sed/grep -approach is to find the type of the variables that are dispatched.

I imagine that visualization can be easily achieved by e.g. graphviz.

Appreciate any inputs on this :)

--
www.github.com/LSTS/
www.lsts.pt
---
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.

To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.