Pilot Code Check Club

[debruine]

[Copied from Slack]

Several people expressed enthusiasm for running a pilot “code check club” in this group. I think it would help us to really flesh out the problems and procedure of doing code check, so let’s organise one for August with whoever can come (note in the thread if you’re interested).

Here’s how I suggest it be organised (please reply to this thread with critique/suggestions):

• one person volunteers an analysis script
• everyone gets access to the script in the way it’s meant to be shared (github, OSF, etc) a week before the session
• one person volunteers to take lead at the session to “live code” their code review
• other attendees offer suggestions and ask questions
• one person tasked as note-taker to record issues and solutions, as the script writer and code reviewer will probably not have the bandwidth during the session to take good notes

[debruine]

I made a repo for this and added an example we could use. If anyone else has ideas, please add them.

https://github.com/code-check-club/code-check-club

[chartgerink]

Nice 🙏

Last year, I did some "Reproducibility livestreams" where I looked into the shared data and code of a paper. This was very interesting to do and taught me that I usually was able to reproduce (or not) in 90-120mins.

Would be happy to participate in a code check club and learn about it with you! 😊

[debruine]

Our next tasks for this are:

• Add more potential scripts to check (something in python would be good)
• Choose a script for the first pilot
• Choose a date/time for the pilot
• Set up a venue (probably Zoom?)
• Run the pilot!
• Debrief on the process

[debruine]

@code-check-club/members: we've not have any other code submissions, so I was thinking we could go with DeBruine_2002 as it's a very simple analysis and my own work. It's my first published paper, and I shared the data and created R code for the analyses (originally done in SPSS) 18 years later. It could definitely use some clarification, but isn't in terrible shape, so should be a quick one to start with. If that's OK with everyone, the next step is to pick a date and time for the pilot.

📅 I set up a when2meet for August 22 to September 2. If you are interested in attending the code check club pilot, please respond by August 17th and I'll announce the date and time on the 18th.

[EPronizius]

There are 3 slots, where we have 6/8. In all 3 slots, I am one of the people who cant make it. BUT I am willing to move things around and make it happen! I updated my entries. :)

[anamartinovici]

Hi. Sorry for not filling in my availability before Aug 17. I'm currently ooo, but will be fully back starting Aug 29. If the meeting takes place after Aug 29 and if it is still ok for me to join, then it would be great if someone could fw the meeting invite. Thank you.

[cconrymurray]

I just updated my availability too--sorry for the delay. I'm feeling behind! It looks like I may be the only one unavailable a few times, but I'm in class so I can't move those times. If you need to meet without me that's fine. I also have a few papers with raw data, clean data and code on OSF that are probably quite messy but I'm open to code check if it's helpful. -- when it's OK to steall: https://osf.io/4zn6t/ -- judgments of abstracts with and without preregistrations: https://osf.io/wdptv/

…

On Tue, Aug 23, 2022 at 2:47 PM Ekaterina Pronizius < ***@***.***> wrote: There are 3 slots, where we have 6/8. In all 3 slots, I am one of the people who cant make it. BUT I am willing to move things around and make it happen! I updated my entries. :) — Reply to this email directly, view it on GitHub <#2 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2KZCMOM6BSWCPUQBCQSJITV2UMEXANCNFSM55KTU3JA> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.*** com>

[lisalevinson]

Are we still doing this or did I miss it? I'm having a really hard time keeping track of things using GitHub discussions. Email notifications mean that everything is just lost in an endless pit for me!