Skip to content Skip to navigation

Connexions

You are here: Home » Content » Low-Pass Filter Implementation: Grading

Navigation

Recently Viewed

This feature requires Javascript to be enabled.

Low-Pass Filter Implementation: Grading

Module by: Mark Butala. E-mail the author

User rating (How does the rating system work?)
Ratings

Ratings allow you to judge the quality of modules. If other users have ranked the module then its average rating is displayed below. Ratings are calculated on a scale from one star (Poor) to five stars (Excellent).

How to rate a module

Hover over the star that corresponds to the rating you wish to assign. Click on the star to add your rating. Your rating should be based on the quality of the content. You must have an account and be logged in to rate content.

:
(0 ratings)

Obtaining a Cycle Count

Obtaining a cycle count for a given section of code is easily accomplished with the aid of Code Composer. Here is the procedure for obtaining a cycle count:

  1. Load the .out file of the program you wish to profile into Code Composer.
  2. Set a breakpoint at the beginning of the section of code that you want to profile. This can be easily done by right-clicking on the line of code beginning the section and choosing "Toggle breakpoint" from the list of options.
  3. Set a breakpoint at the end of the the section of code that you want to profile.
  4. Open the "Profiler" menu in Code Composer. Choose "View Clock." A window should open at the bottom of the Code Composer window that indicates the current value of the cycle counter.
  5. Again, open the "Profiler" menu in Code Composer and choose "Enable Clock."
  6. Choose "Run" from the "Debug" menu to execute your code. Execution will halt at the first breakpoint. Double-click the cycle counter to reset its value to zero (double click the number next to "Clock =").
  7. Again, choose "Run" from the "Debug" menu to continue execution of your code. Execution will halt at the second breakpoint and the cycle counter will display the number of CPU cycles that were needed to execute the section of code delimited by the breakpoints.

Grading Information

This is a two week lab. Your prelab is due a week after the quiz for Lab 4 and the quizzing occurs two weeks after the quiz for Lab 4.

The following details how the 10 points for the lab will be assigned:

  • 1 point: Prelab. You must answer the prelab questions for two filtering techniques in Filtering Techniques. You must fully simulate one filtering technique in MATLAB and demonstrate that the system will meet the specifications as given in the filter specification. Finite precision effects such as coefficient quantization must be modeled in your simulation. You must provide the response of your simulated system to appropriate test inputs.
  • 2 points: Working code. Code that does not meet the specification is not considered working code. You must be prepared to demonstrate that your code meets the specification by showing the system response to a frequency swept sine input. We will check that the ripple specifications have been met in the pass-band and the stop-band. We will also check the for the locations of the pass-band and stop-band edges to make sure that the width of the transition band is met. We will also check to see that the phase constraint given in the specification is met. We will also check to ensure that you have scaled the input signal appropriately so that clipping does not occur at the output for any frequency. Additionally, we will check to make sure that you do not scale the input too conservatively, specifically, a 1 V amplitude sinusoidal input is not allowed to drop below 0.5 V in amplitude at the output for all frequencies in the pass-band.
  • 2 points: Oral quiz.
  • 5 points: Optimization. These points will be assigned based on your cycle count. You will be judged relative to your peers. Code that does not meet the specification will be penalized. After all the cycle counts have been collected, we will order them for scoring in two ways. First, the cycle counts will be ordered globally over the whole class. The groups with the lowest numbered cycle counts will be given the maximum number of points and the groups with the highest numbered cycle counts will be given the minimum number of points. The second ordering will be done locally relative to which of the three filtering techniques the groups have picked. The groups using the same filtering technique will be ordered by cycle count, with the groups with the lowest cycle counts receiving maximum points and the groups with the highest cycle counts receiving minimum points. 3 points will be assigned for the global ordering of groups and 2 points for the local ordering with respect to filtering technique of groups.

Pizza Competition

Your final assembly code and/or C source code for the pizza competition must be emailed to ece320@ews.uiuc.edu no later than 11:59 PM on Monday, March 17. However, your optimization grade will be assigned based on the code turned in during your assigned lab section and is subject to the usual polices for late code.

Content actions

Give Feedback:

E-mail the module author | Rate module ( How does the rating system work?)

Rating system

Ratings

Ratings allow you to judge the quality of modules. If other users have ranked the module then its average rating is displayed below. Ratings are calculated on a scale from one star (Poor) to five stars (Excellent).

How to rate a module

Hover over the star that corresponds to the rating you wish to assign. Click on the star to add your rating. Your rating should be based on the quality of the content. You must have an account and be logged in to rate content.

(0 ratings)

Download:

Module PDF

Add module to:

My Favorites (?)

'My Favorites' is a special kind of lens which you can use to bookmark modules and collections directly in Connexions. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need a Connexions account to use 'My Favorites'.

| A lens (?)

Definition of a lens

Lenses

A lens is a custom view of Connexions content. You can think of it as a fancy kind of list that will let you see Connexions through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to Connexions materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual Connexions member, a community, or a respected organization.

What are tags? tag icon

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

| External bookmarks