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

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?