15 413 HardwareSoftware Allocation Li Qiu Augmented 2

  • Slides: 10
Download presentation
15 -413 Hardware/Software Allocation Li Qiu Augmented 2 Reality Team STARS Project Carnegie Mellon

15 -413 Hardware/Software Allocation Li Qiu Augmented 2 Reality Team STARS Project Carnegie Mellon University 11 November 1999

Current Environment • Pencil and Paper – mark on mini-blueprint – mark on body

Current Environment • Pencil and Paper – mark on mini-blueprint – mark on body of aircraft • Paper Workorders • Paper Technical Manuals

Development Platform • PEDD wearable computer • Java Virtual Machine • Lotus Notes

Development Platform • PEDD wearable computer • Java Virtual Machine • Lotus Notes

Hardware/Software Utilization

Hardware/Software Utilization

General System Performance • Expectations – quick response to user interactions – efficient subsystems

General System Performance • Expectations – quick response to user interactions – efficient subsystems • Example expectations – Augmented Reality - low overhead – Authoring - accuracy – Modeling - efficient algorithm

Input/Output Performance • Response time to user interaction – user actions infrequent compared to

Input/Output Performance • Response time to user interaction – user actions infrequent compared to automated tasks – no problems expected • Possible problems with data transfer rate – limited disk space on PEDD – IETM cannot be fully downloaded • 3 D card preferred but not necessary

Processor Allocation • Two most processor intensive operations – wireframe manipulation – speech recognition

Processor Allocation • Two most processor intensive operations – wireframe manipulation – speech recognition • Constrained by available PEDD – Pentium 233 MMX processor

Memory Allocation • Current PEDD constraints – 64 meg • No accurate estimates of

Memory Allocation • Current PEDD constraints – 64 meg • No accurate estimates of the memory requirements of each subsystem • Should clarify itself as object design proceeds

Hardware Connectivity • The arrows indicate flow of information

Hardware Connectivity • The arrows indicate flow of information

Network Architecture

Network Architecture