Scalability

Shared by: lanyuehua
Categories
Tags
-
Stats
views:
2
posted:
8/28/2012
language:
English
pages:
31
Document Sample
scope of work template
							Office of the Dean of
      Students
Mission: Provide services and programs that
enable and encourage students to achieve
success in their intellectual and personal
development at Purdue and elsewhere.




                     •Advisors: Prof. David Ebert, Kirk Riley
                     •TA: Steve Gunawan
                  ICM
       Interactive Campus Map


► Objective:  To help people with physical
 disabilities locate the best wheelchair
 accessible path between campus locations
 by drawing it on a map



                                Brian Eng – CmpE
                                Matteo Mannino - EE
         How does ICM work?
► User gives start/end
  information on website
► Calculates shortest path
► Draws map
► Encodes image
► Displays map
ICM Demo
              Last Semester
► Completed   version 1.0 of path finding
  software
► Encountered numerous bugs due to faulty
  database
            Semester Goals
► Prepare  kiosk for use and place in MSEE
► Collect user feedback
► Improve and maintain system
► Deliver kiosk with path finding software
► Create node database software
                 Kiosk
► Wheelchair
  accessible
► Touch-screen LCD
            Kiosk Roadblocks
► WiFi connection in MSEE is lost periodically
► Monitor purchased in the past did not fit in
  the kiosk
► Construction of a monitor support system
  was attempted in order to salvage monitor
   Ultimately turned out to be inadequate
      Collecting User Feedback and
              Improving ICM

► User   feedback from wheelchair users
   Not accomplished due to kiosk roadblocks
► Improvements    made from I2P feedback
     Revamped all pages of ICM
     Improved usability of interface
     Improved aesthetics
     Improvement to be made: make output map
      easier to read
           Delivery of Kiosk
► Kioskwas placed in MSEE Atrium
► Troubleshooting manuals can be accessed
  from web
► Contact info given should anything urgent
  come up
► One member will be on campus this
  summer to address any problems
      Node Database Software
► Companion    program that allows for visual
  creation/modification of the node database
► Justification for software
   Several bugs in database from past semesters
   Tracking down which node is faulty is difficult
    and time consuming
   No meaningful descriptions in current database
   Debugging gets harder as database grows with
    expanding campus
       Database Example
Node     Coordinates   Neighbors
0        123,456       1,3,4
Phys
1        213,522       0,2,3
MSEE
2        211,222       1
5
3        887,818       0,1
13
           Node Database Software
             Main Functionality
► Visual representation of all nodes on map
► Add/Delete nodes to database through
  visual point and click operation on map
► Node adjacency also modifiable through
  point and click operation
► Add detailed node descriptions
► Output node database
Node Database Software
  Demo of Early Build
          Node Database Software
          Progress This Semester
► Back    end (C++):
   Implemented quadtree data structure for node
    lookup
   Outputs text file of node database
► Front   end (MS Visual Studio):
   Nodes can be visually added/deleted to map
   Node descriptions can be entered
            This Semester
► Kioskdelivered and placed in MSEE Atrium
► Improved ICM usability and aesthetics
  based on feedback
► Began work on node database software
             Project Planning
► Complete   node database software
► Obtain feedback from wheelchair users
► Expand campus coverage to include new
  buildings in Discovery Park
► Make output map easier to read
           GPS-DVI
Global Positioning System – Device
     for the Visually Impaired




                        Jay Gengelbach – CS
                        Rohit Vankipuram - EE
                        Jonathan Timura - EE
                   Overview
        Overview
► Project
► Semester Achievements
     Forward Mobility
     Fault Tolerance
     Scalability
     Formal Paper
     Data formats
     Roadblocks
► Conclusion
              Project Overview
► Objective:To design and implement a
 portable device that will enable students
 who are visually impaired to navigate
 around campus with the use of the global
 positioning system.

► Solution:   Program – “PUGuide”
   Integrates GPS receiver and PDA to help user
    navigate around campus using voice output.
HP iPAQ PDA with a CF GPS
        Receiver
Updated Campus Map
              Data Format

► Goals:
   Make data easier to maintain and update
   Make data more flexible
   Add the ability to append descriptive
    information to data
                 Data Format

► Before:
   Node database only contained longitude and
    latitude
   Nodes are specified only by number
    ►Hard   for future programmers to debug
   Adjacency matrix format does not allow
    nodes to have more than 5 adjacent nodes
                    Data Format
► Future:
   Introduction of flags
     ►Add new flags without changing unaffected lines
     ►More effective debugging

   Node database will support building names,
    descriptions, and other info
     ►Database     will be easier to read and debug
   Adjacency matrix stores only one edge per line
     ►Additional   data/metadata can be appended
             Forward Mobility
► Before:
   Code designed for Pocket PC 2002
   Code was not well documented
   Most code contained in a single large file
► Now:
   Code updated to Pocket PC 2003
   Documentation improved
   Code separated into logically separate files
            Fault Tolerance
► Before:
   Power-cycling caused program failures
   Accidental double-click launched program
    twice (with failure)
► Now:
   Device recalibrates after power-cycle
   Only single program instance can run (token
    file)
► Future:
   More stable instance detection methods
                 Scalability
► Memory   requirements significantly
  decreased
► Path finding algorithm improved
   Formal paper explaining algorithms and design
    decisions added to team website
► Redundant   code eliminated
              Roadblocks
► Allmembers new to project and new to
  EPICS
► Current GPS nodes are not accurate
► Documentation from previous semesters is
  poor
           Remaining Steps
► Expand  campus coverage and refine current
  GPS nodes
► Design and test a Braille/tactile interface
► Enhance usability/allow for dynamic path
  modification
► Testing
Questions/Comments

						
Related docs
Other docs by lanyuehua
(なまえ1)と(なまえ2)の1日
Views: 55  |  Downloads: 2
博 多 新大阪 東 京
Views: 46  |  Downloads: 4
Working-Slides.ppt - The KCM Blog
Views: 255  |  Downloads: 0
warner_ROMS_scripps.ppt
Views: 208  |  Downloads: 0
View PDF _4mb_ - Southern Local
Views: 248  |  Downloads: 0
to view our latest issue - ASP Ship Management
Views: 266  |  Downloads: 0
Ulum Sherman 1933 07 26.pdf - GenealogyBuff.com
Views: 452  |  Downloads: 0