Dynamic code inspection

Tier 2 · Executable - Silver recommended

A reproducer can explore how the code behaves by running it with small modifications, inspecting intermediate results, or applying code-analysis tools.

Rating

Met

The reproducer can run the code in parts (per script, chunk or function), inspect intermediate results, run it with small modifications (e.g. other parameters or a subsample), and apply code-analysis tools (debuggers, linters, profilers), e.g. because the code is modular and saves intermediate outputs, or runs in an interactive environment such as a notebook or Binder.

Based on: #37 only.

Partially met

The code can be modified and re-run, but only as a whole (monolithic script, no intermediate outputs saved), so inspecting its behavior requires substantial edits.

Based on: #37 only.

Not met

The code cannot be executed or modified by the reproducer (e.g. only compiled binaries or output logs are shared, or the data cannot be accessed), so its behavior can only be checked statically.

Based on: #37 only.

Not applicable

Never.

Prerequisites

Check order: 2

Builds on

Code deposit (1 source)
Data deposit (1 source)

Prerequisite for

No criterion builds on this one.

In the corpus

Sources	Injunctive	Descriptive	Tacit	Automatable	Manual check	Automation unclear	LLM sources
1	100%	0%	0%	0%	0%	100%	0

Text evidence (1 quote)

Show quotes

#37 The four possibilities of reproducible scientific computations · injunctive

“the possibility to explore the behavior of the code, by inspecting intermediate results, by running the code with small modifications, or by subjecting it to code analysis tools”

Note: This sentence implies the ability to execute and manipulate that code to observe its behavior. This is different from static code analysis (“codes consistent with claims”)