We are the https://coderefinery.org project and provide training, such as our workshop on Git, testing, documentation, and collaboration and e-Infrastructure for research software development.
Have you seen this sign in your lab or elsewhere and wondered what it means? (https://github.com/louim/in-case-of-fire/blob/master/in_case_of_fire.png)
-> The #CodeRefinery workshop next week gets you started with version control with #git so that you can protect your work, not only "in case of fire"; and many more topics around code development for research!
More info and registration at: https://coderefinery.github.io/2024-03-12-workshop/
Do you want to learn the basics of keeping track of your research code?
-> The #CodeRefinery workshop starts with the very basics of version control with #git. Get to know how you can contribute to existing projects as well as start your own.
More info and registration at: https://coderefinery.github.io/2024-03-12-workshop/
Maybe you have already "cloned a repository" as part of your computational research training; but git(-hub,-lab) is so much more than that!
-> Join the CodeRefinery workshop next week to learn how git can help you keep your scripts in order, when working alone, on multiple computers or collaborating with others.
More information and registration: https://coderefinery.github.io/2024-03-12-workshop/
How can #CodeRefinery offer its courses to everyone?
By rethinking the system: Courses are #Livestream, so anyone can watch (information should be free), videos are public. Getting help isn't free, so we do what we can for our local audiences.
Why don't you offer local support to your audiences to attend?
-> Week 1 git for research, week 2 reproducible research: https://coderefinery.github.io/2024-03-12-workshop/
Got some code written to conduct your research and want or need to publish it alongside your publication?
-> In the CodeRefinery workshop we'll show you what kind of steps you can take to get your code ready for publication and give others a chance to reuse it.
More info and registration at: https://coderefinery.github.io/2024-03-12-workshop/
Maybe you have heard about #FAIRdata, but do you know about #FAIR software? If you write code for research, this is an important concept for reusability of your code.
-> join the #CodeRefinery workshop to learn how you can take small steps towards producing more FAIR Research Software.
More information and registration:
https://coderefinery.github.io/2024-03-12-workshop/
#CodeRefinery is part of #PhysicsDays 2024, the gathering of Physicists in Helsinki with a poster today.
Wanna know what CodeRefinery is and how the project may help advance your research computing activities?
-> Come chat with Aurélie Vancraeyenest on 2nd floor lobby 16.45 - 18.00 this afternoon
In the last session of #CodeRefinery team week we discussed our onboarding process:
We talked a lot about paths on to CodeRefinery: What's the team and who is on it? How can people be involved? We'll try more community calls, mentors, ambassadors, and we'll also get shirts and something. Our chat (https://coderefinery.zulipchat.com) has a fair number of people and constant stream of interesting ideas on it. Co-teaching in our workshops as a starting point for new instructors has worked very well.
Help wanted: How would you recommend a new student to get started with Git? For example, what editor, how to authenticate to Github, etc. Usability is most important here!
We are interested in answers for every operating system.
More info on context: https://coderefinery.org/blog/2024/02/29/install-instructions/ #RSEng #HPC #OpenScience #SciComp
We looked at results from the post-workshop survey sent to the participants from the last 2 years. Overall, results were quite positive (but we are aware of observation bias) - there is little to complain about.
Our questions about "how to change the format in the future" were inconclusive: it was all over the place, centered around the current format (observation bias).
We will publish the results soon.
We talked about citable lessons. The goal is to better acknowledge people who have contributed.
We roughly agreed on citation levels "editors", "authors", and "acknowledgees" (see https://coderefinery.github.io/manuals/lesson-credits/).
We already build PDFs of all lessons so we'll set up releases to upload to Zenodo. #CodeRefinery
Session summary form #CodeRefinery team week:
We talked about social media strategy. Most of us aren't major social media people, but we'd like to try to be more engaging. Can we share our tips and tricks more widely?
We discussed how #CodeRefinery could evolve later: instead of synchronous (livestream), what are async options: recorded videos and Q&A sessions, something on a MOOC platform that has auto-grading, or what?
We aren't sure. The main issue right now is the time to put on a new course twice a year, especially instructor wrangling. (hint: volunteer with us)
First session today was evaluating the "Modular code development" lesson. Some like the lesson as-is, but also some who thought it should be more engaging.
What do you all think of the lesson? If you haven't seen it before, it gets great feedback for showing the transition form a Jupyter plot to a reusable command line tool: https://youtu.be/x0FoTBZcn2U?t=3714 #RSEng #CodeRefinery #jupyter #CommandLine #OpenScience
Summary from #CodeRefinery team session where we discussed Git lesson redesign:
We are considering starting from the web interface and moving to the command-line or editor only on day 2. We want to bring the lesson closer to how learners are likely to work with Git in future.
Let's see if we manage the rewrite already for the upcoming workshop.
Summary from #CodeRefinery team session where we discussed the install instructions in detail:
As expected, it became a discussion about usability and how to help a broad audience use Git - which these days is *not* pedantically from the command line.
We'll have some follow-up posts where you can help us by giving some thoughts.
Summary from #CodeRefinery team session on workshop formats (2/2):
For large online workshops, we need to better evaluate how it goes (live polls), and we need to reduce the complexity of attending, organizing, and teaching. We do cool stuff, but cool also means new and complex. It's easy to volunteer to teach for 20 people in a room, a higher threshold for online/live-stream/YouTube-posted - even though we do co-teaching and have put a lot of effort into getting instructors started.
Summary from #CodeRefinery team session on workshop formats (1/2):
In our session on workshop formats, we divided into two groups thinking of small workshops (in-person and online), and large workshops (online, and online with concurrent in-person sessions). For small workshops, we would like to make it easier to request one (practically: a way for an organization to provide funding and get an instructor to run a session for them).
The #CodeRefinery in-person meeting week has started.
In the morning, we talked about Git lesson design (how can we make it reflect real work better?).
In the afternoon we shared how we process workshop videos - many of us had never done it before, and it's actually pretty fast and powerful.
#CodeRefinery team meeting summary 2024-02-12
Our March 12-21 workshop is coming near! Mostly we are preparing for that in various forms, for example distributing lessons, outreach, and re-organizing lessons.
The team will meet soon in to discuss the future of the project. Any suggestions?