ETERE AUTOMATION

1
ETERE AUTOMATION

• EVENT LOGGER

2
PROJECT GOALS

• To log Actions from video feeds of sporting
  events, either live or from tape
• To create a fast, powerful and easy to search
  database that supports multiple database and
  video formats
• To store and manage 2 separate and frame-accurate
  video clips at different resolutions

3
DATABASE CONSIDERATIONS

• The search keys for the database should consist
  of Players, Teams and Actions
• Due to the fact that a Player can be on multiple
  teams (IE Rams All-Star), a general database
  is required.
• The logger will be based on a permanent and
  unique ID for each Player
• Different types of Actions are associated with
  different games, so a general Action database is
  also required

4
LOGGER

• Before game start, the logger application will
  load from the general database
• The Teams
• The Players
• The Actions
• This will configure the interface for the proper
  logging of the current game
• At the same time, correct IDs will be inserted on
  the stories
• The logger is independent from the general games
  database

5
DATABASE MAIN DIAGRAM
Players
Teams
Games
6
LOGGER SIMPLIFIED DIAGRAM
Populated Relational Tables
Players
Recorder Clip Table
Actions
Detailed Actions
General Station Database
7
RELATIONAL TABLES

• The relational tables allow the storage of as
  many attributes as desired for any frame of video
• Every frame of video may have any number of
  Players and any number of Actions associated with
  it
• Using pre-selected key Actions allows uniform
  logging and easy and fast information retrieval

8
CONNECTION

• The system is connected to the main events
  database using a simple pointer mechanism
• This scheme makes the Logger independent from the
  main database
• In this fashion, the Logger Application can be
  used for multiple types of events