EDIM
EDIM - An Earthquake Disaster Information System for Marmara
Objective of the EDIM project is to develop an earthquake disaster information system for the Marmara region in Turkey. The already existing Istanbul Early Warning System is extended in terms of area, methodology and data transmission. Novel technologies in seismology, structural engineering, and information technology are developed and tested. The project is funded by the German Federal Ministry of Education and Research.
Partners: GFZ Potsdam, Universität Karlsruhe, KOERI, CEDIM
Roadmap: The project started April 2007
Research Opportunities
This is a list of possible topics for scientific work ("Dissertationen", "Diplom"- or "Studienarbeiten"). Some task are also more engineering like and more suitable for "Studienarbeiten. This list is to be extended and will always be work in progress. It ranges from more or less brain-storming to more concrete ideas:
Dual Channel MAC Protocol
Literature
http://www.utdallas.edu/~mxw013200/MAC_ADHOC.html
Time Synchronization in multi-hop networks
Geo monitoring applications often require knowledge about the exact time a measurement is recorded. However, traditional time synchronization protocols like NTP do not scale well within a multi-hop network. Goal of the project is to evaluate current approaches to time synchronisation, which achieve high precision (10 msec max deviation) combined with low overhead. The example application of the study is the SAFER project, where some of the GPS receivers will have no connection.
Literatur http://www.ais.fraunhofer.de/~mock/Sensornetzwerke/DSNetzwerke_clock_12.pdf
Geographical Routing
Distributed Backup over Wifi
The Wireless Nodes do also take care of longterm storage (5 to 7 days) of seismological data. Due to the nature of earth quakes, one or several nodes could be destroyed and with them their data when an an earth quake happens (and the ones nearest to the quake with the most interesting data are the most vulnerable ones; and their data cannot be examined later). To solve the problem there could be a backup system distributed over several nodes. Possible problems:
- High amounts of data (each node produces 4 MB per hour)
- backup traffic must be very low priority, because an earth quake can always happen (early warning detections)
Archiving system with MiniSeed export
The nodes have mainly two tasks:
- early warning detections of earth quakes
- archiving the data and export it in MiniSeed format
For the second part there already exists the SeisComP system, which needs to be ported to OpenWrt and a plugin needs to be created for the Sensorboard.
See also:
- SEEDLink
- plugin API for SeedLink server (page 23) (source code at /seiscomp/acquisition/src/libslplugin/plugin.c)
- slarchive(1) (part of SeisComP system) and SeisComP file and directory structure for storage of earth quake events
This task could also be split up into more sections.
Simulator coupling
In the SAFER project we use three different simulators: A home-made simulator for the sensor data analysis, ODEMx for the distributed event algorithms and ns-2 for the wireless part. How to couple these simulators (especially ns-2 and the home-made simulator) is still an open issue.
Time Measurements for SAFER Hardware
Answer questions like how fast is the Atheros chipset used? How long does the transmission of an individual packet take?