Project 4
IMPORTANT: You should rename the following functions:
store -> dbstore
insert -> dbinsert
remove -> dbremove
delete -> dbdelete
modify -> dbmodify
This this your sixth electronic submission, so you should use number 6.
You should submit the following files for project 4 (Programming project #5).
- Source file named "pr4.lsp" that contains the definition of all the functions.
- README: This file should contain your name, your class id and anything special that you want the TA to know when grading your project.
Project 3
- Description (postscript) (pdf) (due on Tuesday, Nov 25 11:59pm)
- This is the data file used for grading this project:Grading Data
- As it is stated in the project description the input will be the initial vertex and a list of edges with the corresponding weight on each edge (node1 node2 weight). Note that the graph is undirected, so an edge from node A to node B with weight W implies that there is also an edge from node B to node A with weightW.
- The output should be a list of edges comprising the minimum weight spanning tree in any order. Note that the last element of the list should be the sum of the path costs (as it is also stated in the project description).
- IMPORTANT: You should name your main function cheapest_paths.
This this your fifth electronic submission, so you should use number 5.
You should submit the following files for project 3 (Programming project #4).
- Source file named "pr3.lsp" that contains the definition of all the functions.
- README: This file should contain your name, your class id and anything special that you want the TA to know when grading your project.
Project 2
Important: You should rename the following functions, because they are already predefined in the lisp interpreter we are using.
member -> mymember
union -> myunion
intersection -> myintersection
merge -> mymerge
sort -> mysort
This this your fourth electronic submission, so you should use number 4.
You should submit the following files for project 2 (Programming project #3).
- Source file named "pr2.lsp" that contains the definition of all the functions.
- README: This file should contain your name, your class id and anything special that you want the TA to know when grading your project.
Project 1
Project 1-Part 4
This this your third electronic submission, so you should use number 3.
You should submit the following files for the fourth part of this project.
- Source file(s)
- Makefile: This is your makefile that builds your source code on typing 'make project1d' and creates an executable called p1d.
- README: This file should contain your name, your class id, the list of files that you are submitting, instructions on how to build and execute your code, anything special that you want the TA to know when grading your project.
Project 1-Part 3
As this this your second electronic submission you should use number 2.
You should submit the following files for the third part of this project.
- Source file(s)
- Makefile: This is your makefile that builds your source code on typing 'make project1c' and creates an executable called p1c.
- README: This file should contain your name, your class id, the list of files that you are submitting, instructions on how to build and execute your code, anything special that you want the TA to know when grading your project.
Project 1 - Part 2
- Your decoder should read the standard input, parse each line and print the results to the standard output.
- Test Input and Test Output for Part 2
This is the first electronic submission,so you must use number 1.
You should submit the following files for the second part of this project.
- Source file(s)
- Makefile: This is your makefile that builds your source code on typing 'make project1b' and creates an executable called p1b.
- README: This file should contain your name, your class id, the list of files that you are submitting, instructions on how to build and execute your code, anything special that you want the TA to know when grading your project.
Drawing Routines
You should download the source code and use "unzip".
This contains the following:
- README
- drawing_c.h: Definitions for the drawing routines.
- drawing.c: Implementations for the drawing routines.
- Makefile
- printquad.c: code to generate a ps file displaying the quadtree
- showquad.c: code to display the quadtree
- test.pm1: sample input and output
Using the drawing routines:
First use 'make all' to produce the two executables 'showquad' and 'printquad'. These two are stand-alone applications that pick up a text dump created by your code and display the quadtree. To create the text-dump, use the drawing routines defined in 'drawing_c.h'. The documentation in the header should be useful. Once you have created the text dump (it need not have the .txt extension), 'showquad dump.txt' should display the quadtree on the screen. Use 'printquad dump.txt > dump.ps' to generate a postscript file for printing.
NOTE: If your program does not include library <stdio.h> you should include the statement "#include <stdio.h>" at the beginning of "drawing_c.h"!!!
User options for showquad
- [-f float] for font size
- [-l float] for line width
- [-s float] to scale the picture
- [-t] to show text
User options for printquad
- [-s float] to scale the picture (default is 2)
- [-f float] for font size (default is 0.5)
- [-l float] for line width (default is 0.1)
- [-d float] to change spacing between segments of a dashed line (default is 0.5)
General Submission Guidelines
To submit electronically execute the following command:
~hs420002/BIN/submit N F
N is the project number (1 for project 1, part 2) and F is the file that you want to submit. In order to submit multiple files you will have to "tar" them all, using a command like "tar -cvf ".
Do NOT zip the tar file.
Note that in case of multiple submissions for the same project and part, only the last submission will be saved. The previous ones get overwritten.
Web Accessibility