GENIUS 2

Genius2 is an open architecture for heterogeneous negotiating parties via the internet. It provides the basis for an implementation of a testbed for negotiating parties that includes a set of negotiation problems for benchmarking parties, a library of negotiation strategies, and analytical tools to evaluate an party's performance and their strategies allows user.

Genius2 overview

Genius2 contains a number of components

name	description	more information
the core	the data structures for issues, values, bids, profiles, events and actions, agents etc.	here
profilesserver	a web server that provides profiles and domain descriptions	​profiles server
partiesserver	A web server that provides instances of running parties to use for negotiation	​parties server
runserver	A web server that can run sessions and tournaments	​run server

You can either run these servers locally on either your computer or on your web server, or use a public server somewhere else.

For creating your own profile or party, you don't need these services. You only need them when your party is to be run in a negotiation that you need the runserver. The runserver then will need the partiesserver to atart up your agent, and your agents generally will receive a link to a profilesserver to fetch the profiles from.

Writing a party in Java

Example parties can be found ​here. An agent is compiled with maven. After compilation (mvn package) you get a target/yourparty-X.Y.Z-jar-with-dependencies.jar that can be copied into the parties server for deployment.

The basic structure of an agent looks like this

public class RandomParty extends DefaultParty {
	@Override
	public void notifyChange(Inform info) {
		// System.out.println("Received info:" + info);
		if (info instanceof Settings) {
			fetchProfile(((Settings) info).getProfile());
			this.me = ((Settings) info).getID();
		} else if (info instanceof ActionDone) {
			lastActor = ((ActionDone) info).getAction().getActor();
			Action otheract = ((ActionDone) info).getAction();
			if (otheract instanceof Offer) {
				lastReceivedBid = ((Offer) otheract).getBid();
			}
		} else if (info instanceof YourTurn) {
			myTurn();
		}
	}

	private void myTurn() {
		Action action;
		if (lastReceivedBid != null && profileint.getProfile()
				.getUtility(lastReceivedBid).doubleValue() > 0.6) {
			action = new Accept(lastActor, lastReceivedBid);
		} else {
			AllBidsList bidspace = new AllBidsList(getProfile().getDomain());
			long i = random.nextInt(bidspace.size().intValue());
			action = new Offer(me, bidspace.get(BigInteger.valueOf(i)));
		}
		try {
			getConnection().send(action);
		} catch (IOException e) {
			e.printStackTrace();
		}

	}

	@Override
	public Capabilities getCapabilities() {
			return new Capabilities(new HashSet<>(
					Arrays.asList(new ProtocolRef(new URI("SAOP")))));
	}

	@Override
	public String getDescription() {
		return "places random bids until it can accept an offer with utility >0.6";
	}

}

Preparing the jar file

In order to put your agent on the ​partiesserver for running, you need a jar file of your party.

Normally the party includes all dependencies. The jar files are loaded with an isolated jar class loader that should avoid collisions with possibly identically named but possibly different packages in other jar files.

Party jar files must have a Main-Class set in the MANIFEST.MF file. This main-class must implement Party and have a no-arg constructor.

The example randomagent does this from the maven build script.

We recommend to do initialization of the party only in the init() and not in the constructor or static code. This because instances of your class can be made both for extracting general info as getDescription(), or to really run your class.

Create a domain

There is not yet a domain editor available so you have to create domains by manually editing a file with JSON code.

A domain looks like this

{"name":"jobs",
 "issuesValues":{
  "lease car":{"values":["yes","no"]},
  "permanent contract":{"values":["yes","no"]},
  "career development opportunities":{"values":["low","medium","high"]},
  "fte":{"values":["0.6","0.8","1.0"]},
  "salary":{"values":["2000","2500","3000","3500","4000"]},
  "work from home":{"values":["0","1","2"]}
 }
}

• The name is just a string. It must match the filename and directory name when placed on the profiles server. So your directory must be domainsrepo/jobs and the filename must be jobs.json.
• The issueValues contains a dictionary with issues. Each issue is indicated by a name (a string), followed by a column (:) and then a dictionary. The dictionary can contain either a discrete valueset or a number valueset
  • a discrete valueset looks like "values", a column and then a list of discrete values (all strings)
  • a number valueset contains a range of numbers and looks like {"range":["12.2","12.6","0.3"]} so "range:" followed by a list of 3 values. The first value is the minimum value in the range, the second the maximum value in the range, and the third the step value. This example range thus contains 12.2 and 12.5 (the next one would be 12.8 but that is already outside the range).

Create a profile

A profile (a.k.a utilityspace) looks like this

{
	"LinearAdditiveUtilitySpace": {
		"issueUtilities": {
			"salary": {
				"discreteutils": {
					"valueUtilities": {
						"2000": 0,
						"2500": 0.25,
						"3000": 0.3,
						"3500": 0.75,
						"4000": 1.0
					}
				}
			},
			"fte": {
				"discreteutils": {
					"valueUtilities": {
						"0.6": 0.25,
						"0.8": 0.5,
						"1.0": 0.75
					}
				}
			},
			"work from home": {
.....
					}
				}
			}
		},
		"issueWeights": {
			"salary": 0.24,
			"fte": 0.32,
			"work from home": 0.18,
			"lease car": 0.06,
			"permanent contract": 0.16,
			"career development opportunities": 0.04
		},
		"domain": {
			"name": "jobs", .....
		},
		"name": "jobs1"
	}
}

This is an "LinearAdditiveYtilitySpace", other utilityspaces would have different contents. It contains a number of components:

• issueUtilities. Here, each issue value from the domain gets a utility assigned. The two types of issue values each having their matching utility function:

Issue Value class	Utility class	json serialization example
DiscreteValue	DiscreteValueSetUtilities	"discreteutils": { "valueUtilities": { "2000": 0, "2500": 0.25, "3000": 0.3, "3500": 0.75, "4000": 1.0 } }
NumberValue	NumberValueSetUtilities	numberutils": { "lowValue":12, "lowUtility":0.3, "highValue":18, "highUtility":0.6 }

• issueWeights: this is a map, for each issue there is a value in [0,1] and the sum of the weights in this map must be exactly 1.

• domain: identical to above. We replaced some issueValues with "..." in this example .
• name: a simple string with the name of the profile. The name must match the filename of the profile.

Bids

A Bid is a map with the issue names as keys (strings) and the values being an element from the valueset as in the domain description.

A bid typically looks like

{ "salary":"2000", "fte":"0.8", "work from home","0.6" ...}

This example also illustrates a problem with the json parser. In our jobs example domain, all issues have discrete values, so "2000" is just a string, not a number.

In this case, a specific problem occured that we had to figure a workaround for. Suppose we have a bid in the jobs domain:

Internally BigDecimal is used for computing and storing issue values, utilities etc. Doubles always give rounding problems and can not be assumed to sum properly to 1 and therefore can not be used.

In the special case of issue values, we can not determine a priori if the values are

Since JSON parses normal number directly into doubles, it is necessary to place numbers also inside string objects ("..."). That in turn forces us to put some hard marker in the string to see if "1" would be a discrete value or number value. To do this, any Value contained in a string that is of the form "=X.Y" where X is a positive or negative integer and Y a positive integer is a NumberValue. Anything else is interpreted as a DiscreteValue.

Genius2 sources

downloading source code

You can browse the genius2 core sources directly using the browse button at the right top of this page.

You can download the source code of this component from

​https://tracinsy.ewi.tudelft.nl/svn/genius2/

Import all sources in Eclipse

Normal developers that write new parties do not need to install the genius2 source code. This is only needed if you want to debug/trace into the genius2 code for instance for debugging or understanding the inner workings of genius2.

Install Subclipse using "help/Eclipse MarketPlace" and search for subclipse. Disable the JavaHL native DLLs and install. NOTE: due to a bug in Eclipse Photon the marketplace may not work. We suggest to upgrade...

You may get some errors on JavaHL library. To get rid of those, go to preferences/Team/SVN/

• disable General SVN settings / JavaHL
• SVN interface/Client: select SVNKit instead of JavaHL.

Right click in Package Explorer in Eclipse, select "Import/SVN/Checkout Projects from SVN". Select the root of the project, finish (selecting sub-projects will result in a stupid loop in the checkout procedure in Eclipse and won't lead anywhere...)

Richt click on the checked-out project that you want eclipse to recognise as Maven project (the project are maven but Eclipse does not recognise this after check-out). Select import/maven/existing maven projects. Finish.

Note. Eclipse does not automatically recognise this as a maven project because Eclipse supports this only with GIT repositories while we use SVN.