Project deliverable¶
Please, read carefuly the
Final Project description. Note also that the detailed assessment criteria for each one of the tiers can be found in the return box (Check
Assessment Criteria on the left)
Please, mark first which tiers have you delivered.
Which of the following Tiers are you sending:
In relation with Tier deliverable, take into account that:
- If you are targeting Tier 1, you must deliver the code in Tier 1 return box and the video in the corresponding return box.
- If you are targeting Tier 2, you must deliver the code both in Tier 1 (no video) and Tier 2.
- If you are targeting Tier3, you must deliver the code in Tier1 (no video), Tier2 and Tier3.
This is necessary for being able to assess the work.
General rules¶
The code must be returned to the return box below before the deadline. This will be the code that is evaluated.
- The groups will make a common submission, which means that the points will be visible for every member of the group
- The project has to be uploaded to Lovelace because Finnish law requires us to store the course completions of each students for at least 6 months.
- You will need to submit only your own source code and configuration files with the structure provided in each return box.
- You don't need to submit project configuration files (except CMakeLists.txt), libraries, or examples.
- In comments, mention the names of the group members. Tell, what each of you did (e.g. Aki did the task1, Eva did the implementation of task2 and Veeti modified the sdk.c)-
- For additional points, include the reference material, results of data analysis etc.
- Combine multiple files into one zip-file
- Never submit the whole project folder without it being zipped!! It contains big debug files etc. that are not relevant for the grading but take up space in the server
Tier 1. 6 points (+2 Video)¶
Deliver the code and the video (if you are taking only Tier 1) in its corresponding return box. Use the folder structure provided in the return box. If you need to return the video (only for those who are aiming for Tier 1 only), be sure that the video contains all required content, including the answer to the requested questions .
If you are aiming for Tier 1, include as a comment in the begining of the main.c how do you want to distribute 6 points among different members of the team based on their contribution to the project
|
|
points |
details |
| Minimum requirements |
6.0 |
|
 |
Project compiles and can be flashed in the device
|
1.0
|
Program uses C and FreeRTOS and is compiled and Flashed using the tools provided in the exercises.
|
 |
Program structure
|
2.0
|
The program use the recommended style guidelines in the course. It includes comments, it has significant names for functions and variables and use the folder structure provided in the course.
In addition, it implements at least two different FreeRTOS tasks.
|
 |
Detecting position using IMU
|
1.5
|
The program is able to detect at least two different device positions using the IMU sensor.
|
 |
USB serial writing to a terminal
|
1.5
|
Program is able to send Morse symbols to the terminal via USB serial communication. Symbols follows the provided protocol (using . - and spaces as appropiate)
|
Course Project code Tier 1¶
Upload here your code before the deadline expires.
In a .zip file include the files you have created / modified with the following structure:
myproject
|-- src/
|-- main.c
|-- other_file.c
|-- include/
|-- other_file.h
|-- assets/
|-- file1.csv
|-- file2.png
|--CMakeList.txt
Some notes:
- Include folder might be empty if you have not added new .h files.
- Include also the CMakeList.txt even if you have not modified it.
- Launch target should be hat_app
- The assets folder might also be empty if you do not have any files to add.
Please do not zip and upload the whole project directory, as there are lots of unnecessary extra stuff including large debug files, etc!
Make sure to include your names into the code as comments.
Include also in the assets folder the code and the files you have generated for/after collecting data from the sensors (csv, graphs...)
Tier 1 Video¶
Upload the video only if you are aiming for Tier1. In Tier2 and Tier3, video is substituted by the meeting
Upload the link to the video. You can host the video in any platform. If you want to have the video private you can share it through university OneDrive, Google Drive or Panopto. Be sure that university staff has access to the video. If teacher cannot access to the video, it wont be assessed and hence cannot be evaluated.
If you are sharing the link to a video file, be sure that it is encoded in .mp4.
Be sure that the video:
- Presents clearly that your system is working. Computer and device should be presented in the same shot (no separate windows)
- All members of the team participate in the video.
- Discuss the following topics (using students voice, no synthetized voice):
- How many tasks are used, and what is the functionality of each task?
- How many interrupts are used. For each interrupt, define: the source, the interrupt handler, and a short description of its function.
- How many global variables are used. What are they used for? What is the data type of each global variable? Why was this type selected?
- How do you detect the positions? Do you use any filtering or data processing? Which sensor data do you use? What threshold values are applied to detect the positions?
- How do you send the data to the workstation? Which serial communication protocol do you use? How is the data structured?
Tier 2. 11 points.¶
Deliver the code in its corresponding return box. Be sure that you have delivered also the code in the Tier 1 return box (not the video). Use the folder structure provided in the return box.
Course Project code Tier 2¶
Upload here your code before the deadline expires.
In a .zip file include the files you have created / modified with the following structure:
myproject
|-- src/
|-- main.c
|-- other_file.c
|-- include/
|-- other_file.h
|-- assets/
|-- file1.csv
|-- file2.png
|--CMakeList.txt
Some notes:
- Include folder might be empty if you have not added new .h files.
- Include also the CMakeList.txt even if you have not modified it.
- Launch target should be hat_app
- The assets folder might also be empty if you do not have any files to add.
Please do not zip and upload the whole project directory, as there are lots of unnecessary extra stuff including large debug files, etc!
Make sure to include your names into the code as comments.
Include also in the assets folder the code and the files you have generated for/after collecting data from the sensors (csv, graphs...)
Tier 3. 3 points.¶
Deliver the code in its corresponding return box. Be sure that you have delivered also the code in the Tier 1 (not the video) and Tier 2 return box. Include all the extra files and libraries that you have created using the folder structure provided in the return box.
Course Project code. Tier 3¶
Upload here your code before the deadline expires.
In a .zip file include the files you have created / modified with the following structure:
myproject
|-- src/
| |-- main.c
| |-- other_file.c
|-- include/
| |-- other_file.h
|-- assets/
| |-- file1.csv
| |-- file2.png
|--libs/
| |-- libname/
| | |--include/
| | | |--myheader.h
| | |--src/
| | | |--mylib.c
| | |--CMakeLists.txt
|
|--CMakeList.txt
Some notes:
- Include folder might be empty if you have not added new .h files.
- Include also the CMakeList.txt even if you have not modified it.
- Launch target should be hat_app
- The assets folder might also be empty if you do not have any files to add.
- If you modify existing library or create a new library, please, include the full code of the library you are have created / modified.
Please do not zip and upload the whole project directory, as there are lots of unnecessary extra stuff including large debug files, etc!
Make sure to include your names into the code as comments.
Include also in the assets folder the code and the files you have generated for/after collecting data from the sensors (csv, graphs...)