Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-08-18T11:17:59ZOpen Source Collaboration Platform
Redmine Feature #2648 (New): Setters for TimesyncStrategy optionshttps://code.cor-lab.de/issues/26482016-08-18T11:17:59ZM. Goerlichmgoerlic@techfak.uni-bielefeld.de
<p>Currently the strategies can only be configured through boost::po::variables_map s. Filling those by hand is clumsy, direct setters for time frames and buffer sizes at the time frame strategy as well as for the queue size for the approx time strategy would make usage of timesync as library a lot easier.</p> 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 #2170 (New): Visual indication when rsb-logger* (or any other rsb-tool) is readyhttps://code.cor-lab.de/issues/21702015-02-09T16:58:43ZN. Kösternkoester@techfak.uni-bielefeld.de
<p>When providing/loading multiple idl path(s)/files(s), the logger may take some time to load (as described <a href="http://docs.cor-lab.de//rsb-manual/0.11/html/tool-logger.html#tool-logger" class="external">here</a> and as expected).</p>
<p>Example:</p>
<pre>
rsb-loggercl --idl-path="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/stable/" \
--idl-path="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/sandbox/" \
--load-idl="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/**/*.proto" \
--style=detailed \
/rsbopencv/persons/
</pre>
<p>However, (for usability reasons) it would be nice to get a visual indication/feedback (e.g. simple print saying <strong><code>ready</code></strong>) to know if the logger is ready. This is important when using rsb with socket communication, as the order of launching components is important here.</p> Feature #2139 (New): Finalize introspection implementationhttps://code.cor-lab.de/issues/21392014-12-17T14:32:12ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #2138 (New): Allow constructing scopes from a list of component strings (potentially sing...https://code.cor-lab.de/issues/21382014-12-17T13:13:52ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Java</li>
<li>C++</li>
<li>Python</li>
</ul> Feature #1922 (New): Include environment variables in introspection messages describing processeshttps://code.cor-lab.de/issues/19222014-08-04T10:20:21ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Probably useful</li>
<li>For parity with commandline options</li>
</ul> Feature #1870 (New): Allow (optional) parallel method callshttps://code.cor-lab.de/issues/18702014-05-08T12:36:06ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Johannes will commit patches containing a short-term workaround for C++ and Java</li>
</ul> Feature #1825 (New): bag record: Start timestamp for remote recording starthttps://code.cor-lab.de/issues/18252014-03-31T21:03:35ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>The start method of the remote control interface should accept an optional timestamp</li>
<li>When such a timestamp is supplied, the method will block until the specified time</li>
<li>Recording will start and the method will return</li>
</ul> Feature #1769 (New): Store start and end timestamp of recordinghttps://code.cor-lab.de/issues/17692014-02-14T11:41:13ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>As opposed to timestamps of first/last recorded events.</p> Feature #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.deFeature #1707 (New): Support Java as a client languagehttps://code.cor-lab.de/issues/17072013-12-22T20:19:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1677 (New): Support explicit backend selectionhttps://code.cor-lab.de/issues/16772013-12-04T13:16:06ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ol>
<li>Add a commandline option for forcing a backend</li>
<li>Use new configuration system for backend selection and configuration. Examples of options
<ul>
<li><code>tide.force-recovery</code></li>
<li><code>tide.flush-strategy</code></li>
<li><code>tide.flush-strategy.buffer-limit.limit</code></li>
</ul>
</li>
<li>After switching to service-provider system, add backend auto-detection service</li>
</ol> Feature #729 (New): Allow regex-based converter selection for deserializinghttps://code.cor-lab.de/issues/7292011-11-23T12:26:50ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>e.g. I want the same converter to deserialize all rst-types.</p>
<p>This is required for an improved matlab integration.</p>