__color__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter
3,12,graphviz gets confused by multi-word lexical items,gui,,,defect,somebody,new,2009-07-02T17:24:51Z+0100,2009-07-02T17:24:51Z+0100,,kowey
3,16,possible polarity filtering bug,core,,,defect,somebody,new,2009-07-03T12:30:30Z+0100,2009-07-03T12:30:30Z+0100,"{{{
dist/build/geni/geni -m examples/chatnoir/macros -l examples/chatnoir/lexicon -s examples/chatnoir/suite  --verbose --testcase=""le_mechant_chat_noir_chasser_le_souris"" --opts='pol' --rootfeat='cat:p'
Loading test suite examples/chatnoir/suite... 4 entries
Loading trees examples/chatnoir/macros... 11 entries
Loading lexicon examples/chatnoir/lexicon... 15 entries
Loading test suite examples/chatnoir/suite... 4 entries
Lexical items selected:
 noir
 chat
 chasser
 le
 le
 mechant
 souris

Trees anchored (family) :
 noir:adj_post
 chat:nC
 chasser:vArity2:rel1vn0
 chasser:vArity2:rel0vn1
 chasser:vArity2:qu1vn0
 chasser:vArity2:qu0vn1
 chasser:vArity2:n0vn1
 chasser:vArity2:vinfn1
 le:Det
 le:Det
 mechant:adj_pre
 souris:nC

geni: [polarities] No instances of cat in [].
}}}",kowey
3,38,empty strings should be quoted when producing geni output,core,,,defect,,new,2009-10-10T10:50:57Z+0100,2009-10-10T10:50:57Z+0100,"Should be (""""), was ()

This affects geniconvert on the surface, but it's really a problem with the core printing code.",kowey
3,40,geni: Prelude.foldr1: empty list,core,,,defect,,new,2009-12-07T18:17:56Z+0000,2009-12-07T18:20:22Z+0000,No idea why this happens.,kowey
3,49,results out of order when pre-terminals have more than one terminal,core,,,defect,,new,2010-01-04T21:11:38Z+0000,2010-01-04T21:11:38Z+0000,"(foo (x y)) will give the linear order y x...
",kowey
3,7,percolate features during morphological realisation,core,,GenI 0.22,defect,kowey,assigned,2009-03-31T11:54:29Z+0100,2009-09-29T09:31:15Z+0100,"The morphological realisation (built-in) is dumb in that it unifies each pre-terminal node of the derived tree independently with the morphological lexicon.

This is not good, because it does not allow for mutually exclusive realisations:
he hold*s* the apple vs you hold the apple

Right now, the workaround is to supply the necessary features via the input semantics (morphinfo file), but ideally you should be able to just make it work automatically.",kowey
3,15,feeding non-existent test case to GenI causes it to say bug in GenI,core,,GenI 0.22,defect,somebody,new,2009-07-03T11:38:39Z+0100,2009-09-29T09:29:38Z+0100,,kowey
3,36,document basic flags in manual,doc,,GenI 0.22,defect,,new,2009-09-25T11:44:35Z+0100,2009-09-28T17:01:19Z+0100,,kowey
4,51,avoid crashing if ViewTAG not found,gui,,,defect,,new,2011-07-28T17:41:23Z+0100,2011-07-28T17:41:23Z+0100,GenI should not crash if ViewTAG is not found; it should do something friendlier like give a pop-up box.,kowey
3,8,alternative syntax for anchor (or other) features? generalisation of morphinfo,gui,,,enhancement,somebody,new,2009-03-31T11:56:12Z+0100,2009-03-31T11:56:12Z+0100,"The morphinfo file creates a maintenance problem -- too many files to keep track of and update.  A better solution would be something that lets you supply similar information within the input semantics (test suite).

So something like
feature(m,person:2)
in the input semantics",kowey
3,10,root feature in main window,gui,,,enhancement,somebody,new,2009-07-02T17:22:39Z+0100,2009-07-05T20:13:07Z+0100,"And not just in configuration window...

My idea for how this should work is that it be another field in the input semantics area.  I think this would take some refactoring, some kind of function that goes from config to the input semantics area and back.",kowey
3,21,simple indexing mechanism,core,,,enhancement,somebody,new,2009-07-28T18:47:25Z+0100,2009-07-28T18:50:50Z+0100,"This should reduce generation time somewhat.  It occurred to me that there's actually a very simple way to index the generation chart: just use the semantic index or the category or even a tuple of the root node.  For atomic disjunction and variables, just dump into a variable slot that we always have to look up.

Note that substitution would have to be changed so that items with open substitution sites go back at the end of the agenda instead of on the chart.

Also note that substitution sites with disjunctive or variable indices would just have to look at all chart items.",kowey
3,25,keep track of sets of adjunctions into the same node [old tracker],core,,,enhancement,somebody,new,2009-09-08T21:16:27Z+0100,2009-09-08T21:16:27Z+0100,"This could be a form of packing where we try to store adjunctions into the ""same"" node as a set (that can happen in any order).

Would only be really useful if multi-adjunction happens a lot",kowey
3,27,polarity precompilation [old tracker],core,,,enhancement,somebody,new,2009-09-08T21:18:17Z+0100,2009-09-08T21:18:17Z+0100,What on earth did I mean by this?,kowey
3,48,display number of results found in GUI and console mode...,gui,,,enhancement,,new,2009-12-28T18:11:38Z+0000,2009-12-28T18:11:38Z+0000,Both unique and overall.,kowey
3,14,don't use root feature filtering if it's not specified,core,,GenI 0.22,enhancement,somebody,new,2009-07-03T11:33:27Z+0100,2009-09-28T17:01:41Z+0100,,kowey
3,43,support subsumption with unification variables in relations,core,,GenI 0.22,enhancement,,new,2009-12-09T16:38:06Z+0000,2009-12-09T16:38:06Z+0000,"Not just the arguments, but the relations themselves.",kowey
3,44,elementary tree semantics should be unification of tree schema and lemma semantics,core,,GenI 0.22,enhancement,,new,2009-12-09T16:41:53Z+0000,2009-12-09T16:41:53Z+0000,See also #43,kowey
4,1,bracketed output (new command line argument),gui,,,enhancement,somebody,new,2009-01-17T14:39:40Z+0000,2009-01-17T14:39:58Z+0000,"The bracketed output is a compromise between a full parse tree and a plain string.

Parse tree:
{{{
S(NP(somebody),VP(VP(V(saw),NP(something)),PP(somewhere)))
}}}

Bracketed output:
{{{
somebody ((saw something) somewhere)
}}}

Notice that we try very hard to avoid excess parentheses.  The point is to make it easier for grammar hackers to understand (for example), why we get different instances of the same output.  So we want to keep things as readable as possible",kowey
4,2,replace automaton code with HaLeX?,core,,,enhancement,somebody,new,2009-01-18T09:57:40Z+0000,2009-07-02T17:25:59Z+0100,"See: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/HaLeX

This may affect the polarity automaton performance, but (a) probably not by much and (b) it would only be overhead.  The really important thing is to be fanatical about keeping GenI minimalistic",kowey
4,6,disjunctions of paraphrase selectors,gui,,,enhancement,somebody,new,2009-03-19T18:36:04Z+0000,2009-03-19T18:36:04Z+0000,"Luciana Benotti asked:
> We know that in Geni you can select tree properties in the input  
> semantics by using square brackets next to a literal, for example,  
> runs(e,j)[Active]. Is there a way of indicating a disjunction of the  
> tree properties? Such as runs(e,j)[Active|Passive] in order to obtain  
> the active and passive realizations of runs(e,j).
",kowey
4,41,separate trash pile for last operation performed,gui,,,enhancement,,new,2009-12-09T14:32:50Z+0000,2009-12-09T14:32:50Z+0000,This should make it easier to figure out what GenI is doing and why.,kowey
3,18,unification monad,core,,,task,somebody,new,2009-07-22T11:16:12Z+0100,2009-07-22T11:16:12Z+0100,"OK, it doesn't have to be a monad.  But I want to have some sort of abstraction that guarantees that when I do unification on something, the results from previous unification will be automatically propagated to that thing.  Seems like it should be fairly straightforward.  You could just model this as a state monad for example, and have the unification function get/put the substitutions state.

What may be annoying is having to write a monad transformer and slip it into our current MT stack.

The goal is to have something that makes our code easier to write, and less error-prone, while also staying cheap (we shouldn't be doing any needless traversals).",kowey
3,24,lexical selection factorisation [old todo list],core,,,task,somebody,new,2009-09-08T21:13:55Z+0100,2009-09-08T21:13:55Z+0100,I don't understand what this is about :-(,kowey
3,26,RND: plugging GenI into a systemic grammar based generator [old tracker],core,,,task,somebody,new,2009-09-08T21:17:48Z+0100,2009-09-08T21:17:48Z+0100,The idea is for the SFG based system to generate inputs to GenI,kowey
3,34,include GenI version in manual,core,,,task,somebody,new,2009-09-25T11:20:58Z+0100,2009-09-25T11:20:58Z+0100,"Now that we have geni --version, this should be easy enough...",kowey
3,35,jsonify stupidmorph and tomorph,core,,GenI 0.22,task,kowey,assigned,2009-09-25T11:38:34Z+0100,2009-09-29T09:29:17Z+0100,,kowey
4,22,move NLP.GenI.Console regression testing code to test module,core,,,task,somebody,new,2009-09-04T12:49:54Z+0100,2009-09-04T12:49:54Z+0100,"Hmm, now I have a better idea about the argument for separating test logic from business logic.",kowey
4,28,output to 3rd party morphological generator should include variables,core,,,task,somebody,new,2009-09-11T12:25:40Z+0100,2009-09-11T12:25:40Z+0100,"This is just a TODO.  Check the source code to see if GenI will output variables in feature structures to the third party morphological realiser.

Right now literate GenI only shows constants in the example.
",kowey
5,17,outsource to graphviz library,core,,,task,somebody,new,2009-07-18T16:16:00Z+0100,2011-07-20T19:32:17Z+0100,Note the graphviz is licensed under the EPL (sigh!) so we would have to create an exception in our GPL to allow people to distribute the two as one program.,kowey
