Skip to main content
v2026.11,772 entries · CC-BY 4.0
Dictionary termTrack CStablev2026.2

Computational environment

The full software and hardware context in which an analysis runs, including operating system, language runtime, library versions, configuration, environment variables, and hardware-specific dependencies (e.g., GPU drivers).

ByCASRAI Editorial Board
· Last updated 22 Aug 2026
Share this

Ask CASRAI · included with Regulatory Radar

Ask about Computational environment

Ask CASRAI answers research-administration questions and cites the passages behind every claim — and says so when the corpus does not cover something, instead of guessing. It comes with a Regulatory Radar subscription at $29 a month, alongside the daily digest of regulatory changes and the dashboard of what changed.

150 questions a day, on this site, over the API, or inside your own tools through the CASRAI MCP server.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

Examples

Worked examples

  • Is an instance

    A renv.lock file pinning every R package version used by an analysis.

  • Is an instance

    A Dockerfile producing a reproducible Ubuntu 22.04 image with Python 3.11 and pinned dependencies.

Counter-examples

Looks similar, but isn't

  • Not an instance

    A 'requirements.txt' with unpinned versions (>= or ranges).

  • Not an instance

    A README listing language versions without pinning libraries.

Editorial commentary

A computational environment is the full software and hardware context in which an analysis actually runs: operating system, language runtime and its version, every library and its version, configuration and environment variables, and hardware-specific dependencies such as GPU drivers and CUDA versions. It is the broadest of this site’s reproducibility-mechanism terms — the thing that needs capturing, as distinct from the specific tool used to capture it.

How this relates to containers and workflow tools

A container image is one mechanism for capturing and distributing a computational environment as a single portable artefact. A workflow tool such as Nextflow or Snakemake often specifies a container image per pipeline step, so that each step’s environment is pinned independently rather than relying on one shared, drift-prone environment for the whole analysis. Package and environment managers (conda, renv, poetry) are a lighter-weight alternative that pins library versions without full OS-level isolation — adequate for many analyses, but not equivalent to a container for capturing OS-level or hardware-driver dependencies.

Why “it worked on my machine” is a documentation failure, not bad luck

An analysis that only reproduces on its original author’s own machine has, by definition, an undocumented computational environment — the fix is recording the environment as explicitly as the code and data, not simply retrying.

References

Also known as

execution environment · research environment

Machine-readable encodings

Use in your systems

JATS XML <role> element
xml
<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Computational environment"
      vocab-term-identifier="https://casrai.org/dictionary/term/computational-environment" />
Schema.org DefinedTerm (JSON-LD)
json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/computational-environment",
  "name": "Computational environment",
  "identifier": "https://casrai.org/dictionary/term/computational-environment",
  "description": "The full software and hardware context in which an analysis runs, including operating system, language runtime, library versions, configuration, environment variables, and hardware-specific dependencies (e.g., GPU drivers).",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/reproducibility#set",
  "url": "https://casrai.org/dictionary/term/computational-environment",
  "sameAs": [
    "execution environment",
    "research environment"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "author": {
    "@id": "https://casrai.org/#editorial-team"
  },
  "datePublished": "2026-05-21T02:22:49",
  "dateModified": "2026-08-22T15:44:08",
  "inLanguage": "en-GB",
  "isAccessibleForFree": true
}

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →

Regulatory Radar

Stop finding out after the fact

$29/month, cancel anytime. Daily digest updates from our analysis, a dashboard holding the same items, and a cited assistant for everything they raise.

  • Federal Register, Federal Register+, Grants.gov, Regulations.gov, NSF News, UKRI, plus CASRAI’s own published content.
  • 72,264 indexed passages, and every answer cites the ones it drew on.