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 - 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 - Support #588 (In Progress): AMiRo-BLT overhaulhttps://opensource.cit-ec.de/issues/5882019-03-08T10:57:40ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Currently AMiRo-BLT is a highly modified fork of an quite old version of OpenBLT. For better maintainability it should rather use a current version of OpenBLT and apply any required modifications as patches (like AMiRo-OS does with ChibiOS). This way the tools will profit from the progress made by the OpenBLT developers and the overall software can be kept up to date much easier.</p>
<p>Whether the new version will be released as 1.2 or 2.0 needs to be discussed once the new software architecture is in place. If possible, the new bootloaders should be backwards compatible with the 1.x versions, though.</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 - Bug #525 (New): Maven Template uses default profilehttps://opensource.cit-ec.de/issues/5252017-11-02T07:38:33ZLeroy Rügemerlruegeme@techfak.uni-bielefeld.de
<p>Maven builds use the users .m2 settings file maven should create and use special settings for each.</p>
<p>To build multiple distributions on the same machine i have to switch the default profile to not pull from the wrong distribution</p> Cognitive Interaction Toolkit - Task #520 (Feedback): CITKat WSGI documentationhttps://opensource.cit-ec.de/issues/5202017-09-20T11:32:24ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.de
<ul>
<li>uWSGI for Nginx</li>
<li>mod_wsgi for Apache</li>
</ul> Cognitive Interaction Toolkit - Feature #419 (New): CITK Json Schema validationhttps://opensource.cit-ec.de/issues/4192015-08-28T14:44:29ZJon Weiszjweisz@cs.columbia.edu
<p>A formal json specification a-la <a class="external" href="https://pypi.python.org/pypi/jsonschema">https://pypi.python.org/pypi/jsonschema</a> for the metadata in the repository would really help formal validation tools and generating templates for adding metadata to the repository. It will also help future-proof the repository as it will make conversion easier. Also, the documentation for this package would be the appropriate place to discuss formal and informal requirements for what makes a good metadata file.</p> Cognitive Interaction Toolkit - Feature #349 (New): Build toolkit nightly cmake jobs with VERBOSE=1https://opensource.cit-ec.de/issues/3492014-12-04T15:32:11ZChristian Emmerichcemmeric@cor-lab.uni-bielefeld.de
<p>Build toolkit nightly cmake jobs with VERBOSE=1</p> Cognitive Interaction Toolkit - Feature #287 (New): Read branches out of git to reduce versioning...https://opensource.cit-ec.de/issues/2872014-09-18T13:17:51ZMarian Pohlingmpohling@cit-ec.uni-bielefeld.de
<p>Would it be possible to read the "branches"/"tags" direktly out the git repo instead of listing all branches explicit in the recipe file again.</p> Cognitive Interaction Toolkit - Support #279 (In Progress): Create videos of the most basic tutor...https://opensource.cit-ec.de/issues/2792014-06-20T12:50:26ZFlorian Lierflier@cit-ec.uni-bielefeld.de
<p>To be done...</p> Cognitive Interaction Toolkit - Feature #199 (New): Client-side error handlinghttps://opensource.cit-ec.de/issues/1992014-01-27T10:31:25ZJohannes Wienkejwienke@techfak.uni-bielefeld.de
<p>Clients of the rest client should be able to handle request errors on their own instead of being exited.</p>