Re: Updated dataflow semantics for RTT
S Roderick <[email protected]> Mon, 28 Sep 2015 13:14:50 +0000 (GMT)
| Newsgroups | gmane.science.robotics.orocos.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0853831525== Content-type: multipart/alternative; boundary="Boundary_(ID_lXI83yS+pnuiPg7R0XI1AA)" --Boundary_(ID_lXI83yS+pnuiPg7R0XI1AA) Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: quoted-printable On Sep 28, 2015, at 08:55 AM, Sylvain Joyeux <[email protected]> wrot= e:=0A=0ABut I do not agree with the analysis that RTT is the best thing to= hide=0Acomputations: I have seen way too many control loops implemented w= ith one=0Asingle Orocos component (and activity) per block in a Simulink-l= ike data=0Aflow... Way too many.=0A=0ALike ... iTasc ?=0A=0AUnless you mak= e a system too constrained to be actually useful, there=0Awill always be r= oom to misuse it. That does not spell that the system=0Aitself is bad, onl= y that "best practices" suck (or are inexistent).=0AThis is a neverending = fight, but IMO the solution is education, not=0Asome horrible model-based = environment too complex to every be used.=0A=C2=A0=0A+1, nicely summarized= .=0AS= --Boundary_(ID_lXI83yS+pnuiPg7R0XI1AA) Content-type: multipart/related; boundary="Boundary_(ID_xEMIrgUJowPtLRNkhxgeqg)"; type="text/html" --Boundary_(ID_xEMIrgUJowPtLRNkhxgeqg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable <html><body><div><span style=3D"line-height: 1.5;">On Sep 28, 2015, at 08:55 AM, Sylva= in Joyeux <[email protected]> wrote:</span></div><div><br></div= ><div><blockquote type=3D"cite"><div class=3D"msg-quote"><div class=3D"_st= retch"><blockquote class=3D"quoted-plain-text" type=3D"cite">But I do not = agree with the analysis that RTT is the best thing to hide</blockquote><bl= ockquote class=3D"quoted-plain-text" type=3D"cite">computations: I have se= en way too many control loops implemented with one</blockquote><blockquote= class=3D"quoted-plain-text" type=3D"cite">single Orocos component (and ac= tivity) per block in a Simulink-like data</blockquote><blockquote class=3D= "quoted-plain-text" type=3D"cite">flow... Way too many.</blockquote><span = class=3D"body-text-content"><br>Like ... iTasc ?<br><br>Unless you make a = system too constrained to be actually useful, there<br>will always be room= to misuse it. That does not spell that the system<br>itself is bad, only = that "best practices" suck (or are inexistent).<br>This is a neverending f= ight, but IMO the solution is education, not<br>some horrible model-based = environment too complex to every be used.</span></div></div></blockquote><= span> </span></div><div>+1, nicely summarized.</div><div>S</div></body></html>= --Boundary_(ID_xEMIrgUJowPtLRNkhxgeqg)-- --Boundary_(ID_lXI83yS+pnuiPg7R0XI1AA)-- --===============0853831525== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Orocos-Dev mailing list [email protected] http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev --===============0853831525==--