GameTableRep::WriteNfgFile (in gametable.cc) simply iterates the table of results and outputs the corresponding outcome number. However, if a strategy is deleted from the game, we do not reallocate the table (we simply omit indexing some of the entries of the flattened vector). As a result the list of outcomes is not correct.
Fixing this is straightforward, simply by using the pure strategy profile iterator. The pure strategy profile iterator already has had some improvements that mean that it is largely doing efficient indexing calculations so actually the performance loss is not that bad (and this is not a performance-critical loop anyway!)
GameTableRep::WriteNfgFile(ingametable.cc) simply iterates the table ofresultsand outputs the corresponding outcome number. However, if a strategy is deleted from the game, we do not reallocate the table (we simply omit indexing some of the entries of the flattened vector). As a result the list of outcomes is not correct.Fixing this is straightforward, simply by using the pure strategy profile iterator. The pure strategy profile iterator already has had some improvements that mean that it is largely doing efficient indexing calculations so actually the performance loss is not that bad (and this is not a performance-critical loop anyway!)