Three AMEOpen limitations on Amesim 2511, each exercised

All three were found on 2026-09-03 on Simcenter Amesim 2511 while building the AMEOpen tools in amesim-mcp. Two are honest reds, one is a green that was worth proving because it sits next to a red. Each is marked with the models it was tried on. Re-test all three on 2604, the release the Siemens bundle targets.

1. SimulationResult cannot load values from a re-opened model's saved set

EXERCISED 2026-09-03, models oven_heatup, esp_thermal, 6dof_flight. Red.

amesim_result_sets opens a saved model and lists its result sets and the variable paths inside one of them. That works. Asking SimulationResult for the values behind those paths fails with Failed to load final values on every variant tried: plain open, expanded open, after prepareSimulationData, after compile. The only load that succeeded was on the result object the AMEOpen SimulationRunner returned inside the same session that produced it.

What the tools do about it: amesim_result_values and amesim_plot return the failure as known_limitation and point to the ame_apy path. On 2511, read existing results like this:

1. amesim_result_sets(model) to learn the paths without a run.
2. amesim_open plus amesim_build plus amesim_get_results(paths) through ame_apy.

Do not report this as "no results". The data is on disk; the reader is the part that fails.

2. addPostProcessedVariable does not persist through save

EXERCISED 2026-09-03. Red.

Adding an expression variable with ProcessingData.addPostProcessedVariable and then saving the model produces a file that shows nothing new on re-open. The amesim_post_processing tool verifies every write by re-opening the file and reports persisted: false when this happens, rather than echoing the in-memory list back as success.

3. Global parameters do persist

EXERCISED 2026-09-03. Green.

Create, set and delete of global parameters through AMEOpen, followed by save, survive a re-open: the amesim_global_parameters tool re-opens the file after each write and reads the value back. This is the control that shows the save path itself works, which is what makes limitation 2 a statement about post-processing rather than about saving.

Why the greens are listed with the reds

A write that returns without error is not evidence it landed. Each of these three was settled by re-opening the file and reading the artifact, not by reading the return value. Carry that habit into any new AMEOpen write.