Hippocampal place cells map terrain geometry independently of behavior.
11 blocks of code here have a permanent identifier (oscr:b:…), listed with the matches below: citable for good, with a page of its own. Select a match and press Cite to copy it. What a block identifier is.
The 15 matches
- [1] § MATERIALS AND METHODS › Generalized linear model ↔ utils/PIT_over_glm.m, lines 144 to 221 · score 0.84 · tilt directionality, tilt stability, speed score, terrain score, notation, fitglm · block
oscr:b:B4HFVM5ZRR881-Y· Report a mismatch - [2] § MATERIALS AND METHODS › Place field characteristics ↔ plotting/PIT_fig_8_v1.m, lines 81 to 138 · score 0.77 · Place field detection, minor axis length, major axis length, weighted centroid, regionprops, orientation · block
oscr:b:CYPPEJN6EFWHC-O· Report a mismatch - [3] § MATERIALS AND METHODS › Place field characteristics ↔ plotting/PIT_sup_1sess_v1.m, lines 662 to 719 · score 0.77 · Place field detection, minor axis length, major axis length, weighted centroid, regionprops, orientation · block
oscr:b:DR1H2TEQJXXP8-8· Report a mismatch - [4] § MATERIALS AND METHODS › Generalized linear model ↔ utils/PIT_over_glm.m, lines 59 to 115 · score 0.70 · Partial R2, full model, Terrain score, repetition score, predictor, linear · block
oscr:b:7MF5WGBJPZC2Y-R· Report a mismatch - [5] § RESULTS › Terrain acts as a geometric input to place cells ↔ GIT_audit.m, lines 1 to 141 · score 0.70 · movement bias, behavioral anisotropy, place field elongation, place field anisotropy, S8, slopes · block
oscr:b:036BV0ATT45FV-G· Report a mismatch - [6] § RESULTS › Field repetition and elongation are explained by the BVC model ↔ GIT_audit.m, lines 1 to 141 · score 0.67 · BVC modeled place, Modeled place fields, place field elongation, S7, S13, S6 · block
oscr:b:036BV0ATT45FV-G· Report a mismatch - [7] § MATERIALS AND METHODS › Place field detection ↔ plotting/PIT_fig_8_v1.m, lines 81 to 138 · score 0.61 · contiguous regions, peak firing rate, Firing rate maps, thresholded, detection, place fields · block
oscr:b:CYPPEJN6EFWHC-O· Report a mismatch - [8] § MATERIALS AND METHODS › Place field detection ↔ plotting/PIT_sup_1sess_v1.m, lines 662 to 719 · score 0.61 · contiguous regions, peak firing rate, Firing rate maps, thresholded, detection, place fields · block
oscr:b:DR1H2TEQJXXP8-8· Report a mismatch - [9] § MATERIALS AND METHODS › Firing rate maps ↔ klustest/unused/GIT_hilltest.m, lines 109 to 196 · score 0.57 · Gaussian kernel, Firing rate maps, histograms, interval, smoothed, bin · block
oscr:b:Y89APFERXA98R-N· Report a mismatch - [10] § MATERIALS AND METHODS › Firing rate maps ↔ klustest/unused/GIT_klustest3.m, lines 109 to 196 · score 0.57 · Gaussian kernel, Firing rate maps, histograms, interval, smoothed, bin · block
oscr:b:YJ24E9YK1FS1B-U· Report a mismatch - [11] § MATERIALS AND METHODS › Boundary vector cells ↔ utils/pitch_tuning.m, lines 29 to 77 · score 0.56 · receptive field, tuning curves, angle, Arena, cells · block
oscr:b:N1KDT9NHBH05A-N· Report a mismatch - [12] § MATERIALS AND METHODS › Position tracking ↔ utils/PIT_pitch_tuning.m, lines 56 to 102 · score 0.56 · head roll, surface normal, LED, animals · block
oscr:b:STWMW9ZDWY4WH-H· Report a mismatch - [13] § MATERIALS AND METHODS › Anisotropy simulations ↔ plotting/PIT_sup_fig_9_v1.m, lines 102 to 230 · score 0.53 · Gaussian weight, wall angle, normpdf, anisotropy, distance, axis · block
oscr:b:GZN5ZZ67YDX5S-J· Report a mismatch - [14] § MATERIALS AND METHODS › Anisotropy analyses ↔ GIT_sim.m, lines 189 to 229 · score 0.53 · weighted centroid, axis length, Firing rate maps, histogram, smoothed, place field · block
oscr:b:P4DSB5GH5B98V-Z· Report a mismatch - [15] § MATERIALS AND METHODS › Position tracking ↔ utils/PIT_pitch_tuning.m, lines 56 to 102 · score 0.51 · norm, rx, front, cross, LEDs, azimuth · block
oscr:b:STWMW9ZDWY4WH-H· Report a mismatch
Paper
Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
MATLAB · 224 lines · 7.6 KB · MIT · 2 matches
- % PIT_over_glm
- % Fig S10 for Grieves, Duvelle and Jeffery (2026) Hippocampal place cells map
- % terrain geometry independently of behaviour
- % Reviewer requested, GLM, residuals and stats
- %
- % SEE ALSO GIT_audit
- % HISTORY
- %
- % version 1.0.0, Release 06/02/23 Code conception
- % version 2.0.0, Release 15/04/26 Publication release
- %
- % NOTES
- %
- % 1. This script require the summary dataset:
- % https://doi.org/10.5281/zenodo.17634454
- %
- % 2. This script is intended to be run via the control function GIT_audit
- %
- % AUTHOR
- %
- % Roddy Grieves
- % University of Glasgow, Sir James Black Building
- % Neuroethology and Spatial Cognition Lab
- % eMail: [email hidden]
- % Copyright 2026 Roddy Grieves
- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% INPUT ARGUMENTS CHECK
- % Create figure
- fig_now = figure('Units','pixels','Position',[50 50 210.*3 297.*3],'visible','on');
- set(gcf,'InvertHardCopy','off'); % gives the figure a grey background but means it will save white lines as white
- set(gcf,'color','w'); % makes the background colour white
- fs = [15 10];
- x = 0:10:3000;
- y = 0:10:1500;
- F = 0.299;
- wav = cos(2*pi*F*x+pi);
- wav = ((wav+1)./2)*450;
- [yy,xx] = ndgrid(y,x);
- zz = repmat(wav,size(xx,1),1);
- g = gradient(wav);
- gg = repmat(g,size(xx,1),1);
- clumaa.terrain_score = NaN(size(clumaa,1),1);
- for mm = 1:size(clumaa,1)
- if clumaa.partn(mm)~=2
- continue
- end
- mnow = clumaa.ratemap_surficial{mm};
- gnow = imresize(gg,size(mnow),"nearest");
- r = corr(mnow(:),gnow(:),"Type","Pearson","Rows","pairwise");
- clumaa.terrain_score(mm,1) = r;
- end
- clumaa = PIT_correlations(config,pidx,clumaa,posdata,0);
- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% FUNCTION BODY
- % Dependent variable
- repetition_score = clumaa.repetition_score(pidx & clumaa.partn==2,1); % repetition score, all place cells, ridges
- % Predictors
- speed_score = clumaa.speed_score(pidx & clumaa.partn==2,1); % Nx1 vector, correlation values
- azimuthal_directionality = clumaa.hd_3d_info(pidx & clumaa.partn==2,3); % Nx1 vector, spatial info content
- left_vs_right_stability = clumaa.azimuth_stability(pidx & clumaa.partn==2,1);
- pitch_directionality = clumaa.hd_3d_info(pidx & clumaa.partn==2,7); % Nx1 vector, spatial info content
- up_vs_down_stability = clumaa.pitch_stability(pidx & clumaa.partn==2,1);
- terrain_measure = abs(clumaa.terrain_score(pidx & clumaa.partn==2,1)); % Nx1 vector, terrain correlation
- % figure
- % scatter(repetition_score,speed_score,30,'k','filled','o');
- % refline
- % keyboard
- % Pack predictors and dependent variable into a table
- T = table(speed_score(:), azimuthal_directionality(:), left_vs_right_stability(:), pitch_directionality(:), up_vs_down_stability(:),terrain_measure(:), repetition_score(:),'VariableNames', {'speed_score','azimuthal_directionality','left_vs_right_stability','pitch_directionality','up_vs_down_stability','terrain_measure','repetition_score'});
- % Full GLM (linear regression)
- mdl = fitglm(T,'repetition_score ~ speed_score + azimuthal_directionality + left_vs_right_stability + pitch_directionality + up_vs_down_stability + terrain_measure','Distribution', 'normal', 'Link', 'identity');
- plotPartialRegression(fig_now,mdl);
- % Display outputs
- disp('--- Full Model Summary ---');
- disp(mdl);
- % Get full model R²
- R2_full = mdl.Rsquared.Ordinary;
- % Partial R² loop (from previous code)
- predictors = mdl.PredictorNames;
- partialR2 = zeros(numel(predictors),1);
- for i = 1:numel(predictors)
- reducedPredictors = setdiff(predictors, predictors{i});
- formula = sprintf('repetition_score ~ %s', strjoin(reducedPredictors, ' + '));
- mdl_reduced = fitglm(mdl.Variables, formula);
- SSE_reduced = mdl_reduced.SSE;
- SSE_full = mdl.SSE;
- % Partial R² (unique contribution of predictor i)
- partialR2(i) = (SSE_reduced - SSE_full) / SSE_reduced;
- end
- % % of total R² explained
- percentR2 = (partialR2 / R2_full) * 100;
- % Results table
- T_contrib = table(predictors, partialR2, percentR2,'VariableNames', {'Predictor','PartialR2','PercentOfTotalR2'})
- % keyboard
- %%%%%%%%%%%%%%%% Save the overall figure
- if 1
- fname = [config.fig_dir '\Fig S11a.png'];
- if fast_figs
- frame = getframe(gcf); % fig is the figure handle to save
- [raster, raster_map] = frame2im(frame); % raster is the rasterized image, raster_map is the colormap
- if isempty(raster_map)
- imwrite(raster, fname);
- else
- imwrite(raster, raster_map, fname); % fig_file is the path to the image
- end
- else
- exportgraphics(gcf,fname,'BackgroundColor',[1 1 1],'Colorspace','rgb','Resolution',res);
- end
- close(gcf);
- end
- function plotPartialRegression(fig,mdl)
- % mdl: fitglm or fitlm object
- X = mdl.Variables; % full table of predictors + dependent
- y = mdl.Variables{:, mdl.ResponseName}; % dependent variable
- predictors = mdl.PredictorNames; % list of predictor names
- predictor_plot_names = {'Speed score','Directionality','Directional stability','Tilt stability','Tilt directionality','Terrain score'};
- coefTable = mdl.Coefficients; % GLM coefficient table
- figure(fig);
- tiledlayout(4,3)
- nPred = numel(predictors);
- for i = 1:nPred
- % Current predictor
- x = X.(predictors{i});
- % Regress y on all other predictors (excluding current one)
- otherPreds = setdiff(predictors, predictors{i});
- tbl_y = X(:, otherPreds);
- lm_y = fitlm(tbl_y, y);
- x_resid = lm_y.Residuals.Raw;
- % Regress current predictor on all others
- lm_x = fitlm(tbl_y, x);
- y_resid = lm_x.Residuals.Raw;
- % Plot residuals
- nexttile
- % subplot(ceil(sqrt(nPred)), ceil(sqrt(nPred)), i);
- alpha = 0.5;
- scatter(x_resid, y_resid, 20,'k','filled','MarkerFaceAlpha',alpha,'MarkerEdgeColor','none');
- ylabel([predictor_plot_names{i} ' (residuals)'],'Interpreter',"none");
- if i>3
- xlabel(['Repetition score (residuals)'],'Interpreter',"none");
- else
- xlabel(' ')
- end
- % title(['Partial regression: ' predictors{i}]);
- hold on;
- % Fit line to residuals
- ax = gca;
- ax.XLim = [-0.5 1];
- ax.YLim(2) = ax.YLim(2)*1.15;
- p = polyfit(x_resid, y_resid, 1);
- x_fit = linspace(ax.XLim(1), ax.XLim(2), 100);
- y_fit = polyval(p, x_fit);
- plot(x_fit, y_fit, 'r-', 'LineWidth', 2);
- % Extract GLM results for this predictor
- row = coefTable(strcmp(coefTable.Row, predictors{i}), :);
- beta = row.Estimate;
- se = row.SE;
- tval = row.tStat;
- pval = row.pValue;
- if pval < .05
- % Scientific notation: mantissa × 10^{exponent}
- [mantissa, exponent] = sprintf('%.2e', pval); % format in scientific
- parts = regexp(sprintf('%.2e', pval), '([-+]?\d*\.\d+)e([-+]?\d+)', 'tokens');
- mantissa = parts{1}{1};
- exponent = str2double(parts{1}{2});
- pStr = sprintf('\\it{p} = %s \\times 10^{%d}', mantissa, exponent);
- else
- % Normal decimal, strip leading zero
- pStr = sprintf('\\it{p} = %.3f', pval);
- pStr = regexprep(pStr, '0\.', '.');
- end
- % Annotation string
- txt = sprintf('\\beta = %.3f, SE = %.3f\nt = %.2f, %s', beta, se, tval, pStr);
- % Place annotation at the very top of the plot
- text(0.5, 1, txt, 'HorizontalAlignment', 'center', 'VerticalAlignment','middle','FontSize', 7, 'Interpreter','tex','Units','normalized');
- end
- end
PIT_over_glm.m at commit d3a03d4, under MIT · at the source
Overview
- School of Psychology and Neuroscience, University of Glasgow, Glasgow, UK
- Department of Psychological and Brain Sciences, Dartmouth College, Hanover, NH, USA
Abstract
How does the brain map uneven terrain? While spatial neurons such as hippocampal place cells and entorhinal grid cells have been extensively studied in flat, horizontal environments, the natural world is hilly and irregular. To investigate how place cells represent irregular terrain, we recorded from the hippocampus of rats foraging across either flat or ridged terrain. Place cell activity reflected terrain shape, consistent with a surface-bound cognitive map rather than a volumetric one. Place fields were elongated parallel to terrain contours, which contrasted with the movement biases of the rats, and are inconsistent with a predictive coding model. Reflecting the importance of terrain information, a third of the place cells exhibited repeating fields on each ridge. A boundary vector cell model of place cell firing replicated these results. These findings demonstrate that the cognitive map is sensitive to topography, bringing our understanding of spatial cognition closer to the real world.
Reproduced under the paper's license (CC BY-NC), from the paper cited above.
Repository
Its files are read in the Code ↔ Paper reader above, with 15 matches between paragraphs and lines of code.
Neuroesc/Hillscape_analyses
d3a03d4bc00e9a3ac94af3a8406ebc992f85f09b, 25 September 2026Availability: 1 check, the latest on 27 September 2026: the link answers
- 27 September 2026: the link answers
93 files
- GIT_audit.m, MATLAB, 180 lines, 2 matches
- GIT_sim.m, MATLAB, 830 lines, 1 match
- io/
PIT_load_sdata.m , MATLAB, 161 lines - io/
get_dat_for_audit.m , MATLAB, 116 lines - io/
run_fun_for_audit.m , MATLAB, 405 lines - klustest/
GIT_klustest.m , MATLAB, 989 lines - klustest/
convert_to_cluma_cut.m , MATLAB, 47 lines - klustest/
fig_clus_hills.m , MATLAB, 265 lines - klustest/
fig_parts_hills.m , MATLAB, 592 lines - klustest/
fit_hill_frame.m , MATLAB, 360 lines - klustest/
fit_hill_frame_v2.m , MATLAB, 365 lines - klustest/
fit_maze_frame.m , MATLAB, 210 lines - klustest/
get_SPIKESV.m , MATLAB, 89 lines - klustest/
get_dacq_data.m , MATLAB, 370 lines - klustest/
get_dacq_headers.m , MATLAB, 128 lines - klustest/
get_git_path.m , MATLAB, 70 lines - klustest/
get_lfp.m , MATLAB, 97 lines - klustest/
get_lfp_volts.m , MATLAB, 134 lines - klustest/
get_manual_cell_type.m , MATLAB, 425 lines - klustest/
get_manual_cell_type_v2. , MATLAB, 521 linesm - klustest/
get_neuralynx_headers.m , MATLAB, 135 lines - klustest/
get_rawpos.m , MATLAB, 101 lines - klustest/
get_spikes.m , MATLAB, 38 lines - klustest/
get_spikes_volts.m , MATLAB, 132 lines - klustest/
hill_analysis.m , MATLAB, 451 lines - klustest/
hill_analysis_v2.m , MATLAB, 414 lines - klustest/
hill_field_analysis.m , MATLAB, 161 lines - klustest/
hill_repeat_analysis.m , MATLAB, 160 lines - klustest/
hill_repeat_analysis_v2. , MATLAB, 166 linesm - klustest/
pitch_modulation_analysi , MATLAB, 606 liness.m - klustest/
postprocess_dacq_data.m , MATLAB, 204 lines - klustest/
read_LFP3.m , MATLAB, 94 lines - klustest/
unused/ , MATLAB, 1,157 lines, 1 matchGIT_hilltest.m - klustest/
unused/ , MATLAB, 1,058 lines, 1 matchGIT_klustest3.m - plotting/
PIT_fig_1_v1.m , MATLAB, 420 lines - plotting/
PIT_fig_2_v1.m , MATLAB, 902 lines - plotting/
PIT_fig_3_v3.m , MATLAB, 842 lines - plotting/
PIT_fig_3_v4.m , MATLAB, 654 lines - plotting/
PIT_fig_5_v1.m , MATLAB, 864 lines - plotting/
PIT_fig_6_v1.m , MATLAB, 383 lines - plotting/
PIT_fig_7_v1.m , MATLAB, 905 lines - plotting/
PIT_fig_8_v1.m , MATLAB, 1,228 lines, 2 matches - plotting/
PIT_sup_1sess_v1.m , MATLAB, 904 lines, 2 matches - plotting/
PIT_sup_fig_10_v1.m , MATLAB, 127 lines - plotting/
PIT_sup_fig_11_v1.m , MATLAB, 690 lines - plotting/
PIT_sup_fig_12_v1.m , MATLAB, 175 lines - plotting/
PIT_sup_fig_13_v1.m , MATLAB, 642 lines - plotting/
PIT_sup_fig_14_v1.m , MATLAB, 449 lines - plotting/
PIT_sup_fig_15_v1.m , MATLAB, 272 lines - plotting/
PIT_sup_fig_16_v1.m , MATLAB, 126 lines - plotting/
PIT_sup_fig_1_v1.m , MATLAB, 194 lines - plotting/
PIT_sup_fig_1_v2.m , MATLAB, 288 lines - plotting/
PIT_sup_fig_1_v3.m , MATLAB, 311 lines - plotting/
PIT_sup_fig_2_v1.m , MATLAB, 394 lines - plotting/
PIT_sup_fig_3_v1.m , MATLAB, 551 lines - plotting/
PIT_sup_fig_4_v1.m , MATLAB, 263 lines - plotting/
PIT_sup_fig_5_v1.m , MATLAB, 249 lines - plotting/
PIT_sup_fig_6_v1.m , MATLAB, 339 lines - plotting/
PIT_sup_fig_7_v1.m , MATLAB, 267 lines - plotting/
PIT_sup_fig_8_v1.m , MATLAB, 715 lines - plotting/
PIT_sup_fig_9_v1.m , MATLAB, 259 lines, 1 match - tests/
GIT_field_distribution.m , MATLAB, 298 lines - tests/
PIT_fig_3_v1.m , MATLAB, 1,170 lines - tests/
PIT_fig_3_v2.m , MATLAB, 1,453 lines - tests/
PIT_fig_4_v1.m , MATLAB, 920 lines - tests/
PIT_fig_4_v2.m , MATLAB, 1,395 lines - tests/
angle_slope.m , MATLAB, 45 lines - tests/
fit_ellipse.m , MATLAB, 287 lines - tests/
maze_plots_grant.m , MATLAB, 56 lines - tests/
plot_some_trajs.m , MATLAB, 158 lines - utils/
GIT.m , MATLAB, 75 lines - utils/
GIT_rat_calib.m , MATLAB, 184 lines - utils/
PIT_3D_heading.m , MATLAB, 183 lines - utils/
PIT_behaviour.m , MATLAB, 231 lines - utils/
PIT_correlations.m , MATLAB, 762 lines - utils/
PIT_elongation.m , MATLAB, 260 lines - utils/
PIT_field_anisotropy.m , MATLAB, 363 lines - utils/
PIT_localisation.m , MATLAB, 290 lines - utils/
PIT_over_glm.m , MATLAB, 224 lines, 2 matches - utils/
PIT_pitch_tuning.m , MATLAB, 477 lines, 2 matches - utils/
PIT_plot_mazes.m , MATLAB, 270 lines - utils/
PIT_remapping.m , MATLAB, 237 lines - utils/
PIT_repetition.m , MATLAB, 396 lines - utils/
PIT_spatial_selectivity. , MATLAB, 88 linesm - utils/
PIT_stability_analysis.m , MATLAB, 304 lines - utils/
PIT_template.m , MATLAB, 80 lines - utils/
PIT_testing.m , MATLAB, 465 lines - utils/
get_map_mask.m , MATLAB, 45 lines - utils/
get_snames.m , MATLAB, 146 lines - utils/
map_hd_3d.m , MATLAB, 165 lines - utils/
pitch_tuning.m , MATLAB, 1,013 lines, 1 match - LICENSE, License, 21 lines
- README.md, Text, 319 lines
The paper's code and data availability statement is in the Data section.
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 1 repository of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 91 scripts, each with its path and the digest of its content;
- 15 matches between paragraphs of the paper and lines of the code (method lexical-v1);
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
Datasets cited
- zenodo:17634455, at Zenodo; found in “Data, code, and materials availability:”
Data, code, and materials availability
All data and code needed to evaluate and reproduce the results in the paper are present in the paper and/
Reproduced under the paper's license (CC BY-NC), from the paper cited above.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 27 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 3 authors, 7 MeSH terms, 2 funders, 100 references.
Cite
This paper
Grieves, R. M., Duvelle, É., & Taube, J. S. (2026). Hippocampal place cells map terrain geometry independently of behavior. Science advances, 12(23), eadz9893. https://
BibTeX
@article{grieves2026hipp
author = {Grieves, Roddy M. and Duvelle, Éléonore and Taube, Jeffrey S.},
title = {{Hippocampal place cells map terrain geometry independently of behavior}},
journal = {Science advances},
year = {2026},
month = jun,
volume = {12},
number = {23},
pages = {eadz9893},
publisher = {American Association for the Advancement of Science},
issn = {2375-2548},
doi = {10.1126/
url = {https://
pmid = {42234755},
pmcid = {PMC13232613}
}
RIS
TY - JOUR
AU - Grieves, Roddy M.
AU - Duvelle, Éléonore
AU - Taube, Jeffrey S.
TI - Hippocampal place cells map terrain geometry independently of behavior
T2 - Science advances
J2 - Sci Adv
PY - 2026
DA - 2026/
VL - 12
IS - 23
SP - eadz9893
SN - 2375-2548
PB - American Association for the Advancement of Science
DO - 10.1126/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1126/
"type": "article-journal",
"title": "Hippocampal place cells map terrain geometry independently of behavior",
"container-title": "Science advances",
"author": [
{
"family": "Grieves",
"given": "Roddy M."
},
{
"family": "Duvelle",
"given": "Éléonore"
},
{
"family": "Taube",
"given": "Jeffrey S."
}
],
"container-title-short":
"volume": "12",
"issue": "23",
"page": "eadz9893",
"DOI": "10.1126/
"PMID": "42234755",
"PMCID": "PMC13232613",
"ISSN": "2375-2548",
"publisher": "American Association for the Advancement of Science",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
6,
3
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.1371/journal.pcbi.1011763 [code]
- Estimating neuronal firing density: A quantitative analysis of firing rate map algorithms.Journal: PLoS computational biologyIn common: CircStat, Image Processing Toolbox, Statistics and Machine Learning Toolbox, 17 references, author Roddy M. Grieves
- [2] doi:10.7554/elife.85599 [code]
- Leveraging place field repetition to understand positional versus nonpositional inputs to hippocampal field CA1.Journal: eLifeIn common: rat, 17 references
- [3] doi:10.1038/s41467-024-54935-2 [code]
- Vector coding and place coding in hippocampus share a common directional signal.Journal: Nature communicationsIn common: CircStat, Signal Processing Toolbox, Image Processing Toolbox, rat, 15 references
- [4] doi:10.1111/ejn.70365 [code]
- Tolman's Sunburst Maze 80 Years on: A Meta-Analysis Reveals Poor Replicability and Little Evidence for Shortcutting.Journal: The European journal of neuroscienceIn common: Statistics and Machine Learning Toolbox, rat, 7 references, 2 authors
- [5] doi:10.1038/s41598-024-66755-x [code]
- Modeling hippocampal spatial cells in rodents navigating in 3D environments.Journal: Scientific reportsIn common: rat, 13 references
- [6] doi:10.3389/fncom.2022.1039822 [code]
- Adapting hippocampus multi-scale place field distributions in cluttered environments optimizes spatial navigation and learning.Journal: Frontiers in computational neuroscienceIn common: 15 references
- [7] doi:10.1038/s41467-024-48374-2 [code]
- Primacy of vision shapes behavioral strategies and neural substrates of spatial navigation in marmoset hippocampus.Journal: Nature communicationsIn common: CircStat, Curve Fitting Toolbox, Signal Processing Toolbox, 2 other tools, 9 references
- [8] doi:10.1038/s41586-024-07139-z [code]
- Subicular neurons encode concave and convex geometries.Journal: NatureIn common: Signal Processing Toolbox, Image Processing Toolbox, Statistics and Machine Learning Toolbox, 11 references
- [9] doi:10.1038/s41467-024-45098-1 [code]
- Environment geometry alters subiculum boundary vector cell receptive fields in adulthood and early development.Journal: Nature communicationsIn common: CircStat, Image Processing Toolbox, Statistics and Machine Learning Toolbox, rat, 10 references
- [10] doi:10.7554/elife.96627 [code]
- Spatial periodicity in grid cell firing is explained by a neural sequence code of 2-D trajectories.Journal: eLifeIn common: CircStat, Image Processing Toolbox, Statistics and Machine Learning Toolbox, extracellular electrophysiology (units, LFP), 9 references
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, 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 OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: 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, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 1 repository of the authors' code, each at its verified commit and with its license, 91 scripts, and 15 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:98324274fb59ae08…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1126/sciadv.adz9893)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1126/sciadv.adz9893.svg
:target: https://openscicode.org/badge/doi/10.1126/sciadv.adz9893
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1126/sciadv.adz9893"><img src="https://openscicode.org/badge/doi/10.1126/sciadv.adz9893.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".
If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, 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).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
