Changes between Version 315 and Version 316 of WikiStart

Timestamp:

07/29/20 14:19:28 (4 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -506 +506 @@
 }}}
 
-Each of the components can also be parameterized. You just add their parameters to the list. All parameters are forwarded to all components, these components will figure out themselves which of the provided ones are relevant for them.
+Each of the components can also be parameterized. You just add their parameters to the list. All parameters are forwarded to all components, these components will figure out themselves which of the provided ones are relevant for them. See the section on writing a Boa Party below for more details on the components.
 
 
@@ -681 +681 @@
 }}}
 
+
 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. 
+
+== BoaState
+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.
+
+A DefaultBoa uses three major components: the OpponentModel, the BiddingStrategy and the AcceptanceStrategy. 
+
+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.
+
+=== BiddingStrategy
+A BiddingStrategy determines what action to take in which state, through this interface function
+{{{
+Action getAction(BoaState state);
+}}} 
+The following implementations are provided with the Boa Framework
+
+||Implementation||behaviour||parameters||
+||TimeDependentBiddingStrategy||Bids according to an exponentially decreasing utility target. See javadoc for details. ||e,k,min,max. See javadoc for details.||
 
 = Writing a party in other languages