Research for Cognitive Interaction: Issueshttps://opensource.cit-ec.de/https://opensource.cit-ec.de/favicon.ico?14265323552019-11-14T10:52:36ZResearch for Cognitive Interaction
Redmine AMiRo-OS - Feature #596 (New): automated test scripthttps://opensource.cit-ec.de/issues/5962019-11-14T10:52:36ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Introduce a test script, that sweeps compile parameters (e.g. AMIROOS_CFG_DBG), compiles all modules with these settings and evaluates compilation results (success, failure, warning) to match the expected output.<br />Since such a thorough compilation test will probably take quite some time, this should not be executed automatically by some CI tool but only on demand.</p>
<p>Preferably, this script will be included in the ./setup.sh bash script environment.</p> AMiRo-OS - Feature #591 (New): More generic QtCreator project setuphttps://opensource.cit-ec.de/issues/5912019-03-08T12:20:12ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Recently, the AMiRo-OS QtCreator project setup script has been enhanced to use the GCC output for generating according project files. This enhancement should be ported to AMiRo-BLT and enhanced, so also AMiRo-OS (as well as any further higher level projects) can take advantage of this script.</p> AMiRo-OS - Feature #589 (New): Enhanced I/O eventshttps://opensource.cit-ec.de/issues/5892019-03-08T12:13:28ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Currently I/O interrupts result in I/O events and propagate the causing EXTI line via event flags (e.g. EXTI <a href="https://opensource.cit-ec.de/issues/3" class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="fix colored output in installink target (Closed)">#3</a> propagates (1 << 3) = 0x00000008). Since EXTI lines can aggregate multiple I/O pins (e.g. PA3 and PC3) this method can result in ambiguous events, because only the EXTI line but not the actual pin is specified.</p>
<p>To solve this issue, I/O events should not propagate plain eventflags_t data, but a struct like<br /><pre>
struct {
uint32_t flags : 24; // alternatively 28
uint32_t pin : 8; // alternatively 4
};
</pre>Since there is no EXTI hardware so far which provides more than 24 lines this solution is feasible. Alternatively the ratio can be set to 28:4 assuming that there will not be more than 2^4-1 pins aggregated in a single EXTI line. The -1 is important here, since the value of <code>pin</code> = 0 must be reserved to indicate ambiguity. This was the new method is compatible to plain eventflags_t and there might be cases where the exact pin can not be determined.<br />The determination can be realized within the ISR, which is called by the EXTI driver.</p> AMiRo-OS - Feature #587 (New): Implement I2C bus clear functionhttps://opensource.cit-ec.de/issues/5872019-02-25T16:02:00ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Implement the I2C bus clear function as specified by the <a href="https://www.nxp.com/docs/en/user-guide/UM10204.pdf" class="external">I2C standard</a> (Rev. 6; section 3.1.16).<br />This function should also be made available as dedicated unit test command.</p>
<p>Such a procedure has already been implemented for <a href="https://opensource.cit-ec.de/projects/amiro-os/repository/revisions/1.0_stable/entry/boards/DiWheelDrive/board.c" class="external">AMiRo-OS v1</a> as well as a device specific reset for the AT24C01B EEPROM.</p> AMiRo-OS - Feature #586 (New): Configurable shell historyhttps://opensource.cit-ec.de/issues/5862019-02-25T15:53:41ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Introduce a configurable buffer for the shell, which holds the N last commands.<br />With N set to 0, the behavior should be like now, with the input buffer acting as a <em>wannabe</em> 1-command history.<br />With N set to 1, the behavior would be very similar, but there would be a <em>true</em> 1-command history.</p> Cognitive Interaction Toolkit - Feature #584 (New): citkat: Indicate external links using an icon...https://opensource.cit-ec.de/issues/5842018-10-16T08:38:22ZJan Moringenjmoringe@techfak.uni-bielefeld.de
<p>Links to project homepages and bug trackers, for example.</p> Cognitive Interaction Toolkit - Task #576 (New): citkat: Browse » Persons should have a GDPR noticehttps://opensource.cit-ec.de/issues/5762018-07-10T10:47:05ZJan Moringenjmoringe@techfak.uni-bielefeld.de
<p>At least when the person list is empty.</p> Cognitive Interaction Toolkit - Task #554 (New): citkat: move to python webassets and sasshttps://opensource.cit-ec.de/issues/5542018-01-31T13:55:28ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.de
<blockquote>
<p>webassets is a general, dependency-independent library for managing the assets of your web application. It can merge and compress your CSS and JavaScript files, supporting a wide variety of different filters, and supports working with compilers like CoffeeScript or Sass.</p>
</blockquote> Cognitive Interaction Toolkit - Task #518 (New): CITKat Jenkins build state integrationhttps://opensource.cit-ec.de/issues/5182017-09-20T11:04:43ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.deCognitive Interaction Toolkit - Task #517 (New): add hardware XSL template https://opensource.cit-ec.de/issues/5172017-09-20T10:52:07ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.de
<p>also specify hardware schema in the XML schema</p> IPAACA - Task #472 (New): Should basic logging (level >= WARNING) be enabled by default?https://opensource.cit-ec.de/issues/4722016-03-08T14:29:51ZHendrik Buschmeier
<p>Currently logging is disabled by default and needs to be enabled via `ipaaca.misc.enable_logging()`. This however results (e.g.) in exceptions occurring in iu_handlers being hidden from the user.</p>
<p>A better default behaviour would therefore be to have a log level (>= WARNING) enabled by default.</p> Cognitive Interaction Toolkit - Task #426 (New): Multiple build jobs per componenthttps://opensource.cit-ec.de/issues/4262015-10-14T15:32:38ZFlorian Lierfl@techfak.uni-bielefeld.de
<p>Add multiple build jobs to components, because there cannot only be "one" job</p> RML - RobotMetaLogger - Support #145 (New): Documentation additions DRAFThttps://opensource.cit-ec.de/issues/1452013-02-18T23:38:48ZFlorian Lierflier@cit-ec.uni-bielefeld.de
<p>I would like to add:</p>
<p>+ Install (Debian Dependencies): sudo apt-get install python-opencv in any other case rml init will fail like:<br /><code><br />flier@m0thership:~/Projects/Ongoing/RML/data$ /home/flier/Projects/Ongoing/Gar-Trunk/bin/rml initTraceback (most recent call last):<br /> File "/home/flier/Projects/Ongoing/Gar-Trunk/bin/rml", line 5, in <module><br /> pkg_resources.run_script('RobotMetaLogger==0.4', 'rml')<br /> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 499, in run_script<br /> self.require(requires)[0].run_script(script_name, ns)<br /> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1239, in run_script<br /> execfile(script_filename, namespace, namespace)<br /> File "/home/flier/Projects/Ongoing/Gar-Trunk/lib/python2.7/site-packages/RobotMetaLogger-0.4-py2.7.egg/EGG-INFO/scripts/rml", line 40, in <module><br /> import rml.config, rml.probes<br /> File "/home/flier/Projects/Ongoing/Gar-Trunk/lib/python2.7/site-packages/RobotMetaLogger-0.4-py2.7.egg/rml/probes/__init__.py", line 52, in <module><br /> from opencv.camera import OpenCVProbe<br /> File "/home/flier/Projects/Ongoing/Gar-Trunk/lib/python2.7/site-packages/RobotMetaLogger-0.4-py2.7.egg/rml/probes/opencv/camera.py", line 10, in <module><br /> import cv<br /></code></p>
<p>+ In case you have chosen a custom $prefix (./configure --prefix=/some/custom/path), extend your PYTHONPATH like the following:<br /><code><br />export PYTHONPATH=$PYTHONPATH:/some/custom/path/lib/python2.7/site-packages<br /></code></p> RML - RobotMetaLogger - Support #144 (New): PYTHONPATH / LIBDIR unclearhttps://opensource.cit-ec.de/issues/1442013-02-18T23:25:01ZFlorian Lierflier@cit-ec.uni-bielefeld.de
<p>If you configure RML using ./configure --prefix=/tmp (for instance) /tmp/bin/rml init will fail due to the std path for python libs, e.g.:</p>
<p><code><br />flier@m0thership:~/Projects/Ongoing/RML/data$ /tmp/bin/rml init<br />Traceback (most recent call last):<br /> File "/tmp/bin/rml", line 4, in <module><br /> import pkg_resources<br /> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2815, in <module><br /> working_set.require(__requires__)<br /> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 690, in require<br /> needed = self.resolve(parse_requirements(requirements))<br /> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 588, in resolve<br /> raise DistributionNotFound(req)<br />pkg_resources.DistributionNotFound: RobotMetaLogger==0.4<br /></code></p>
<p>Shall we introduce a $prefix variable? Import paths on runtime using sys.append.path() ? Extend $PYTHONPATH ?</p> XTT - eXtensible Task Toolkit - Support #122 (New): Move event id and timestamps into TaskState s...https://opensource.cit-ec.de/issues/1222012-10-29T16:05:08ZIngo Lütkebohleiluetkeb@techfak.uni-bielefeld.de
<p>Currently, these are stored inside the Notification protobuf type. This is a violation of information layering, and complicates unpacking such structures.</p>