Robotics Systems Types: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-07-26T09:50:03ZOpen Source Collaboration Platform
Redmine Tasks #2626 (In Progress): Separate libraries for protocol buffer converter plugins and specializ...https://code.cor-lab.de/issues/26262016-07-26T09:50:03ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p><code>rst-converters-cpp</code> has a bunch of optional dependencies which allow building plugins with specialized converters within the same build system as the protocol buffer converter plugins.</p>
Optional dependencies are suboptimal in themselves, but in this context, more problems arise:
<ul>
<li>The OpenCV plugin forces the whole <code>rst-converters-cpp</code> project to be built against a specific OpenCV version</li>
<li>The humavips and amarsi flavors of the project have caused countless headaches, especially for packaging</li>
<li>RCI in particular, with its Eigen dependency, has further aggravated the problem (<a href="https://code.cor-lab.de/issues/2625" class="issue tracker-1 status-3 priority-4 priority-default closed" title="rst-converters-cpp does not build with modern Eigen 3 versions (e.g. Ubuntu Xenial) (Resolved)">#2625</a>)</li>
</ul> Tasks #2617 (New): Please document usage of RST with RSBhttps://code.cor-lab.de/issues/26172016-07-19T14:57:50ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>A minimal informer/listener example for the supported languages would already be helpful that just shows:</p>
<ul>
<li>how to register / configure converters</li>
<li>the usage of RST types</li>
<li>the usage of typed RSB objects with these RST types</li>
</ul>
<p>This could become a section within the RST manual as there is also already a <em>Developer</em> tutorial:<br /><a class="external" href="http://docs.cor-lab.de//rst-manual/trunk/html/index.html">http://docs.cor-lab.de//rst-manual/trunk/html/index.html</a></p>
<p>However, developer does not mean usage here. Hence, we would need a <em>User</em> tutorial.</p> Tasks #2442 (New): Collect all necessary types for home automation patcheshttps://code.cor-lab.de/issues/24422015-11-23T10:56:12ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>The previous type proposal, <a href="https://code.cor-lab.de/issues/2144" class="issue tracker-5 status-6 priority-4 priority-default closed" title="Homeautomation Patch (Rejected)">#2144</a>, contains a set of homeautomation-related message type.</p>
<p>To make any progress in reviewing this proposal, we need multiple, small patches. While trying to apply graph-based methods for identifying subsets of messages for such patches, I noticed that the patch is incomplete. At least the following files are missing<br /><pre>
proto/sandbox/rst/vision/HSVColor.proto
proto/sandbox/rst/configuration/MetaConfig.proto
proto/sandbox/rst/person/Person.proto
</pre><br />(there may be more, but I stopped at that point).</p>
<p>Please attach a version of the patch to this issue that at least builds. I will try to repeat the analysis and suggest subsets for smaller patches after that.</p> Tasks #2441 (New): Integrate homeautomation typeshttps://code.cor-lab.de/issues/24412015-11-23T10:47:22ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #1724 (New): Document Windows Installation from Source and Binaryhttps://code.cor-lab.de/issues/17242014-01-23T12:54:29ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>Similar to RSB itself, we require documentation for installation of the C++ libraries on windows of RST. In particular for</p>
<ul>
<li>users that just want to use existing RST types and</li>
<li>developers that want to create or update existing data types.</li>
</ul> Tasks #1466 (New): Review and merge RST changes of ISY lecturehttps://code.cor-lab.de/issues/14662013-04-19T08:32:46ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>The ISY students currently (WS12/13) work on their own copy of the RST repository. We should decide when to merge (which) changes into RST master to make this visible to the wider public.</p> Tasks #1384 (In Progress): Highlight distinction between stable and sandbox types in generated ma...https://code.cor-lab.de/issues/13842013-02-01T17:07:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Ideas:
<ul>
<li>Add "stable"/"sandbox" and package name to breadcrumbs, if technically possible ✓</li>
<li>Add "draft" overlays to message icons for sandbox types ✓</li>
<li>Add unobtrusive "draft" background images to @<div/>@s containing documentation about sandbox types</li>
</ul> Tasks #1277 (In Progress): Reorganize directories to allow foreign types and mappingshttps://code.cor-lab.de/issues/12772012-11-30T20:04:37ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #842 (New): Extract Joint Mapping Information from JointState.proto into Seperate BodySchem...https://code.cor-lab.de/issues/8422012-02-02T14:16:01ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>Since the JointAngles representation is much more compact than the JointState but the mapping from vector indices to body schema elements is still a required information, a new type shall be created after the upcoming RST release.</p> Tasks #738 (New): Specify color modes in rst.vision.Image more preciselyhttps://code.cor-lab.de/issues/7382011-11-28T17:18:05ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>The current documentation is insufficient to e.g. find the correct fourcc code for <code>COLOR_YUV</code>.</p> Tasks #631 (Feedback): Make revisions for each IDL file available at runtimehttps://code.cor-lab.de/issues/6312011-10-14T15:18:55ZJ. Wienkejwienke@techfak.uni-bielefeld.de
Also as:
<ul>
<li>preprocessor declarations for C++</li>
<li>XML file or comparable for use outside of target languages or in external tools.</li>
</ul>