= 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||-||

== 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||
||57||Implementation of real issues should be checked and fixed||Medium||5||
||449||Tournament sessions all have number one||Low||1||
||475||The session counter does not function, it always returns one||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)'''||
||435,445,459,460||Creating a new scenario using the GUI is not user friendly and buggy||Medium||5 - 10||
||-||GUI exceptions thrown during a tournament||low||1||
||-||Caching of repository, now each draw of the GUI the repository is reloaded||low||1||
||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||
||439||Show short preference profile name instead of full path in tournament||Low||1||
||437||Make it possible to edit information in the tournament settings. What happens now is that the previous setting (for example a set of agent A agents) is cleared.||Low||2||