MATLAB: Parsim does not appear to recognise Enumerations

enumerationsparsim

I'm getting parsim up and running in my environment (where I have predefined Enumerations).

When I run 'sim' then the Enumerations are recognised.

When I run 'parsim' (even only for a single iteration) then the Enumerations are not recognised.

For Example:

Invalid setting in 'End_to_End_TB/Data Type Conversion22' for parameter 'OutDataTypeStr'.

'Enum: myEnum' does not resolve to a valid data type for parameter 'OutDataTypeStr' in 'End_to_End_TB/Data Type Conversion22'.

Cannot register enumerated data type because value specified is not a class.

Best Answer

Attach the m-file where the enum is defined using the 'AttachedFiles' option on parsim.

out = parsim(in, 'AttachedFiles', {'full/path/to/your/enum/file'});

Related Solutions

MATLAB: How to get the list of variables with enumerated data using classdef in a model

You can use the following codes in order to get all variables with enumerated types used in model blocks.

% Find all variables with enumerated types used in model blocks
usedTypesVars = Simulink.findVars('EnumsReporting','IncludeEnumTypes',true);
% Here, EnumsReporting is the name of the model and
% usedTypesVars is an array of Simulink.VariableUsage objects
% Find indices of enumerated types that are defined by MATLAB files or P-files
enumTypesFile = strcmp({usedTypesVars.SourceType},'MATLAB file');
% Find indices of enumerated types that are defined using the function 
% Simulink.defineIntEnumType
enumTypesDynamic = strcmp({usedTypesVars.SourceType},'dynamic class');
% In one array, represent indices of both kinds of enumerated types
enumTypesIndex = enumTypesFile | enumTypesDynamic;
% Use logical indexing to return the names of used enumerated types
enumTypeNames = {usedTypesVars(enumTypesIndex).Name}'

You can see the above code in the following manual.

- Migrate Enumerated Types into Data Dictionary

http://www.mathworks.com/help/releases/R2015b/simulink/ug/migrate-enumerated-types-into-data-dictionary.html

MATLAB: Do I receive the error ‘Signal 127’ when submitting to LSF

This error presents itself because the default LSF queue only supports interactive type jobs.

Because MDCS is a background batch type job, the LSF administrator needs to allow non-interactive jobs on the default queue, or they need to explicitly supply the correct arguments to tell LSF to run the job on a particular queue which allows batch workflows.

The SubmitArguments property of the LSF object are the arguments that pass directly to the bsub command that submits the job to LSF - it is here that the correct syntax for telling LSF which queue to use should be inserted.

Best Answer

Related Solutions

MATLAB: How to get the list of variables with enumerated data using classdef in a model

MATLAB: Do I receive the error ‘Signal 127’ when submitting to LSF

Related Question