Printer$3$D: Code Challenge

See the overview slide for a full description of the task and system to implement.

The scaffold provided here includes a main.c$,$ model.h header file and a template for a Makefile. Source $(.$c$)$ files should be placed in the $"$src$"$ sub$-$directory and header $(.$h$)$ files in the "include" sub$-$directory. The Makefile will look for files here, compile object files into a sub$-$directory "build" and produce a binary executable "printer$3$d$"$ which runs the network $3$D printer program. You will need to update the Makefile for any additional source files you create$/$use$.$

The provided file "model.h$"$ includes an example structure "Model" which you might use to store the data and details of each model you receive. You can edit any files provided in the scaffold and add your own files to suit your needs.

Building, Running and Marking

Your program is expected to be built, without errors, using a Makefile and should build an executable called "printer$3$d$".$ During testing, your program will be built using:

make clean && make

To test your program, we will run $./$printer$3$d with no input arguments. You can click "test" in the bottom right corner of this window to run the test cases. Once you have completed your submission and you are ready to submit the assignment, click on the "Submit" button on the top right.

Input testing file:

The scaffold also includes a file "example$\_$input$\_001.$txt$"$ which contains a hypothetical set of message data that your program might receive. You can use this for testing your program by calling:

$./$printer$3$d $$ example$\_$input$\_001.$txt

which calls your program and re$-$directs the contents of the file through to the standard input. When doing this, you will see the output messages your code produces in response to this input, which may be useful during the implementation and testing process.

You might want to also create your own "test" txt files containing various messages that your program and intepret while testing out the different features of your implementation.