Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732018-10-09T14:34:32ZOpen Source Collaboration Platform
Redmine Enhancement #2772 (New): Uniformed path for System-Config in Windowshttps://code.cor-lab.de/issues/27722018-10-09T14:34:32ZS. Barutsbarut@techfak.uni-bielefeld.de
<p>Currently, the path where the system-wide rsb.conf lies is not specified under windows. (see: <a class="external" href="http://docs.cor-lab.org/rsb-manual/trunk/html/specification-config.html#effective-configuration">http://docs.cor-lab.org/rsb-manual/trunk/html/specification-config.html#effective-configuration</a> ; PREFIX is not clearly defined).</p>
<p>Some proposals would be:</p>
<p>- C:\rsb.conf <br />Straightforward but maybe too messy and not clear enough...</p>
<p>- C:\Users\Public\.config\rsb.conf <br />Would have a <span>userprofile</span>\.config\rsb.conf design, but beeing effective for every user (Public) making it system-wide</p>
<p>It is more or less a proposal derived from:<br /><a class="external" href="https://blogs.msdn.microsoft.com/patricka/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions/">https://blogs.msdn.microsoft.com/patricka/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions/</a></p>
<p>Actually "C:\Users\Public" is only intended for documents but with the ".config" subdirectory it should be a nice and clear like in the home directory.</p> Enhancement #2676 (New): Allow to specify output stream for show-progress style "ready"https://code.cor-lab.de/issues/26762016-11-08T13:38:49ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>This can be used to prevent conflicts with warnings appearing on stderr.</p> Enhancement #2563 (New): Flush indices based on combined memory consumption of all indiceshttps://code.cor-lab.de/issues/25632016-06-12T13:36:55ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>The current approach of independent flush strategies for all indices is unsuitable for controlling the maximum memory used by indices.</p> Enhancement #2376 (New): Allow to deduplicate participants in introspection exporthttps://code.cor-lab.de/issues/23762015-08-31T11:34:37ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>When using <code>bag introspect</code> it would be nice if one could specify something like primary keys for the different elements in the introspection tree so that e.g. participants of the same type and scope, but different IDs could be deduplicated.</p> Enhancement #2368 (New): Add average rate field to logger styleshttps://code.cor-lab.de/issues/23682015-08-26T14:47:20ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>number of events / number of origins</p>
<p>+ variance?</p> Enhancement #2367 (New): Scope-specific max-depth overrides for the tree view of the loggerhttps://code.cor-lab.de/issues/23672015-08-26T14:32:57ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Allow to specify different max-depth values for certain subtrees of the system.</p> Enhancement #2366 (New): Improve frequency calculationhttps://code.cor-lab.de/issues/23662015-08-26T14:28:57ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Use a wider horizon compared to the <code>print-interval</code> so that sparse events are better reflected without constantly changing measurement values.</p> Enhancement #2359 (In Progress): Graph for introspection web interfacehttps://code.cor-lab.de/issues/23592015-08-08T06:48:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Must scale (algorithmically) to thousands of participants</li>
<li>Intelligent restriction
<ul>
<li>Based on selected node</li>
<li>Maybe show neighbors, respective ancestors and immediate children of selected node?</li>
</ul></li>
</ul> Enhancement #2225 (New): Use sphinx.ext.ifconfig for version-dependent information in the manualhttps://code.cor-lab.de/issues/22252015-04-20T13:18:39ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>We have several TODOs in the manuals which need to be updated on each release because of things diverging between release and master version. The <code>sphinx.ext.ifconfig</code> module (<a class="external" href="http://sphinx-doc.org/ext/ifconfig.html">http://sphinx-doc.org/ext/ifconfig.html</a>) could help here.</p> Enhancement #2149 (Feedback): Provide simple API to programmatically set preferred convertershttps://code.cor-lab.de/issues/21492015-01-04T06:57:44ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<p>Currently converters can only be configured via the RSC config system. <br />Preferred converters are filtered out in rsb::ParticipantConfig::Transport::handleOption.</p>
<p>As usually the programm needs to specifiy its required converters (rather than the system), there should be an easy mechanism to specify preferred converters on that level.<br />I suggest to add methods addConverter(wireschema, datatype) and addConverters(ConverterNames)</p> Enhancement #2055 (New): Extend documentation on using and writing converters in the manualhttps://code.cor-lab.de/issues/20552014-10-10T11:56:49ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Robert Haschke wrote:</p>
<blockquote>
<p>Außerdem habe ich ein paar kleine Ergänzungen in der Doku der converters vorgenommen (attached for review). Ich fände es wichtig, dass von der specification-Seite auf die converters-Doku (bislang nur in Form der examples-converters.rst) verwiesen wird. Habe ich aber nicht hinbekommen.</p>
</blockquote>
<p>Robert's patch is attached.</p> Enhancement #1831 (Feedback): Provide introspection functionality as shared object (as opposed to...https://code.cor-lab.de/issues/18312014-04-01T14:40:48ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Questions to consider:
<ul>
<li>How should the shared object be exported on the CMake-level?
<ul>
<li>Probably similar to converter plugins in <a href="https://code.cor-lab.de/projects/rst" class="project">Robotics Systems Types</a></li>
<li>However, we probably do not want CMake components since they make everything more complicated</li>
<li>Probably add a <code>RSB_INTROSPECTION_LIBS</code> variable and export it in <code>rsb-config.cmake</code></li>
</ul>
</li>
<li>How should the initialization and cleanup be performed when the introspection shared object is used?</li>
<li>What happens if a client programs links against the introspection shared object and then loads the plugin?</li>
</ul> Enhancement #1777 (In Progress): Add commandline options to exclude scopes from logging https://code.cor-lab.de/issues/17772014-02-18T16:18:29ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Allow to exclude certain scopes from the logging process using command line arguments.</p> Enhancement #1757 (In Progress): Add intermediate results to request-reply patternhttps://code.cor-lab.de/issues/17572014-02-10T10:28:55ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Allow RPC methods to provide intermediate results during processing using asynchronous communication.</p> Enhancement #1597 (New): setup.py should specify the protobuf dependency with the exact versionhttps://code.cor-lab.de/issues/15972013-08-20T07:53:27ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>As the generated protocol files are coupled to a specific protobuf version, setup.py should declare the protobuf dependency explicitly with the version of protoc used to generated the protocol.</p>