Registration
There is no deadline and you are welcome to register and join even after the event started. You can attend just those days or sessions you want but please register anyway.
Should all in a team sign up? Or only one person? We recommend that all register so that they get all necessary information.
If you want to join as organization to provide local helpers or in-person sessions, please do! This usually takes the form of a "watching party" with coordinated breaks for exercises.
Some organizations offer their own registration form. In this case please register with them and then you do not have to register here centrally as well. We will then make sure that everybody gets all necessary information.
Schedule
All times are displayed in the local timezone of your browser. Detected timezone offset compared to UTC:
Breaks: 10 minutes every hour, between xx:50 and xx:10, but it is difficult for us to indicate exactly when.
|
Installation help and on-boarding |
|
| , - | On-boarding for team leaders (option 1) |
| , - | On-boarding for team leaders (option 2) |
| , - | Installation help for everybody (option 1) |
|
Installation help and on-boarding (you don't need to attend all sessions, choose the one that is better for you) |
|
| , - | On-boarding for team leaders (option 3) |
| , - | On-boarding for team leaders (option 4) |
| , - | Installation help for everybody (option 2) |
|
Day 1 |
|
| , - |
Welcome and introduction
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 1/4
Why we want to track versions and how to go back in time to a working version: Motivation, Browsing, Commiting
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 2/4
Presenters: TBA
|
|
Day 2 |
|
| , - |
Introduction to version control with Git - part 3/4
Presenters: TBA
|
| , - |
Introduction to version control with Git - part 4/4
Presenters: TBA
|
|
Day 3 |
|
| , - |
Collaborative distributed version control - part 1/2
Presenters: TBA
|
| , - |
Collaborative distributed version control - part 2/2
Presenters: TBA
|
|
Day 4 |
|
| , - |
Reproducible research
Preparing code to be usable by you and others in the future
Presenters: TBA
|
| , - |
Social coding and open software
What can you do to get credit for your code and to allow reuse
Presenters: TBA
|
|
Day 5 |
|
| , - |
How to document your research software
Presenters: TBA
|
| , - |
Jupyter notebooks
A tool to write and share executable notebooks and data visualization
Presenters: TBA
|
|
Day 6 |
|
| , - |
Automated testing
Preventing yourself and others from breaking your functioning code
Presenters: TBA
|
| , - |
Modular code development
Making reusing parts of your code easier
Presenters: TBA
|
| , - |
Concluding remarks, general Q&A, and where to go from here
Presenters: TBA
|
|
Optional: Bring your own code session |
|
| , - | Bring your own code and discuss and ask; you can also join this session if you have not attended the workshop |
|
Optional: Bring your own code session |
|
| , - | Bring your own code and discuss and ask; you can also join this session if you have not attended the workshop |
Introduction
The EARL Workshop on Evaluating and Applying Recommendation Systems with Large Language Models invites contributions that utilize LLMs to enhance and innovate within the realm of recommendation systems.