Variant Subsystems control by Model Workspace variables?

Dear Community,

does there exist a way to use Model Workspace variables instead of Base Workspace variables for variant control?

I would like to avoid using callbacks for variant override.

I wonder why hierarchical symbol resolution ( http://blogs.mathworks.com/seth/2009/02/15/where-does-that-variable-come-from/ ) does not apply for variant control ...

Best regards,

Tilman

[Christopher Slack]

I would like to bump this question as I have just come across the same problem. In R2016b when trying to use Simulink.Variant in the model workspace variable the error is "...must be a condition expression or name of a Simulink.Variant object in the global scope workspace of the model."

Unfortunately, this just ends up with more bloat in the base workspace.

[Francis Gagnon]

I have exactly the same problem in R2017b. I would like to hide the Simulink.Variant variables from the global workspace...

[Markus]

I agree to the above. I would also prefer to have Simulink Variant objects in the model workspace.

[Lee]

Where is this limitation even mentioned in the documentation? I don't understand why variables referenced by variant control conditions would need to be present in a specific workspace. Furthermore, even after moving said variables into the base workspace, Simulink throws an error as it's still unable to evaluate logical expressions such as 'and' or '|' or 'not'

Answer 1

[Mobashar Ahmad]

Any updates on this? i would also like to use the Model Workspace to manage the variants control variables.

[Markus]

Same here. These make more sense in the model workspace anyway.

Any update from a staff member?

Answer 2

[Jonas]

You can create a Simulink.Variant variable and put it inside a Data Dictionary, and then link this Data Dictionary to the model.