Codecheck progress update

[sje30]

Dear @codecheckers/codecheckers

as you may have seen on Twitter, we have now published a preprint on F1000R summarising our progress to date with CODECHECK.

https://f1000research.com/articles/10-253/v1

We thank you again for showing an interest in our project. COVID affected our plans to energise the community, and instead we focused on checking papers that we (Daniel and I) could mostly do.

Now that our paper is out, the question is - what next for CODECHECK?

We have made a pre-application for funding to the Wellcome Trust, to help develop the community. If this is not successful, we might try for other funding sources.

A few journals are beginning to show interest, so if you would like to still be involved in CODECHECK, and would like to volunteer to check an article, just let us know by commenting below. We also welcome other ideas for how we can grow this initiative.

Best wishes,

Daniel @nuest and Stephen @sje30

[GNilsonne]

That's great! Happy to stay involved with future developments.

Best wishes, Gustav

Gustav Nilsonne MD, PhD, Associate Professor | National Coordinator of Domain Specialists Karolinska Institutet | Swedish National Data Service Nobels väg 9, 171 77 Solna +46 736798743 @.**@.> | ki.sehttp://ki.se/en/startpage

---

Från: Stephen Eglen @.> Skickat: den 1 april 2021 11:10 Till: codecheckers/discussion @.> Kopia: Gustav Nilsonne @.>; Team mention @.> Ämne: [codecheckers/discussion] Codecheck progress update (#18)

Dear @codecheckers/codecheckershttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Forgs%2Fcodecheckers%2Fteams%2Fcodecheckers&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601425366%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9TiPKLgzfy8IkvjhQuG21s1TTdZqa%2FLsSjlExZbCl6A%3D&reserved=0

as you may have seen on Twitter, we have now published a preprint on F1000R summarising our progress to date with CODECHECK.

https://f1000research.com/articles/10-253/v1https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ff1000research.com%2Farticles%2F10-253%2Fv1&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601435362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zR%2Fzpgw6ZVd5QMAyntQB%2FcxK2WOT0HVSywad2xwVLCE%3D&reserved=0

We thank you again for showing an interest in our project. COVID affected our plans to energise the community, and instead we focused on checking papers that we (Daniel and I) could mostly do.

Now that our paper is out, the question is - what next for CODECHECK?

We have made a pre-application for funding to the Wellcome Trust, to help develop the community. If this is not successful, we might try for other funding sources.

A few journals are beginning to show interest, so if you would like to still be involved in CODECHECK, and would like to volunteer to check an article, just let us know by commenting below. We also welcome other ideas for how we can grow this initiative.

Best wishes,

Daniel @nuesthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnuest&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601435362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=79Mr3BvdQ5ER4BVk5usFN5%2BLFuKMSIngcmS0tOXOTr4%3D&reserved=0 and Stephen @sje30https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsje30&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601445354%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=su9ncKIPcUhF0kux2VXhspzTByCHN5K9z9E%2FYdQQfpo%3D&reserved=0

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcodecheckers%2Fdiscussion%2Fissues%2F18&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601445354%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TVh859Vge%2FEKP4TBg41vi3zc12bweNMsTMhxRGVO0Do%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABKXN3ZT5L2MHQT4N4XPIW3TGQ2CDANCNFSM42GWN7RA&data=04%7C01%7Cgustav.nilsonne%40ki.se%7C70286e020e724877cd9a08d8f4ee107b%7Cbff7eef1cf4b4f32be3da1dda043c05d%7C0%7C0%7C637528650601455349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QiH%2BakT85ekIiGY%2FuqhsWh683mcygs53lQ8geQ1%2FfzA%3D&reserved=0.

När du skickar e-post till Karolinska Institutet (KI) innebär detta att KI kommer att behandla dina personuppgifter. Här finns information om hur KI behandlar personuppgifterhttps://ki.se/medarbetare/integritetsskyddspolicy.

Sending email to Karolinska Institutet (KI) will result in KI processing your personal data. You can read more about KI’s processing of personal data herehttps://ki.se/en/staff/data-protection-policy.

[GiulioCentorame]

Dear Daniel and Stephen,

Thank you for the update. I confirm I still want to take part in the project and I renew my availability in terms of time. Cheers

Giulio

[Remi-Gau]

Count me in!!!!

[NathanSkene]

Happy to hear this! I'm also happy to be involved, I think this is a great initiative

On Thu, 1 Apr 2021, 10:10 Stephen Eglen, @.***> wrote:

This email from @.*** originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address.

Dear @codecheckers/codecheckers https://github.com/orgs/codecheckers/teams/codecheckers

as you may have seen on Twitter, we have now published a preprint on F1000R summarising our progress to date with CODECHECK.

https://f1000research.com/articles/10-253/v1

We thank you again for showing an interest in our project. COVID affected our plans to energise the community, and instead we focused on checking papers that we (Daniel and I) could mostly do.

Now that our paper is out, the question is - what next for CODECHECK?

We have made a pre-application for funding to the Wellcome Trust, to help develop the community. If this is not successful, we might try for other funding sources.

A few journals are beginning to show interest, so if you would like to still be involved in CODECHECK, and would like to volunteer to check an article, just let us know by commenting below. We also welcome other ideas for how we can grow this initiative.

Best wishes,

Daniel @nuest https://github.com/nuest and Stephen @sje30 https://github.com/sje30

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/codecheckers/discussion/issues/18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5ZPE3PZPIPFCJBRMY4CF3TGQ2CFANCNFSM42GWN7RA .

[NathanSkene]

BTW, we've been having lots of discussions within the my institute about institutional policies re open science. Seems to me that a good goal would be to get an institute to make code checking part of their open science policy.

On Thu, 1 Apr 2021, 12:15 Nathan Skene, @.***> wrote:

Happy to hear this! I'm also happy to be involved, I think this is a great initiative

On Thu, 1 Apr 2021, 10:10 Stephen Eglen, @.***> wrote:

This email from @.*** originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address.

Dear @codecheckers/codecheckers https://github.com/orgs/codecheckers/teams/codecheckers

as you may have seen on Twitter, we have now published a preprint on F1000R summarising our progress to date with CODECHECK.

https://f1000research.com/articles/10-253/v1

We thank you again for showing an interest in our project. COVID affected our plans to energise the community, and instead we focused on checking papers that we (Daniel and I) could mostly do.

Now that our paper is out, the question is - what next for CODECHECK?

We have made a pre-application for funding to the Wellcome Trust, to help develop the community. If this is not successful, we might try for other funding sources.

A few journals are beginning to show interest, so if you would like to still be involved in CODECHECK, and would like to volunteer to check an article, just let us know by commenting below. We also welcome other ideas for how we can grow this initiative.

Best wishes,

Daniel @nuest https://github.com/nuest and Stephen @sje30 https://github.com/sje30

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/codecheckers/discussion/issues/18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5ZPE3PZPIPFCJBRMY4CF3TGQ2CFANCNFSM42GWN7RA .

[ethanbb]

Thanks for the update - I'm still interested!

[stm]

Thanks for the update! I still think it's a great initiative and I'm happy to help!

[bhym]

Thank you for the update. Count me in as well!

[chenyenchung]

Thanks for letting us know! I am still interested as well.

[mstimberg]

Hi everyone! Same here, still interested in contributing :+1:

[Christian-T]

Thanks for the update; I'm still interested as well :)

[jmoldon]

Thanks for the information! I am still interested as well.

On Sat, Apr 3, 2021 at 9:32 AM Christian-T @.***> wrote:

Thanks for the update; I'm still interested as well :)

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/codecheckers/discussion/issues/18#issuecomment-812827890, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIBDCSIULZHKKBWXRXP2XDTG3ABXANCNFSM42GWN7RA .

[sjvrijn]

I'm still interested.

[leipzig]

I'm still interested. BTW, I also have some opportunities for others to kick the tires on a couple of bioinformatics analyses for my dissertation work. If you are interested in splicing or m6a epitranscriptomics please reach out to me. There is a survey and I would like participants to do 4 hours or so of robustness testing. A $250 recompense is provided.

[LindaNab]

Hi! Thanks for keeping us updated. I'm still interested as well!

[nuest]

Thank you all for the positive feedback!

@NathanSkene I think a pre-submission workflow execution by a third party "in house" is a great idea. What part of CODECHECK do you think is directly transferable, and what not? Happy to continue the discussion in a new issue if you like.

[DanielaGawehns]

Sorry for the late reaction. I am happy to stay involved, as well!