Protected model has different behavior from base model

When protecting a model I find there is a difference in results between the base model and the protected model.

I have found that the issue specifically exists when I choose the below option.

I have not changed any of the data in anyway. So I am not sure why this discrepancy exists.

I am using a data dictionary for this model

Answer 1

[Ayush]

Hi @Jake Gareau

A protected model may have a different behaviour from its base model due to the implementation of certain security measures or restrictions. These measures are typically put in place to safeguard the model's sensitive or proprietary information, prevent unauthorized access or modifications, or enforce usage limitations.

Here are few reasons why protected model different behaviour might have compared to its base model:

1. Code obfuscation: means that the original source code is intentionally made difficult to understand or reverse engineer.
2. Feature limitations: The protected model may have certain features or functionalities disabled or restricted to prevent unauthorized use or modification.
3. Licensing and access control: The protected model might have licensing or access control mechanisms in place to ensure compliance with usage agreements or to restrict access to certain features or data.
4. Runtime environment differences: The protected model may require a specific runtime environment or dependencies that differ from the base model.
5. Anti-tampering measures: Protected models often include anti-tampering measures to detect and prevent unauthorized modifications or reverse-engineering attempts.

You may read on protected models from here:

https://in.mathworks.com/help/rtw/ug/create-a-protected-model-using-the-model-block-context-menu.html

Thanks,

Ayush Jaiswal