OSCR

Block oscr:b:V5E99ADZASEPK-U

A block of code linked to a paper, with an identifier OSCR gives it for good: it is never reused nor deleted. What a block identifier is · this block in JSON

Identifier
oscr:b:V5E99ADZASEPK-U
Status
Current: the registry links these lines to the paper today.
Paper
doi:10.1073/pnas.2505434122 · its page here
Code
github.com/pangyuj/explosive-sync-proximity, computational_model/SL_FindingCriticalPoint.m, lines 1 to 106
Commit read
f6f719d13a065f8a4251146db5e33b3ee152e456
SWHID
swh:1:cnt:a1da2edfba80e1e27462f1d21a59f4ec53b89ed1;origin=https://github.com/pangyuj/explosive-sync-proximity;anchor=swh:1:rev:f6f719d13a065f8a4251146db5e33b3ee152e456;path=/computational_model/SL_FindingCriticalPoint.m;lines=1-106 (the Software Heritage identifier of the file as its authors published it, before any email address is hidden for display; it opens in Software Heritage's archive once the repository is archived there)
In the paper
paragraph 13 (Results › The Proximity of a Complex Network to ES Determines Rapid or Prolonged); paragraph 10 (Results › The Proximity of a Complex Network to ES Determines Rapid or Prolonged)
Linked by
the registry's matching program (lexical-v1), which can be wrong
Identifier given
2026-11-14

Open these lines beside the paper

Cite this block

Copy this text: the identifier and its page first, then the code, the paper and the SWHID.

Code block oscr:b:V5E99ADZASEPK-U (https://openscicode.org/b/oscr:b:V5E99ADZASEPK-U)
computational_model/SL_FindingCriticalPoint.m, lines 1 to 106, in github.com/pangyuj/explosive-sync-proximity (https://github.com/pangyuj/explosive-sync-proximity), commit f6f719d13a065f8a4251146db5e33b3ee152e456.
Paper: https://doi.org/10.1073/pnas.2505434122
SWHID: swh:1:cnt:a1da2edfba80e1e27462f1d21a59f4ec53b89ed1;origin=https://github.com/pangyuj/explosive-sync-proximity;anchor=swh:1:rev:f6f719d13a065f8a4251146db5e33b3ee152e456;path=/computational_model/SL_FindingCriticalPoint.m;lines=1-106