News
Project 2 Release
Written on 29.04.2025 17:57 by Tim Rausch
Hi everyone,
as announced in the lecture, we're releasing project 2 today. Submission deadline is July 4. Along with the handout in the Materials section, here are further instructions for how to access the skeleton, use our remote development environment, and how to submit your solution:
To get the skeleton code for project 2, you need to pull the
project2 branch from the reference repo. Below is an example of how this can be done:# add the reference repo as an upstream if you have not done so already # if you use SSH, replace the URL with ssh://git@lab-pets.privacy-preserving.systems:2224/pets25-h/ref/ref.git $ git remote add ref https://lab-pets.privacy-preserving.systems/pets25-h/ref/ref.git # pull the new branches and checkout $ git pull $ git checkout project2 # if you so wish, you can create a separate branch to host your work $ git checkout -b project2-wip
The project skeleton depends on the
petrelic library. See the project REAMDE for installation instructions. We also provide you with a remote development environment that already has the library pre-installed for your convenience. Use the following information to access your personal development environment via SSH:- Host:
lab-pets.privacy-preserving.systems- Port: 6464
- Username & password: as shown in the note on your Personal Status page in CMS, format:
username,passwordOnce your SSH session is active, you can toy around and start working:
- Files under
/persist will be persisted, so you can safely store your code here. All other files may be lost during server maintenance and restart.- You should be able to use the
petrelic package in Python.- You should be able to upload your code via SFTP.
A few points to note:
- Please use the persistent storage with courtesy, do not use it as your Google Drive.
- Use this environment only for working on this project. In particular, do not run resource-intensive tasks.
- If you need addition Python packages, use pip inside a virtual environment.
- In the rare case where the envs might need a restart, we will publish a notification in advance on Mattermost, so you can plan accordingly.
- Backup your progress often. We have configured the persistent storage to persist, of course, but backing up is always a good idea.
To submit:
- Push your code to the
project2-submission branch of your personal repo before the deadline. We will update this news post with submission instructions for the report later.Should you have any questions or run into unexpected issues, don't hesitate to ask on Mattermost.