direct numerical simulation
Enable an agent to recognise a direct numerical simulation, assess whether its claimed physical scales are resolved, and judge which analyses its results support.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 14 findings · 29 questions
DNS claim and physical scope Establishes what is being simulated directly and which approximations remain.
Governing flow problem
Identifies the equations, regime and conditions defining the calculation.
Equations and regime
Record the instantaneous equations, material assumptions, forcing and nondimensional parameters with their conventions.
- Which governing equations and constitutive assumptions define the flow, and which physical processes are omitted? definition
- How are Reynolds number and any additional controlling parameters defined and measured for this case? measurement
Direct-resolution boundary
Separates resolved turbulent motion from explicitly or implicitly represented unresolved processes.
Closure and label
Record the basis of the DNS designation, including turbulence closures, filters and any narrower scope of direct resolution.
- Which turbulent motions are claimed to be resolved, and does any closure or numerical mechanism stand in for unresolved turbulence? boundary
- Which publication or run documentation supports the DNS designation and states its limitations? provenance
- For coupled scalar, reacting or multiphase physics, which processes are resolved directly and which remain modelled? boundary
Scale and domain resolution Captures evidence that the calculation represents the relevant small scales, large structures and time evolution.
Small-scale spatial resolution
Assesses local and directional resolution against appropriate physical scales.
Local resolution evidence
Record mesh or spectral resolution, its spatial variation and the diagnostics used to justify adequacy.
- Which small-scale criteria apply to this flow, and how do local grid spacings or spectral cutoffs compare with them? measurement
- Where do walls, intermittency or coupled transport introduce resolution demands that a domain-average criterion could conceal? boundary
- Which refinement comparisons or spectral diagnostics support resolution of the observables being reported? provenance
Time and domain coverage
Checks temporal accuracy and whether domain boundaries constrain relevant flow structures.
Temporal and domain adequacy
Record time-step evidence, domain dimensions and boundary sensitivity separately from solver stability.
- What time-step refinement evidence demonstrates accuracy for the fastest relevant dynamics and target observables? measurement
- How do domain-size checks, correlations or boundary-sensitivity studies establish that important structures are accommodated? measurement
- Which time-step, domain or boundary changes should be tested before accepting the DNS claim? action
Numerical fidelity and run evidence Connects discretisation choices and executed-run records to the accuracy of the flow solution.
Discretisation and error control
Examines numerical mechanisms that can distort resolved turbulence.
Numerical error budget
Record spatial and temporal schemes, solver tolerances, applicable aliasing control and numerical contributions to flow budgets.
- Which discretisations, tolerances, filters and aliasing controls were used, and how could they affect small-scale motion? definition
- What applicable conservation, constraint or energy-budget checks quantify residual numerical error? measurement
- How is artificial dissipation distinguished from the physical dissipation represented by the governing equations? measurement
Executed-run traceability
Links reported results to the actual solver configuration, initial state and execution history.
Reproducible flow realisation
Record the software version, inputs, initialisation, forcing, restarts and verification evidence needed to reconstruct the calculation.
- Which versioned code, configuration, initial conditions and forcing records identify the executed run? provenance
- What verification cases or convergence results support the solver for the equations and boundary conditions used here? provenance
- What must be preserved to reproduce the setup and statistically comparable results despite chaotic trajectory divergence? action
Statistical evidence and use Determines what the resolved flow record can support as a statistical or physical conclusion.
Sampling and observables
Relates transient handling, averaging and stored outputs to each reported quantity.
Observable-specific sampling
Record how statistics are formed and whether their temporal, spatial or ensemble support is adequate.
- Which transient intervals are excluded, and what supports stationarity or the chosen treatment of a nonstationary flow? measurement
- How are correlations, averaging assumptions and effective sample counts reflected in uncertainty for each target statistic? measurement
- Does the saved field resolution and output cadence support the proposed spectra, gradients or event analysis? action
Comparison and transfer
Constrains validation, model assessment and generalisation to cases supported by the simulation.
Supported inference
Record reference comparisons, mismatched conditions and limits on treating DNS outputs as evidence for other regimes.
- Which experimental or reference datasets provide relevant comparisons, and how closely do their parameters and boundary conditions match? provenance
- Which conclusions are confined to this Reynolds number, geometry, forcing and physical formulation? boundary
- What additional checks or simulations are required before using these outputs to assess a closure model or generalise a physical claim? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these typical measurements hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of direct numerical simulation this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- thing
- Plane
- ACT
- Domain
- ACT.ACT
What it is Filled
Direct numerical simulation (DNS) is a computational approach to turbulent flow that solves the governing fluid equations without a turbulence closure model, resolving the dynamically relevant spatial and temporal scales down to those at which molecular dissipation acts.
In scope
- The physical equations, flow regime and scales covered by a DNS claim
- Distinction between DNS, large-eddy simulation and Reynolds-averaged simulation
- Spatial and temporal resolution of dynamically relevant flow scales
- Numerical accuracy, execution integrity and reproducibility
- Statistical adequacy and permitted interpretation of simulation outputs
Out of scope
- General computational fluid dynamics methods independent of a DNS claim
- Development and calibration of turbulence closure models
- Computing hardware and cluster administration
- Experimental measurement apparatus and procedures
- The complete theory of turbulence
- Direct numerical solution of arbitrary equations where no DNS-specific resolution claim is made
Why it exists Filled
Enable an agent to recognise a direct numerical simulation, assess whether its claimed physical scales are resolved, and judge which analyses its results support.
Distinguishing features Filled
- The calculation evolves instantaneous flow fields rather than solving only for turbulence-averaged quantities.
- A turbulent-flow DNS claim requires evidence that the relevant turbulent spatial and temporal scales are resolved without a turbulence closure model.
- Omitting an explicit subgrid model is insufficient: a calculation that relies on numerical dissipation to represent unresolved turbulence does not thereby establish DNS.
- Resolution must be justified for the particular flow, location and observable; a large mesh or successful solver completion alone does not establish DNS.
- DNS remains a numerical solution of selected governing equations and physical assumptions; it does not imply atomistic resolution or the absence of every constitutive model.
What robots and AI may and may not do Filled
Must not
- Present underresolved simulations as direct numerical simulation.
- Extrapolate results to conditions the simulation did not cover without warning.
- Consume shared computing resources beyond the allocation granted.
- Fabricate or alter simulation data.
Only with a human decision
- Using simulation results for safety-critical engineering decisions.
May
- Run or analyze direct numerical simulations on computing resources the agent is authorized to use.
- Report simulation parameters, resolution and validation alongside results.
Moral aspects Filled
- Simulation results inform designs that affect safety.
- Large simulations use significant energy and shared resources.
Who is affected
- Engineers and designers
- Research users
- Users of shared computing
Owners Filled
Steward
Nobody owns the method; the research group answers for each simulation.
Links to other meta-models Filled
parent
- Q2004848 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.direct-numerical-simulation
- Wikidata: Q1227572 (https://www.wikidata.org/wiki/Q1227572)
Direct properties not applicable Not applicable
- DNS claim status: claimed; supported within stated scope; contested; insufficiently evidenced
- Physical formulation: Governing equations, compressibility treatment, constitutive assumptions and coupled transport equations
- Reynolds number and convention: Dimensionless, with the velocity, length and viscosity definitions recorded
- Spatial resolution relative to physical scales: Local mesh-spacing-to-scale ratios or spectral cutoff-to-scale products; wall units where applicable
- Temporal resolution: Time step in seconds or declared nondimensional units, with ratios to relevant physical timescales
- Domain extent and boundary conditions: Domain dimensions relative to flow scales, linked to each imposed boundary condition
- Turbulence closure and numerical dissipation: Declared turbulence closures, filters, stabilisation and dissipation mechanisms
- Sampling support: Transient exclusion, sampling duration, output cadence, independent realisations and observable-specific uncertainty
Plane ACT: no invented physical properties.
Recognition optional Filled
- Results appear as detailed visualizations of turbulent eddies and vortices across many scales.
Capabilities and actions required Filled
- Assess a DNS claim against its equations, closure choices and resolution evidence.
- Identify locations, scales or observables needing mesh, time-step or domain refinement.
- Design convergence checks and comparisons with applicable reference cases.
- Extract flow structures, spectra, budgets and statistics within the output's sampling limits.
- Determine whether a dataset supports turbulence-model assessment or a proposed physical inference.
- Specify a reproducible continuation or rerun with targeted changes.
Hazards and failure modes required Filled
- Insufficient resolution produces misleading results.
- Overconfidence in simulations without experimental validation.
Standards and interfaces required Filled
- ASME V&V 20, issued by the American Society of Mechanical Engineers, provides a verification and validation framework for computational fluid dynamics and heat transfer that can be applied to direct numerical simulation.
Context of use required Filled
- Direct numerical simulation is used in fluid dynamics research to study turbulent flow while resolving its dynamically relevant scales.
- Its detailed flow fields support analysis of turbulence mechanisms and evaluation of simplified turbulence models.
- Computational cost generally restricts its use to flow conditions and domains that available computing resources can resolve.
Sources Filled
- Wikidata item Q1227572: direct numerical simulation - identity and sense of the item
- Wikipedia: Direct numerical simulation - general description of the item
Open questions
- Does the registry intend the conventional turbulent-flow meaning of direct numerical simulation, or also established uses in other disciplines?
- Which flow-specific resolution criteria and acceptance evidence should the model require for wall-bounded, compressible, reacting and multiphase cases?
- How should borderline calculations with appreciable filtering or stabilisation be classified when the authors call them DNS?
- What minimum evidence should distinguish a supported DNS claim from a designation whose underlying run data are unavailable?
- Which observable-specific uncertainty and sampling requirements should govern reuse of DNS datasets for model assessment?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q1227572/spec.json