Here - Agents Lab - University of Nottingham

Recommendations

Info

tate them in the same way as in the interface. Additionally, other non abstractmethods can be implemented with arbitrary domain logic to bring about servicefunctionalities. If no generation is wanted, the wrapper class can also beimplemented completely by the programmer.Fig. 8. Banking REST web service screenshotIn Fig. 8 a screenshot of the banking REST web interface is shown. Thisweb site is produced by a banking agent with a publish annotation as shownabove. This interface is automatically generated by the getServiceInfo() methodand is per default linked to the root resource URL of the service (here localhost:8080/banking1/).It can be seen that the web site contains a new part foreach service method with basic information about it, i.e. the method signature,REST call details, the URL and a form with input elds for all parameters.According to the media types the service method is able to consume a choicebox is added to allow the user specifying in which format the input string shallbe interpreted. This can be seen in the getAccountStatement() method, whichaccepts JSON and XML. Currently, the result value of a method call is producedin the same media type as the request but it is easily possible to add anothercontrol that allows to request the service to produce an alternative format.4.3 WSDL InvocationWSDL service invocation is illustrated using a geo IP service, which oers amethod to determine the position of an IP address. After having generated theJava classes for data types and service using wsimport, based on the generatedservice interface an asynchronous version needs to be dened (cf. lines 1-3 in33
01: public interface IGeoIPService {02: public IFuture getGeoIP(String ip);03: }04:05: @Agent06: @ProvidedServices(@ProvidedService(type=IGeoIPService.class,07: implementation=@Implementation($component.createServiceImplementation(08: new Mapping(GeoIPService.class)))09: public class GeoIPAgent {10: . . .11: }Fig. 9. Java code for invoking a WSDL serviceFigure 9). In the component declaration (lines 4-8) a provided service is speciedusing the asynchronous service interface (line 5) and an automatically generatedimplementation (lines 6-7). The framework method that is called to create theimplementation takes as argument the wsimport generated service class.4.4 REST InvocationREST invocation is exemplied using the Google chart API, which can be usedto create chart images of dierent types for a given data set. The implementationis shown in Figure 10. It consists of the asynchronous service interface (lines 1-4), the REST service mapping (lines 6-13) and the chart component denition(lines 17-23). For illustration purposes the component interface is reduced to onemethod that can be used to create a bar chart. The method expects the widthand height of the image to produce, possibly multiple data series, label textsand series colors as input and produces an png image as output. The mapping isdened within an interface called IRSChartService (lines 6-15). It declares thatthe generated REST call uses HTTP GET on the google chart URL. In addition,parameter mappers for in- and output values need to be employed (lines 10-11,mapper code not shown) as the REST API expects a specic textual encodingsfor the data. The component implementation is very similar to the WSDL variantwith exception of the mapping denition in terms of an interface.Fig. 11 shows a chart application screenshot. In the background the Jadexcontrol center window of the platform is displayed while in the foreground thechart window is shown. The application consists of two agents. The Chart-Provider agent that takes over the wrapper role and oers an IChartService instanceand on the other hand the ChartUser agent which own the graphical userinterface for entering chart requests and displaying the resulting chart graphics.On the lower left hand side of the control center the running agent instanceswith required and provided services are depicted. It can be seen that the Chart-Provider oers an IChartService and the ChartUser requires an IChartService.The processing is done as follows. After a user has entered some congurationdata in the chart window including e.g. width and height of the target image,series data, and colors, and issued a chart request via pressing the draw but-34
Page 2 and 3: Proceedings of the Tenth Internatio
Page 4 and 5: OrganisationOrganising CommitteeMeh
Page 6: Table of ContentseJason: an impleme
Page 10 and 11: in Sect. 3 the translation of the J
Page 12 and 13: init_count(0).max_count(2000).(a)(b
Page 14 and 15: For instance, a failure in the ERES
Page 16 and 17: {plan, fun start_count_trigger/1,fu
Page 18 and 19: single parameter, an Erlang record
Page 20 and 21: 1. Belief annotations. Even though
Page 22 and 23: decisions taken during the design a
Page 24 and 25: Conceptual Integration of Agents wi
Page 26 and 27: Fig. 2. Active component structurep
Page 28 and 29: the service provider component. As
Page 30 and 31: Fig. 4. Web Service Invocationretri
Page 32 and 33: 01: public interface IBankingServic
Page 36 and 37: 01: public interface IChartService
Page 38 and 39: implementations being available for
Page 41: deliberative behavior in BDI archit
Page 44 and 45: layer modules (i.e. nodes) can be d
Page 46 and 47: different methods to choose the cur
Page 48 and 49: also a single scheduler module, imp
Page 50 and 51: andom choice (OR), conditional choi
Page 52 and 53: - Dealing with conflicts based on p
Page 54 and 55: 5. Brooks, R. A. (1991) Intelligenc
Page 56 and 57: An Agent-Based Cognitive Robot Arch
Page 58 and 59: It has been argued that building ro
Page 60 and 61: EnvironmentHardwareLocal SoftwareC+
Page 62 and 63: a cognitive layer can connect as a
Page 64 and 65: can reliably be differentiated and
Page 66 and 67: 4 ExperimentTo evaluate the feasibi
Page 68 and 69: learn or gain knowledge from experi
Page 70 and 71: A Programming Framework for Multi-A
Page 72 and 73: exchange and storage of tuples (key
Page 74 and 75: Although some success [13] [14] hav
Page 76 and 77: as well as important non-functional
Page 78 and 79: component plans have been instantia
Page 80 and 81: A in the example) can evaluate all
Page 83 and 84: 1. robot-1 issues a Localization(ro
Page 85 and 86:
ACKNOWLEDGMENTThis work has been su
Page 87 and 88:
The code was analysed both objectiv
Page 89 and 90:
a conversation is following. Additi
Page 91 and 92:
the context of a communication-heav
Page 93 and 94:
Table 1. Core Agent ProtocolsAgent
Page 95 and 96:
statistically significant using an
Page 97 and 98:
to the conversation and has a perfo
Page 99 and 100:
principal reasons. Firstly, it is a
Page 101 and 102:
2. Muldoon, C., O’Hare, G.M.P., C
Page 103 and 104:
In the following section we will at
Page 105 and 106:
DevelopmentProductionHuman Readabil
Page 107 and 108:
will then evaluate this new format
Page 109 and 110:
encoder, it is first checked if the
Page 111 and 112:
nents themselves. However, since th
Page 113 and 114:
optimized for this format feature s
Page 115 and 116:
Java serialization and Jadex Binary
Page 117 and 118:
10. P. Hoffman and F. Yergeau, “U
Page 119 and 120:
Caching the results of previous que
Page 121 and 122:
querying an agent’s beliefs and g
Page 123 and 124:
or relative performance of each pla
Page 125 and 126:
were run for 1.5 minutes; 1.5 minut
Page 127 and 128:
Size N K n p c qry U c upd Update c
Page 129 and 130:
epresentation. The cache simply act
Page 131 and 132:
6 ConclusionWe presented an abstrac
Page 133 and 134:
Typing Multi-Agent Programs in simp
Page 135 and 136:
1 // agent ag02 iterations (" zero
Page 137 and 138:
3.1 simpAL OverviewThe main inspira
Page 139 and 140:
3.2 Typing Agents with Tasks and Ro
Page 141 and 142:
Defining Agent Scripts in simpAL (F
Page 143 and 144:
that sends a message to the receive
Page 145 and 146:
* error: wrong type for the param v
Page 147 and 148:
Given an organization model, it is
Page 149 and 150:
Learning to Improve Agent Behaviour
Page 151 and 152:
2.1 Agent Programming LanguagesAgen
Page 153 and 154:
choosing actions is to find a good
Page 155 and 156:
1 init module {2 knowledge{3 block(
Page 157 and 158:
of a module. For example, to change
Page 159 and 160:
if bel(on(X,Y), clear(X)), a-goal(c
Page 161 and 162:
mance. Figure 2d shows the same A f
Page 163 and 164:
the current percepts of the agent.
Page 165:
Author IndexAbdel-Naby, S., 69Alelc
show all

Here - Agents Lab - University of Nottingham

Create successful ePaper yourself

Delete template?

Save as template?