Backward Compatibility Error with SubModelClones

[Stefan Hattinger]

I encountered a problem when working with the new JaamSim Release on my old Model. As this is quite big, i recreated the bug with a new, small file by executing the following steps:

1. Create new cfg File with JaamSim 2023-01
2. Create simple subModel with only one Object within (e.g. ExpressionThreshold, add a simple openCondition like sub.NumberAdded % 2'
3. Add a clone of this subModel by drag and drop from Pre-builds
4. Save and close
5. open with JaamSim 2023-01
6. do anything within the clone to enable save option (click into input fields, change values)
7. save and close, you can notice that some extra lines in the cfg file appeared
8. Open again with JaamSim 2023-01

You will receive Input errors that look like this:
*** INPUT ERROR *** Entity: template1.ExpressionThreshold, Keyword: Region - Input value is locked

Fortunately, it is still executable with 2023-03.
But if you try to open it again with 2023-01, you receive the following errors for every object:
*** ERROR *** Could not find Entity: template1.ExpressionThreshold

To sum it up, if you created your model with an older version of JaamSim and used submodel clones, editing this model with JaamSim 2023-03 partially breaks your model

[Harry King]

Stefan,

Thanks for the bug report. Obviously there are a few more rough edges to the sub-model system after the changes to the prototype and clones structure.

We will make another release in a few days that will correct these problems.

Harry

[Knut Arild Maråk]

Hi, 

I also got the "Input value is locked". 

I have a submodel which is called Export, which has 5 clones. The error turned up after I created a custom output in the CustomOutputList of the "Export.ShipsUnderwayToImport"-object. It appears that the error is caused when it refers to another object within the same submodel, see screenshot below. Referring to an object outside the submodel works fine.

The error does not occur in the "Expression"-part of the Export.ShipsUnderwayToImport-object.

Yesterday when I made the custom output in version 2023-06, the model worked fine with these custom outputs for an hour, all until I re-opened the model. Today, after upgrading to 2024-03 (which I hope had fixed the problem - it hadn't), I seem to get the problem straight away, without saving or re-opening the file.

 

Knut Maråk

[Harry King]

Knut,

Please attach a copy of your model along with instructions on how to reproduce the error. Better yet, provide a simple example that reproduces the error.

Harry