Saturday, April 25, 2009

Notes and video for April 23

Notes for April 23 have been posted to the documents page.

Direct links: doc, pdf.

Lecture video (this is a playlist):



To see lecture video broken down by subject, visit the course YouTube channel.

Notes and video for April 21

Notes for April 21 have been posted to the documents page.

Direct links: doc, pdf.

Lecture video (this is a playlist):



To see lecture video broken down by subject, visit the course YouTube channel.

Tuesday, April 21, 2009

Job posting

I received the following message today. I have no details at all except what is in this post. For your info ...


Potential applicants should contact Andrey J. Szpynda: andrey.szpynda@astilbenetworks.com

Software Developer / QA Engineer

Unique opportunity for a Software Developer / QA Engineer in a mobile software startup. We are productizing cutting-edge research from North American universities in the area of wireless mobile communications.

We are seeking a mature, self-motivated Software Developer and/or QA Engineer with 2+ years of experience in the design and development of mobile applications in Windows Mobile/.NET environment. This role comes with significant responsibilities for product development, quality assurance and customer support, and a corresponding equity stake in the company.

Minimum requirements: MS Windows programming using either C# or C++; some familiarity with Windows Mobile/CE, SQL, TCP/IP. Previous experience in WIFI, cellular software development, GPS, mobile databases, Internet and messaging middleware are a definite plus.

An ideal candidate will have strong written and oral communication skills and will approach every problem with enthusiasm and positive attitude.

* Location: GTA
* Compensation: DOE
* Principals only. Recruiters please don't contact this job poster.
* Please, no phone calls about this job!
* Please do not contact job poster about other services, products or commercial interests.

Lab 2 deadline extension

The lab 2 deadline is extended until April 30.

Sunday, April 19, 2009

Source code must be submitted with labs

Starting with lab 2, and for all future labs, your source code must be submitted along with your lab report.

Friday, April 17, 2009

Notes and video for April 16

Notes for April 16 have been posted to the documents page.

Direct links: doc, pdf.

Lecture video (this is a playlist):



To see lecture video broken down by subject, visit the course YouTube channel.

Thursday, April 16, 2009

Note to all those who received an extension on Lab 1

If you received an extension on Lab 1 for any reason, you must submit it by 5 PM on Friday, April 17. Otherwise your lab will not be graded.

Monday, April 13, 2009

Notes and video for April 9

Notes for April 9 have been posted to the documents page.

Direct links: doc, pdf.

Lecture video (this is a playlist):



To see lecture video broken down by subject, visit the course YouTube channel.

Thursday, April 9, 2009

Midterm information

The midterm will take place on Tuesday, April 14, in class. All material up to and including the Tuesday, April 7 lecture is testable. You are allowed one 8.5x11 sheet of handwritten personal notes (written on both sides), as well as a calculator.

Lab 2 posted

Lab 2 has been posted to the Documents page. Direct link here.

The lab is due on April 23.

Notes and video for April 7

Notes for April 7 have been posted to the documents page.

Direct links: doc, pdf.

Lecture video (this is a playlist):



To see lecture video broken down by subject, visit the course YouTube channel.

Tuesday, April 7, 2009

Survey or Tutorial Paper (GRADUATE STUDENTS ONLY)

For the graduate students, a description of the survey and tutorial paper has been posted to the Course Policies page. Here's the full text:

Survey or Tutorial Paper

Graduate students are required to submit either a survey paper or tutorial paper as part of their course grade. Please see the Course Schedule for the due dates.

Paper

  • Survey paper: Pick a topic of mobile communications research related to the course material. Using 10-12 recent papers, describe the state of the art in this area of research. Example topic: Space-time codes.
  • Tutorial paper: Pick a mobile communications protocol and completely describe its operation and applications, in such a way as to educate someone who wanted to learn about that protocol. Example topic: ZigBee.

Your paper will be roughly 10 pages in length (12 pt font, double spaced), and will be graded on writing quality and technical accuracy. Furthermore, survey papers will be graded based on the breadth and depth of the reference list, while tutorial papers will be graded based on the pedagogical quality of the paper.

Proposal

All students must submit a brief proposal, including the proposed title of the paper, the type (survey/tutorial) of the paper, and a summary of the paper topic. The summary should be no longer than one paragraph in length.

Monday, April 6, 2009

Text chapters

I have added a column on the course schedule page, giving the textbook chapter that we are following. Please note: Reading Chapter 2 is not an adequate replacement for the Physical Layer material covered in class; the course notes are much more comprehensive.

UPDATE: These chapters are intended to be supplementary material, for those people who prefer to read the textbook. They should NOT be considered mandatory readings for everyone.

Notes, lab revision

Notes for March 31 and April 2 have been posted to the documents page.

Direct links for March 31: doc, pdf.

Direct links for April 2: doc, pdf.

Lab 1 has been revised: a typo was removed in the first question. You can get the new version from the documents page. Direct link here. (The revision says "Revised April 6" -- you may need to clear your browser cache in order to see the revised version.)

Thanks for your patience

Thanks for your patience while I was away. Everything should be back to normal this week. You can expect to get your quizzes back on Thursday.

If you are still waiting for an email response from me, please feel free to send the question again.