ECE 4920 Syllabus and Procedure

ECE 4920 Contents

Course Description
Syllabus and Procedure

Note: Projects and Labs, Lecture Notes and Handouts, and Homework and Exams are not available for this course.

Procedure

The goal will be to rewrite (and perhaps extend) your final project report in ECE4760 for publication. You must have taken ECE4760 the previous Fall. To do this you will need to:

  1. Print out the form [PDF] required to add the course!
    Form must be submitted first or second week of classes.
    Typically completed at first meeting with instructor.
  2. Pick a publication to target. Depending on the project, the target could be a computing or music magazine, or a IEEE journal or IEEE conference. I will help you choose a target publication with a reasonable chance of publication. [Only a few projects will support submission to an IEEE publication.]
  3. Obtain the style guide for the target publication and read it (see below for some links).
  4. Read some articles from the target publication.
  5. IF your project was a group project then you must consider the IP of your partners
    and do one of:
    1. All partners participate in this class and therefore be co-authors.
    2. Some partners do not participate in this class and must each specify TO ME in email one of two options:
      1. They will be co-authors and therefore participate in approving the writing,
        but not do the writing.
      2. They will not be co-authors and therefore will acknowledged, but not participate.
  6. Rewrite your final project report:
    1. Reorganize for top-down explanation of the project.
      Take a step back and consider the non-specialist reader. Have a friend who is not an engineer read it.
    2. Remove all local references (e.g. “We used Bruce’s board.”) and replace with more general statements.
    3. Delete the ABET-specific sections and convert it to a design narrative suitable for the target audience.
      In most cases, ethics, safety, and work distribution will not be part of the final manuscript.
    4. Find, analyze, and incorporate appropriate background publications
      Build a reference list to include in the manuscript.
    5. Reorganize, re-analyze and extend the results section of the original report, which is often written in a hasty fashion at the end of 4760.
    6. Follow the style guide for the target publication
    7. Repeat from step 1
  7. At about the third revision, make sure you are following the style guide for the target publication.
  8. Revise often.
  9. Submit the manuscript!

Time Line

bar
  1. Meet to talk about strategy the first or second week of classes.
    Bring this form with you [PDF]
    –Discuss the style guide(s) you have already read.
    –Discuss the article(s) you have already read.
  2. First draft due by week 4 of classes,
    — meet to mark up hardcopy draft.
  3. Second draft due by week 7 of classes,
    — meet to mark up hardcopy draft.
  4. Third draft due by week 10 of classes. As you can see, the mode number of drafts is 3.
    — meet to mark up and check for following the style guide for the target publication
  5. Fourth draft (if necessary) week 13 of classes
    — meet to mark up and check for following the style guide for the target publication
  6. Submit the manuscript and copy the instructor!

Grading

Grades will be based on:

  • –Timely submission of writing drafts during the semester.
    Your grade will fall if you miss a deadline! A late draft will lose one grade-step.
    (A grade-step means, for instance A to A-, or B+ to B)
    — A first draft which is a cut/paste hack of the course final report will lose one grade-step.
    –Most manuscripts require three or four drafts, but a few may require more.
  • –Attention to detail (top-down explanation, grammar, sentence structure, paragraph structure).
  • –Increase in draft quality with each draft.
    Failure of improvement in a draft may result in loss of one or more grade-steps.
  • –Quality of the final draft.
  • Your grade is not dependent on the manuscript being accepted for publication.
Ambient TV Lighting A low-power solution for creating ambient light based on a TV signal For my ECE 5760 final project, I have created a real-time system that can use an NTSC video signal to simulate the lighting effects of a TV in a low-power fashion. This enables such applications as real-time ambient TV lighting, as well as simulating a TV's light in an unoccupied home to give the appearance of an occupied home. For this to be believable, the system must be able to keep up with the flickering and update speed of a TV signal, and therefore requires a dedicated, real-time processor. The goal of this project was to create a general purpose algorithm that can accomplish this task, and use PWM outputs to drive a larger circuit that controls an RGB LED for verification. The user can send in any NTSC video signal and see the immediate changes on the LED as the video's dominant color changes.
Instructor using a gesture interface to an FPGA game.
Two magazine covers (Circuit Cellar Magazine) featuring images from our student projects.