Aside from maximizing the MTBF to meet industrial standards, the pace at which API either change or deprecated is also another topic to address. <div><br></div><div>There is also the issue of dependence on other libraries for important functionality, (OpenCV, PCL etc.). OpenCV seems fairly stable, but PCL like ROS is still 'settling in'.</div>
<div><br></div><div>How would we reconcile the need for new 'certified versions' to be backwards compatible with older certified releases, and the need to incorporate new, cutting edge packages so that ROS can grow as a whole?</div>
<div><br></div><div>K<br><div>
<br><div class="gmail_quote">2012/4/16 Adolfo Rodríguez Tsouroukdissian <span dir="ltr"><<a href="mailto:adolfo.rodriguez@pal-robotics.com" target="_blank">adolfo.rodriguez@pal-robotics.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div>On Mon, Apr 16, 2012 at 4:40 AM, Jonathan Bohren <span dir="ltr"><<a href="mailto:jonathan.bohren@gmail.com" target="_blank">jonathan.bohren@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Sun, Apr 15, 2012 at 9:31 PM, Edwards, Shaun M. <span dir="ltr"><<a href="mailto:sedwards@swri.org" target="_blank">sedwards@swri.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I agree that hardware drivers are a good place to start. However, I think the sooner we can certify ROS core (communications, node handling, etc..), the better. </div></blockquote><div> </div></div></div><div>I know this is the first question I get asked by someone unfamiliar with ROS when I mention it. This is an especially important focus here at Hopkins where so many research systems are being developed for applications with high-cost-of-failure like robotic surgery, deep sea exploration, and on-orbit telerobotics.</div>
</blockquote></div><div><br>I see two very valid and mostly orthogonal use cases so far.<br><br>1. Ensuring that certain core ROS functionalities comply with some (3rd-party certified) criteria, so that people that deal with high-cost-of-failure or safety-critical systems can trust what they are using.<br>
<br>2. Ensuring that a certain piece of hardware/software is ROS-compatible, so that people that venture into using them can expect compliance with specified ROS interfaces (no surprises attached).<br><br>I see great value in both, but to clarify, my initial answer to this thread was oriented mostly towards 1.<span><font color="#888888"><br>
<br>Adolfo.<br><br></font></span></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><span><font color="#888888">
<div><br></div><div>-j</div><br>-- <br>Jonathan Bohren<div>PhD Student</div><div>Dynamical Systems and Control Laboratory</div><div>Laboratory for Computational Sensing and Robotics</div>
<div>The Johns Hopkins University</div><div><br></div><div><a href="tel:%28707%29%20520-4736" value="+17075204736" target="_blank">(707) 520-4736</a></div><div><a href="mailto:jbo@jhu.edu" target="_blank">jbo@jhu.edu</a></div>
<div><br></div>
</font></span><br></div><div>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></div></blockquote></div><br><br clear="all"><div><div><br>-- <br>Adolfo Rodríguez Tsouroukdissian<br>Robotics engineer<br><a href="mailto:adolfo.rodriguez@pal-robotics.com" target="_blank">adolfo.rodriguez@pal-robotics.com</a><br>
<a href="http://www.pal-robotics.com/" target="_blank">http://www.pal-robotics.com</a><br>
<br>PAL ROBOTICS S.L<br>c/ Pujades 77-79, 4º4ª<br>08005 Barcelona, Spain.<br>Tel. <a href="tel:%2B34.93.414.53.47" value="+34934145347" target="_blank">+34.93.414.53.47</a><br>Fax.<a href="tel:%2B34.93.209.11.09" value="+34932091109" target="_blank">+34.93.209.11.09</a><br>
<br>AVISO DE CONFIDENCIALIDAD: Este mensaje y sus documentos adjuntos, pueden contener información privilegiada y/o confidencial que está dirigida exclusivamente a su destinatario. Si usted recibe este mensaje y no es el destinatario indicado, o el empleado encargado de su entrega a dicha persona, por favor, notifíquelo inmediatamente y remita el mensaje original a la dirección de correo electrónico indicada. Cualquier copia, uso o distribución no autorizados de esta comunicación queda estrictamente prohibida.<span style="border-collapse:collapse;font-size:13px"><span style="border-collapse:collapse;font-size:13px"><span style="font-size:13px"><tt><font face="'times new roman', serif"><font color="#333333"><br>
<br></font></font></tt></span></span></span>CONFIDENTIALITY NOTICE: This e-mail and the accompanying document(s) may contain confidential information which is privileged and intended only for the individual or entity to whom they are addressed. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of this e-mail and/or accompanying document(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender at the above e-mail address.<br>
</div></div><br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div></div>