OSCR

The therapeutic potential of exercise in post-traumatic stress disorder and its underlying mechanisms: A living systematic review of human and non-human studies.

This page is built on request from the registry's record of the paper. The 6,000 most recent papers have a fuller page, built ahead of time, with the Code ↔ Paper reader, the tracing map and its validation, the record's versions, how to cite it and similar papers. This paper is older: its record, its code, its data and the requests about it are below.

Code

8 files of its code read; 5 matches between paragraphs and code. The Code ↔ Paper reader is built for the 6,000 most recent papers only: this paper's code is read at its source.

galenos-project/LSR2_exercise_H

License: none: the authors keep all their rights
State: the link answers
Copies: kept by the registry: this license allows it

galenos-project/LSR2_exercise_A

License: none: the authors keep all their rights
State: the link answers
Copies: kept by the registry: this license allows it

OSF q8uhz

License: none: the authors keep all their rights
State: the link answers

OSF zn5p4

License: none: the authors keep all their rights
State: the link answers
Tools found in the code: ggplot2, ggpubr, JAGS, metafor, patchwork, tidyverse

Overview

Authors: Simonne Wright, Virginia Chiocchia, Olufisayo Elugbadebo, Ouma Simple, Toshi A Furukawa, Claire Friedrich, Charlotte Austin, Hossein Dehdarirad, David Gilbert, Jaycee Kennett, Edoardo G Ostinelli, Jennifer Potts, Fiona Ramage, Emily Sena, Spyridon Siafis, Claire Stansfield, James Thomas, Francesca Tinsdeall, Thomy Tonia, Malcolm Macleod, Andrea Cipriani, Georgia Salanti, Soraya Seedat
Published: 1 January 2024
Type: Systematic review
Status: code verified (how the code is found and verified)
License: CC BY

Data

Datasets cited

Contribute

The authors of this paper can claim it and correct its record, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to the registry's own machine, which answers it; your account page follows them.

Sign in with ORCID to claim this paper as one of its authors or correct its record: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.

Add the badge to the code's README

OSCR: the badge of this paper

Authors and maintainers of this paper's code: the badge says what OSCR knows of the paper and links the code to this page. Paste one of these under the README's title. Keep the two marks around it: they let the badge be replaced in place, never added twice. Nothing is changed for you.

Markdown
<!-- oscr-badge:start -->
[![OSCR](https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4.svg)](https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4.svg
   :target: https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4"><img src="https://openscicode.org/badge/doi/10.12688/wellcomeopenres.23033.4.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->

On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".

Or let it be kept for you, once you choose it: oscr badge --write from the command line, or the GitHub Action in your repository's workflows. Every other form is on the badge page.

Request its removal

To ask for this record, the copies of its authors' scripts or its tracing map to be removed, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).