Open GoogleCodeExporter opened 9 years ago
after making some research in the code I came up with the following points and
conclusions:
1. the abstract optimizer (Optimizer.java)delegates an IEstimator object. This
means the Optimizer object has a ref to an IEstimator object.
2. The only interface function is optimize() and it returns a BidBundle object.
3. Like every other module, it has a simulationReady() function that
initializes all parameters, such as the BidBundle (a non-open class --> have to
follow the basic optimizer to know how to use it), initialBid, capacity,
capacityWindow etc.
4. initialBid should be saved after each simulation into the config file for
next simulation
5. The basic Optimizer contains a LinkedList<BasicOptimizerQuery>. An
OptimizerQuery holds data for each of the 16 possible queries. The data is
optimized along the simulation's runtime, and can be obtained back from the
object.
6. The optimizer has a function to handle the daily sales report and the daily
query report coming from the server. Right now it seems that the parsing
happens there but this isn't for sure (line 169, 181, 222, 235 in
BasicOptimizer.java). Need to see if and what can be outed to the parser/DB
module
Original comment by arielthe...@gmail.com
on 17 Nov 2010 at 7:51
Original issue reported on code.google.com by
arielthe...@gmail.com
on 13 Nov 2010 at 6:23