EE 265 Digital Signal Processing Lab

Final Project: A Simple OFDM Receiver


EE 265    Project Q&A    Labs & Documents

 

Important Dates

 

Matlab Prototype Demo: 3/09/2008 (Sunday)    5pm    If you finish Matlab Prototype and demo before this due, you will get 0.7 bonus point.

Don’t ask me why 0.7 point. :P

 

Basic Receiver Demo:     3/16/2008 (Sunday)    5pm    If you finish real time implementation of basic requirements before this due,

you will get 0.7 bonus point.

 

Project Demo Due:         3/22/2008 (Saturday)  5pm   Your codes will be collected and evaluated right after the demo, so please prepare your codes

in a neat and clean condition.

No extension will be granted.  You have to show me whatever you would have before the due.

 

Project Report Due:        3/23/2008 (Sunday)    1pm    Just send one ‘doc’ or ‘pdf’ file to jwseo@stanford.edu. 

Feel free to use colors in your report, but don’t include codes in the report.

Late reports won’t be accepted and you will simply lose all 4 points out of 30.

I’m strict about due dates because of the University Grades Due.

 

Documents & Files

 

Project Description: EE265_Final_project.pdf

 

A Simple OFDM Transmitter in Matlab: pulsegen.m, write_vector_to_file_for_DSP.m

 

Text Files for Testing a Receiver: infernodat.txt, jackandbeanstalk.txt, and OFDMverification.txt

 

Verification: verify.m

 

Project Write-up Template (doc)

 

 

Grading Policy

 

Grading Template: project_grade_Winter07-08.pdf

 

I do care about your coding style!  (3 out of 30 points.  1 point of project is equivalent to 1% of total scores.)

Illegible code makes tons of problems, especially when you ask someone to read your code. -_-;

I will collect every code right after your demo.  I’m not trying to torture you but trying to help

you be a better engineer!

 

However, my coding standard is not that high. :)

Look at the ‘pulsegen.m’ file which I updated for this quarter. 

If your coding style is comparable to this file, you will get all 3 points.

 

Make sure to use meaningful variable & function names!  ‘aa’ ‘bb’ ‘cc’ are not good variable names at all. -_-;

Don’t use ambiguous numbers in your codes without defining variables!  Assign numbers to variables (or constants)

with meaningful names and use ‘variables’ instead of ‘numbers’. 

(e.g. SymbolsPerPacket = 14; BitsPerCarrier = 2; samplingRate = 8000;)

 

I don’t require extensive comments in your codes.

 

 

 


Last modified: Feb. 27, 2008