RSBag: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-11-08T13:38:49ZOpen Source Collaboration Platform
Redmine 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 #979 (In Progress): bag record: Make status output more intuitivehttps://code.cor-lab.de/issues/9792012-04-10T14:17:07ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>The current output of bag-record is not very intuitive, hard to read and sometimes confusing.</p>
<p>Status output as in the attached screenshot would be better.</p> Enhancement #971 (New): Allow limiting recording timehttps://code.cor-lab.de/issues/9712012-03-25T14:45:22ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
There should be
<ul>
<li><code>--for-events NUMBER-OF-EVENTS</code></li>
<li><code>--for-time TIME-EXPRESSION</code></li>
<li><code>--until TIME-EXPRESSION</code><br />commandline options</li>
</ul>