CSci 2101 Data Structures --
2101 Wiki page]
Click on the link above for some advice on program
writing/debugging. Re-read it every once in a while. It is helpful!
Submission instructions and guideline
- Problem sets are due at the beginning of the class on the due
- You may submit printouts of programs or you may send them to me
by e-mail to me: firstname.lastname@example.org (as plain-text
files, or zip or tar archive; no Word
documents please). Please send the actual files, no links would be
- All .java files must follow indentation and naming
conventions. Each .java file must start with comments with your
name, assignment number, and problem number. Each .java file must be
properly commented. The program must be easy to understand. You may
loose points if you don't follow these guidelines.
- Your submitted program must compile and run. Even if it does not
work exactly as specified, partial credit will be given for the parts
of the program that work correctly. If you can't get some of your code
to compile, comment it out before the submission to make sure that the
rest of the program can be tested. If your program doesn't compile, no
credit will be given for it.
- Paper-and-pencil problems may be submitted in class (handwritten
or send by e-mail in any reasonable format (including Word
documents and PDF files).
- Please keep a copy of all your electronic
submissions until the end of the semester. DO NOT modify them after
- You may submit a part of your problem set by e-mail, and a part in
class. If you do so, please write on each part of the submission how
the other part is submitted.
- Please send only one e-mail submission per problem set. If I get
too many e-mail messages from you with a problem set submission,
points may be taken off ("too many" may mean any number greater than
1, at the instructor's discretion).
The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.