Guidelines

These are the guidelines for the hackathon, adapted from here.

Schedule and format

Timetable: The hackathon starts on Wednesday at 16:00 with the coffee break followed by the Qiskit tutorial, and runs until Friday evening.  On Wednesday and Friday the coding sessions are open-ended: so long as there are volunteers around, we will keep the rooms open. On Thursday we will finish at 17:30 to leave for the school dinner.

Rooms: Tutorials and supervised free coding will take place in room G3. Room G2  will be open for unsupervised coding. There are also some scattered desks outside the rooms, and the cafeteria downstairs is open for studying outside meal times.

Teams: You are welcome to form teams to work on specific projects, or to work on your own.

Platforms covered:

  • Q# – Chris Granade and Bettina Heim, Microsoft
    To prepare for the hackathon, you may download the install guide and work through the online tutorials.
  • ProjectQ – Damian Steiger and Thomas Häner, ETH Zurich
    To prepare for the hackathon, you should install the software. You may go over the online tutorials, but this is not a requirement, as they will be covered in the morning session.
  • Cirq – David Yonge-Mallo, Google 
    Cirq is a Python library for writing, manipulating, and optimizing quantum circuits and running them against quantum computers and simulators.
  • Qiskit – Stefan Wörner, Pauline Ollitrault and Christa Zoufal, IBM Research
    Introduction to Qiskit Terra and Qiskit Aqua, which provide the foundations to program quantum computers and a library of quantum algorithms e.g. for chemistry, optimization, and machine learning. To run these algorithms, follow the install guides for Qiskit Terra and Qiskit Aqua. Follow the instructions under  “configuring your system” to access the real quantum hardware.
  • Forest – Keri McKiernan, Rigetti
    Forest is a simple yet powerful quantum developer environment, designed to accelerate your research in quantum computing and its applications. To prepare for the hackathon, you should install PyQuil.

Code of conduct

Short and simple: be excellent to each other!

To avoid misunderstandings, assume by default that other participants’ projects are confidential, unless they tell you otherwise.

As this event takes place at ETH, the applicable parts of its code of conduct hold.

If you run into problems with your code or other participants, reach out to one of the volunteers.

And please… don’t leave crumbs in the lecture rooms. We want ETH to let us to organise a second edition next year. 🙂

 

Licencing

The rights of all projects started at QuID stay with the authors, i.e. the participants who created them (and, if this applies, to their home institutions). There is no transfer of rights to ETH, the organisation of QuID or other companies.

You are encouraged to publish your code on GitHub and tag it under topic QuID2018, but this is by no mean means mandatory. If you want to give credit to QuID and the tutors of a given session in the final version of your work, this would be greatly appreciated. You are encouraged to publish your code under an open source licence  (we suggest MIT License).