Hi again, I will take the blue color for my answers On 01/07/15 17:17, Colombatto Davide wrote: Hi Iñigo and Gianmario, Below in red, some points/questions to Iñigo related to FIROSv2 and the RCM Feature “FIROS Interaction”. D Da: Iñigo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: mercoledì 1 luglio 2015 12:21 A: Bollano Gianmario; Colombatto Davide; Garino Pierangelo; fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] R: Demo Sprint 4.3.3 Hi, yesterday we tell fabio how to dissable the map server bring up in FIROS. We haven't said anything more because we were waiting to know the results of removing that configuration. FIROSv2 works near the same way as v1 does, the difference is that the configuration you add by hand in the v1's code now can be added in robots.json. Hence FIROSv2 works in the same way of FIROSv1 for what concern the hardcoded data (the only difference is that in FIROSv1 the data are put inside the code whereas in FIROSv2 they are in a config JSON file)? Consequently, this different behavior is not enough to show the RCM Feature “FIROS interaction” which is related to dynamically exchange these data btw RCM Driver and FIROS instead of keep them hardcoded. Firosv2 handles the robots in the same way as Firosv1 does. The difference is what you have said, that the configuration is not hardcoded in the code, it is in configuration files: - robots.json: Creates its robots' subscription and publishing topics. It doesn't matter if the robot doesn't exist (Firosv1 hardcoded robot does the same) - whitelist.json: On firos startup or when the robot connection api (rest or topic) is used, searches for the robots that matches with this whitelist and connects to it. It also has the firos-RCM integration, but it hasn't been tested, so maybe is better not to use it by now. Does FIROSv2 already implement the data exchange with RCM Driver using the protocol we have specified in the OpenSpec Draft (Pub/Sub and service)? The CB entity is created/deletes when FIROSv2 is started/stopped or when it receives the notification from RCM Driver? Even if the response are positive, the integration and test phase (i.e. correct data exchange through RCM Driver) requires more than 2 days. The reason is that, for now, Fabio (for RCM Driver) and you (for FIROS) have worked in a standalone way to implement the interaction but it is not sure that the two components really “talk” together in synch way. For instance, some issues about FIROSv2 is that it is not aligned with the OpenSpec Draft we wrote. Examples: · *.msg and *.srv files should be in a standalone ROS package “robotics_msgs” and not in the ROS package “firos” · in FIROSv2 there is RCM_Event instead of Robot_Event · In FIROSv2 there is FIROS_Info with “robot_name” instead of “instance_name” · … Said that, although we have closed the RCM Feature “FIROS interaction” in JIRA we cannot show it in the demo; for this reason I added additional workitems for the 4.4.1 related to Integration and Testing related to “FIROS interaction”. As I said before, it is done. While we where doing that draft we were developing the functionalities. But this haven't been tested so I am agree with you, it is better not to show it in the demo. To test it, is there a way to emulate what RCM provides us when a robot is connected and when we ask for robot topics? Tomorrow we will try FIROSv2 but the demo on Monday will have hardcoded data as using FIROSv1. Is it correct? What we can do to be able to test FIROSv2 is sending me the configuration you want (robots names, topics to work with, ports, context_broker ip...) and I'll send you back all the configuration files properly configured. We think that we still have 3 days to make trials with FIROSv2 and this time is enough to make it work, since we are already using it without any problems. Also, Gianmario, what do you want to say when you said the "FIROS interaction"? Robot connection, disconnection handler, and the RCM topics and services consuption? Regards, Iñigo On 01/07/15 12:04, Bollano Gianmario wrote: Hi all, at the yesterday call we set as an Action Point (AP0) to discuss and take a decision by e-mail (deadline was yesterday) on how and where hold the demo. Davide made a proposal and I could not see any feedback or further proposal from the other people in the team, than we should assume that proposal is accepted. Pier clearly explained that we should be able to demonstrate the development of the features closed in this minor release (4.3). In principle, development closed means that also the testing has been done and the feature is ready to be demonstrated. However, we do not need to add useless complication. What’s important for the demo is to clearly explain what we’ll show, not to provide tech details for the implementation. Considering the short time available, I’d propose: - In this demo we can focus on RCM actions, together with movement commands through FIROS (through CB). - If the integration of the last releases of RCM and of FIROS still has issues, we should safely use FIROSv1 and the settings proposed by Davide. - BTW, What are the results of tests done with last release of FIROS and RCM? Weren’t last issues solved anyway? - The only feature is not yet fully covered in the demo may be the FIROS.interaction; however this is something that a user cannot perceive without a more advanced GUI/widget . - Thus we can focus on showing that both FIROS and RCM are working and doing their tasks, and I’d omit any detail about their communication for this demo, because we do not have yet a nice way to show it anyway… - .. and we’ll show it at the first live demo! - Finally, go to the poll http://doodle.com/fb6gx4wbbqupwkwu and pick a timeslot for the call with Kurento/Wirecloud: we should not delay our answer further!!!! Gianmario Da: Colombatto Davide Inviato: mercoledì 1 luglio 2015 10:43 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Hi Pier, FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction> is intended as interaction between RCM and FIROSv2 through RCM Driver in order to exchange information. As already said in the past, this required more testing before show it in a demo (FIROSv2 was delivered last Friday). For this reason in the call of yesterday (and on Friday) we can show a pre-demo using FIROSv1 (which we think already implements the two Features SendNGSI/ReceiveNGSI due to the robot moves through the web-app). For now, FIROS Interaction is related to start/stop FIROS by RCM when a robot gets connected/disconnected whereas FIROS has already hardcoded the information to publish in the CB (i.e. CB-entity‘s name and attributes). Davide Da: Garino Pierangelo Inviato: mercoledì 1 luglio 2015 10:17 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Cc: Bollano Gianmario Oggetto: R: Demo Sprint 4.3.3 Dear All, I’d like to remind that the demo is intended to cover the advances in the implementation of a GE. In the case of the Robotics one, it should therefore show the functionality added by latest Features designed, i.e. the following (according to the technical workplan R4.3): * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.PlatformEvent> * FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.Robotics.RCMPlatformManager.FIROSInteraction> * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.SendNGSI> * FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.Robotics.FIROSContextBrokerManager.ReceiveNGSI> BR Pier Da: Colombatto Davide Inviato: martedì 30 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Cc: Garino Pierangelo; Bollano Gianmario Oggetto: Demo Sprint 4.3.3 Hi guys, as said in the call we (RCM team) propose to show the demo on TI’s office like that shown this morning. Some additional points: · Use hangout · Use FIROS vers1 · In addition to the FORWARD button I added a BACKWARD button in the web-app o The web-app is hosted in the local PC and not in a public Server · Use a hangout account to show the camera (which shows the robot) and another account to show the shared desktop (for the web-app and the REST-API calls through the Postman-plugin) · Use the two RDAPIs used this morning before and after Robot connection/disconnection in order to show the Robotics Config Data changes · RCM team is not able to retrieve/show information stored in the CB (we have not worked with the CB at all) o the unique feedback is the RDAPIs and the robot’s movement · Pre-demo: Friday, slot 11-12 I summarized our proposal in the attached file of this email; we could use it to prepare the presentation. Some additional points: · hidden slides have to be rewritten/completed · (if required) slide’s comments have to be rewritten Let we know, BR Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150702/0523b959/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy