Changes between Version 296 and Version 297 of WikiStart

Timestamp:

04/28/20 11:40:09 (5 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -452 +452 @@
 
 
-The parties is a list of party URIs, just like in the session settings 
-
-The profiles is a list of profile URIs, just like in the session settings
-
-If reuseParties is set to to false, parties are drawn from the list without return. If it is set to true, parties are drawn with return (meaning all parties can occur multiple times in each session)
-
-partiesPerSession sets the number of parties (and matching profiles) for each session. Profiles are always drawn without return (never appear twice in a session)
+'teams' is a list of Team objects. Must contain at least <teamsPerSession> elements. The teamsize must match the protocol: (SAOP:1, SHAOP:2). A Team is a group of parties, each with their own parameters. Each will be coupled to a {@link ProfileList} in the generation phase of the protocol. The first team member is the team master, only he can do the bidding on the team's behalf. In SAOP, there is only 1 team member, the main party, while in the SHAOP protocol the first element is the SHAOP party and the second team member the COB party.
+
+The profileslist is a list of list of ProfileRefs. Each list of ProfileRefs has exactly 1 profile for each team member, in the same order as the Teams.
+
+If reuseTeams is set to to false, teams are drawn from the list without return. If it is set to true, teams are drawn with return (meaning all teams can occur multiple times in each session)
+
+teamsPerSession sets the number of teams (and matching profiles) for each session. Profiles are always drawn without return (never appear twice in a session)
 
 sessionsettings contains basically all the normal run-sessionsettings. This is used as a "template" for all sessions of the tournament. You can put any use any session setting here, and each session will be run according to the protocol you select here. In the example we use the SAOP protocol which takes participants and deadline as arguments, as discussed above. The participants list this time is empty, the AllPermutationsProtocol adds the the required parties to this list. So if you provide a non-empty list here, then these parties would be present in every session in the tournament.
-
-If the tournament is used with a SHAOP sessionsettings, a number of rules are used to generate the COB party from the settings
-* The COB party is assumed to be the {{{comparebids-1.0.0}}} party on the same server as the party you provide. So if you provide {{{http://server/../party1-1.2.3}}} then the cob party will be assumed to be at {{{http://server/../comparebids-1.0.0}}}.
-* The provided parties that you provide are the SHAOP parties (you can also use SAOP parties). 
-* The provided profile is also given to the SHAOP party. Be aware that you typically need a filter like {{{partial=10}}}.
-* The COB party gets the profile as specified, but without the query part. 
-* The COB and SHAOP party are thus a fixed pair.
-
 
 = Example Parties