Use Case
The models being built are using scopes.
The skills do not include the knowledge about how to add signal names on lines, and activate logging.
Using signal names and logging, with Simulink Data Inspector is far superior to using a lot of scopes.
Related to this is the usage of Data Dictionaries with Simulink.Signal objects.
For software models, the signal lines must be names and must resolve to Simulink.Signal objects that are defined in a Data Dictionary that is linked to the model. Signals must also be logged for Simulation, so that Simulink Data Inspector can be used.
The skill files are lacking this. Data is created in M-Files and are put into the Base Workspace, which is a horrible practice and must be forbidden.
Relevant Skill or MCP Tool
Model creation skill.
Proposed Behavior
Created Models must used named Signals.
The names must be consistent throughout the model.
The signal must only be logged ONCE at the original where it is created.
Lines must only contain signal names where they are created. Other lines should not have names, otherwise it clutters the model.
The signal must resolve to a Simulink.Signal object in a Data Dictionary linked to the Model.
The signal in the DD must contain meta data like Unit, Description, Min, Max, Datatype.
Putting Data in the Base Workspace must be forbidden, only allow Simulink Data Dictionaries, so that models can be self-contained without running any scripts.
Usage of Simulink Data Inspector must be encouraged. Scopes must be forbidden.
Current Workaround
I have to prompt the agent many times and it takes many iterations for the logging, resolve to Signal and Data Dictionary usage to work.
Additional Context
No response
Use Case
The models being built are using scopes.
The skills do not include the knowledge about how to add signal names on lines, and activate logging.
Using signal names and logging, with Simulink Data Inspector is far superior to using a lot of scopes.
Related to this is the usage of Data Dictionaries with Simulink.Signal objects.
For software models, the signal lines must be names and must resolve to Simulink.Signal objects that are defined in a Data Dictionary that is linked to the model. Signals must also be logged for Simulation, so that Simulink Data Inspector can be used.
The skill files are lacking this. Data is created in M-Files and are put into the Base Workspace, which is a horrible practice and must be forbidden.
Relevant Skill or MCP Tool
Model creation skill.
Proposed Behavior
Created Models must used named Signals.
The names must be consistent throughout the model.
The signal must only be logged ONCE at the original where it is created.
Lines must only contain signal names where they are created. Other lines should not have names, otherwise it clutters the model.
The signal must resolve to a Simulink.Signal object in a Data Dictionary linked to the Model.
The signal in the DD must contain meta data like Unit, Description, Min, Max, Datatype.
Putting Data in the Base Workspace must be forbidden, only allow Simulink Data Dictionaries, so that models can be self-contained without running any scripts.
Usage of Simulink Data Inspector must be encouraged. Scopes must be forbidden.
Current Workaround
I have to prompt the agent many times and it takes many iterations for the logging, resolve to Signal and Data Dictionary usage to work.
Additional Context
No response