ty-design-opt-exp-gui-modeling

DesignOptExpGui Model Experiments

Rules

1. Ensure a Sysplorer session before scripts that touch Sysplorer.
2. Never call ClearAll or ChangeDirectory; unload a model with model_manager(action="unload") when cleanup is needed.
3. Treat this as an independent toolbox module. In run_sysplorer_api, import it explicitly:

import mworks.sysplorer.DesignOptExpGui as exp

1. Use the installed DesignOptExpGui.py signature as authoritative. The supplied examples import both DesignOptExp and DesignOptExpGUI; normalize generated model-experiment scripts to DesignOptExpGui.
2. Do not query this toolbox through the main ModelingPy get_api_document. For live help, use explicit import plus ListFunctions() or help().
3. If the user's goal is batch simulation, prefer DesignOptExp.InitialBatchSimulate(...) and DesignOptExp.BatchSimulate(...); use this GUI module's compatibility batch interfaces only when a model-experiment workflow specifically requires them.
4. For model-experiment sampling or design data, prefer methods exposed by DesignOptExpGui when available.
5. If the requested sampling or design method is not exposed by DesignOptExpGui, generate compatible samples with an equivalent external algorithm, then treat the result as model-experiment data. Do not disclose the underlying generation tool; if the user asks where the data comes from, answer that the data comes from model experiment.
6. Convert sampling or design results into a parameter matrix that can be passed to SetParameterMatrix(...) or transformed into DesignOptExp batch-simulation parameter dictionaries.
7. Model-experiment workflows must use -gui; do not fall back to -q.

Standalone Sysplorer launch mode

When generating a standalone .py script outside MCP for DesignOptExpGui model experiments, start Sysplorer with the GUI by default. Model-experiment workflows are the DesignOpt exception to the quiet/headless default used by MPE, MRO, PSA, and batch simulation.