CPS 182S, Final Project Details

There is information here on formatting, submitting, and group/project evaluation.

Formatting

Title page and Page Number

You can skip the page numbering on the title page with this (before maketitle use the command below).

\thispagestyle{empty}
\maketitle

Make sure your project/paper has an abstract

For the final Latex submission of your paper I'd like it with wider margins than the default Latex and double-spaced. One easy way to get wider margins is to use the following commands just after your \usepackage{...} declaration and before the \author{...} tag.


\sloppy
\setlength{\textwidth}{470pt}
\setlength{\textheight}{640pt}
\setlength{\topmargin}{-1in}
\setlength{\oddsidemargin}{0pt}
\setlength{\evensidemargin}{0pt}
\setlength{\parindent}{0in}
\setlength{\parskip}{0.05in}

Of course you can fiddle with these parameters to see what how the document changes.

Double Spacing

To double-space your document you can download the setspace.sty style file. On my Windows-based WinEdt system I installed this file in the c:\texmf\latex\tools\ folder. Then from WinEdt I chose the menu item Accessories>MikTex Options> and clicked the Refresh Now button in the General tab-pane.

After this I could simply add the \doublespace command after my abstract and the entire document was doublespaced. You must first add the package setspace to the package list at the top of the latex file, e.g.,

  \usepackage{url,epsf,graphicx,setspace}

Submit

I'd like all latex and bib files, and all diagrams/figures if these are in separate graphics. The easiest way to do this is to zip up all the files and submit them as one zip/tar file. Be sure it's incredibly obvious which is the main latex file. I'll assume I can generate output with the equivalent of the commands below (these work from the command-line, WinEdt has equivalent menu options).

  latex mainfile
  bibtex mainfile
  latex mainfile
  latex mainfile

Please submit a .pdf file too in case there's trouble generating output from your Latex files. I'd like a hard copy turned in too, this ensures we'll have something in case transmissions/submissions are garbled.

Please turn in the hard copy to me, Owen Astrachan, in D241. I'll expect these before noon on Thursday, December 11.

Submit electronically by uploading your files/tar/zip file to your acpub account and typing the command below. You can submit multiple files after the project name, the example below shows one file.

  /afs/acpub/project/cps/bin/submit_cps182s project foo.zip

Project Group Evaluation

Whether working by yourself, or with a group, you must evaluate your own efforts and work. If you're in a group you must also evaluate the efforts and work of your group members.

Please write a plain text file and email or submit as described below. In this file you should provide the following details.

How much effort and time you personally put into the project (effort isn't measured in hours, but it's probably proportional in some way to time).
- Please grade your effort, not your final project. A grade of A means outstanding and goes beyond expectations. A grade of B means good, meets expectations and shows effort. A grade of C means there's recognzible effort, but it's short of what you could do. A grade of F means you put in little or no time on the project.
- If you work in a group please name each group member and grade his or her effort on the same scale. Please justify your evaluation with some details.
Please grade your project. A grade of A indicates an outstanding achievement, one that you'd be proud to show future sections of 182 as an examplar of what dedicated students can produce, and one you'd be proud to have on the 182 web pages for the world to see as your (group's) effort. An A doesn't mean that there is not room for improvement, it's a measure of what you've produced. However, if there are serious flaws/holes/gaps, you probably shouldn't give yourself an A.
A grade of B means a solid project, but perhaps not one that's outstanding or that exceeds expectations.
A grade of C means you really didn't spend the time needed, there are very serious omissions or gaps in your work, and the writing/project are poor-to-adequate, but not good.

Turn in your project/group evaluation either by submitting:

  /afs/acpub/project/cps/bin/submit_cps182s project-eval eval.txt

or by email to ola with the evaluation sent as a plain-text attachment.

Owen L. Astrachan

Last modified: Wed Dec 10 21:15:27 EST 2003