Changes between Version 105 and Version 106 of WikiStart

Timestamp:

04/13/21 09:13:04 (4 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -73 +73 @@
 Figure. Settings for playing conceder (jobs1) against SHAOP (jobs2?partial=10)
 
-== Showing the results of a session run
-Some time (depending on the deadline you set) after starting your session, links are provided to the log file, and to a visualizer that can plot the utilities of the bids recorded in the log file.
-
-[[Image(sessioncompleted.png, 70%)]]
-
-
-You can also view the log files later, through the "View logs" option in the main menu of the runserver.
-
-
-
-If you click on "view the log file" you get an exact log of all the actions taken by the parties. Notice that in the SAOP protocol, this log file becomes available only after the session has been completed. 
-
-You can click on "render a utilities plot" to show a graphical representation of the utilities of all the offers made in the session, as in the figure below. Notice that this is only possible if (1) the log file is already available (2) the profiles are publicly available (3) the profiles are a UtilitySpace.
-
-[[Image(utilplot.png, 70%)]]
-
-If you ran a SHAOP session, the plotter tries to show the utilities of the SHAOP parties in the negotiation as they place the real Offers. However the SHAOP party uses a partial profile without utility function. The plotter tries to be smart here: if the profile is a filtered utilityspace of the form "URL.?partial=N" it removes the "partial=N" filter option and uses the unfiltered profile for the plotting. It should be clear that these utilities have no real meaning in the partial profile that the SHAOP party is using, but the partial profile will normally get the utilities sorted corresponding to this original profile.
-
-The information made available about the running session is determined by the protocol. For SAOP, there are currently two ways to check the progress on the running session
-* Check the output of the tomcat web server (eg in catalina.out)
-* Check the log files written by the protocol. 
-
-In general log files are available only after the session completes, because this information could be abused by the negotiating parties.
-
-At the bottom of the plot is a message "Agreement:X" where X can be 'yes', 'no' or 'partial' (or '?' if the protocol is not fully supported by the plotter). 
-
-[[Image(mopacplot.png, 50%)]]
-
-The MOPAC protocol shows the utilities of the offers made by the parties. In each round, all remaining parties place an offer (in non-deterministic order) so as the negotiation progresses less and less parties make subsequent offers. In negotiations with many parties and partial deals it may be necessary to check the log file for further details about what happened in the negotiation.
-
 === Learn
 A learn session is special, because no negotiation is done during this session. 
 Therefore, you can not select any profiles. 
 You should provide the parties their 'persistentstate' and 'negotiationdata'. The GUI already adds these to the parameters, but the values probably should be fixed to the values you used in the earlier sessions. 
+
+
+
+
+== Showing the results of a session run
+Some time (depending on the deadline you set) after starting your session, links are provided to the log file, and to a visualizer that can plot the utilities of the bids recorded in the log file.
+
+[[Image(sessioncompleted.png, 70%)]]
+
+
+You can also view the log files later, through the "View logs" option in the main menu of the runserver.
+
+
+
+If you click on "view the log file" you get an exact log of all the actions taken by the parties. Notice that in the SAOP protocol, this log file becomes available only after the session has been completed. 
+
+You can click on "render a utilities plot" to show a graphical representation of the utilities of all the offers made in the session, as in the figure below. Notice that this is only possible if (1) the log file is already available (2) the profiles are publicly available (3) the profiles are a UtilitySpace.
+
+[[Image(utilplot.png, 70%)]]
+
+If you ran a SHAOP session, the plotter tries to show the utilities of the SHAOP parties in the negotiation as they place the real Offers. However the SHAOP party uses a partial profile without utility function. The plotter tries to be smart here: if the profile is a filtered utilityspace of the form "URL.?partial=N" it removes the "partial=N" filter option and uses the unfiltered profile for the plotting. It should be clear that these utilities have no real meaning in the partial profile that the SHAOP party is using, but the partial profile will normally get the utilities sorted corresponding to this original profile.
+
+The information made available about the running session is determined by the protocol. For SAOP, there are currently two ways to check the progress on the running session
+* Check the output of the tomcat web server (eg in catalina.out)
+* Check the log files written by the protocol. 
+
+In general log files are available only after the session completes, because this information could be abused by the negotiating parties.
+
+At the bottom of the plot is a message "Agreement:X" where X can be 'yes', 'no' or 'partial' (or '?' if the protocol is not fully supported by the plotter). 
+
+[[Image(mopacplot.png, 50%)]]
+
+The MOPAC protocol shows the utilities of the offers made by the parties. In each round, all remaining parties place an offer (in non-deterministic order) so as the negotiation progresses less and less parties make subsequent offers. In negotiations with many parties and partial deals it may be necessary to check the log file for further details about what happened in the negotiation.
+
+
 
 == Run a Tournament