Student Projects

Project database

If you would like to perform a project at LAP, choose one among our project database and contact the responsible of the project.

Note that many projects can be taken at different levels (reduced or expanded scope, deeper scientific emphasis or not, etc.). The acceptable levels are indicated just under the title. We at LAP hope that you’ll find something challenging in our list: we have a very wide selection of topics. If you think you should find something interesting at LAP and yet there is nothing that you quite like, please don’t hesitate: come and talk to us, and we will try to tailor something which is challenging for you and interesting for us.

Steps for a project at LAP

In addition to the standard EPFL procedure, you have to follow next steps:

  • Register to the project:
    • Come to the secretary’s office (INF136) together with the supervisor.
    • You will fill an internal form to confirm your registration, and we will assign you to the project on the web application.
    • Do not forget to register your project on IS-Academia (the LAP internal registration does not replace the registration on IS-Academia).
  • At the beginning of the project:
    • Please read all the info on this webpage.
    • You will be assigned a desk and a computer in the lab.
    • We will ask for your weekly availabilities in order to organize intermediary presentations.
  • During the project:
    • Update your planning regularly and discuss it with your supervisor.
    • Keep track of your progress (e.g., write notes) and, if applicable, use version control software (e.g., Git, CVS) for your code.
    • Make sure that your code is well-structured and commented. Provide clear instructions for future users on how to compile and run your code.
    • The dates of the intermediary and final presentations are communicated to the students as soon as possible. Students are required to attend the whole session and not only their own presentation. In case of unavailability, please inform Paolo Ienne as soon as the date of the presentations is communicated.
    • Follow the deadline given by the faculty to deliver your report.
  • At the end of the project:
    • Follow your supervisor’s deadline to send them your report as PDF. 
    • Send all the documents related to your project (presentation, report, abstract, project data, etc.) to your supervisor; they will upload the documents on the LAP project database.
    • Clean up your place station to make it ready for the next student to work.

The grades will be sent to the SAC only when the documents have been attached and the desk has been cleaned up.

Presentation

The presentation is an extremely important part of your project, please discuss it sufficiently in advance with your supervisor, show them your slides, and rehearse it many times. Note that a good timing is essential.

Come to the presentation room in advance and plan enough time to verify that everything works well with the beamer and the internet connection, that you have a pointer, etc.

Length of the presentation:

Intermediary: 15 min + 10 min questions/discussion.

Final: 20 min + 10 min questions/discussion.

Report

The report is to be sent as PDF to your supervisor.

Format

    • Use A4 paper and leave sufficient margins.
    • Spell check the document.
    • Follow scientific journal style for the references (see bibliographic references below).
    • Sign and date the conclusion.
    • Write preferably in English (French is also accepted).

Report content

  • Cover page
    • Project title (if any change, the final title has to be discussed before the end of project with your supervisor).
    • Professor’s, supervisor’s and student’s name.
  • Abstract
  • Table of contents
  • Report body
    • It clearly and didactically presents the project. If your project is based on a previous one, objectives and results are reminded precisely.
    • The report has to be based on block schematics, functional diagrams, algorithmic and software module descriptions, and has to refer to the appendices for any implementation details.
  • Conclusion
    • Good synthesis and critical analysis of the original achievements.
  • Bibliography
    • Use any standard format such as these:
      1. I. M. Author. Some related article I wrote. Some Fine Journal, 99:1-100, 1999.
      2. A. N. Expert. A Book He Wrote. His Publisher, 1999.
  • Appendix
    • Include detailed schematics and timing diagrams.
    • Discuss other appendices with your supervisor (e.g., VHDL, software).

Miscellaneous

Useful information for your report, for your presentation, and on good coding practices is available on our writing style page. Please read it carefully.

Awards

The awards list is available on the SAC website.