Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-04-21T14:24:14ZOpen Source Collaboration Platform
Redmine Feature #2227 (Feedback): Symlinks/Aliases for Scopeshttps://code.cor-lab.de/issues/22272015-04-21T14:24:14ZC. Leichsenringcmertes@cit-ec.uni-bielefeld.de
<p>For various reasons it would be useful to make the same informer have multiple scopes, i.e. de facto symlinks or aliases for scopes. Example use cases would be:</p>
<ul>
<li>provide a list of services or devices by human-readable name and number</li>
<li>list services by different criteria</li>
<li>provide different formats under different scopes but link to a default scope</li>
<li>.... basically every reason why one would want symlinks in file systems, too</li>
</ul> Feature #2185 (New): Provide Contrib Library or Folder for Community Additionshttps://code.cor-lab.de/issues/21852015-02-24T10:43:19ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>The proposal here is to provide a <code>contrib</code> folder or library that contains community additions to the framework core. These additions should primarily consist of plugins or additional implementations for the RSB extension points that do not justify a standalone plugin library or can not (yet) be included in the core library. This should allow faster dissemination of new experimental features to the community without fragmentation or erosion of the library core.</p>
<p>The technical means to achieve this (folder vs. library, cmake components or not, integration with core documentation, ...) needs to be discussed.</p> Feature #1771 (In Progress): Add META block to TIDELog backendhttps://code.cor-lab.de/issues/17712014-02-14T11:48:57ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1770 (In Progress): Add TYPE block to TIDELog backendhttps://code.cor-lab.de/issues/17702014-02-14T11:43:09ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1747 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17472014-02-06T17:32:47ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1746 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17462014-02-06T17:32:34ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1745 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17452014-02-06T17:32:22ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deBug #1401 (New): Sphinx-based documentation for rsb-matlabhttps://code.cor-lab.de/issues/14012013-02-06T19:34:50ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>We need to udpate and transform the rsb-matlab documentation from the Wiki to a Sphinx module.</p> Feature #1102 (In Progress): Use data type definitions stored in log fileshttps://code.cor-lab.de/issues/11022012-07-27T08:53:25ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p><code>bat-{cat,play,merge}</code> should use the data type definitions stored in log files when possible. This avoids loading IDL files all the time.</p> Tasks #897 (New): Verify Elan backendhttps://code.cor-lab.de/issues/8972012-02-24T16:12:28ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Attached xsd-file may specify some version of the EAF file format.</p> Tasks #886 (New): Scope renaming (C++)https://code.cor-lab.de/issues/8862012-02-16T17:04:25ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Implement scope renaming and an associated configuration mechanism (see <a href="https://code.cor-lab.de/projects/rsb/wiki/Meetings2012-02-16" class="wiki-page">Meetings2012-02-16</a>).</p>
<em>The following should be move to a "scope renaming" wiki page (see <a href="https://code.cor-lab.de/issues/885" class="issue tracker-4 status-1 priority-4 priority-default child" title="Specify scope renaming (New)">#885</a>)</em>
<ul>
<li>The renaming mechanism should applied when participants are instantiated</li>
<li>Default scopes of participants remain constant
<ul>
<li>Default scopes become effective scopes when no renaming is applied</li>
<li>Default scope names are referenced in renaming rules</li>
</ul>
</li>
<li>Renaming rules are specified as configuration options</li>
</ul> Tasks #885 (New): Specify scope renaminghttps://code.cor-lab.de/issues/8852012-02-16T17:00:59ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Specify scope renaming and an associated configuration mechanism (see <a href="https://code.cor-lab.de/projects/rsb/wiki/Meetings2012-02-16" class="wiki-page">Meetings2012-02-16</a>):
<ul>
<li>Renaming semantics</li>
<li>Configuration syntax</li>
</ul>
Update:
<ul>
<li><a href="https://code.cor-lab.de/projects/rsb/wiki/Configuration" class="wiki-page">Configuration wiki page</a></li>
<li>New wiki page for scope renaming?</li>
<li>RSB manual (<a href="/projects/rsb/repository/entry/trunk/manual" class="source">source:trunk/manual</a>)</li>
</ul> Feature #471 (New): Support for RPC clients which do not require a running server parthttps://code.cor-lab.de/issues/4712011-08-04T15:17:20ZL. Schillingmannlschilli@techfak.uni-bielefeld.de
<p>It should be simple to code a rpc client which is able to handle different states of the rpc server availability:</p>
<ul>
<li>reconnect if server disappears and reappears</li>
<li>detect server availability</li>
<li>wait for server to appear (with timeout)</li>
</ul> Tasks #392 (In Progress): Multi-Connector Setups lead to duplicate reception of Eventshttps://code.cor-lab.de/issues/3922011-06-24T15:04:24ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>See <a href="https://code.cor-lab.de/projects/rsb/wiki/Inter-Transport_Communication" class="wiki-page">Inter-Transport Communication</a>. The current implementation causes events to arrive at receiving clients twice as shown by the linked example programs.</p>
<p>While no nameservice, introspection or model information is available, the problem could be addressed using a simple tagging scheme:<br /><img src="https://code.cor-lab.de/attachments/download/106/multi-transport-handling.png" title="proposed short-term solution" alt="proposed short-term solution" /></p> Feature #382 (In Progress): Interaction with Foreign Nameservicehttps://code.cor-lab.de/issues/3822011-06-22T19:34:18ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Implement these scheme-behavior combinations:
<ul>
<li><code>tcp+ros://HOST:PORT/SCOPE</code>
<ul>
<li>Connect to <em>HOST:PORT</em> using TCPROS protocol</li>
<li>Assume the node publishes the topic <em>SCOPE</em></li>
</ul>
</li>
<li><code>ros:/SCOPE?master=URL</code>
<ul>
<li>Assume the ROS master is at <em>URL</em></li>
<li>Ask it for publishers of topic <em>SCOPE</em></li>
</ul></li>
</ul>