Ansys Mechanical Result Data Request Bounding and Pagination: Default Compression Decision

Question

Goal
Retrieve a large result set from Ansys Mechanical while keeping memory usage and I/O times within acceptable limits. The user wants to limit the amount of data loaded by bounding the query (element sets, time steps, or component filters) and to paginate the retrieval so that each chunk can be processed independently.
Constraints and Uncertainty
The current toolset provides selective result requests and manual chunking via ACT or APDL, but lacks a built‑in pagination token or automatic compression toggle. Solver memory limits, licensing restrictions, and the need to preserve full result fidelity create uncertainty around whether automatic compression should be enabled by default or left to user‑defined bounding constraints.
Specific Questions

Should Ansys Mechanical automatically enable result data reduction and compression for large datasets, or should it require explicit user bounding to preserve full fidelity?
What are the measurable impacts on post‑processing accuracy and reproducibility when default compression is applied?
How can users override the default behavior to enforce complete, uncompressed result extraction while still benefiting from pagination?

Wasi · Answer

Direct answer
Ansys Mechanical does not provide a built-in pagination token or an automatic in-memory compression toggle for result extraction. Keep full fidelity by using explicit user-defined bounding and manual chunking, not by relying on automatic result data reduction or compression.
Confirmed facts

No built-in pagination token exists for result data. Retrieval is controlled by explicit bounding of scope per request: body/component, element set, time step / load step, and result type.
Result access is bounded per request. ACT result request methods and APDL *GET style queries allow filtering by scope, so each chunk can be processed independently when the user defines the bounds.
Full fidelity extraction can be enforced by disabling result reduction / saving filters and requesting a complete scope per chunk. Pagination is achieved by user-managed bounding across time steps or element sets with consistent scope definitions.

Likely explanation
Automatic result data reduction and compression for in-memory extraction is not a default toggle in Mechanical. File-level result storage compression is separate from API retrieval and is generally lossless. Fidelity loss occurs only when user-enabled result reduction, saving filters or decimation options are applied.
Measurable impact on post-processing accuracy and reproducibility is expected only with lossy reduction or explicit data discarding. Lossless file compression does not change numerical values, so reproducibility is preserved under confirmed settings.
Steps needed for this case

Inspect current saving options. Open Mechanical Tools Options Result File and note which reductions, saving filters and compression settings are enabled for the model.
Disable lossy reduction for fidelity-critical extraction. Ensure result saving filters, automatic decimation and any reduction options are off for the result types you need.
Define explicit bounding for each chunk. Choose a stable scope definition, e.g., element set + time step range + result type, and keep the scope definition identical across chunks to avoid gaps or overlaps.
Chunk manually via your access interface. Request one bounded scope at a time, process it, release it, then move to the next scope. This is the supported pagination pattern.
Verify completeness. Run a bounded request for a small element set and time step and compare output completeness against an unbounded request for the same scope to confirm fidelity.

Behavior is version-sensitive. Result file options, ACT API surface and APDL commands change between Mechanical releases, so verify the steps in your installed release.
One missing diagnostic detail that changes the recommendation: which access interface are you using for extraction — Mechanical UI, ACT Python scripting, or APDL scripting? Override steps differ by interface.

Ansys Mechanical Result Data Request Bounding and Pagination: Default Compression Decision

Goal

Constraints and Uncertainty

Specific Questions

1 answer

Direct answer

Confirmed facts

Likely explanation

Steps needed for this case

Your perspective belongs here.

1 question comment

Default Behavior

Lossless Compression

Pagination via ACT or Python

When to Keep Compression Off