<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 27.09.2012 08:51, Jakob Schwendner wrote:
<blockquote cite="mid:5063F75F.8050409@dfki.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 09/26/2012 04:59 PM, Alexander Duda wrote:
<blockquote cite="mid:5063183D.90000@dfki.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 09/26/2012 04:24 PM, Matthias
Goldhoorn wrote:<br>
</div>
<blockquote cite="mid:5063100D.60801@dfki.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 26.09.2012 16:22, Javier Hidalgo Carrió wrote:
<blockquote cite="mid:50630F89.9020605@dfki.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 09/26/2012 03:33 PM,
Matthias Goldhoorn wrote:<br>
</div>
<blockquote cite="mid:5063042B.7070602@dfki.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hmh, <br>
<br>
i think we should add base::Temperature analog to
base::angle WITHOUT an timestamp, becasue the temperature
can then be added to any class without duplicate the time
field.<br>
<br>
</blockquote>
In this case we will not be able to log the temperature
alone in a port with a timestamp. We will need to use the
timestamp from other port.<br>
</blockquote>
Thats the reason why you should add also the
"base::TemperatureReading" type, which includes the time and
the base::Temperature ;).<br>
<br>
In general in the past i was for an generic data type
Stamped<T> which is in general for this kind of thinks,
but there was some points against this, but i would like to
point to it again ;).<br>
</blockquote>
<br>
I do see Matthias point but I would rather go for:<br>
base::Temperature <br>
and<br>
struct base::samples::Temperature <br>
{<br>
base::Time time;<br>
base::Temperature temperature;<br>
}<br>
<br>
Alex<br>
<br>
</blockquote>
This seems to be most consistent with what we already have. Come
to think of it I wouldn't even mind having an origin string field
in the base::samples::Temperature type, as Matthias suggested.<br>
</blockquote>
One addition why i would like to have an origin field, the origin
field could be used for some user GUIs, that can be created
automatic an overview over all system temperatures, without needing
the gui-creation-user to know where temperature sensor is located,
and from what task they came and where the device for the task is
located inside the system. (for manual connecting gui-parts with
tasks)<br>
<blockquote cite="mid:5063F75F.8050409@dfki.de" type="cite"> <br>
Jakob<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rock-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rock-dev@dfki.de">Rock-dev@dfki.de</a>
<a class="moz-txt-link-freetext" href="http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev">http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dipl.-Inf. Matthias Goldhoorn
Space and Underwater Robotic
Universität Bremen
FB 3 - Mathematik und Informatik
AG Robotik
Robert-Hooke-Straße 5
28359 Bremen, Germany
Tel.: +49 421 178 45-4193
Zentrale: +49 421 178 45-6550
Fax: +49 421 178 45-4150
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:matthias.goldhoorn@uni-bremen.de">matthias.goldhoorn@uni-bremen.de</a>
Weitere Informationen: <a class="moz-txt-link-freetext" href="http://www.informatik.uni-bremen.de/robotik">http://www.informatik.uni-bremen.de/robotik</a></pre>
</body>
</html>