Open bclenet opened 9 months ago
Thanks @bclenet! Ping: @elodiegermani @Arshitha @Remi-Gau @yarikoptic @mrneont this is our submission for the OHBM Brainhack 2023 proceedings.
Thank you @bclenet and all, such outstanding achievements! We are considering going for more paragraph-like content than list, what do you think? To ease the process, I've rewritten the results content as a paragraph (line breaks just to ease the read, not new paragraphs). If you'd like to make changes, please feel free to copy the content to the main text in this issue.
During the OHBM Brainhack 2023, participants had the opportunity to improve the project in various ways. Firstly, they focused on fostering a more inclusive environment for new contributors, refining the contribution process through proofreading and testing. Several pull requests (PR #66, PR #65, PR #63, PR #64, PR #52, PR #50) were dedicated to this effort, rectifying inconsistencies in the documentation and contributing procedures. Additionally, they implemented GitHub Actions workflows to enable continuous integration, ensuring the testing of pipelines with each alteration (PR #47), and crafted a new workflow to detect code comments and documentation typos (PR #48). Skill acquisition was a significant aspect, with individuals diving into NiPype and advancing pipeline reproductions. Thanks to Paul Taylor's contributions, a deeper understanding of AFNI pipelines emerged, particularly benefiting from afni_proc examples within the NARPS project (Taylor et al., 2023). This endeavor resulted in the initiation of new pipeline reproductions (PR #62, Issue #61, PR #59, Issue #57, Issue #60, PR #55, Issue #51, Issue #49). Ultimately, the Hackathon yielded substantial progress: 6 pull requests merged, 4 issues opened, 4 closed, and 6 opened, showcasing a fruitful collaboration and dedication to project enhancement.
Hi @anibalsolon and thanks for the comment, I'm fine with this new shape, as long as the links are still available and lead to the right place (e.g.: #47 should not point to this repo's issue number 47 but to narps_open_pipelines' one).
Certainly, I'll make sure the links are correct. Thank you!
hello all, could you please provide the authors information in the following link by May 15th? https://docs.google.com/forms/d/e/1FAIpQLSckbC4F6KOtge1KOyzwj5yIbWR7tB8HrnqQ4KPZB7Mr3UcvMw/viewform
Authors
Affiliations
Boris Clénet1, Élodie Germani1, Arshitha Basavaraj2, Remi Gau3, Yaroslav Halchenko4, Paul Taylor5, Camille Maumet1
Contacts
Boris Clénet boris.clenet@inria.fr Élodie Germani elodie.germani@inria.fr Arshitha Basavaraj arsh2794@gmail.com Remi Gau remi.gau2@mcgill.ca Yaroslav Halchenko Yaroslav.O.Halchenko@dartmouth.edu Paul Taylor ptaylor.afni@gmail.com Camille Maumet camille.maumet@inria.fr
Summary
Introduction
Different analytical choices can lead to variations in the results, a phenomenon that was illustrated in neuroimaging by the NARPS project (Botvinik-Nezer et al., 2020). In NARPS, 70 teans were tasks to analyze the same dataset to answer 9 yes/no research questions. Each team share their final results as well as a textual description (COBIDAS-compliant Nichols et al., 2017) of their analysis.
The goal of NARPS Open Pipelines is to create a codebase reproducing the 70 pipelines of the NARPS project and share this as an open resource for the community.
Results
The OHBM Brainhack 2023 gave the oppurtunity to:
make the repository more welcoming to new contributions:
Proof-read and test the contribution process : everyone helped in finding and fixing inconsitencies in the documentation and in the processes related to contributing. PR#66, PR#65, PR#63, PR#64, PR#52, PR#50
Create GitHub Actions workflows for enabling continuous integration, i.e.: testing existing pipelines everytime there are changes on them. PR#47
Develop a new GitHub Actions workflow to detect typos in code comments and documentations at each commit. PR#48
learn new skills:
advance pipeline reproductions
In the end a total of:
References (Bibtex)