next up previous
Next: Mors Up: Dynamic Scalable Distributed Face Previous: Demeter

Nemesis

Figure 5: Nemesis interaction with Ares and Mors
\begin{figure}\begin{center}
\epsfxsize 240 pt
\epsfysize 110 pt
\epsffile{figures/nemesis.eps}\end{center}\end{figure}

Nemesis - the Greek Goddess of vengeance who punished those who had broken the moral code. This component contains the face-recognition engine. It receives the camera feed from Ares and compares the image to the ones in its database (see Fig: 5). Since the face recognition task on a large scale of images is quite computationally intensive, this component requires a hefty pool of high-performance machines (preferable). The images not processed immediately are buffered. This allows for the later matching of faces. When a match occurs, an event is sent to Mors along with the image from the camera feed, the matching image, date, and location of match (see Fig: 6). This event is also saved locally for redundancy purpose.

Figure 6: Event from Nemesis
\begin{figure}\begin{center}
\epsfxsize 178pt
\epsfysize 110pt
\epsffile{figures/event.eps}\end{center}\end{figure}

The under-laying face recognition technology is quite computationally intensive . To accommodate high inflow of camera feed among these systems the inflow of data needs to be distributed across the pool. It is also worth noting it is possible to have a number of face recognition engines in the Nemesis component. This would allow for finding a match that intersects the results of the face recognition engines.

The mechanism for finding Mors component is the same as in all other components - by contacting Hermes, the load balancer and finding the least loaded Mors server. The transport mechanism to receive the camera feed is the same as in Demeter - RTP.

In summary, Nemesis is the most second important component of this framework - it does the face recognition and notifies other components about possibly matches.


next up previous
Next: Mors Up: Dynamic Scalable Distributed Face Previous: Demeter
2002-05-26