Changes between Version 323 and Version 324 of WikiStart
- Timestamp:
- 07/30/20 10:17:59 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v323 v324 697 697 So basically you just implement the functions that provide the opponent model, bidding strategy and acceptance strategy into the DefaultBoa party. Your jar file has to be prepared identically as with a normal party. 698 698 699 === Running the parameterized BoaParty in a custom project 700 As you include the boa package, you also include the standard BoaParty in your module. To run that as the party implementation, simply fix the pom references to mainClass to point to the standard BoaParty: {{{<mainClass>geniusweb.boa.BoaParty</mainClass>}}}. Remember that this party requires the proper paremeters to run. This party differs from the original in that all your custom components are now also available. 701 702 699 703 == BoaState 700 704 The internal state information of DefaultBoa is stored in the BoaState. This allows efficient sharing of these internals with the major components of a Boa party. … … 703 707 704 708 These components may be configurable through the parameters. Currently they just share the parameters with the DefaultBoa party. This means that the names of your parameters should avoid names already in use. 709 705 710 706 711 == Bidding Strategy … … 713 718 ||= Implementation =||= behaviour =||= parameters =|| 714 719 ||TimeDependentBiddingStrategy||Bids according to an exponentially decreasing utility target. See javadoc for details. ||e,k,min,max. See javadoc for details.|| 720 721 You can create a custom BiddingStrategy by just implementing the BiddingStrategy interface. 715 722 716 723 == Acceptance Strategy