Visualization agent

[argenos]

The following visualization proposals were accepted:

• Historical view Historical view #34
• Individual order status Visualizing individual order status #35
• Message queues by agent Visualizing the message queues by agent #36
• Order board Order board by stage #37
• Street network Street network visualization #38

The pull request should also contain their interfaces added to the base class (#39), so other teams can seamlessly integrate it into their projects.

The selected framework is JavaFX.

[argenos]

@HBRS-MAAS to clarify the deadline: although the complete functionality does not need to be there by next week, your messages and a prototype of your agent which can receive them are a good start for this assignment.

In case you don't want to implement the issue that was assigned to you, please write on this thread so other teams who might be interested can switch if they want. NB some of this might be converted into an assignment later on if not taken up by someone.

[anenriquez]

@HBRS-MAAS/mas_maas has decided to not implement their visualization issue.

[madmax2012]

@HBRS-MAAS/team_pjt Will implement their visualization task

[tmeule2s]

did anyone fix the build issue with javafx yet?

[argenos]

@HBRS-MAAS/ws18 please make sure that the README contains instructions on how to run your interface agents and visualization components. Remember that only interfaces and visualization that are merged and runnable from this repository will be counted. Deadline for this is Thursday 18:00.

[anenriquez]

Does the visualization agent should run in this repository? We have created the visualization for the doughPrep stage using the agents of our architecture, i.e., the visualizator not only receives messages from the proofer agent but also from other agents in our internal architecture. If we add visualization to upstream we would also need to include the internal agents of our doughPrep stage to this repository. Is this correct? Thanks!

[argenos]

No need to add your project agents here, however, the visualization should run even if it doesn't receive any updates. Keep in mind that, at least in theory, your interface agents should talk to your visualization component (I am aware that not all visualizations do this).

Your interface agents are a different story, those should run, regardless of the existance of your other agents.

[anenriquez]

Thanks for the quick reply. Unfortunately, our visualization will not work if it does not receive the messages sent by our agents. I opened a pull request with everything that the visualization needs. However, we understand if this is not sufficient for getting the visualization points.

[anenriquez]

Should we make the pull request to develop or to master? I have opened a new pull request to develop. Should I modify it to be merged into master? Thanks!