Abaqus Export
Overview
Treat an export as a controlled transformation with an explicit source,
purpose, format, units, and destination. A successful export is an artifact
record, not automatic engineering evidence.
When to use
Use when exporting geometry, mesh, input data, images, or selected result data
from an approved Abaqus model or ODB. Use a separate review before exporting
anything that contains private project or manuscript material.
Inputs
- Approved source model or ODB and read/write status
- Object, step, frame, region, variable, or geometry scope
- Target format, units, coordinate system, and evidence purpose
- Destination directory, overwrite policy, and expected consumers
Outputs
Return the exported artifact path, source scope, format and unit metadata,
selection rules, validation result, and a SHA-256 or equivalent manifest entry.
State whether the artifact is scoping material, a reproducibility package, or
an engineering-review input.
Workflow
- Confirm the source, object scope, format, destination, and authorization.
- Inspect result exports read-only and record step, frame, variable, region,
position, aggregation, and coordinate information.
- Use a no-write preview for geometry, mesh, or input-deck exports.
- Refuse silent overwrite; create a task-specific destination when approved.
- Verify existence, size, parseability, metadata, and digest after export.
Safety gates
- Never overwrite a source model, ODB, existing export, or formal asset.
- Do not export credentials, private data, or proprietary geometry.
- Do not call a guessed or partial export a formal engineering result.
- Do not bypass dry-run, read-only inspection, or human authorization.
Example prompts
Prepare a read-only export manifest for the displacement field at the final
frame on a named synthetic region. List units, coordinates, selection rules,
destination, and validation checks; do not modify the ODB.
Common failures
- Omitting the frame or region and exporting an ambiguous result.
- Mixing local and global coordinates or silently changing units.
- Writing an export beside the source and overwriting an earlier artifact.
- Treating an image or input deck as proof of physical correctness.
Acceptance checklist
1---2name: abaqus-export3description: Use when an approved Abaqus geometry, mesh, input-deck, image, or read-only result export needs a traceable destination and format.4---56# Abaqus Export78## Overview910Treat an export as a controlled transformation with an explicit source,11purpose, format, units, and destination. A successful export is an artifact12record, not automatic engineering evidence.1314## When to use1516Use when exporting geometry, mesh, input data, images, or selected result data17from an approved Abaqus model or ODB. Use a separate review before exporting18anything that contains private project or manuscript material.1920## Inputs2122- Approved source model or ODB and read/write status23- Object, step, frame, region, variable, or geometry scope24- Target format, units, coordinate system, and evidence purpose25- Destination directory, overwrite policy, and expected consumers2627## Outputs2829Return the exported artifact path, source scope, format and unit metadata,30selection rules, validation result, and a SHA-256 or equivalent manifest entry.31State whether the artifact is scoping material, a reproducibility package, or32an engineering-review input.3334## Workflow35361. Confirm the source, object scope, format, destination, and authorization.372. Inspect result exports read-only and record step, frame, variable, region,38 position, aggregation, and coordinate information.393. Use a no-write preview for geometry, mesh, or input-deck exports.404. Refuse silent overwrite; create a task-specific destination when approved.415. Verify existence, size, parseability, metadata, and digest after export.4243## Safety gates4445- Never overwrite a source model, ODB, existing export, or formal asset.46- Do not export credentials, private data, or proprietary geometry.47- Do not call a guessed or partial export a formal engineering result.48- Do not bypass dry-run, read-only inspection, or human authorization.4950## Example prompts5152> Prepare a read-only export manifest for the displacement field at the final53> frame on a named synthetic region. List units, coordinates, selection rules,54> destination, and validation checks; do not modify the ODB.5556## Common failures5758- Omitting the frame or region and exporting an ambiguous result.59- Mixing local and global coordinates or silently changing units.60- Writing an export beside the source and overwriting an earlier artifact.61- Treating an image or input deck as proof of physical correctness.6263## Acceptance checklist6465- [ ] Source, scope, format, units, coordinates, and destination are explicit.66- [ ] Read-only or no-write behavior was preserved where required.67- [ ] Overwrite and privacy checks passed.68- [ ] Artifact is parseable and its digest is recorded.69- [ ] Evidence status and remaining engineering review are stated.
1348109517