Robotics Systems Types: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732017-09-14T15:13:06ZOpen Source Collaboration Platform
Redmine Feature #2737 (Feedback): Add "Corenlp Dependency Tree" to SpeechHypothesishttps://code.cor-lab.de/issues/27372017-09-14T15:13:06ZD. Hamanndhamann@techfak.uni-bielefeld.de
<p>branched from 0.15 and like to have it added to 0.15</p> 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> Bug #2612 (New): Wrong RST version used in python when building downstream project with setuptoolshttps://code.cor-lab.de/issues/26122016-07-14T14:59:59ZN. Kösternkoester@techfak.uni-bielefeld.de
<a name="Issue"></a>
<h2 >Issue<a href="#Issue" class="wiki-anchor">¶</a></h2>
<p>There is a bug which leads to python processes silently using old/not the newest RST version. To reproduce one has to</p>
<p>1. Install RST (eg. rst0.13.3)</p>
<ul>
<li>This installs RST but uses custom CMake magic to create the egg file, copy it into the lib folder and also write a <strong>rst$VERSION.pth</strong> file. This does not include crating/updating the <strong>easy-install.pth</strong> in the according lib folder as used by setuptools.</li>
</ul>
<p>2. Install a downstream python project with setuptools (used setuptools version 18.8.1) that reqires RST in the same prefix</p>
<ul>
<li>Setuptools by default checks the <strong>easy-install.pth</strong> file and updates it accordingly if RST is present and writes down the version number (rst0.13.3)</li>
</ul>
<p>3. Make changes to RST and re-install it (will lead to rst0.13.4)</p>
<ul>
<li>Same process as above.</li>
</ul>
<p>4. Update the downstream python project</p>
<ul>
<li>Setuptools will <strong>only</strong> check the <strong>easy-install.pth</strong> and realise that the version number written there (rst0.13.3) is within your provided range (eg. rst>=0.13) and therefore make the installation use this (the old) RST lib instead of the newer and installed version (rst0.13.4)</li>
</ul>
<a name="Possible-fix"></a>
<h2 >Possible fix<a href="#Possible-fix" class="wiki-anchor">¶</a></h2>
<p>When using the toolkit, one might add this post build hook:</p>
<pre>
export PYTHONPATH=${toolkit.dir}/lib/python2.7/site-packages:$PYTHONPATH
# dirty hack due to bug in cmake and/or setuptools
chmod -R u+rwx ${toolkit.dir}/lib/python2.7/site-packages/*
cd \\$WORKSPACE/build/python/stable
python2.7 setup.py install --prefix=${toolkit.dir}
cd \\$WORKSPACE/build/python/sandbox
python2.7 setup.py install --prefix=${toolkit.dir}
cd \\$WORKSPACE/build/python/deprecated
python2.7 setup.py install --prefix=${toolkit.dir}
</pre>
<p>This will install over the custom CMake install procedure and update the correct pth file. I would not say that this is a clean way.</p>
<a name="How-to-actually-fix-this"></a>
<h2 >How to actually fix this<a href="#How-to-actually-fix-this" class="wiki-anchor">¶</a></h2>
<p>Separating the languages so that individual install procedures can be done?</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.deBug #1824 (New): Wrong message URLs in sandbox package overviewhttps://code.cor-lab.de/issues/18242014-03-27T10:08:30ZAnonymous
<p>In sandbox packages, e.g. <a class="external" href="http://docs.cor-lab.de//rst-manual/trunk/html/generated/sandbox/package-rst-cbse.html">http://docs.cor-lab.de//rst-manual/trunk/html/generated/sandbox/package-rst-cbse.html</a>, links to the documentation of the contained messages are wrong.</p>
<p>E.g. for the ComponentState, the link is<br /><a class="external" href="http://docs.cor-lab.de//rst-manual/trunk/html/generated/stable/package-rst-cbse.html#rst.cbse.ComponentState">http://docs.cor-lab.de//rst-manual/trunk/html/generated/stable/package-rst-cbse.html#rst.cbse.ComponentState</a><br />where it should be<br /><a class="external" href="http://docs.cor-lab.de//rst-manual/trunk/html/generated/sandbox/package-rst-cbse.html#rst.cbse.ComponentState">http://docs.cor-lab.de//rst-manual/trunk/html/generated/sandbox/package-rst-cbse.html#rst.cbse.ComponentState</a><br />(so should be <code>../sandbox/..</code> instead of <code>../stable/..</code>)</p> Tasks #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> Feature #1476 (Feedback): Allow explicit selection of built convertershttps://code.cor-lab.de/issues/14762013-04-25T10:06:50ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>In my current scenario, I want to explicitly switch off compilation for OpenCV converters (as OpenCV can not be easily build as a univeral binary on MacOS). Currently, this seems not possible as what is build is completely determined through the found packages in the configuration step.</p>
<p>Once we modularize the converters into separate libraries this shouldn't be a problem any longer. For instance, in this case, the best solution would be to have a dedicated plugin library for OpenCV with a library architecture that matches the installed version of the dependency. Another aspect in favor of the plugin system...</p> 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.deFeature #1276 (In Progress): Use rosetta for code generationhttps://code.cor-lab.de/issues/12762012-11-30T20:02:21ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deBug #1261 (Feedback): RST manual (ab)uses Sphinx' Python domain for data typeshttps://code.cor-lab.de/issues/12612012-11-26T17:04:51ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>We generate reStructuredText similar to the following</p>
<pre>
.. py:class:: rst.audition.SoundChunk
[...]
@author [...]
.. py:attribute:: data
:type: :py:class:`OCTET-VECTOR`
[...]
</pre>
<p>This works OK and renders nicely but is quite wrong semantically.</p>
<p>Is there a solution short of writing a custom Sphinx domain?</p> Tasks #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>