Great! We gladly welcome anyone who is interested in helping bootstrap the education of the HEP community. At this point in time, we as a group have accrued a fair bit of experience and offer to work with you to make your event as effective and efficient as possible. We aim to do this in a way that stays coherent with the approach and “philosophy” of the HSF-Training group so as to make the tools and techniques that are developed persistent, reusable, and broadly accessible.
If you have an inkling that you are keen to do this, go to our top page and ping us or join our weekly meetings. We don’t bite, reach out and say “Hi!”.
What is the HSF-Training “philosophy”?
Pedagogy is important to engage and help our community grow - Watch this TED Talk. Having a common approach to education will help ensure that everyone involved in your training is “on the same page” and knows what you and we are aiming to achieve. To a large extent, our approach is inspired by the Software Carpentries organization and we encourage you to educate yourself about that organization if you are not already familiar. But in short, we strive to cultivate education that is :
Hands-On : A workshop where no work is done is not a workshop. Learning, particularly when it comes to programming, is achieved by doing. Strive to get participants doing more than just copy-pasting and embrace bugs and crashes as “learning opportunities”.
Student-Centric : We are all students and we are all learning - this holds for participants and educators alike. No one has perfect knowledge of any topic and there is no such thing as a stupid question. If a question arises, strive to help that person appreciate it from their perspective, not how you understand it.
Experiment Agnostic : HEP is a huge community! Rote learning of the pattern of commands that should be run to be successful in a single context is not learning. Aim to teach tools and techniques that are independent of a specific context and accept that at some point, every individual wanting to do real research will have to be responsible to extrapolate what you teach them to their specific application.
Reusable : If resources already exist, use them. If they do not exist, develop them in a way such that they can be adiabatically developed and used by others in the future.
Open and Accessible : If someone wants to learn, they should be able to learn, and we will support this.
Please reflect on these points and adopt a mindset that keeps these in mind while transforming your idea into reality. And, if you feel like this philosophy should be modified or extended, don’t hesitate to bring it up to the conveners.
What type of event are you holding?
Two formats of events have been carried out within the group, and you should give some concerted thought about which is more appropriate for your education goals.
In Person
An in-person event is akin to a standard conference or workshop where everyone gathers in a single place, someone leads the instruction by working through one of the SWC-style modules showing both the webpage and their own terminal, on which they actively do what the participants do. Typically, a module takes ~4 hours to complete and a couple hours of free time following the execution of the module is helpful to let participants work with educators to clarify understanding or being applying the tools to their own work.
More fluid interactions between educators and participants (e.g. SWC sticky notes)
Easier to modify content/organization “on the fly”
Builds a community and network within HEP by having formal or ad-hoc social gatherings
Have near 100% of the attention of participants 100% of the time
Cons
Logistical challenges with rooms (e.g. 2 screens and 2 projectors)
Less equitable - Only those with the ability to be in the room due to any number of resources (e.g. money, scheduling) can participate
Virtual
An virtual event takes place entirely online. It commences with a “kickoff” where the facilitator describes how the event will function and proceeds in one of two ways.
The instructor works through the webpage/terminal module while sharing their screen with live question/answer as if you were in the same room.
The participants watch pre-recorded lectures at their own pace and use Mattermost to communicate and ask questions. Some time later, everyone gathers for group “hands-on” work to discuss confusions or challenging aspects of the lessons.
Broader reach and more equitable. Individuals can participate from around the globe on a schedule that is potentially more flexible.
Easier logistically (e.g. no rooms to book, use of pre-recorded lessons)
Low level of commitment needed by educators (e.g. no need to travel “just” to teach) means you will likely have broader support from our community of educators
- Cons
Participants may “flake out” and not attend if they get busy near to the event
Participants may be trying to multi-task and get distracted throughout training
Non-personal - Only get to meet educators/participants in the virtual world. Reduces the chance to have an ad-hoc but meaningful interaction
What will you be teaching?
Give some thought as to what you want to teach and why, particularly in the context of the philosophy of this group. If you want to cultivate a generic skill among a portion of the HEP community (perhaps only those in your local research group) then its probably should be an “HSF event” and we can offer support. If you want to teach a few of your students “how to do HEP analysis on LHCb with machine learning for track reconstruction” then its probably outside of the scope of this group.
Does the material already exist?
STOP!
Before you go ahead and begin making a new set of slides or designing your module, see if there is something that already exists in the HSF-Training archives. Here you will find a number of resources that may pertain to your goal. And if it doesn’t exactly pertain to your training goal, then it can provide a starting point in the form of a HSF-SWC module like this (which generates a website like this) that you can fork and develop for your specific training. You can extend it by adding on a couple of pages at the end which contain experiment specific lessons and/or you can simply modify the setup page of a lesson to give participants guidance on how to use specific resources that you are providing to them.
I can’t find an HSF module for the training I want to organize …
In some cases, however, there may be a hole in our coverage of training material and that should be evident on the training archive. In that case, you have a unique opportunity to contribute something truly original by creating a training from the ground up! Doing so requires a larger investment of time, and likely a longer lead time in planning your event and we have found it typically takes approximately one month to produce a first draft that can be reviewed by mentors who will eventually be helping teach it. However, we are prepared to support and give guidance on the development of this material, and to the extent that we can, offer technical expertise to produce a quality product that adheres to the HSF-Training philosophy. If you find yourself in this scenario, consider reflecting on whether your training goal will cover one of the items on the “wishlist of HSF modules” from the February 2020 Blueprint Meeting. If it will, then we are very keen to help in developing this.
Who will do the educating?
Once determining what you will teach, it is important to build a team that can execute a quality event while not over-burdening any single individual (Remember, everyone is doing this out of a desire to educate and learn, rarely is anyone getting paid to expressly contribute their time or energy to HSF training). We have found that there are three broad “Educator” roles that are necessary to fill and defining these from the start is critical. More details can be found on the page about educators, but briefly:
Facilitator : This person sends all the emails, organizes the indico, and makes sure everyone is on the same page
Instructors : These are the super-experts on one of the given training modules you will be working through. If it is an in person event, they are the persons in the front of the room driving lesson and making sure everything is running on time.
Mentors : These are energetic and eager individuals who know the material to varying degrees and are willing to help teach other individuals. Once you know your target attendance, you should be prepared to have at least 1 mentor for every 5 participants.
In principle, if you are the person reading this page and wanting to organise an event, you will slot in as the Facilitator. It is then your responsibility to find the Instructors and Mentors and while this may be you or individuals from your institution, there is a growing community of educators within HSF training that you can draw upon and recruit to help with your event. Furthermore, we have a number of private Mattermost channels that serve as a communication point for educators and once discussing with the conveners, they can add you there to find further individuals to serve as Instructors and/or Mentors.
Diversity Matters : When recruiting instructors, please bear in mind that particularly in training events, there is a self-evident differential of authority where educators are often “looked-up to” by participants. As such, make a concerted effort to create a diverse team of educators. If you feel like “you just can’t find {X,Y,Z}” then please reach out to us. This is an important tenet of the group of which you are (now) aware well in advance.
In all of this, please bear in mind, everyone is doing this out of a desire to educate and learn, rarely is anyone getting paid to expressly contribute their time or energy to HSF training.
What do I need to do to organize this thing?
If you have organized a workshop/conference yourself, some of this may already be intuitive to you. Likewise, some of it may not. Please take a second to read through this as it is a recipe at which we have arrived through iteration. If you have an alternative approach, we are eager to learn from your experience.
Indico Page (Agenda/Registration)
We use the HSF Training Indico Space to house training event pages. The conveners have rights to modify this category and once the event is confirmed to go ahead, we will create a “Conference” and give you master edit rights. If you do not have a CERN account, you will need to create a lightweight account for this purpose.
Registration Form
One of the primary reasons to use Indico for the primary point of organization and distribution of information is due to its ability to handle registration organization. Since registration will be one of the primary points of contact for knowing who your audience is, you should carefully consider the questions you include here. They are particularly necessary/helpful if you will be doing a pre-registration stage. Some important questions include :
Academic level : This can help if you need to limit attendance and want to specifically cater to a particular demographic (e.g. early PhD students) who are probably all having roughly similar issues/challenges, as opposed to first year university students.
Institutional affiliation : This can be used to ensure that the individual is “actually” in HEP. We have had web developers who don’t seem to be involved in academic science register in the past.
Experimental/community affiliation : This can be useful to try and help gauge who the audience is and perhaps tailor the educator team to the registrants.
Resource access : If you are going to intimately rely on using CERN-based resources (e.g. gitlab.cern.ch or lxplus) then it would be good to know if they have access to specific things like this and/or you would be willing to accommodate them if they don’t.
Prior knowledge : Do they know a specific pre-requisite knowledge. For example, if you want to teach something about continuous integration and they don’t understand how to use version control or git, then it would be good to tell them that they should attend a different event first, or need to study something.
Accessibility accommodation : Though we should make every attempt to make our content accessible, this can admittedly be challenging. Therefore, it is helpful to know where your energy should most immediately be used to help accommodate the audience who is attending your event.
Physical location (if virtual) : If you are doing a virtual event, knowing if they will be in Asia, while you are in Europe, or whether you need to recruit instructors in the Americas so you are not teaching at 22h00 is important.
Consent for photos/recording : This can be little more than a statement that says that registration implicitly means they agree to being recorded or having their photo taken, but documenting things is easy and this helps ensure that there is a minimal level of consent we are following.
Justification for attendance : If you have a limited set of resources and must limit attendance, having some sort of a justification can really help be a tie-breaker for determining who will be engaged the entire time. However, bear in mind when evaluating this that the verbosity of the response can vary by culture.
Additional friction: In order to get a realistic estimate of the number of people who will actually attend the event (especially when it is purely virtual), it can make sense to make it a bit “harder” to sign up. This can for example mean to charge a small fee for the event (but bear in mind that this will complicate things) or a justification for attendance (as already proposed for a tie-breaker)
Mattermost
Mattermost is an open source messaging platform (similar to Slack). We use the CERN Mattermost server. For each training event, we use a new “workspace” with a number of public channels which are used for communication with the participants and private channels that function for internal communication between the educators who are involved in the event.
Teleconferencing - Zoom
We prefer to host virtual events using the Zoom platform and if you cannot host it through your home institute, the necessary logistics can be sorted out using the cern.zoom.us instance. Keeping a consistent platform choice that is more broadly used than others (e.g. Vidyo) means that educators and participants will more likely be familiar with its features.
Planning Document
It is important to have a common and shared point of documenting the development of material, todo lists, emailing drafts, etc. that will need to be developed throughout the planning of your event. This can be in the form of a Google doc like the one from the LBNL training event or using another application such as codi.md. Given that this document is not for broad public consumption and really for sharing information between the education team, what you use is really up to you.
Advertisement
Depending on your desired participant recruitment, we can help advertise your event by publicizing it on the hsf-training-wg google group, our list of training events and other HSF fora. Beyond this, we have compiled a suite of communication pathways that can broadly reach large communities within various experimental collaborations. As these are event-specific, once you are ready to advertise the event, just ask the conveners for this list of emails.
Code of Conduct
Your participation in HSF and subsequently the participation of educators and participants in your event are contingent on your and their agreement to behave according to a code of conduct. By default, HSF-Training follows the CERN Code of Conduct and you should make it abundantly aware to anyone participating in the event that they are agreeing to follow this code. And you, as the facilitator are responsible for enforcing this code of conduct. Do not hesitate to ask the conveners if you are unsure of what this entails.
We have found that in addition to protecting participants from harm, an addition to the code of conduct that facilitates education is to stress the concept that “There is no such thing as a stupid question.”.
Do I need to consider aspects of Accessibility and Diversity/Inclusion/Equity?
YES!
The HSF-Training group believes that it is important to reduce the barriers to entry into the field of HEP. Our activities implicitly do this by working to ease the learning curve for the essential aspects of computing in HEP. However, there are barriers that exist beyond the intellectual ones and it is important that you consider these throughout planning and execution. A summary of how to do this for a generic workshop is provided here from the US-ATLAS Diversity and Inclusion committee. To highlight a couple important things that are often overlooked, but which we would ask you to consider from the beginning are :
Captioning/Signing : Both in the case of in-person and virtual events, it is important to consider if you need to accommodate individuals who are deaf/HoH. For this, you should be sure you know your educator team and in the participant registration, you should leverage the inclusion of a question of “accessibility accommodation” to know your audience. Please also consider that in case you are providing pre-recorded training videos and/or recording the event. If you want to broadly reach the entire HEP community by providing such recordings, consider how you will be providing captioning for these recordings.
Diversity in Leadership : Consider that the educator team will be viewed by participants as “experts” and “leaders” in the field. Seek out colleagues who help cultivate a more diverse field of HEP and can serve as role models for demographics that are not equitably represented including individuals from URM, female, LGBT+ communities.
Financial Support : If you are holding an “in person” event, seek out whether there is funding available from your institution or CERN that can be used to support students to attend your event that would otherwise not have the ability to do so.
What does the event look like when we gather?
Organizing the event carefully is very important to ensure that it is effective. The general motif to keep in mind is that you want to make sure that everyone attending can digest the material as easily as possible and get personalized attention when necessary. How this happens is different for in person and virtual events and we highlight the most important things to keep in mind in each.
General Considerations
Terminal layout : Because the lessons require that the instructor work through things on their own terminal, it is important that the configuration of their terminal is legible. This means (1) black background, (2) not transparent, (3) high contrast, (4) large font.
Coffee breaks : Explicitly schedule time for breaks where individuals can go to the toilet, get a coffee, or just a breath of fresh air. If you are developing lesson content, consider even inserting these coffee breaks as lesson pages within the webpage itself to intentionally break your momentum.
In Person Event
Room : The room layout is critical. The most important aspect is that every participant can easily be accessed by a mentor for one-on-one assistance. Typically this means not holding it in an auditorium. Also consider that the instructor at the front will be describing things with two projects, both of which should be viewable from the back of the room.
Technical setup : Be prepared with 2 screens and 2 projectors that can serve to simultaneously showing (1) the SWC-style webpage and (2) the instructors terminal. Do not convince yourself that you can jump back and forth between the two - this will only serve to confuse and frustrate participants.
Sticky notes : Following the SWC approach to questions, be sure to have a stack of red and green sticky notes that participants can put on their laptop of they understand (green) or don’t understand (red) something.
External connection : Simply put, don’t stress about having an external connection. We have found that there are enough hurdles to being effective to the participants in the room and catering to a broader community compounds these challenges. However, if you would like to make your content more broadly accessible, we would encourage you to consider pre-recording your lesson.
Virtual Event
“Recorded lesson” or “on the fly” : There are two ways to hold a virtual event. (1) Have the instructor present the content in real time with questions from participants. (2) Pre-record the lessons for a given module and host them on YouTube with a focused Q/A session a few days after the event begins.
Record the event : Be sure to record the event to ensure that no one is left wondering what they are “supposed” to do. Doing this will also make the lesson more “persistent” so that future individuals can refer it to new individuals.
Host the event on Zoom : We prefer to host virtual events using Zoom. More details on this can be found in the dedicated section.
Have a “small group” session : Plan to arrange a time for mentors to meet with groups of no more than five or six participants to attempt to recreate the “hands-on” attention of an in-person environment. How these groups are created and organized can be done based on {experience, timezone, collaboration} or other categories.
Be wary of timezones : Keep in mind that a virtual training advertised broadly has the potential to attract participants from many disparate timezones. Plan accordingly, but keep in mind that there is not perfect solution. Assuring participants that recordings will be taken (and then making the recordings!) will help mitigate these issues.
Captioning : BE INCLUSIVE! If the event is virtual, then there may be some individuals who can only participate if there is captioning. Refer to the section on “Accessibility” for more details but bear in mind that this is a bit more of a unique accommodation from an in person event.
Do I care about gathering information on the event? (Surveys)
YES!
Surveys
We care about documenting our successes as well as where we can improve using self-reported feedback (i.e. surveys). For this, we request that you use Google forms/surveys and create a survey to send to participants (but not educators) both (1) at the start of the workshop, the “Pre-workshop Survey” and (2) at the end of the workshop, the “Post-workshop Survey”. What this should include has a set of baseline questions, but is also up to you.
Pre-Survey
Contact Info : Name/email to allow for you to identify who has and has not filled out the survey.
Demographics : We care about knowing who attended a given event in a self-reported way. The set of questions and answers choices that are “appropriate” have been refined over time and can be provided to you.
Generic Knowledge : There is a set of questions we have, which can be provided as a start, and this section is intended to help you understand the audience you are teaching to. If collected ahead of time, it can frame your event a bit more appropriately. If not, it is still useful to provide some hindsight understanding of challenges you may have had.
Event-Specific Knowledge : This is a set of questions that should be tailored to each of the learning goals you wish to achieve. Usually there will be one survey section per training module and the questions are a self-reported ranking on a scale of [1-5] on the individuals understanding of a particular thing. You will then repeat these same questions in the post-workshop survey to gauge their differential of understanding.
Post-Survey
Contact Info : Name/email to allow for you to identify who has and has not filled out the survey.
Event-Specific Knowledge : These are the same set of self-reported understanding questions.
Event Feedback : This is tailored to your event and is aimed at helping to understand how we can improve the execution of future events. It should be a combination of multiple choice and open-ended questions.
Debriefs
Following the event, it is customary for you to find a time to gather with the educators to have a time to discuss and debrief about what was successful and what was not. This typically occurs after you have the results of the post-(and pre-) workshop surveys to help give some focus to the discussion. This feedback should be documented on your planning document.
After all of this, we would ask that you make a short presentation of your experience with the event at the HSF-Training weekly meeting.
Example Timeline
To give you an example of an event organization that follows this paradigm, let’s pretend you want to hold your event at time T and examine an approximate timeline.
[T-4 months] Develop/discover content with HSF-Training and/or the instructors
[T-4 months] Organize the venue/format
[T-3 months] Recruit a team of educators
[T-3 months] Fix the precise dates of the event
This could happen before you have secured an educator team if there are more important constraints.
[T-3 months] Develop the indico page and registration form
It is best to have this rather fully developed before announcing it so as to not miscommunicate with potential participants.
[T-2 months] Announce the event for (pre-)registration
Depending on who you announce this to, you may want to consider accepting only pre-registrations and then accepting a subset to not overflow your capacity. If you do this, ensure it is done in a timely fashion.
[T-2 weeks] Develop the pre- and post-workshop surveys
[T-2 weeks] Perform “dry run” of material with the educator team
[T-1 week] Request registrants to complete pre-workshop survey
[T] Kickoff workshop
[T ⟶ T+few days] Execute lessons
[T+1 week] Request registrants to complete post-workshop survey
[T+2 weeks] Debrief with the educator team
[T+3 weeks] Make closing presentation with HSF Training group
And don’t forget …
There are a few logistical items that the facilitator (i.e. you) should bear in mind when the actual event is going on. We have found that these are the type of things that often “slip one’s mind” but are mission critical to the longevity of the HSF Training effort.
Take Photos : Whether in person or virtual, be sure to document the event with photos which can be used in talks or on our website. Don’t be afraid to “stage” photos with participants to more appropriately highlight things in the training event.
Use the Sticky Notes : The SWC training approach using sticky notes has been found to be very effective, particularly for participants that do not want to raise their hands. Encourage the instructor to use them throughout the teaching to break up the lessons, and encourage students to use them throughout to indicate they are having an issue at any point.
Get the Surveys : Don’t assume that all participants will automagically fill out the pre- and post-workshop surveys. You as the facilitator should actively work to keep a tally and get them to fill them out.
Monitor the Mattermost : Whatever your central communication point for educators and participants is, monitor it. It’s important to not leave participants hanging by themselves.
Keep “How to improve” Notes : On your internal document, note down ideas of how to improve the training for next time, logistically or otherwise, throughout the execution of the event. Encourage all educators to do likewise.
Take Coffee Breaks : Don’t go for multiple hours without taking a break. Even if the training is online, break once per hour to give participants an explicit chance to take a stretch while being assured they will not “miss something”.