Infrastructure Development for a London-based Disaster Test Scenario
Ongoing project...
Objective
This project aims to develop a geographic information model based on part of the City of London, so that such an information can be used by the RoboCup Rescue simulator . The idea is to use this scenario to analyse and improve the performance emergency response teams in disaster situations like that:
|
"One hour ago an aeroplane crashed on the City of London. The aeroplane, a civil cargo transport, had begun to break up before impact, scattering debris and fuel over the entire area. As a result, multiple fires have broken out, roads are blocked, and a number of people, many injured, some seriously, are now trapped in burning buildings." [Source]
|
A second important step in this project is to define and implement the methods that support an appropriate integration of the simulator to the framework that intends to be demonstrated/evaluated. In our case this framework is being developed according to the e-Response proposal and, in particular, the I-X Architecture for planning and coordination.
A summary of the aims of this project is presented in follow:
- Modelling of a geographic information set (node.bin, road.bin and building.bin) based on part of London;
- Definition of a semantic level that contains additional information about the scenario objects;
- Integration between simulator and planning/coordination architecture.
More details about this project can be found here.
Scenario
The scenario for our model is represented by the City of London, region showed in orange in the map below. This region is one of the most important areas of London due to the number of important historical and financial buildings, also presenting a considerable concentration of civilians and intense traffic in the roads. Together, such features characterise London city as a problematic region in case of disasters. The description in follow gives an abstract idea about this region.
|
"The City of London is home to the 'Square Mile', the main financial district of London, and as such many of the buildings are given over to office use, with residential use relatively low. Nonetheless, the City has around 8,000 residents, many of whom are concentrated in the Barbican Estate, the City's largest residential sector. The Estate, home to around 4,000 people, contains three of London's tallest buildings (Cromwell Tower, Shakespeare Tower and Lauderdale Tower, each 42 stories and 123 metres high), as well as the Barbican Centre, a centre for the arts, drama and business expositions, the City of London School for Girls, the Museum of London and the Guildhall School of Music and Drama. In addition, located within the City are a number of famous landmarks of historic, cultural or symbolic significance, including St. Paul's Cathedral, the Old Bailey, the Inns of Court, St. Bartholomew's Hospital (no A&E), the Bank of England and, on the fringes of the City, the Tower of London, as well as a number of more recent prominent additions to London's skyline, such as the Tower 42 (the "NatWest Tower") and 30 St. Mary Axe (the "Swiss Re Tower" or the "Gherkin"). Several important bridges across the Thames are located within the City, as are a number of mainline railway stations and Tower Gateway Docklands Light Railway station. The Central, Circle, District, Northern and Waterloo and City underground lines and the London Post Office Railway (now mothballed) pass under the sector." [Source]
|
In an initial moment we are focusing our model in the Southeast of London City (down right corner in the map, bounded by the red trace-line). The satellite photo shows the details of this region, such as the Tower of London and London Bridge (actually they are not officially part of City of London).
|
Map source: http://www.cityoflondon.gov.uk
|
Detailed map
|
Satellite images are a powerful resource to our modelling process because we can have a better notion about the region and its features. For example we can retrieval, with a reasonable precision, information about, for example, ground area of buildings, shape of buildings and roads, length and width of roads and general relative positions of such objects. For that it is important to consider the scale used by the image, in this case about 1cm to 100m in the real world.
Note that, during the real disaster operation, the command and control center must consider a wider area thah that directly affected by the disaster. For example, essential resources such as hospitals will be away from this area.
Map source: http://maps.google.co.uk
See also the interactive satellite image for this region.
|
Scale: |_____________| = about 200 meters.
|
Methodology
The efforts associated with this project can be divided into principal modules: the geographic information modelling process and the simulator/I-X integration. The steps of each of these modules are detailed in follow:
- Geographic Information Modelling Process
- Step 1.: Scenario definition with acquisition of maps (with scale) that give a clear idea about the objects of this scenario (roads, buildings, river, open areas and so on);
- Step 2.: Information retrieval of roads' properties. Such properties are: name, length, width, width for walkers, road kind (elevation road, bridge or tunnel) and number of lanes;
- Step 3.: Information retrieval of buildings' properties. Such properties are: name/number, entrance position(s), number of floors, kind of building (wooden, steel frame or reinforced concrete), area of the ground floor and total area of all floors;
- Step 4.: Use of a modelling tool that convert all this information in data to be used by the RoboCup Rescue simulator (node.bin, road.bin and building.bin). In our case, this tool is JGISEdit. Download and details about this tool are available here;
- Simulator/I-X Integration
- Step 5.: Definition of a semantic layer that maps simulation information about the scenario objects to a common sense representation. an examples in this direction is the use of buildings and roads names rather than object simulation codes;
- Step 6.: Implementation of skeleton agents that contains functions associated with the representational translation of data between the two platforms. For example, consider the geographic information format. While the simulator uses the orthogonal distance (x,y) from a pre-defined point to a specific object, in millimetres, to indicate the position of such a object; I-X agents use latitude/longitude values for that;
- Step 7.: Organisation of the stuff related to the simulation execution on the I-X platform: map, object images and any other resource.
Results and comments about the performance of such steps are disclosed in the next sections.
Modelling Process
Step 1.: Scenario Definiton
As discussed at the beginning of this document, our initial focus is on the Southeast part of City of London. Good source of resources, such as maps and images, for this scenario are:
Step 2.: Roads Properties
| Ref. | Name | Length (m) | Width (m) | Width/walk (m) | Type | N. lanes | Strip |
| 01 | Gracechurch Street | 325 | 20 | 5 | normal | 4 | no |
| 02 | Whittington Avenue | 50 | 6.7 | 2 | normal | 2 | no |
| 03 | Lime Street Passage | 62.5 | 6.7 | 2 | normal | 2 | no |
| 04 | Pudding Lane | 100 | 6.7 | 2 | normal | 2 | no |
| 05 | Botolph Lane | 87.5 | 6.7 | 2 | normal | 2 | no |
| 06 | Philpot Lane | 87.5 | 6.7 | 2 | normal | 2 | no |
07 | Loyal Lane | 100 | 4.7 | 1 | normal | 1 | no |
| 08 | Saint Mary at Hill | 125 | 6.7 | 2 | normal | 2 | no |
| 09 | Rood Lane | 87.5 | 6.7 | 3 | normal | 1 | no |
| 10 | Lime Street | 225 | 10 | 3 | normal | 2 | no |
| 11 | Idol Lane | 112.5 | 3.3 | 0 | normal | 1 | no |
| 12 | Fencourt | 75 | 6.7 | 2 | normal | 2 | no |
| 13 | Mincing Lane | 137.5 | 6.4 | 2 | normal | 2 | no |
| 14 | Saint Dunstan's Hill | 100 | 4 | 1.5 | normal | 1 | no |
| 15 | Billter Street | 125 | 6.7 | 2 | normal | 2 | no |
| 16 | Mark Lane | 250 | 6.7 | 2 | normal | 2 | no |
| 17 | London Street | 112.5 | 4 | 1.5 | normal | 1 | no |
| 18 | Fenchurch Place | 125 | 4 | 1.5 | normal | 1 | no |
| 19 | Seething Lane | 150 | 6.7 | 2 | normal | 2 | no |
| 20 | Trinity Square | 137.5 | 6.7 | 2 | normal | 2 | no |
| 21 | Savage Gardens | 57.5 | 6.7 | 2 | normal | 2 | no |
| 22 | Cooper's Row | 150 | 6.7 | 3 | normal | 2 | no |
| 23 | Fenchurch Street Station | 150 | 4 | 1.5 | normal | 1 | no |
| 24 | Lloyd's Avenue | 137.5 | 5.3 | 1.5 | normal | 1 | no |
| 25 | Northumberland Alley | 100 | 6.7 | 2 | normal | 2 | no |
| 26 | Jewry Street | 200 | 9.3 | 2.5 | normal | 2 | no |
| 27 | Vine Street | 287.25 | 5.3 | 1.5 | normal | 1 | no |
| 28 | King William Street | 200 | 25 | 6 | normal | 4 | yes |
| 29 | Minories | 400 | 12 | 2.7 | normal | 3 | no |
|
| Ref. | Name | Length (m) | Width (m) | Width/walk (m) | Type | N. lanes | Strip |
| 30 | Tower Bridge Approach | 275 | 20 | 9.3 | normal | 2 | no |
| 31 | Leadenhall Street | 375 | 20 | 4 | normal | 4 | no |
| 32 | Leadenhall Market | 50 | 5.3 | 1.5 | normal | 1 | no |
| 33 | Leadenhall Place | 75 | 5.3 | 1.5 | normal | 1 | no |
| 34 | Ship Tavern Passage | 75 | 8 | 2.5 | normal | 2 | no |
| 35 | Cullum Street | 87.5 | 8 | 2.5 | normal | 2 | no |
| 36 | Fenchurch Avenue | 112.5 | 6.7 | 2 | normal | 2 | no |
| 37 | Fenchurch Street | 450 | 10 | 3 | normal | 3 | no |
| 38 | Aldgate | 125 | 17 | 4 | normal | 4 | yes |
| 39 | Talbot Court | 45 | 4 | 1.5 | normal | 1 | no |
| 40 | Eastcheap | 175 | 10 | 3 | normal | 4 | no |
| 41 | Monument Street | 125 | 6.7 | 2.5 | normal | 2 | no |
| 42 | Lower Thames Street | 375 | 17 | 4 | normal | 4 | yes |
| 43 | Fish Street Hill | 95 | 8 | 3 | normal | 2 | no |
| 44 | Great Tower Street | 200 | 10 | 3 | normal | 4 | no |
| 45 | Dunster Court | 80 | 8 | 3 | normal | 2 | no |
| 46 | Star Alley | 40 | 6.7 | 2.5 | normal | 2 | no |
| 47 | Tower Hill | 125 | 17 | 4 | normal | 4 | yes |
| 48 | Crosswall | 125 | 10 | 3 | normal | 2 | no |
| 49 | Hart Street | 112.5 | 10 | 3 | normal | 2 | no |
| 50 | Crutched Friars | 75 | 10 | 3 | normal | 2 | no |
| 51 | Pepys Street | 167.5 | 10 | 3 | normal | 2 | no |
| 52 | Muscovy Street | 62.5 | 10 | 3 | normal | 2 | no |
| 53 | Carlisle Avenue | 75 | 8 | 3 | normal | 2 | no |
| 54 | India Street | 55 | 8 | 3 | normal | 2 | no |
| 55 | Lower Thames Path | 550 | 15 | 15 | normal | 1 | no |
| 56 | Byward Street | 225 | 17 | 4 | normal | 4 | yes |
| 57 | Tower Hill Path | 118 | 15 | 15 | normal | 1 | no |
| 58 | Gloucester Court | 57.5 | 6.7 | 2 | normal | 2 | no |
|
|
See the map with the roads' number references here.
|
Observation: values in this table are not precise and some of them are fictitious.
Step 3.: Buldings Properties
| Ref. | Obj. | Name (building or one of its establishments) | Address | Ground Area (m2) | Total Area (m2) | Floors | Type |
| 01 | 224 | Waterstones Booksellers | 2, Whittington Avenue | 199.984 | 799.936 | 4 | steel |
| 02 | 225 | Flats Building | 9, Lime Street Passage | 96.592 | 579.552 | 6 | steel |
| 03 | 226 | Barbour & Sons | 12, Ship Tavern Passage | 344.032 | 2064.192 | 6 | steel |
| 04 | 227 | Austin Reed Ltd. | 13, Fenchurch Street | 130.424 | 1304.240 | 10 | concrete |
| 05 | 236 | The Ship | 11, Talbot Court | 206.984 | 1034.920 | 5 | steel |
| 06 | 237 | AIG Europe | 37, Fenchurch Street | 232.624 | 1163.120 | 5 | steel |
| 07 | 238 | Greggs | 13, Eastcheap | 244.240 | 1221.200 | 5 | steel |
| 08 | 239 | The Britannia | 20, Monument Street | 166.432 | 998.592 | 6 | concrete |
| 09 | 240 | Tesco | 6, Eastcheap | 56.736 | 340.416 | 6 | steel |
| 10 | 241 | Speakers for Business | 1, Pudding Lane | 95.760 | 574.560 | 6 | concrete |
| 11 | 242 | Coral | 20, Fish Street Hill | 138.512 | 831.072 | 6 | concrete |
| 12 | 243 | Snax | 41, Fish Street hill | 123.848 | 743.088 | 6 | concrete |
| 13 | 244 | St. Magnus House | 3, Lower Thames Street | 81.400 | 976.800 | 12 | concrete |
| 14 | 264 | Express Newspaper | 10, Lower Thames Street | 55.008 | 660.096 | 12 | steel |
| 15 | 263 | Billingsgate Management Ltd. | 16, Lower Thames Street | 133.304 | 1599.684 | 12 | concrete |
| 16 | 297 | Cafe Nero | 88, Leadenhall Street | 262.568 | 2100.544 | 8 | steel |
| 17 | 298 | Chapters | 105, Leadenhall Street | 334.832 | 4077.984 | 12 | concrete |
| 18 | 299 | Flats Building | 4, Leadenhall Place | 205.720 | 1851.480 | 9 | steel |
| 19 | 296 | Flight Centre | 17, Lime Street | 701.208 | 3506.040 | 5 | concrete |
| 20 | 303 | Flats Building | 10, Fencourt | 341.496 | 2048.814 | 6 | concrete |
| 21 | 300 | Blades | 8, Cullum Street | 306.304 | 1837.824 | 6 | steel |
| 22 | 304 | Cafe Taj | 80, Fenchurch Street | 105.304 | 842.432 | 8 | steel |
| 23 | 275 | Swattybetty | 5, Rood Lane | 220.440 | 3306.600 | 15 | concrete |
| 24 | 276 | Flats Building | 3, Rood Lane | 245.192 | 2206.728 | 9 | steel |
| 25 | 246 | Benjys | 26, Eastcheap | 150.968 | 1358.712 | 9 | concrete |
| 26 | 247 | The Royal Town Institute | 41, Botolph Lane | 149.136 | 894.816 | 6 | concrete |
| 27 | 248 | London School of Commerce | 36, Botolph Lane | 90.032 | 540.192 | 6 | concrete |
| 28 | 250 | City Harvest | 37 Eastcheap | 119.840 | 719.040 | 6 | steel |
| 29 | 249 | Werna House | 31, Monument Street | 184.568 | 1107.408 | 6 | concrete |
| 30 | 251 | Reliance Bank | 23, Loyal Lane | 188.512 | 1131.072 | 6 | steel |
| 31 | 262 | The Vigilant Trust House | 20, Lower Thames Street | 104.480 | 835.840 | 8 | concrete |
| 32 | 261 | FB Offices | 30 Lower Thames Street | 137.456 | 274.912 | 2 | concrete |
| 33 | 277 | HSBC | 60, Fenchurch Street | 496.048 | 10913.056 | 22 | concrete |
| 34 | 279 | British Telecom | 11, Great Tower Street | 327.384 | 3928.608 | 12 | steel |
| 35 | 252 | Global Visas | 20, Saint Mary at Hill | 214.048 | 2140.480 | 10 | concrete |
| 36 | 253 | International Medical Press | 36, Saint Mary at Hill | 111.360 | 890.880 | 8 | concrete |
| 37 | 256 | Japanese Canteen | 19, Great Tower Street | 117.552 | 705.312 | 6 | concrete |
| 38 | 257 | St. Marys Court | 4, St. Durstan's Hill | 197.808 | 197.808 | 1 | wooden |
| 39 | 260 | Custom Hq. | 40, Lower Thames Street | 335.264 | 2011.584 | 6 | concrete |
| 40 | 302 | Flats Building | 20, Fencourt | 103.296 | 619.776 | 6 | steel |
| 41 | 305 | Lamas Ltd. | 105, Fenchurch Street | 279.416 | 2514.744 | 9 | steel |
| 42 | 399 | Nuclear Risk Injurers | 42, Mincing Lane | 277.832 | 3333.984 | 12 | steel |
| 43 | 400 | Japan England Insurance | 64, Mark Lane | 304.032 | 2432.256 | 8 | steel |
| 44 | 313 | Lorega Ltd. | 28, Great Tower Street | 363.360 | 4360.320 | 12 | concrete |
|
| Ref. | Obj. | Name (building or one of its establishments) | Address | Ground Area (m2) | Total Area (m2) | Floors | Type |
| 45 | 259 | Nordic Bank | 20, St. Durstan's Hill | 55.008 | 3376.464 | 6 | steel |
| 46 | 258 | Man Group Plc. | 50, Lower Thames Street | 102.824 | 616.944 | 6 | concrete |
| 47 | 293 | Institute of London Underwriters | 22, Billter Street | 495.608 | 2973.648 | 6 | concrete |
| 48 | 292 | Lloyds Bank | 113, Leadenhall Street | 417.304 | 2503.824 | 6 | steel |
| 49 | 294 | Auberge | 56, Mark Lane | 121.208 | 727.248 | 6 | steel |
| 50 | 295 | Blacks | 16, London Street | 89.104 | 534.624 | 6 | steel |
| 51 | 316 | Superdrug | 1, Fenchurch Place | 53.696 | 322.176 | 6 | steel |
| 52 | 320 | Fenchurch Station | 10, Crutched Friars | 327.752 | 655.504 | 2 | steel |
| 53 | 308 | St. Olaves Church | 8, Hart Street | 127.448 | 764.688 | 6 | steel |
| 54 | 321 | Market Bar | 2, Crutched Friars | 145.232 | 1161.856 | 8 | steel |
| 55 | 309 | The city | 2, Seething Lane | 154.432 | 617.728 | 4 | steel |
| 56 | 315 | Novotel London | 10, Pepys Street | 337.104 | 2696.832 | 8 | Steel |
| 57 | 307 | Costa Coffe | 74, Mark Lane | 649.456 | 3896.736 | 6 | concrete |
| 58 | 272 | Rattner Mackenzie Ltd. | 35, Seething Lane | 577.824 | 3466.944 | 6 | concrete |
| 59 | 314 | Red Rose | 37, Crutched Friars | 101.176 | 809.408 | 8 | steel |
| 60 | 273 | English Club | 26, Savage Gardens | 227.184 | 2271.840 | 10 | steel |
| 61 | 271 | Tower View | 13, Byward | 107.360 | 858.880 | 8 | steel |
| 62 | 274 | Tower Green | 1, Tower Hill | 464.728 | 464.728 | 1 | wooden |
| 63 | 268 | Easygroup | 42, Gloucester Court | 415.576 | 831.152 | 2 | steel |
| 64 | 269 | GNI Ltd. | 60, Lower Thames Street | 313.056 | 1252.224 | 4 | steel |
| 65 | 270 | E D & F Man Holdings Ltd | 70, Lower Thames Street | 408.384 | 1633.536 | 4 | steel |
| 66 | 265 | Centurium House | 100, Lower Thames Street | 404.832 | 2428.992 | 6 | concrete |
| 67 | 317 | NatWest | 116, Fenchurch Street Station | 87.984 | 351.936 | 4 | steel |
| 68 | 323 | Lazio Ltd. | 109, Fenchurch Street | 72.280 | 289.120 | 4 | steel |
| 69 | 322 | JLT Services | 5, Lloyd's Avenue | 162.744 | 813.720 | 5 | steel |
| 70 | 290 | Norwich Union | 1, Lloyd's Avenue | 199.360 | 1196.160 | 6 | steel |
| 71 | 289 | AXA Insurance | 1, Aldgate | 505.728 | 2022.912 | 4 | concrete |
| 72 | 291 | Travel Alliance Ltd. | 7, Jewry Alliance Ltd. | 227.200 | 1363.200 | 6 | concrete |
| 73 | 281 | London Metropolitan University | 31, Jewry Street | 159.880 | 959.280 | 6 | concrete |
| 74 | 280 | St. Johns House | 50, Vine Street | 163.792 | 982.752 | 6 | concrete |
| 75 | 282 | Medical Centre | 75, Crosswall | 449.448 | 2696.668 | 6 | steel |
| 76 | 283 | Barclays Bank | 24, Minories | 230.688 | 1384.128 | 6 | steel |
| 77 | 286 | Benjys | 3, Cooper's Row | 336.768 | 1010.304 | 3 | steel |
| 78 | 284 | Defence House Executive | 42, Minories | 137.576 | 550.304 | 4 | steel |
| 79 | 288 | Grange City Hotel | 8, Cooper's Row | 611.304 | 2445.216 | 12 | concrete |
| 80 | 285 | BSC Management | 150, Minories | 89.512 | 537.072 | 6 | steel |
| 81 | 287 | Hospital Block | 4, Tower Hill | 537.760 | 537.760 | 1 | wooden |
| 82 | 266 | The casemates | 6, Tower Hill | 429.600 | 429.600 | 1 | wooden |
| 83 | 267 | Tower of London | 1, Tower Hill | 4657.700 | 5657.700 | 1 | wooden |
| 84 | 301 | Ecclesiastical Insurance Group | 19, Billter Street | 168.768 | 1012.608 | 6 | steel |
| 85 | 278 | RBS | 5, Great Tower Street | 241.008 | 2892.096 | 12 | concrete |
| 86 | 245 | Fuego | 1A, Pudding Lane | 115.568 | 693.408 | 6 | steel |
| 87 | 324 | Kennedys | 50, Mark Lane | 20.448 | 81.792 | 4 | steel |
| 88 | 319 | Halifax | 159, Fenchurch Street | 79.920 | 319.680 | 4 | steel |
|
|
See the map with the buildings' number references here.
|
Observation1: values in this table are not precise and some of them are fictitious.
Observation2: the ground floor and total areas are calculated by the modelling tool. Thus we don't need to complete such values in this step.
Observation3: the names and addresses of buildings or their establishments are real, however their position in the road are not precise.
Observation4: the parameter "Obj." represents an internal identifier, which is specified by the modelling tool to each object of the scenario.
Step 4.: Modelling Tool
We are using JGISEdit as modelling tool to this London-based scenario. When we create a new project in this tool, we first need to specify the following parameters:
- Left-Top coordinate (meters) - specifies the position of the scenario's left top corner. All the positions of the objects (nodes, buildings, roads and agents) in the scenario are given as the orthogonal distance (x,y) from this position. In our case we are using the the value (0,0) as the left-top corner coordinate;
- Map Extent (meters) - specifies the total width and height of the scenario, or its area. In our case, this values are [width=888, height=695];
- Raster file - specifies a optional image file that can be used as a background image for the map that is being modelled.
The package with the first version (Version 1.0) of our London-based scenario can be found here. Such package contains the following six files: gisini.txt, node.bin, road,bin, building.bin, galpolydata.dat and shindopolydata.dat. We are not using the two last files because they are specific to earthquakes events. Note that, rather than earthquakes, this project is interested in events associated with fire related disasters. The paper " Tools for checking & creating ***polydata.dat files" is a good resource if you are interested in the outcome format of the files.
Note that this scenario is still in a stage of tests and several of its features should change or be decided soon. These features are:
|
Number of buildings
|
=
|
88
|
|
Number of roads
|
=
|
57
|
|
Number of refugees
|
=
|
01
|
|
Number of fire stations
|
=
|
01
|
|
Number of police offices
|
=
|
01
|
|
Number of hospitals
|
=
|
to be decided
|
|
Number of fire brigades
|
=
|
10
|
|
Number of police forces
|
=
|
10
|
|
Number of ambulances
|
=
|
to be decided
|
|
Number of civilians
|
=
|
to be decided
|
|
Number of fire points
|
=
|
02
|
Future versions tend to increase the area and details of the scenario. Furthermore is also possible to set more precise values to the objects' properties. New requirements depend on the ongoing use of this scenario during the demonstrations of the AKT research group.
I-X Integration
Step 5.: Skeleton Agents
The architecture that is being used for this initial version is illustrated bellow. Agents are divided into two groups: RCR agents and I-X agents. RCR agents are provided in the simulator package (yapapi) and represent very simple agents that can be used as a basis for more complex implementations. I-X agents are the components that we have implemented and that are being evaluated inside the RCR environment. The main elements of this architecture are introduced in follow:
- Police forces (PF) - one of their function is to cover the environment and send problems to the Police Office, which forwards such problems to the appropriate agent. For example, if any fire is discovered by a PF, a message is sent to the fire station via the police office;
- Fire Station - accounts for receive the fire messages, creating new activities to be allocated to its fire brigades in an optimal way. This process can be manually carried out by users, or autonomously by the fire station agent. Handlers associated with this process can be provided as plug-ins;
- Fire Brigades - if they do not have activities to be performed, they tend to stay in refugee places, where they can refill their water tanks. When they receive activities from the fire station, in the form Extinguish ?building, they try to find the best route to the specific building place to extinguish the fire in such a building;
- Gray communication channel - uses the two basic RCR methods to perform communication between two or more agents. These two methods are: tell(message) and head(sender,message)
- Red communication channel - uses the two basic I-X method to transmit and receive messages: sendObject(destination,contents) and handleInput(message), where message can bean issue, an activity, a constraint, a report or a chat message.
- Blue communication channel - IX agents are, in this application, hybrid agents because they implement inner classes that represent RCR agents. In this way, the communication between IX and RCR agents are done via the RCR methods, however special functions are used to translate information between them because the internal formats used by RCR and IX agents are different.
|
|
We need to understand two forms of information translation performed during the blue communication. The base of facts of RCR agents (we are considering their implementation via the YAPAPI) is represented as a unique object (world) that contains several other objects, each of them modelling a specific object of this world (building, road, civilian, etc.). So the first method of translation consists in mapping the objects attributes to the I-X constraint format. An example is given below to a building:
Considering this example, we can see that the information translation is a direct and easy process. However, there is a problem associated with the position due to the different semantic used for each system (RCR and I-X). While the RCR simulator uses the orthogonal distance (x,y) from a pre-defined point to a specific object, in millimetres, to indicate the position of such an object; I-X agents use latitude/longitude values for that. Thus, we need to use a additional method of translation. For this case in particular we are using the regression method, a numerical technique of fitting a simple equation to real data points. This is possible because we know the set of position RCR values and their correspondent I-X values. Then, we just need to find a function that map a set to the other set. An example of result of this process is shown in follow.
public Double convertLongitude(int x) {
double m = 65.532;
double b = -48572.5553;
double longitude = ((m*(x/1000))+b)/100000;
return new Double(longitude);
}
|
|
This is the function, codified in Java, that is being used to convert x values to longitude values. The mathematical tool used to obtain that function was Data Lab - Version 2.1, which is available in a limited version (evaluation copy) for free. The same tool can be used to convert y values to latitude values.
This method of converting positions works well for small areas, like City of London. The inconvenient detail is that it is not a general method so that different areas will need different equations. A more general method is to use the UTM (Universal Transverse Mercator) projection. This approach is likely to be explored in future works.
Step 6.: Semantic Layer
The Semantic Layer accounts for augmenting the information about the disaster environment. In this way, there are two specific ideas associated with this layer: (1) to provide human-directed information rather than internal code or reference of objects, and (2) to produce new information that can improve the simulation purpose. Functions in this direction are:
- Buildings' address - buildings are referred in the RCR as a unique integer value, such as 256. Thus, the attributes representation of this building using I-X constraints is ((attribute 256) = value). Note that this is not an appropriate representation for human users;
- Roads' names - as buildings, roads are also referred as a unique integer value. Furthermore, due to internal representation used by RCR simulator, the same road can be represented for a set of segments. For example, the Billter Street is represented for the set (412,411,486,485);
- Fire floor - the simulator just indicates the reference of the building in fire. An interesing information could be de levels that are in fire. This information could be used during the reasoning of fire brigade allocation so that the most appropriate agent could be sent to each fire site.
A brief explanation about the implementation of such functions are given in the table below.
|
Buildings' address functions
|
|
Couple of functions where the first receives a RCR building reference number and returns the address of this building. In a similar way, the second function receives the address and returns the RCR reference. Note that here the relation between the two sets is 1:1.
|
|
Roads' name functions
|
|
Also involves two functions: the first function receives a RCR road reference number and returns the name of this road. The second receives an array of road references (route), returning the corresponded road names for this route. Differently of buildings, here we have a 1:n relation between the sets. In other words, each RCR integer value corresponds to a unique road name, while a road name corresponds to a subset of integer values. The package documentation brings more details about this feature.
|
|
Fires' floors function
|
|
As this information does not exist in the simulator, it is generated in an aleatory way by the semantic level. This can be performed by a Random number generator function, which must observe the total number of levels of the building
|
Step 7.: I-X Application Package
I-London is an I-X application that evaluates planning and coordination ideas using the RoboCup Rescue Simulator and the London scenario discussed here. The I-London manual in follow, available in pdf and doc versions, gives details about the features and configuration of this application. The QuickStart document is a practical way of setting and running the application. For that, users must have installed the current version of the I-X package. Then the I-London Zip file (available soon) must be extracted in the ix-/apps directory.
Documents:
I-London Manual (PDF version)
I-London Manual (DOC version)
I-London Quick Start
Artificial Intelligence
Applications Institute
Centre for Intelligent Systems and their Applications
School of Informatics, The University of Edinburgh
Page maintained by
c.siebra@ed.ac.uk,
Last updated: Wed Mar 22 00:39:41 2006
|