Experimental Physics and
EPICS Codeathon 2014
25-29 August, 2014
The Controls Group at the Stanford Linear Accelerator Center (SLAC) in California will host the 2014 EPICS Codeathon, to work on some of the items on the EPICS To Do list. SLAC will provide a comfortable environment with wired and wireless networking and space for up to 20 people to work on EPICS core and related development projects. Attendees will be responsible for their own travel and expenses, and must bring a laptop or notebook computer to work on with all necessary development software.
By taking developers out of their home environment they can be freed up from interruptions and local problems and allowed to concentrate on specific EPICS development tasks. A lab that is looking to both improve their EPICS expertise and to give something back to the collaboration might find this an appropriate way to do both at the same time.
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.
The four previous EPICS Codeathons have had 8-15 attendees from several different labs/sites, and have resulted in many useful advances for EPICS.
This workshop is intended for experienced EPICS users who wish to contribute towards the future of EPICS. There are usually several core developers in attendance as well as a number of other people; see the participant list below for the people we're currently expecting to attend this year.
Our numbers will be limited to at most 20 developers by the space available. It's not necessary to attend for the whole week, but preference will be given to those who will. Most tasks will require a good understanding of EPICS and the ability to read and write C/C++ code, but there will be tasks involving the updating of documentation which don't require writing code (but will need the ability to read and understand record-type implementations).
If you are interested email Andrew Johnson as soon as possible to reserve a spot. If there are places available we should be able to accept late entries, subject to entry .
This codeathon is now listed as a sprint on the Launchpad website, registration there is optional. If you have a specific project you're planning to work on it might be good to describe it in a Blueprint for that sprint.
Where is it being held?
In the Redwood A & B conference rooms at SLAC, from 9am to 5pm.
Wireless networking will be available with high-speed access to the internet so you should be able to connect back to your home institution for email and other services. The ability to test software on your own hardware back home can also be useful if you're able to do that.
Information about visiting SLAC can be found here. All visitors will need to show government-issued ID (drivers license or a passport) to gain access to the SLAC campus, and must be named as one of the participants in the list below.
Where to stay
The Stanford Guesthouse is located on the SLAC campus within easy walking distance of the Redwood meeting rooms. There are also a number of hotels in the Menlo Park/Palo Alto area if you will have your own transport.
If you make an online reservation at the Guesthouse your affiliation is with
Our list of development projects comprises tasks of varying levels of complexity that we would like to see implemented, and lists specific work needed for the 3.15 release. Development work for EPICS V4 would also be appropriate for this event.
Participants can also bring or suggest additional projects themselves, but please try to discuss these ideas on core-talk before the event if possible. You will be able to pick the project or projects you will work on after a discussion with the other participants to avoid duplication of effort.
The core developers who attend will be working on their own projects, but will also be available to provide advice and assitance to others as needed.
The EPICS core developers have to review and approve all changes and additions that can be merged into official releases of EPICS Base. Contributions of code can only be accepted that are offered under the terms of the EPICS Open License. Please confirm with your management in advance that your code can be distributed this way.
How to Prepare
What can/should you do in advance in order to make life at the event itself easier for you and the other participants? Here are some suggestions, if you have other ideas that you think would help let me know and I'll add them here.
The following people attended:
At the end of the week the white-board recording our progress looked like this (click image for full-size photo):
Crossed check-marks mean that some work was done but not completed.
Last updated: 2014-09-03
|ANJ, 03 Sep 2014||
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·