Simualtor Project

Date & Duration

1-18-2005

Location

RESCUE office

Members present

Chris, Sharad, Alex, Jonathan, Thomas, Ali, Qi

Main Task

Activities

Qi did a presentation on the overal design of the project.

To Do

1-13-2005 meeting

Date & Duration

1-13-2005

Location

RESCUE office

Members present

Alex, Jonathan, Thomas, Ali, Qi

Main Task

Activities

1, everybody present the interface design for different classes

- Agent (Jonathan)

- Map/Location/Information (Alex / Ali)

- Sensors (Thomas)

- Simulation (Qi)

- Communication Media (Vidya)

2, integration of class diagram design

3, detailed sequence diagram

4, discussion

In today's simulator meeting, we have discussed the following issues:

1, CVS server set up

host: rescue15.ics.uci.edu

path: c:\cvsroot\NEW (I changed it!!)

username: alex

passwd : ******** (or you can email me your unique username/passwd and I'll create one for you)

protocol : pserver

cvs toturial : http://www.cvsnt.org/ wiki/InstallationTips

cvs client : wincvs, tortoiseCvs, eclipse(java development environment with cvs client integrated)

2, System architecture design

(2a) the data structure to store the maps/Rooms/Doors

(2b) models to compute evacuation plan, minmax flow model, shortest path model

(2c) representation of people's location

(2d) representation of Information exchange in the simulator. We agreed on Information class should define a updateKnowledge(Agent a) method which modify an agent's knowledge. In the initial version, we plan to implement MapInformation, a sub class of Information. A MapInformation class contains a map and it will try to merge two maps during updateKnowledge process.

(2e) During decision-making process, an agent will

   o decide what type of action should be performed. Only Move/Wait in version 1.

   o if Move, use predefined models to analyze the knowledge in his collection and return the next Door d

   o Move to Door d

   o if successful, update location; otherwise, Wait. (due to constrains)

3, Class Diagram design

UML toturial : just search "uml toturial" on google!

4, Assignment.

To Do

1-10-2005 meeting

Date & Duration	2-1-2005 2~4pm
Location	RESCUE office
Members present	Qi, Alex, Jonathan, Vidya, Chris, Ali, Thomas, Earth, Sharad, Nalini
Main Task	1. Minute assignment and tasks division 2. IT Solutions integration 3. Next steps of the simulator's development
Activities	1. Minutes assignment: 02/01 Alex 02/08 Ali 02/15 Earth 02/22 Jonathan 03/01 Qi 03/08 Vidya 2. IT Solutions integration: 2.1 Data collection: this part deals with localization of people, in particular techniques using GSM, Wi-fi and Bluetooth connectivity are being investigated. At the moment it's not so clear how to integrate this component in the context of the simulator. 2.2 Data dissemination: the research problem has the objective to find the best dissemination plan given agents, devices and communication channels. The model is constituted by a graph, where agents are nodes and communication channels are links. It's important in this context the concept of reliability, associated with both communication channels and devices. This component is a black box and the desire is to plug-in it into the simulator to be tested with it. 3. Next steps: 3.1 Add some semantic to maps, that means another layer to the simulator. This process can begin translating the current map representation into a rooms/doors representation, according to the original design (that now is frozen for the first release) 3.2 Add interactions between agents: for example a Floor Warden could tell some people how to evacuate, and they have to move according to his instructions. 3.3 Try to combine simulation with reality (this is a future activity); for example we can think at a real Floor Warden (say Chris) giving instructions about evacuations. The role of sensors in this case is to understand what the Floor Warden is doing and to interpret his actions; how this can be translated into a simulated scenario? Thinking at implementation this shouldn't be a big issue: as the original design shows, the scenario generator is something separated from the simulator, so different scenarios can be incorporated into the same simulation logic. 3.4 The first release of the simulator should be ready in 15-20 days, and the objective is to build a system where users can start simulations over any map represented by a .gif file. Many research papers can be generated from all these challenges. 4. Tasks division: Alex -- Data Dissemination component Ali -- Spatial data modeling: how to translate maps into rooms and doors? Earth -- Conversion from CAD files to GIF files Jonathan -- Data Collection component Qi - Thomas -- Implementation of the first release Vidya -- Agent modeling
To Do	Do what is defined in Task division

Date & Duration	1-25-2005 3~5pm
Location	RESCUE office
Members present	Chris, Vidya, Alex, Jonathan, Thomas, Ali, Qi
Main Task	1, Discuss different agent models during a crisis evacuation 2, Show the code for the demo
Activities	1, Evacuation procedures from EHS fire safety site. 1.1 What to do if there is a fire? Evacuate the building using the nearest exit (or alternate if nearest exit is blocked). Do not use elevators! If save to do so, take personal belongings (keys, purses, wallets, etc.) If save to do so, secure any hazardous materials or equipment before leaving. Follow instructions from Building/Floor Wardens, Police Officers and emergency services personnel. Go to Evacuation Assembly Point (EAP) designated in the building's evacuation plan and on building emergency evacuation signs. Assist persons with disabilities. http://www.ehs.uci.edu/firesafe.html 1.2 R.A.C.E. (Rescue Alert Confine Extinguish) DO NOT PANIC! Alert people nearby and enlist their aid. Call 911 or 824-5222 Evacuate the building immediately and go to the designated assembly point. DO NOT USE ELEVATORS. Do not block roadways as emergency services may need to use them. Follow instructions from Building/Floor Wardens, Police Officers and emergency services personnel. http://www.ehs.uci.edu/firesafe.html 1.3 There are some questions regarding current evacuation procedures - specific questions are related to information about assembly area, fire alarms in buildings, role of building coordinator and zone captain, more information needed. 2. Possible test cases for information dissemination and information collection 2.1 Information dissemination: Information about assembly area is currently provided by floor warden. In case people miss this information this information has to be disseminated to users. Disseminating instructions of floor warden to the people If there are no fire alarms in the building (didnt see fire alarms in the Rescue office), disseminate this information to peopl Information collection Can help in determining if the room is empty or not - can reduce the number of rooms the floor warden has to personally inspect. Provide information to floor warden regarding possible paths and dynamic changes - can help floor warden decide better evacuation routes Number of people entering a room Number of people currently in a room/floor/building/assembly area Alessandro and Jonathan have to think about these issues and decide on some plausible test cases. 3. Current Demo http://www.itr-rescue.org/simulator/Simeva_0_1.exe Code base is in the CVS server.
To Do	1,Schedule meeting with Linda Bogue to get more information about evacuation procedures - Chris and Vidhya

Date & Duration	1-18-2005
Location	RESCUE office
Members present	Chris, Sharad, Alex, Jonathan, Thomas, Ali, Qi
Main Task
Activities	Qi did a presentation on the overal design of the project.
To Do

Date & Duration	1-13-2005
Location	RESCUE office
Members present	Alex, Jonathan, Thomas, Ali, Qi
Main Task
Activities	1, everybody present the interface design for different classes - Agent (Jonathan) - Map/Location/Information (Alex / Ali) - Sensors (Thomas) - Simulation (Qi) - Communication Media (Vidya) 2, integration of class diagram design 3, detailed sequence diagram 4, discussion In today's simulator meeting, we have discussed the following issues: 1, CVS server set up host: rescue15.ics.uci.edu path: c:\cvsroot\NEW (I changed it!!) username: alex passwd : ******** (or you can email me your unique username/passwd and I'll create one for you) protocol : pserver cvs toturial : http://www.cvsnt.org/ wiki/InstallationTips cvs client : wincvs, tortoiseCvs, eclipse(java development environment with cvs client integrated) 2, System architecture design (2a) the data structure to store the maps/Rooms/Doors (2b) models to compute evacuation plan, minmax flow model, shortest path model (2c) representation of people's location (2d) representation of Information exchange in the simulator. We agreed on Information class should define a updateKnowledge(Agent a) method which modify an agent's knowledge. In the initial version, we plan to implement MapInformation, a sub class of Information. A MapInformation class contains a map and it will try to merge two maps during updateKnowledge process. (2e) During decision-making process, an agent will o decide what type of action should be performed. Only Move/Wait in version 1. o if Move, use predefined models to analyze the knowledge in his collection and return the next Door d o Move to Door d o if successful, update location; otherwise, Wait. (due to constrains) 3, Class Diagram design UML toturial : just search "uml toturial" on google! 4, Assignment.
To Do

Date & Duration	1-10-2005 11am~1pm
Location	RESCUE office
Members present	Alex, Jonathan, Thomas, Ali, Qi
Main Task	1, Discuss different agent models during a crisis evacuation 2, Show the code for the demo
Activities	1, CVS server set up 2, System architecture design 3, Class Diagram design (using UML) 4, Testing Plan 5, Project timeline
To Do