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 #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> 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> GazeTK - Feature #442 (New): Application and plugin specific setting storagehttps://opensource.cit-ec.de/issues/4422015-12-09T16:38:12ZThies Pfeiffertpfeiffe@cit-ec.uni-bielefeld.de
<p>We need a way to store preferences for the application and for each plugin</p> GazeTK - Feature #441 (New): Dialog to show the pluginshttps://opensource.cit-ec.de/issues/4412015-12-09T16:37:35ZThies Pfeiffertpfeiffe@cit-ec.uni-bielefeld.de
<p>Should list the plugins found by the pluginloader<br />For each plugin it should show a page in which settings specific to the plugin could be made</p> GazeTK - Feature #439 (New): Connection to Browserhttps://opensource.cit-ec.de/issues/4392015-12-09T16:35:33ZThies Pfeiffertpfeiffe@cit-ec.uni-bielefeld.deCognitive 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> Finite State Machine Based Testing - Feature #410 (New): Add comment field to testshttps://opensource.cit-ec.de/issues/4102015-03-27T11:29:20ZChristian Mertescmertes@cit-ec.uni-bielefeld.de
<p>It would be nice to have an optional <code>comment</code> field that is output when a particular test fails alongside the usual messages. This would enable the developer to add some more specific and therefore potentially more meaningful error messages as to what it means that a particular test failed.</p> IPAACA - Bug #408 (New): Delay/framedropping in AsapRealizer rendering when closing the injectorhttps://opensource.cit-ec.de/issues/4082015-03-26T14:08:04ZHerwin van Welbergenhvanwelbergen@techfak.uni-bielefeld.de
<p>When sending a BML message to AsapRealizer using the iu-injector, rendering/movement temprorarly stalls. This seems to occur AFTER the message is delivered, e.g. while the injector is closing. If the Python UI or Java UIs to send BML over IPAACA is used, the delay does not occur.</p>
Workarounds:
<ul>
<li>Insert a delay after sending the message</li>
<li>Keep the OutputBuffer open.</li>
</ul>
Open questions:
<ul>
<li>Does this only occur in Python?</li>
<li>Does this occur for every closing of an outputbuffer?</li>
</ul> IPAACA - Feature #406 (New): add time stamps to IUs/messageshttps://opensource.cit-ec.de/issues/4062015-03-26T09:48:59ZMatthias Priestersmpriesters@uni-bielefeld.deCognitive 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 #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> XTT - eXtensible Task Toolkit - Feature #128 (New): Confirmation of 'completed' statehttps://opensource.cit-ec.de/issues/1282012-11-22T15:24:47ZMaikel Linkemalinke@techfak.uni-bielefeld.de
<p>Currently, a task submitter can set a task 'completed' and the task server may react on this. This can lead to ongoing processes for already completed tasks. Therefore, a submitter should only send a message 'complete' and the server has to acknowledge that by setting the task 'completed' after informing regarding processes about the completion.</p> XTT - eXtensible Task Toolkit - Feature #45 (Feedback): Display transitionshttps://opensource.cit-ec.de/issues/452012-07-24T16:54:10ZIngo Lütkebohleiluetkeb@techfak.uni-bielefeld.de
<p>There is a request to display transitions, and whether they are ever taken, in the GUI.</p>
<p>It is not directly clear what the label of a transition could be for display. It might be that the purpose of this request is better served through progress and/or liveness checking, but those are more complicated, too.</p> XTT - eXtensible Task Toolkit - Feature #34 (New): Configurable submissionhttps://opensource.cit-ec.de/issues/342012-03-16T13:43:21ZIngo Lütkebohleiluetkeb@techfak.uni-bielefeld.de
<p>Allow configuring a timeout for the first reply to 'initiated' to quickly detect the case when no server is running.</p>