Abaqus ODB Read-Only Inspection
Overview
Extract bounded, reproducible evidence from a result database. Every reported
value carries database identity, step, frame or time, region, variable,
component or invariant, coordinate interpretation, and units.
When to use
Use for result inspection, claim audits, monitoring extraction, or diagnosing a
missing field/history output. Do not use it to repair the source model.
Inputs
- Approved ODB and expected job identity
- Step, frame or time, and named region
- Field or history variable and component/invariant
- Position, coordinate system, units, and aggregation rule
- Export destination and requested evidence format
Outputs
Return an inventory, extraction table, provenance header, missing-data findings,
and a bounded export plan. Open with readOnly=True and close deterministically.
Workflow
- Confirm file identity, size, timestamp, and expected job relationship.
- Inventory steps, frames, instances, sets, surfaces, and available outputs.
- Resolve the requested region and variable before reading values.
- Apply explicit component, invariant, position, and aggregation rules.
- Record provenance and close the database in a guaranteed cleanup path.
Safety gates
- Always open the database read-only.
- Never infer units from variable names alone.
- Never compare values from different frames, positions, or coordinate systems silently.
- Never overwrite the source database or export into its source directory by default.
Example prompts
Read the last converged frame and extract vertical displacement for a named
monitoring set. Report time, coordinates, units, extrema rule, and provenance.
Common failures
- Selecting the last frame without checking whether it is the intended state.
- Mixing nodal, integration-point, and extrapolated values.
- Reporting an invariant when a signed component was requested.
- Leaving the database open after an exception.
Acceptance checklist
1---2name: abaqus-odb3description: Use when reading an Abaqus ODB to inspect steps, frames, field outputs, history outputs, regions, coordinates, units, extrema, paths, or bounded result exports without modification.4---56# Abaqus ODB Read-Only Inspection78## Overview910Extract bounded, reproducible evidence from a result database. Every reported11value carries database identity, step, frame or time, region, variable,12component or invariant, coordinate interpretation, and units.1314## When to use1516Use for result inspection, claim audits, monitoring extraction, or diagnosing a17missing field/history output. Do not use it to repair the source model.1819## Inputs2021- Approved ODB and expected job identity22- Step, frame or time, and named region23- Field or history variable and component/invariant24- Position, coordinate system, units, and aggregation rule25- Export destination and requested evidence format2627## Outputs2829Return an inventory, extraction table, provenance header, missing-data findings,30and a bounded export plan. Open with `readOnly=True` and close deterministically.3132## Workflow33341. Confirm file identity, size, timestamp, and expected job relationship.352. Inventory steps, frames, instances, sets, surfaces, and available outputs.363. Resolve the requested region and variable before reading values.374. Apply explicit component, invariant, position, and aggregation rules.385. Record provenance and close the database in a guaranteed cleanup path.3940## Safety gates4142- Always open the database read-only.43- Never infer units from variable names alone.44- Never compare values from different frames, positions, or coordinate systems silently.45- Never overwrite the source database or export into its source directory by default.4647## Example prompts4849> Read the last converged frame and extract vertical displacement for a named50> monitoring set. Report time, coordinates, units, extrema rule, and provenance.5152## Common failures5354- Selecting the last frame without checking whether it is the intended state.55- Mixing nodal, integration-point, and extrapolated values.56- Reporting an invariant when a signed component was requested.57- Leaving the database open after an exception.5859## Acceptance checklist6061- [ ] ODB identity and job relationship are confirmed.62- [ ] Step, frame/time, region, variable, and position are explicit.63- [ ] Component/invariant, coordinates, units, and aggregation are recorded.64- [ ] Missing outputs are reported rather than fabricated.65- [ ] Database closure and export boundaries are verified.66
1348109517