This section will document any updates applied to the project since original release:

• revision #: <description> (DATESTAMP)

In this project, we get started with some course initialization and review activities.

You're reading this, so you've likely already found your way to the course homepage. It consists of the syllabus plus additional course resources.

Please familiarize yourself with it, bookmarking important resources as appropriate, so that you can refer back when needed.

I'd recommend knowing how to get to the projects page (where you found the link for this project), as new content will be posted there.

Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course.

Familiarize yourself with your Journal, and once there:

• customize it (title/subtitle)
• add an introduction
• create your first week content

NOTE: Week 1 journal entry will be due before Monday of week2, the remainder of the intro Journal content will be due by this project's deadline.

Using the resources found on the course homepage (or the lab46 website in general), locate and subscribe a preferred and frequently checked e-mail address to the class mailing list (known as DISCRETE).

We will use this for class discussions (along with irc, the notes wiki page, your Journal, etc.) and to disseminate announcements and other information.

Once subscribed, please send a message to the list introducing yourself (also so I can know to associate a particular e-mail address with you).

Using the tutorial, set up a screen session and join the #csci channel on irc. This has proven useful for more interactive (debugging!) conversations.

Additionally, the C/C++ Programming students will be on this channel, so you could further review your C skills by helping them out.

Ensure you can still (or if you are new to this, that you can successfully) log into lab46 via an ssh or mosh client.

Lab46 will be the primary and supported development environment for the course. While you are free to use your own systems for any projects not intimately tied to Lab46 or the LAIR, any assigned projects:

• MUST be submitted via lab46 (typically via the submit tool)
• MUST compile, run, and function as required ON lab46

Remember, during open LAIR times you can always come in and use the pods.

To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your Lab46 mercurial repository.

This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong.

Like the Journal, I will be looking for a minimal amount of repository-related activity PER WEEK (for example, I will be looking for AT LEAST 1 commit in relation to your program for week 1).

NOTE that you only need to set up your repository ONCE. If you've done it in a previous semester, you are already all set.

To be successful in this project, the following criteria must be met:

• Project must be submit on time, by the posted deadline.
  • Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
• Run the submit tool by the deadline to record your completion.

Let's say you have completed work on the project, and are ready to submit, you would do the following:

lab46:~/src/discrete/dsi0$ submit discrete dsi0
Submitting discrete project "dsi0":

SUCCESSFULLY SUBMITTED
lab46:~/src/discrete/dsi0$