Problem Statement:

In this project, you are required to implement and evaluate the performance of the three types of error detection approaches. We will simulate the process of sending data, transmitting data with errors introduced, and receiving the data with error detection.

The workflow is:

1.   Read data to be sent from the given data file.

2.   Calculate and the check codes (CRC, Checksum, Parity) for each data.

3.   Append the check codes to the data following the corresponding rules.

4.   Introduce the random bits error (given in the data file).

5.   Check the received polluted data using the three error detection approaches.

6.   Print whether the received data would be accepted (pass) or not (not pass).

Data File

We provide a data.txt file that includes the data to be sent and the errors introduced during transmitting. Each line includes a binary data and the error bits, separated by a space, examples are shown below.

Note that the error bits are introduced to the sending codeword, rather than the original data. This means you should first process the binary data with check codes (adding CRC, checksum, or parity), then introduce the errors.

To introduce the random bits error, do XOR operation to the codeword: if it is 0, there is no error at the  position; if it is 1, the bit of the codeword will be flipped. We will apply left alignment for the error bits with the codeword, meaning that comparison starts from the leftmost bit of both the codeword and the   error bit, and the error introducing process stops if either one reaches the end.

How errors will be introduced:

Codeword:                                                                          10011010110101111100001100

Error bit:                                                                             000010000010000000000010000010

Codeword with errors (left alignment):                              10010010111101111100000100

Part 1: CRC

In this project, you are required to implement and evaluate the performance of two types of CRC codes: CRC-8 and CRC- 16.

CRC-8 generator: x8  + x5  + x4  + 1= 1 0011 0001

CRC- 16 generator: x16  + x12  + x5  + 1 = 1 0001 0000 0010 0001

You need to calculate and print out the CRC remainder pattern for transmitting the codeword. Then the

receiver will print out the decision whether the received data should be accepted (Pass) or not (Not pass).

Part2: Checksum

Using one-byte version of checksum, you are required to calculate and print the checksum value in

binary. Then, after introducing errors to the transmitting codeword, print out the decision result of error detection using checksum.

Part3: Parity2D

Using one-byte version of 2D parity check, you are required to calculate and print the column parity and row parity. In input data are all 64-bit, leading to eight 8-bit blocks. We will calculate the column parity first and get the 8-bit parity for each raw data blocks. Then, we will consider the column parity as an extra row and calculate the row parity for all the 9 blocks, leading to a 9-bit row parity. You should print the column and row parities in the following format, then print out the decision result of error detection for the receiving polluted data using 2D parity check.

Code Files

Your implementation should include the code files described below:

1.   Error detection source code: you must name your code file: error_detection.c or error_detection.cc or error_detection.cpp (all small letters).

2.   Head  file:  you must call the corresponding header file (if you have one; it is not mandatory) error_detection.h (all small letters).

3.   Makefile: you should use a “Makefile” to compile and run your program.

TA will compile and run your codes using make all. It should automatically compile and run your program and print the results.

Makefile tutorial:

https://www.cs.swarthmore.edu/~newhall/unixhelp/howto_makefiles.html

README File

Along with your code files and the Makefile, include a README file in text. In the README file you should include:

1)   Your Full Name as given in the class list

2)   Your Student ID

3)   The platform you use (the ubuntu version)

4)   What you have done in the assignment.

5)   What  your code files are and what each one of them does. (Please do not repeat the project description, just name your code files and briefly mention what they do).

6)   Any idiosyncrasy of your project. It should say under what conditions the project fails, if any.

7)   Reused Code: Did you use code from anywhere for your project? If not, say so. If so, say what functions and where they're from. (Also identify this with a comment in the source code.)

Example Output Formatting

Assumptions:

If you need to have more code files than the ones that are mentioned here, please use meaningful names and all small letters and mention them all in your README file.

Requirements:

1.   Your programs should terminate itself after all done.

2.   All the naming conventions and the on-screen messages must conform to the previously mentioned rules.

3.   All the on-screen messages must conform exactly to the project description. You should not add anymore on-screen messages. If you need todo so for the debugging purposes, you must comment out all the extra messages before you submit your project.

Programming platform and environment:

1.   All your  submitted  code MUST work well on the provided virtual machine (Ubuntu 20.04 or Ubuntu 22.04).

2.   All  submissions will only be graded on the provided Ubuntu. TAs won’t make any updates or changes to the virtual machine. It’s your responsibility to make sure your code is working on the provided Ubuntu. “It works well on my machine” is not an excuse. SeekTA’s help if you are having difficulty by going to office hours or make an appointment.

3.   Your  submission  MUST  have  a  Makefile.  Please  follow  the  requirements  in  the  following “Submission Rules” section.

Programming languages and compilers:

You must use only C/C++ on UNIX.

You can use a unix text editor like emacs or gedit to type your code and then use compilers such as g++ (for C++) and gcc (for C) that are already installed on Ubuntu to compile your code. You must use the following commands and switches to compile yourfile.cor yourfile.cpp. It will make an executable by the name of "yourfileoutput” .

gcc -o yourfileoutput yourfile.c

g++ -o yourfileoutput yourfile.cpp

Do NOT forget the naming conventions mentioned before!

Submission Rules:

Along with your code  files,  include  a README file  and  a Makefile. Submissions  without README and Makefile will be subject to a penalty.

1. Files your need to submit includes: a source code file, a head file (if applicable), a Makefile, and README. Do not submit the given data.txt file. We will test on a different dataset.

2.  Compress  all  your   files  including  the  README   file   into  a  single  “tar  ball”   and  call  it: ee450_PA1_yourUSCusername.tar.gz. Please make sure that your name matches the one in the class list. Here are the instructions:

a. On your VM, go to the directory which has all your project files. Remove all executable and other unnecessary files. Only include the required source code (head) files, Makefile and the README file.

b. Use these commands in the terminal to compress your files into atar ball:

tar cvfee450_PA1_yourUSCusername.tar *

gzip ee450_PA1_yourUSCusername.tar

Now, you will find a file named “ee450_PA1_yourUSCusername.tar.gz” in the same directory. Please notice there is a space and a star(*) at the end of first command.

c. Do NOT include anything not required in your tar.gz  file. Do NOT use  subfolders. Any compressed format other than .tar.gz will NOT be graded!

2.   Please consider all kinds of possible technical issues and do expect a huge traffic on the blackboard website close to the deadline which may render your submission or even access unsuccessful.  So, don’twait till the last minute to submit.

3.   Please DO NOT wait till the last 5 minutes to upload and submit because some technical issues might happen, and you will miss the deadline. And a kind suggestion, if you still get some bugs one hour before the deadline, please make a submission first to make sure you will get some points for your hard work!

4.   After receiving the  confirmation email, please  confirm your  submission by  downloading  and compiling it on your machine. If the outcome is not what you expected, try to resubmit, and confirm again. We will only grade what you submitted eventhough it’s corrupted.

Grading Criteria:

Notice: We will only grade what is already done by the program instead of what will be done.

Your project is graded for 100 points and your grade will depend on the following:

1.   Correct functionality.

2.   Inline comments in your code. This is important as this will help in understanding what you have done.

3.   Whether your programs work as you say they would in the README file.

4.   If your submitted codes, cannot be compiled, you will receive 10 out of 100 for the project.

5.   If your submitted codes compile using make but when executed, produce runtime errors without performing any tasks of the project, you will receive 15 out of 100 for the project.

6.   If you forget to include the README file or Makefile in the project tar-ball that you submitted, you will lose 15 points for each missing file (plus you need to send the file to the TA in order for your project to be graded.)

7.   Do not submit datafile used for test, otherwise, you will lose 5 points.