User Tools
milestone_3_task_1
Differences
This shows you the differences between two versions of the page.
|
milestone_3_task_1 [2023/02/07 11:27] scott [Filter Code] |
milestone_3_task_1 [2023/02/17 16:34] (current) scott [Pass Off and Code Submission] |
||
|---|---|---|---|
| Line 75: | Line 75: | ||
| You are expected to create and implement the following file. See the provided header file (.h) for a description of each function. | You are expected to create and implement the following file. See the provided header file (.h) for a description of each function. | ||
| - | |||
| * lasertag/filter.c | * lasertag/filter.c | ||
| Line 228: | Line 227: | ||
| ==== Computing Power ==== | ==== Computing Power ==== | ||
| - | Implement all of the power-related functions (they all have the word "power" in their names). You will need to make sure to write ''filter_computePower()'' so that it does not take too much execution time. Carefully think about how you might be able to reuse computations performed in a previous invocation of ''filter_computePower()'' to reduce overall computation time. To initially debug your power code, you can fill the power queues with constant values, say 2.0 for example, and then compare the output from the function with your own calculation. The provided test code contained in the file filterTest.c (see below) provides a comprehensive test of the power functions. | + | Implement all of the power-related functions (they all have the word "power" in their names). You will need to make sure to write ''filter_computePower()'' so that it does not take too much execution time. Carefully think about how you might be able to reuse computations performed in a previous invocation of ''filter_computePower()'' to reduce overall computation time. To initially debug your power code, you can fill the output queues with constant values, say 2.0 for example, and then compare the output from the function with your own calculation. The provided test code contained in the file filterTest.c provides a comprehensive test of the power functions. |
| To compute power, you must keep a running history of 200 ms of output data from each of the 10 IIR-based band-pass filters. To achieve this, do the following: | To compute power, you must keep a running history of 200 ms of output data from each of the 10 IIR-based band-pass filters. To achieve this, do the following: | ||
| Line 252: | Line 251: | ||
| ==== Filter Function Usage ==== | ==== Filter Function Usage ==== | ||
| - | The code below provides context on how the filter functions will be used. It is provided as an example of how you will use the ''filter_addNewInput()'', ''filter_fir()'', and ''filter_iir()'', ''filter_computePower()'' functions in a future task. You would run the code below each time there is at least one new available value. Assume that the code is called continuously and forever. For this task, you are only verifying that your filters work correctly so you don't need to write this code yet. Use the provided filter test code to call your filter functions and test them. | + | The code below provides context on how the filter functions will be used in a future task. Assume that this code is called whenever there is a new scaled ADC value available. |
| + | |||
| + | **You don't need to write this code yet.** For now, just enable the provided filter test code to verify that your filter functions work. The test code will call your filter functions with meaningful arguments. | ||
| <code C> | <code C> | ||
| Line 351: | Line 352: | ||
| * You will show the TAs how your code behaves when running the provided test code. You will mostly show the TAs the information displayed on the LCD on the board. | * You will show the TAs how your code behaves when running the provided test code. You will mostly show the TAs the information displayed on the LCD on the board. | ||
| * You will submit your source code by doing the following: | * You will submit your source code by doing the following: | ||
| - | - from the top-level directory (e.g. ecen390), run the check_and_zip program: "./check_and_zip.py 390m3-1". | + | - From the top-level directory (e.g. ecen390), run the check_and_zip program: "./check_and_zip.py 390m3-1". |
| - The resulting .zip file will be in the top-level directory. Submit that to Learning Suite. | - The resulting .zip file will be in the top-level directory. Submit that to Learning Suite. | ||
| - | - Submit only one .zip file per team. The TAs will make sure that both team members receive credit. | + | - Submit only one .zip file per team. Both team members will receive credit. |
| ---- | ---- | ||
milestone_3_task_1.1675794463.txt.gz · Last modified: 2023/02/07 11:27 by scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
