open a session for your class.
You open a session, your students join with a link or a code, and everyone has the same tool and the same credit, whoever they are and whatever they could pay for themselves. The work stays theirs after the course.
For a teacher, a course coordinator or a PI. The first courses ran at TU Delft; we set the first session up with you, from the class wallet to the first assignment.
portrait of the schoolteacher p. d. anslijn, carte-de-visite, 1850–1865 · rijksmuseum, cc0
how a session works.
One form makes everything the room needs. The limits switch themselves on and off; you watch the class, the page watches the rest.
create the session
On your account page, give it a date, a start time and how long it runs; three hours is the default. You get one link, like makemode.eu/org/two-words. It works from the moment you make it, so it can go on the slide today. People who join early are simply enrolled.
put the link on the first slide
Students open it and sign in with their email, on the laptop they build on. The sign-in email carries a link and a six-digit code, so an email read on a phone still signs in the laptop. Whoever joins through the link gets the room's credit and limits; a student who skips it builds on everyday limits.
watch the room, hand out credit
The session page lists who is building, with their first message and their first page, and marks anyone who is ten minutes in without one, so you know where to walk over. One press gives everyone credit; a single top-up sits under one name. Running over? Keep the room's limits for one more hour.
If builds slow down, the workspace switches to a faster model by itself. A build that was cut off is kept with a note, so nobody starts over.
close it the day after
The join link stops working and the room is back on everyday limits; forgetting is safe, because the limits already switched off at the end time. Students keep their accounts, their credit and their work. If you opened a gallery wall, it stays up.
what you arrange.
Four things, all before the first session. We do them with you the first time, from the same checklist we run every workshop from.
What a student spends depends on what they build and how often they rebuild it. Ask us; we set the starting credit with you and top everyone up during the course when it runs low.
- a course wallet
- One organisation for your course, with a wallet that pays for everyone in it. Credit goes from the wallet to each student, and can be taken back into the wallet.
- sign-in that works
- Ask your IT to allow mail from makemode.eu, and let one student sign in from their own inbox a week before. Sign-in with your university account through SURFconext is planned.
- a room on one network
- A lecture hall shares one internet address. The room's limits follow the session and the person who joined, so a full room builds at once.
- one assignment
- What we saw in the first course: a concrete assignment works better than an invitation. A ten-minute build on the students' own material gets a class going.
what stays in colab, what you do here.
A course that analyses data has notebooks already, and they can stay where they are. MakeMode is where students make something shareable out of the result.
In the first course here, the image analysis stayed in Colab; the MakeMode assignment was an interactive atlas of the collection, at a link. One exercise that asked every student for a paid API key could run on MakeMode's image model in the EU instead, from the class wallet. It took three lines in the notebook.
- stays in colab
- Analysis that needs a GPU, TensorFlow or Google Drive. The notebooks you already have.
- happens here
- The thing people can click: an explorer of the dataset, an atlas, a matcher, a study tool for participants, a page to hand in. Described in plain words, published at a link.
- can move here
- A step that calls a model, such as describing images. The models run in France and are paid from the class wallet, so a student needs no key of their own.
a course is a sequence of sessions.
Open one session per class meeting, each with its own date and time. Between meetings, students keep building on everyday limits with the credit they have. The accounts, the wallet and the work carry over from the first session to the last.
- session 1
- Sign in through the link, first build, first published page. The gallery wall shows the class what came out.
- sessions 2 and on
- An assignment on the students' own material. Top up the credit from the wallet when it runs low.
- hand-in
- A published link, and a review link where you comment on the page itself, without an account.
set the first one up with us.
Tell us about your course and we set it up with you before the first session: the wallet, the sign-in test, the first assignment. Then you run the next ones yourself.
the same tool and the same credit for every student.
what your organisation needs to know is on the trust page