Simulating the evacuation of very large populations in large domains using a parallel implementation of the buildingEXODUS evacuation model

Computer egress simulation has potential to be used in large scale incidents to provide live advice to incident commanders. While there are many considerations which must be taken into account when applying such models to live incidents, one of the first concerns the computational speed of simulations. No matter how important the insight provided by the simulation, numerical hindsight will not prove useful to an incident commander. Thus for this type of application to be useful, it is essential that the simulation can be run many times faster than real time. Parallel processing is a method of reducing run times for very large computational simulations by distributing the workload amongst a number of CPUs. In this paper we examine the development of a parallel version of the buildingEXODUS software. The parallel strategy implemented is based on a systematic partitioning of the problem domain onto an arbitrary number of sub-domains. Each sub-domain is computed on a separate processor and runs its own copy of the EXODUS code. The software has been designed to work on typical office based networked PCs but will also function on a Windows based cluster. Two evaluation scenarios using the parallel implementation of EXODUS are described; a large open area and a 50 story high-rise building scenario. Speed-ups of up to 3.7 are achieved using up to six computers, with high-rise building evacuation simulation achieving run times of 6.4 times faster than real time.

Validation of evacuation models

Too often, validation of computer models is considered as a "once and forget" task. In this paper a systematic and graduated approach to evacuation model validation is suggested. This involves, (i) component testing, (ii) functional validation, (iii) qualitative validation and (iv) quantitative validation. Viewed in this manner, validation is considered an on-going activity and an integral part of the life cycle of the software. While the first three components of the validation protocol pose little or no significant problems, the task of quantitative validation poses a number of challenges, the most significant being a shortage of suitable experimental data. Finally, the validation protocol used in the development of the EXODUS suite of evacuation models is examined.