Research for Cognitive Interaction: Issueshttps://opensource.cit-ec.de/https://opensource.cit-ec.de/favicon.ico?14265323552020-01-25T03:33:38ZResearch for Cognitive Interaction
Redmine Cognitive Interaction Toolkit - Bug #597 (New): Orchestration fails if single build job cancelledhttps://opensource.cit-ec.de/issues/5972020-01-25T03:33:38ZRobert Haschkerhaschke@techfak.uni-bielefeld.de
<p>Cancelling a single job stops the whole orchestration because the CancellationException that is thrown when done.get() is called, is not caught.</p>
<p>The attached patch provides a dirty workaround, ignoring cancelled jobs completely. However this way:<br />- other potential exceptions thrown by done.get() are not caught yet<br />- the failure is not reported back to the main spinning loop</p>
<p>Probably, Jan, you have a better idea how to fix the problem.</p> 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 - Bug #595 (New): SSSP has issue with IO event in breakout boardhttps://opensource.cit-ec.de/issues/5952019-04-01T15:25:49ZCung Lian Sangcsang@techfak.uni-bielefeld.de
<p>Enabling the SSSP flag has some conflicts with the IO event in the UWB breakout board of the Light Ring module.<br />The UWB breakout uses a PB9 pin as an event trigger. The application of UWB is working as expected when the SSSP flag (AMIROOS_CFG_SSSP_ENABLE) is disabled.<br />However, when the SSSP flag is enabled, the event is not triggered any more on the breakout board.</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> 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 - Bug #582 (New): citkat: Expanders for components/systems with mul...https://opensource.cit-ec.de/issues/5822018-09-14T13:36:17ZJan Moringenjmoringe@techfak.uni-bielefeld.de
<p>Clicking the link text or expander icon does nothing.</p>
<p>Firefox version is 60.2.0esr (64-bit)</p> hlrc - Bug #581 (New): flobi lookat does not work anymore due to hardcoded floka prefixhttps://opensource.cit-ec.de/issues/5812018-08-15T09:20:26ZGuillaume Walckgwalck@techfak.uni-bielefeld.de
<p>I am using flobi, and we get this error now :<br /><pre>
2018-08-15 10:39:20,004 hlrc_client.Middleware ERROR > publish_lookat_target timed out waiting for result or soemthing else went wrong
and in the log of hlrc_server :
[ WARN] [1534322517.517683315]: "floka_BASE_LINK" passed to lookupTransform argument target_frame does not exist
</pre></p>
<p>I tracked down the error to a recent change with a hardcoded prefix.</p>
<p><a class="external" href="https://opensource.cit-ec.de/projects/hlrc/repository/diff/server/include/ROS/LookatCallbackWrapperROS.h?utf8=%E2%9C%93&rev=01ff84641a5a769064e8656fcfd4d48f69a24d18&rev_to=60b91de0f20bdd7fac9fb448b2fad1079a7b9891">https://opensource.cit-ec.de/projects/hlrc/repository/diff/server/include/ROS/LookatCallbackWrapperROS.h?utf8=%E2%9C%93&rev=01ff84641a5a769064e8656fcfd4d48f69a24d18&rev_to=60b91de0f20bdd7fac9fb448b2fad1079a7b9891</a></p>
<p>Maybe the prefix could be taken from the scope name (unless you want to make that cleaner) that is passed to the arguments anyway<br /><pre>
hlrc_server ROS ROS flobi flobi pulse
</pre></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> Finite State Machine Based Testing - Bug #409 (New): Implement non-children killing process end s...https://opensource.cit-ec.de/issues/4092015-03-26T14:50:42ZNorman Kösternkoester@techfak.uni-bielefeld.de
<p>This strategy assumes that developers care for their child processes themselves, thus only the top process is killed with usual timeouts strategies. Children are <strong>explicitly not</strong> ended by FSMT.</p> meta-openrobotix - Bug #339 (New): Check debricated opencv.pchttps://opensource.cit-ec.de/issues/3392014-11-23T14:50:46ZTimo Korthalstkorthals@cit-ec.uni-bielefeld.de
<p>Remove -lopencv_ts from opencv.pc because it is debricated</p> ivTools - Bug #283 (New): ivrender colors broken depending on Mesa3D versionhttps://opensource.cit-ec.de/issues/2832014-07-10T14:07:04ZJens Peter Lindemannj.lindemann@cit-ec.uni-bielefeld.de
<p>Color problems on recent Debian-based linux systems (tested: Ubuntu 12.04 and 14.04, Debian 7.5). Older versions work as expected (tested: Ubuntu 10.04).</p>
<p>Red and blue color channels are swapped in the rendering output. This behaviour seems to appear between osmesa Debian/Ubuntu package versions 7.7.1 and 8.0.4.</p>
<p>Workaround: Create OSMESA GL context with OSMESA_BGR instead of OSMESA_RGB in the MesaOffscreenRenderer constructor code (line ivRender/LibRender/MesaOffscreenRenderer.cpp:43).</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> ivTools - Feature #39 (New): ivTrace: Reload 3D world parametershttps://opensource.cit-ec.de/issues/392012-06-28T13:51:40ZJens Peter Lindemannj.lindemann@cit-ec.uni-bielefeld.de
<p>Make reload/change of 3D world parameters possible without need to restart ivTrace</p>