Changes between Version 329 and Version 330 of WikiStart

Timestamp:

07/30/20 10:54:36 (4 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -273 +273 @@
 The party module also contains basic interfaces for implementing your negotiation party. These interfaces are only relevant to create a party compatible with our reference implementation of the [https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebPartiesServer partiesserver]. The main class is Party, which defines the basic functionality required for a negotiation party on our server. The heart of the party is that your Party implements Connectable<Inform,Action>. Connectable contains 2 main functions: connect and disconnect.  When connect is called, your party receives a Connection over which it receives Inform objects and can send Action objects. What exactly is sent and received is determined by the protocol (see the protocol section below). For example if the SAOP protocol is used, your party will receive a YourTurn message, after which it decides on its action and sends it into the Connection. See also the example party discussed below. 
 
+
 === Capabilities
 The party specifies its capabilities.
@@ -348 +349 @@
 ||= Implementation =||= behaviour =||= parameters =||
 ||FrequencyOpponentModel||Counts for each issue the frequency of offered values to estimate opponent UtilitySpace. || - ||
+
+
+== BOA
+Boa (Bidding, Opponent Model, Acceptance Model) is an attempt to split negotiation into three basic components: modeling the opponent's profile, determining a proper next action and determining when to accept [https://homepages.cwi.nl/~baarslag/pub/Decoupling_Negotiating_Agents_to_Explore_the_Space_of_Negotiation_Strategies_ACAN_2012.pdf]. The boa module allows parties to be written with this and provides example implementations of the components.
+
+
+=== BoaParty, DefaultBoa
+DefaultBoa is an abstract party that takes BOA components and makes it into a runnable Party. How this is done is discussed in #WritingaBoaParty.
+
+BoaParty is a party that allows you to select the BOA components as needed using the Parameters. This is discussed in more detail in #BoaParty.
+
+== BoaState
+The internal state information of DefaultBoa is stored in the BoaState. This allows efficient sharing of these internals with the components of a Boa party and helps improving efficiency of the code.
+
+The BOA model uses three major components: the OpponentModel, the BiddingStrategy and the AcceptanceStrategy. OpponentModel has been discussed already (see [#OpponentModel]). 
+
+All subcomponents may be configurable through the parameters. The DefaultBoa just shares its state, with all parameters with all subcomponents. This means that the names of your parameters should avoid names already in use.
+
+=== Bidding Strategy
+A Bidding Strategy 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.||
+
+You can create a custom BiddingStrategy by just implementing the BiddingStrategy interface. 
+
+=== Acceptance Strategy
+A Acceptance Strategy determines what action to take in which state, through this interface function
+{{{
+Boolean isAcceptable(Bid bid, BoaState negoState);
+}}} 
+The following implementations are provided with the Boa Framework
+
+||= Implementation =||= behaviour =||= parameters =||
+||TimeDependentAcceptanceStrategy||Accepts according to an exponentially decreasing utility target. See javadoc for details. ||e,k,min,max. See javadoc for details.||
 
 == BidSpace
@@ -707 +747 @@
 
 
-== 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. OpponentModel has been discussed already (see [#OpponentModel]). 
-
-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.
-
-
-=== Bidding Strategy
-A Bidding Strategy 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.||
-
-You can create a custom BiddingStrategy by just implementing the BiddingStrategy interface. 
-
-=== Acceptance Strategy
-A Acceptance Strategy determines what action to take in which state, through this interface function
-{{{
-Boolean isAcceptable(Bid bid, BoaState negoState);
-}}} 
-The following implementations are provided with the Boa Framework
-
-||= Implementation =||= behaviour =||= parameters =||
-||TimeDependentAcceptanceStrategy||Accepts according to an exponentially decreasing utility target. See javadoc for details. ||e,k,min,max. See javadoc for details.||