You can load this project in RStudio by opening the file called 'NPQ_correction.Rproj'.

This project uses the Workflow for Open Reproducible Code in Science (WORCS) to ensure transparency and reproducibility. The workflow is designed to meet the principles of Open Science throughout a research project.

• To learn how WORCS helps researchers meet the TOP-guidelines and FAIR principles, read the preprint at https://osf.io/zcvbs/
• To get started with worcs, see the setup vignette
• For detailed information about the steps of the WORCS workflow, see the workflow vignette
• For a brief overview of the steps of the WORCS workflow, see below.

1. Create a (Public or Private) remote repository on a 'Git' hosting service
2. When using R, initialize a new RStudio project using the WORCS template. Otherwise, clone the remote repository to your local project folder.
3. Add a README.md file, explaining how users should interact with the project, and a LICENSE to explain users' rights and limit your liability. The worcs project template does this automatically.
4. Optional: Preregister your analysis by committing a plain-text preregistration and tagging the commit as "preregistration".
5. Optional: Upload the preregistration to a dedicated preregistration server
6. Optional: Add study Materials to the repository

6. Create an executable script documenting the code required to load the raw data into a tabular format, and de-identify human subjects if applicable
7. Save the data into a plain-text tabular format like .csv. When using open data, commit this file to 'Git'. When using closed data, commit a checksum of the file, and a synthetic copy of the data.
8. Write the manuscript using a dynamic document generation format, with code chunks to perform the analyses.
9. Commit every small change to the 'Git' repository
10. Cite essential references with @, and non-essential references with @@

11. Use dependency management to make the computational environment fully reproducible
12. Optional: Add a WORCS-badge to your project's README file
13. Make a Private 'Git' remote repository Public
14. Optional: Create a project page on the Open Science Framework
15. Connect your 'OSF' project page to the 'Git' remote repository
16. Add an open science statement to the Abstract or Author notes, which links to the 'Git' remote repository or 'OSF' page
17. Render the dynamic document to PDF
18. Optional: Publish the PDF as a preprint, and add it to the OSF project
19. Submit the paper, and tag the release of the submitted paper, as in Step 3.

Some researchers might want to share their work only once the paper is accepted for publication. In this case, we recommend creating a "Private" repository in Step 1, and completing Steps 13-18 upon acceptance.