= Known bugs =
The overview below visualizes the bugs found in Genius documented in the tracker and by students. I could also have used the bugtracker, but this tracker also contains bugs of the !PocketNegotiator. Before removing a bug, please ensure that it is fixed in '''all main branches'''.


== Genius 4.0 decisions ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||472,474||Opt for Xstream for serialization of domains, or keep all files the same||High||-||
||-||Determine which branch(es) are going to be kept up-to-date as main branches||High||-||
||-||Determine which branch(es) are going to be merged||High||-||

== Core ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||462||Check for memory leaks, specifically agent cleanup||High||1||
||467||AgentID is not required in actions||Low||1||
||320||Domain files and utility spaces should be checked upon repository loading, in some cases the utility may be higher than 1||Low||3||
||25,57||Implementation of real issues should be checked and fixed||Medium||3 - 5||
||25||Implementation of integer issues should be checked and fixed||Medium||3 - 5||
||449||Tournament sessions all have number one||Low||1||
||475||The session counter does not function, it always returns one||Low||1||
||-||Currently cost constrains are not generic (cost <= 900). I think it would be nice if we could set this per domain||Low||2||
||105||It is currently not possible to load a utiliyspace directory, the domain is requested, which is strictly not necessary||Low||1||
||469,470||Use a (single) generic evaluation method in Utilspace instead of Evaluator||Low||10||
||468||Make an objective extend an issue||Low||2||
||31||A utilityspace can be loaded with any domain||Low||1||
||37||Objective.getSiblings overly complex||Low||1||
||38||Implementation of getType of issue seems inefficient||Low||1||
||60,72||Format of XML files needs to be checked, it is possible to cripple agents using corrupted domains||Medium||1||
||64,67||Ensure that the type of issue matches the evaluator||Low||1||


== Extra features ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||461||Allow the analysis of stored negotiations by the Analytical toolbox||Low||1||
||632||GNU license||Low||1||
||-||Store global as ini file||Low||2||
||-||Decision function predictor for BOA framework||Low||3||
||-||Add options such as deadline, play both sides, self play as tournament options which can be specified in the GUI||Low||1||

== GUI ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||68,70,71,435,445,459,460||Creating a new scenario using the GUI is not user friendly and buggy||Medium||5 - 10||
||57||Check creating real issue domains using GUI||Low||5||
||-||Upon starting a match the tournament progress table may not be visible||Low||1||
||443||Ensure that the deadline can be set and works||Low||1||
||458||Sometimes the costs in the GUI of the values of an issue are reset to zero.||Low||1||
||26||Show model gives an exception if the negotiation template file name is left empty||Low||1||