EPICS Codeathons and Documentathons provide concentrated time for EPICS code and documentation development to take place in an atmosphere where the main purpose is to do just that and not give or watch presentations. By taking developers out of their home environment they can be freed up from interruptions and local problems and allowed to concentrate on those specific EPICS-related tasks.
This edition will allow both remote and onsite participation. We hope you will consider attending in person to maximize collaborative opportunities.
There is no registration fee for this event.
Coding Marathons, also called Code Sprints or Hackathons are popular in many open source projects as a way of making progress on certain development efforts, clearing up bug reports and introducing new developers to the project internals. They usually involve design discussions between developers, coding (individually or using techniques like Pair Programming), code testing and debugging, writing documentation, and coaching for developers who are new to the code-base.
Previous EPICS Codeathons have attracted between 8 and 34 attendees from many different labs/sites, and have resulted in many useful advances for EPICS. There are always core developers present to help newcomers get started and suggest answers to any questions that arise. We will also be asking attendees to test and review each others' projects as well as working on their own, further broadening their experience.
EPICS Codeathons are intended for EPICS users who wish to contribute towards the future of EPICS, either by writing code or working on various documentation tasks. They are generally not suitable for those just starting to learn EPICS unless you have considerable experience in a related software field and are a self-starter. Several core developers wlll be available to act as mentors, including members of the team responsible for developing and maintaining the epics-controls website.
It isn't necessary to attend all 5 days, but please try to make it for enough time that you'll be able to finish at least one project. You don't have to be a C or Java programmer, we will have some tasks that involve writing and updating the EPICS documentation, although most tasks will require some understanding of EPICS, C/C++ or Java coding and/or Linux scripting.
EPICS Codeathon Tracks
EPICS Core, Modules, and Extensions (C/C++)
Organizer Andrew N. Johnson Argonne National Laboratory
Java Extensions (Control System Studio, etc.)
Organizer Kunal Shroff Brookhaven National Laboratory
Python Extensions (PyDM, BlueSky, Ophyd, etc.)
Organizer Ken Lauer SLAC National Accelerator Laboratory
We've reserved a block of rooms at the conference rate at the following hotels: Cardinal Hotel and the Stanford Guest House. The room blocks will be released to the public on April 17th. Please reserve your room before this date.
If you do not have a valid SLAC badge, you must access the site via the Sand Hill Road main gate. Stay in the left entry lane and stop at the guard house; you will need to let the guard know the reason for your visit or the name of your SLAC contact and present a valid government-issued photo ID. Please note that you must present a valid driver's license in order to drive anywhere on the SLAC site.
Requirements for fully-vaccinated individuals vary from those who are not fully vaccinated or decline to verify their vaccination status. COVID-19 safety protocols will continue to adjust to align with the latest Cal/OSHA, CDC, and DOE guidance.
Participants by Institution & Type
Map of Participating Institutions
Participants By Institution and Track
SLAC is operated by Stanford University for the U.S. Department of Energy’s Office of Science. The Office of Science is the single largest supporter of basic research in the physical sciences in the United States and is working to address some of the most pressing challenges of our time