Final Engineering Projects

From CsWiki
Jump to: navigation, search

The final stage of an engineering degree at the Rachel and Selim Benin School of Computer Science and Engineering is a final engineering project.

Final engineering projects are done in the last year and a half of the B.Sc. engineering programme. In the second semester of the third year, the projects commence in course 67546 for Computer Science students and course 83519 for Applied Physics students.

The completion stage of the projects takes place in a year-long fourth year course 67547 for CS students and 83520 for AP students.

Working Remotely

To work from home or from a remote site, please take a look at the CSE Wiki guides detailing public servers and methods for connecting remotely.

Project Storage

In the final year of the project, all projects are granted a special project directory with 10 GB of storage space for their project. The path to the directory is


where DDD is the project group code.

For example, in the 5781 academic year, CS project group codes are of the form 1xx while AP project group codes are 2xx so CS group 135 would have the project directory /cs/ep/135 while AP project group 211 would have the project directory /cs/ep/211.

Project directories are group-writable to all the members of the project group. Care must be taken by project members when they create new files/directories that they be writable to all members of the group (see Working in a Group Directory).

Source Code

All project source code should be kept under the CSE Github revision control system.

For detailed instructions on using the CSE Github, see Github.


Often, when installing software packages (e.g. Python), large hidden directories (dot directories) are created in the installation directory.

Since one's home directory is relatively small, it is highly recommended that these packages be installed in your project directory using virtualenv -- for example:

     virtualenv /cs/ep/535/venv1

To read about the various methods and options on using virtualenv, see Virtualenv.

Working in a Group Directory

Before starting to work in your project directory, you need to set your umask to 2 so that your partner(s) will be able to edit the files/directories that you create there.

To change your umask, do:

    umask 2

A detailed discussion on working in group directories under Unix can be found at Sharing Files.