[Fiware-robotics] Robotics call - minutes

[Thomas Michael Bohnert]

ment HI all,

Please apologize my absence yesterday. I had a full-day management training.

I went through the minutes and I appreciate the good advances you made. 
I am, in particular, looking forward to the technical proposal you plan 
to share with me.

There are a number of references to KIARA. Indeed, I spent the time 
after the KOM intensively with KIARA and we make good progress. The call 
on Thu will be a good chance to inform all of you and I will dully do so.

Cheers, Thomas

On 10/07/2014 05:41 PM, Garino Pierangelo wrote:
> Hi All,
>
> this is a short summary of our Robotics confcall.
>
> It’s rather schematic, please add anything you could consider worth to
> include to make it clearer. As said, next time we’ll use a shared
> document so that everybody can add own contributions whenever necessary.
>
> Pier’ intro/agenda:
>
> ·First item to address is defining the approach for robotics
>
> ·Afterwards we’ll have to:
>
>       o Agree on the architecture
>           + Submit to Thomas a proposal for his vision on the point
>       o Define who does what
>       o Define the roadmap of GE developments
>
> Robotics calls:
>
> ·1 weekly call
>
> oAgreement on date/time:
>
> oBetter beginning or at the end of day for Exte-tar
>
> oBetter beginning of the day for Roberto
>
> o10am of Thursday is fine for everybody
>
> ·AP: Pier to organise the shared doc for minutes and send periodic
> calendar reminder
>
> ·Note: Every 2 weeks there is an I2ND chapter PhC (Thu @ 11am)
>
> Angel: are we going to use JIRA or not?
>
> ·There will be JIRA tracker for Robotics
>
> _Discussion on Scenarios_
>
> __
>
> Pier concerning first item of agenda: the overall robotics approach in
> FIWARE should consider the following:
>
> oOur proposition must be targeting users like i.e. SMEs, start ups, etc
> in the full spirit of the FIWARE and FI-PPP initiative
>
> oWe want to provide functionalities to ease robot management in FIWARE
>
> oWe want to support a wide range of possible implementations
>
>           +  From sophisticated to dumb robots
>           +  From single to many robots
>
> __
>
> __
>
> ·ET proposal: Worries about latency when outside a local network
>
> ·TI: different tasks should be considered
>
> ·Reactive tasks: can be placed on the RCM
>
> ·(simplified) sequence diagram sent by Roberto
>
> oSome task can be moved to the robot side, in case of more performant device
>
> oOthers can be moved to the platform side
>
> ·ET: Agreement on the basics of the architecture, but:
>
> ·No raw data from robot to platform.  However, this is not raw data to
> high level application
>
> What would be the KIARA role in Robotics GE?
>
> Two main components:
>
> ·Robot clone (RCM)
>
> ·FI-ROS (translator to NGSI)
>
> oET: translating into different protocols; it does also additional
> functionality, like Making robots talk to each other
>
> oRoberto: there is not a single ROS core, but several, one for each
> container
>
> Need to identify the behaviour of each component in the Robotics GE
>
> Roberto: Decentralise to share functionality in a platform
>
> Question by Angel: what are the ways for a web developer to write a
> robotics application?
>
> According to Roberto:
>
> ·access to APIs of the platform,
>
> ·plus maybe some IoT interaction,
>
> ·the like done when developing an app for a smartphone (don't like to
> manage data of a single sensor, but rather some higher level functionality)
>
> Angel: we should have one way to talk to the robot
>
> ·This is within FIWARE in the case of the ET example
>
> ·Roberto: agree on this approach
>
> What would be the communication with FIWARE?
>
> ·Communication should go through KIARA (always?)
>
> ·Single northbound interface, and one only way to interact with robots
>
> ·What about NGSI??
>
> ·We need to understand better KIARA beforehand
>
> ·FI-ROS should be the communication channel towards FIWARE
>
> ·Also top to bottom it is the way to communicate to robots or through
> the RCM
>
> oIf RCM is used, then it is in the cloud
>
> oIf using directly FI-ROS, then it can be on the robot
>
> Roberto: In the case of RCM communicating with robot, KIARA is most
> likely not used
>
> ET: We'll do the exercise to put the functions in the boxes, and compare
> them
>
> Roberto: Some issue to understand the 'grab me a soda' scenario
>
> Is FI-ROS a bridge?
>
> ·Roberto: in this case it would be helfpul to expose the platform APIs
> through it
>
> FI-ROS is on the robot or on the Robot Clone Manager, always a way to
> talk to the robot is present
>
> ·Single way to talk to the robot
>
> Roberto: RCM is not only ROS
>
> ·it can be multiple ROSes,
>
> ·which are managed as a platform
>
> AP:ET will update the diagram and share this with all
>
> AP:TI to update it accordingly
>
> ·reminders for I2ND call on Thu:
>
> ·We need to have more ideas on KIARA
>
> ·Ask information on OFNIC
>
> Angel: What about asking Ogilvy about the scenarios we're going to provide?
>
> ·It can be a very high level video promoting robotics in FIWARE
>
> ·We'll agree on the contents
>
> ·Pier: Let's talk about it in the call I2ND
>
> Closing the call at 4:30pm
>
> BR
>
> Pier
>
> ------------------------------------------------------------------
> *Telecom Italia
> *Pierangelo Garino
> Innovation – Research & Prototyping
>
> Via G. Reiss Romoli 274, I-10148 TORINO
>
> Tel: +39 011 228 7142
>
> 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./
>
> *rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non
> è necessario.*
>
>
>
> _______________________________________________
> Fiware-robotics mailing list
> Fiware-robotics at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-robotics
>