CSC 453 Software for Wireless Sensor Systems Fall 2013, Section 001 Rudra Dutta.

CSC 453CSC 453Software for Wireless Sensor SystemsSoftware for Wireless Sensor Systems

Fall 2013, Section 001Fall 2013, Section 001

Rudra Dutta

Copyright Fall 2013, Rudra Dutta, NCSU

Course ObjectivesCourse Objectives Learn about sensor networks

– Sensors– Networks of sensors– Programming sensors, networking, distributed sensors– Architectural issues– Introductory knowledge

Assume prior knowledge– Operating System concepts– Programming familiarity

Additional helpful base, not assumed prior, but pick up– Networking concepts– Virtual environments– Linux / UNIX system– Embedded systems programming

BackgroundBackground Curriculum and year Operating System (236) Programming familiarity Networking (401, 402, …) Socket programming Embedded devices

– Arduino– BeagleBoard X– Raspberry Pi– Any other ARM

Work experience


Instruction Modes, Work ProductsInstruction Modes, Work Products Descriptive – lectures

– Networking, wireless networking– Sensor networking, applications, network control

Programming – lectures, demo code– Network programming– Sensor reading, communication, control

Homework assignments– Repeat labs, extend– Research literature/websites/blogs, answer questions

Project– Extend labs, explore, design, build– Report, demo

Final test– Descriptive part of homeworks


You will need …You will need … “CSC 453 class kit”

– BeagleBone Black (A5A or compatible above)– Compatible WiFi dongle (Edimax known to work)– Breadboard, standard (400 pin or more suggested)– Power supply (at least 2.0 Amps)

Student-owned computing – very helpful– Virtual Box– Ubuntu 12.04 VM– OS-appropriate drivers from BB site– Alternatively, EOS lab machines

Many BBBK add-on options– Sensors, display, battery pack, microSD card …– Can choose to buy for individual projects



GradingGrading Work Products

– Homeworks (50%)– Project (30%)– Final Test (20%)

Homework assignments– Include programming– Use WolfWare submit

Final test– Open book, open notes (BYON)– Open Internet (only static)– Three hours– Answer on test provided– May attach additional sheets for

space if needed– Take home ?

ProjectProject Written work products

– Project proposal (with possible required resubmission) (5%)

– Interim report (5%)– Final report (5%)– Work products should be competently written

Code and demo of realized system (15%)– Build instructions (strongly prefer makefile)– Minimal documentation

Slide pack for final system


Project proposalProject proposal Required (graded)

– Identify team– Brief description of functionality of system– Clear description of envisioned final demo– Preliminary entity-level design– Task/timeline/point person decomposition (for teams)

Website for project– Project name, team, brief description– Update throughout semester, archive work products– Open to instructor, TAs, class (minimum)

Receive approval from instructor– Mandatory changes may be suggested– Requires resubmission (short timeline: 2 – 4 days)


Interim and Final ReportsInterim and Final Reports Interim report

– Completed design– Course corrections, changes if any (justification)– Changes may incur small penalty based on

reasonableness– (Much larger penalty if undeclared changes in final)

Final report– Reiterate problem statement, design– Description of experiments, results– Self-contained, correctly sized (paper-level)


Project TopicsProject Topics Develop a solution/tool for some specific purpose

– Sensor network related – cannot be simple socket app

System oriented– Typically requires development– Simply testing somebody else’s code is aiming low

Learn by doing Topics / platform / framework

– Delving deeper in some issue raised by labs– Might start with literature, attempt realization– Some samples will be provided


Project TeamsProject Teams Individual, or teams (2, 3 or 4) All mails copied to all team members

– Failure imposes penalty

Work product and grade – per team– Individual assessments – confidential to instructor/TA– Well-oiled machines produce high grades for all– Malfunctioning teams (rare) pull everybody down– Broken teams (hardly ever) may cause instructor

intervention



Administration and CommunicationAdministration and Communication WolfWare website WolfWare Message board

– Not instantaneous, but regular– Primary means of communicating with instructor– Archived after each major work product

Office hours– In person

Email … WolfWare submit, GradeBook

SupportSupport Teaching Assistants

– Amlakawit Medhin (Quarter-FTE)– Trisha Biswas (Volunteer – specific tasks and time

only)

Unity / VCL computing help Yourself.

– BB and associated websites, videos– Non-affiliated websites, blogs– New platform – effort/benefit tradeoff


CSC 453 Software for Wireless Sensor Systems Fall 2013, Section 001 Rudra Dutta.

Documents

Transcript of CSC 453 Software for Wireless Sensor Systems Fall 2013, Section 001 Rudra Dutta.