AGI_VOICE

Use when the task needs deeper API or protocol detail across CMAPI, APO, IPGRoad API, GPUCodingInterface, or other advanced CarMaker extension points beyond the basic workflow guides.

Use when the task is about CarMaker for Simulink, APO-based online integration, or external coupling workflows that connect CarMaker to other tools or runtime environments.

Use when the task is to structure vehicle data requests, identify missing model inputs, or design validation maneuvers, signals, and checklists from the CarMaker RequestForm materials.

Use when the task is about CarMaker project structure, loading a project, choosing a TestRun, selecting a vehicle or trailer, or understanding how datasets relate inside a run configuration.

Use when the task is to load or modify CarMaker TestRun, vehicle, trailer, or other parametrization objects from Python and shape new variations programmatically.

Use when the user wants to execute CarMaker from Python, queue variations, use Runtime or SimControl, read or write quantities, wait on conditions, or capture simulation data.

Use when the user is starting CarMaker, creating a first TestRun, learning the GUI workflow, or asking for the shortest path into vehicle dynamics, ADAS, powertrain, Scenario Editor, or CM4SL.

Use when the task involves CarMaker Scenario Editor, OpenSCENARIO schemas, road authoring, or IPGRoad API and you need to separate GUI workflow from schema and code-level API work.

Use when a task mentions IPG, CarMaker, IPGControl, Movie NX, Instrument Designer, or IPGGraph and you need to route the request to the right product, manual, example set, or companion tool.

Use when the task is about choosing or using IPGControl, Movie NX, Instrument Designer, or IPGGraph for plotting, postprocessing, dashboards, scene scripting, or result visualization.

Use when the task needs deeper API or protocol detail across CMAPI, APO, IPGRoad API, GPUCodingInterface, or other advanced CarMaker extension points beyond the basic workflow guides.

Use when the task is about CarMaker for Simulink, APO-based online integration, or external coupling workflows that connect CarMaker to other tools or runtime environments.

Use when the task is to structure vehicle data requests, identify missing model inputs, or design validation maneuvers, signals, and checklists from the CarMaker RequestForm materials.

Use when the task is about CarMaker project structure, loading a project, choosing a TestRun, selecting a vehicle or trailer, or understanding how datasets relate inside a run configuration.

Use when the task is to load or modify CarMaker TestRun, vehicle, trailer, or other parametrization objects from Python and shape new variations programmatically.

Use when the user wants to execute CarMaker from Python, queue variations, use Runtime or SimControl, read or write quantities, wait on conditions, or capture simulation data.

Use when the user is starting CarMaker, creating a first TestRun, learning the GUI workflow, or asking for the shortest path into vehicle dynamics, ADAS, powertrain, Scenario Editor, or CM4SL.

Use when the task involves CarMaker Scenario Editor, OpenSCENARIO schemas, road authoring, or IPGRoad API and you need to separate GUI workflow from schema and code-level API work.

Use when a task mentions IPG, CarMaker, IPGControl, Movie NX, Instrument Designer, or IPGGraph and you need to route the question to the right product, manual, example set, or companion tool.

Use when the task is about choosing or using IPGControl, Movie NX, Instrument Designer, or IPGGraph for plotting, postprocessing, dashboards, scene scripting, or result visualization.