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> Cognitive Interaction Toolkit - Feature #573 (New): catalog: licenses for more entity typeshttps://opensource.cit-ec.de/issues/5732018-05-31T20:50:05ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.de
<p>Make licenses available also for not-project types.</p> Cognitive Interaction Toolkit - Feature #537 (New): add pagination to file listings https://opensource.cit-ec.de/issues/5372017-11-23T16:05:51ZMartin Wiechmannmwiechmann@techfak.uni-bielefeld.deImage Component Library - Bug #528 (New): camera render in scene if pos is 0,0,0https://opensource.cit-ec.de/issues/5282017-11-09T11:22:13ZGuillaume Walckgwalck@techfak.uni-bielefeld.de
<p>If the camera extrinsic is identity (pos is 0,0,0), rendering in the scene creates errors</p>
<pre>
[/media/local/jenkins/jobs/icl-nivision-trunk-ci-deploy-lsp-famula-nightly/workspace/ICLGeom/src/ICLGeom/Scene.cpp:prepareForRendering,line: 149] WARNING: error visualizsing camera: no intersection -> plane normal is perdendicular to view-ray direction
</pre>
<p>Looking deeper, here is maybe the explanation :</p>
<p>When creating the vertices of the pyramid/frustrum of the camera, the 4 base corners are defined as the intersection of the image plane with the "viewRays" of the 4 image corner ( 0,0 / 0,479 / 639,479 / 639,0). However, this view rays never intersec the plane if they are in the plane which happens when position of the camera is zero. <br />See Scene.cpp:142 and Scene.cpp:145 as well as Camera.cpp:720 and Camera.cpp:770</p>
<p>there might me more to this issue, for instance why can the camera center and the image plane be at the same place, there should be focal length in between at all time. This comes maybe from the depth image model which considers the plane to be at zero Z in order to mesure depth from there.... then maybe the position of the camera center should always substract the focal length...</p> Cognitive 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> 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> 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> 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 - 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> 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> RML - RobotMetaLogger - Feature #160 (New): Add codec config key to screen probehttps://opensource.cit-ec.de/issues/1602013-03-02T13:44:15ZFlorian Lierflier@cit-ec.uni-bielefeld.de
<p>E.g. : libtheora, h264 etc.</p> XTT - eXtensible Task Toolkit - Feature #132 (New): Capability query mechanismhttps://opensource.cit-ec.de/issues/1322012-12-04T10:27:55ZIngo Lütkebohleiluetkeb@techfak.uni-bielefeld.de
<p>A capability query mechanism would make it possible to enhance the protocol, e.g. to detect servers that have crashed automatically through pinging after a timeout, without loosing backwards compatibility.</p> XTT - eXtensible Task Toolkit - Feature #36 (New): checksum computationhttps://opensource.cit-ec.de/issues/362012-06-05T12:36:41ZIngo Lütkebohleiluetkeb@techfak.uni-bielefeld.de
<p>dapi-struct should support some types of checksums, e.g. at least XOR.</p>
<p>This should be a first step towards a more general verification and auto-generation interface.</p> ivTools - Feature #25 (New): Be more tolerant with AVI formathttps://opensource.cit-ec.de/issues/252011-12-05T09:47:23ZJens Peter Lindemannj.lindemann@cit-ec.uni-bielefeld.de
<p>Change AVI reader to a standard library supporting the AVI format more generally. (Currently only certain non-audio uncompressed grayscale streams are supported).</p>