Age-related change in task-evoked amygdala-prefrontal circuitry: A multiverse approach with an accelerated longitudinal cohort aged 4-22 years.
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
200 files of its code read; 18 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.
pab2163/amygdala_mpfc_multiverse
pab2163.github.io/amygdala_mpfc_multiverse
Code blocks with an identifier
Each block below is lines of the authors' code linked to a paragraph of this paper, with an identifier given for good: it is never reused nor deleted, and its page says what it names and how to cite it. What a block identifier is.
oscr:b:29K4VTRTFTRS6-A: 0_setup_and_behavioral_analyses/ , lines 1 to 76 (paragraph 47)2_model_task_behavior.R oscr:b:DSWESTJ31WXN1-A: 8_interactive_multiverse_app/ , lines 61 to 120 (paragraphs 78, 77)reactivity_ui.R oscr:b:T8KYAQSERJ5E7-9: 8_interactive_multiverse_app/ , lines 1 to 60 (paragraph 87)bsc_ui.R oscr:b:E4HPKZ3KY6C0E-O: _site/site_libs/ , lines 1 to 2 (paragraphs 48, 38)highlightjs-9.12.0/ highlight.js oscr:b:RHSDVNYKZP84V-J: 8_interactive_multiverse_app/ , lines 1 to 60 (paragraphs 69, 44)gppi_ui.R oscr:b:1TQ90821ZGFJV-X: 7_group_level_analyses/2_make_plots_inspect_mod , lines 135 to 272 (paragraph 49)els/ 2f_reactivity_connectivi ty_motion_cors.Rmd oscr:b:A7DTG39XY4KJ9-6: 9_specification_curve_walkthrough/ , lines 732 to 766 (paragraph 50)into_the_bayesian_multiv erse.Rmd oscr:b:XBS8H0NTKC1KZ-P: 1_head_motion/2_haba_bold_motion_asses , lines 22 to 44 (paragraph 48)s_all_emotions.py oscr:b:GX83SNGH25E4P-C: 7_group_level_analyses/2_make_plots_inspect_mod , lines 501 to 601 (paragraphs 65, 83)els/ 2d_amyg_within_scan_chan ge_plots.Rmd oscr:b:TZPZF9D40277E-F: 7_group_level_analyses/1_run_multiverse_group_l , lines 336 to 385 (paragraph 93)evel_models/ 1i_reliability_longitudi nal_bayes.Rmd oscr:b:RC66BPT3Z8E8Y-I: 7_group_level_analyses/0_compile_data/ , lines 168 to 202 (paragraph 38)0h_make_supplemental_dem og_table.Rmd oscr:b:0MMJHWA8ADKWV-J: 4_gppi/1_gppi_regressors_with_d , lines 24 to 93 (paragraph 67)econvolution.py oscr:b:FHMPP60XX0S1F-T: _site/4_gppi/ , lines 24 to 93 (paragraph 67)0c_make_afni_style_regre ssors_fear_happy.py oscr:b:4VHNB6ZS3DPM6-F: 7_group_level_analyses/2_make_plots_inspect_mod , lines 127 to 164 (paragraph 90)els/ 2g_brain_sep_anxiety_plo ts.Rmd
Overview
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.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record.
Add the badge to the code's README
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 -->
[](https://openscicode.org/badge/doi/10.1002/hbm.25847)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1002/hbm.25847.svg
:target: https://openscicode.org/badge/doi/10.1002/hbm.25847
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1002/hbm.25847"><img src="https://openscicode.org/badge/doi/10.1002/hbm.25847.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).
