Every week we meet for about an hour. The team meeting has three sections:
- [30 min] Papers & software: we discuss either a paper or some software. The discussion is lead by a team member and the presentation is made public on YouTube while the discussion is kept private.
- [10 min] Data Science guidance sessions: we talk about our sessions and provide internal feedback.
- [20 min] Help requests: we give open the floor to discuss anything we need help on from the rest of the team. If you have a topic in mind, add it to the team meeting calendar.
On some occasions we have meetings fully dedicated to:
- A paper or software
- A practice presentation by one of our team members in order to build up and polish our presentation skills. These are typically held during the Summer or prior to specific conferences/LIBD seminars.
- Code written by one of our team members: show us something you’ve been working on, something you want feedback on, etc. Think of it as a group-level paired coding session.
Each week, we rotate team members as shown on this presenters Google Spreadsheet. That team member is in charge of:
- finding a paper or a software of interest
- notifying the group about it at least one week ahead on Slack using the
@channeltag on the libd_team_lcolladotor Slack channel
- preparing a few slides to explain the main concepts to us (plan for a 15 minute presentation)
- add some quick notes or short summary on the Google Spreadsheet
The rest of the team members are responsible for reading the main PDF of the paper or software. Optionally, members can read the supplementary material, check the GitHub repository(ies) associated with the paper, or public peer reviews (some journals make them public). If the paper was recorded on the presenters Google Spreadsheet at least a week in advance, then team members are expected to have read the paper regardless of whether the presenter sent a reminder Slack message or not.
Overall, all team members have to contribute and be engaged in our continuous learning activities. It is likely useful for everyone to register on Google Sheets for automatic updates 12 from the the presenters Google Spreadsheet.
We record that portion of our meeting and make it publicly available through the presenters Google Spreadsheet. We then discuss privately our thoughts on the paper or software. Here’s our first video:
You can also find the rest of them under the team lcolladotor YouTube playlist at lcolladotor/playlists.
Every week, the DSgs-guides meet to discuss recent guidance sessions with the following objectives:
- identify common topics that can be addressed in other venues such as the LIBD rstats club, this book, blog posts, etc
- ensure consistency of our responses to similar questions
- identify and address issues with our DSgs interaction rules
We might identify topics that we need to either train the DSgs-guides on or our LIBD/JHU colleagues, as well as useful R functions/packages that we can write to help us and others.
While each team member has an individual weekly meeting, sometimes some problems can be solved with other/fresh eyes looking at them as well as new ideas. If you are having one such problem, this is a great venue to get help for it. This space and time can also be used for asking some quick questions as well as addressing any administration announcements.
On Mondays at 10:30 am everyone meets with Leo sequentially for 30 min to discuss individual updates. These meetings are useful to talk about what projects take priority on a given week, personal issues, and personal career development decisions such as which conference(s) to attend. Here’s a list of conferences/courses of interest.
Here’s the list of project meetings and who should attend them:
- recount3: Nick, Leo. Optional: Geo.
- Moods: Louise, Leo.
- spatial team meeting: Louise, Nick, Leo.
- deconvolution: Louise, Nick, Leo. Optional: Hédia.
- habenula: Bukola, Louise, Leo.
- CHESS-BRAIN: Geo, Hédia, Leo.
- LIBD rstats club: everyone.
- team meeting: everyone.
I recommend a daily digest instead of an email per update.↩︎