The community will undergo maintenance on October 16th at 10:00 PM PDT and will be unavailable for up to one hour.
Hello,
We are using PTC Integrity 11.0.0.506, API Version 4.16.506
We have a .mdl MATLAB Simulink file which appears to be an ASCII text file
https://www.mathworks.com/matlabcentral/answers/46400-how-to-view-mdl-files
However when a check-in is attempted, the following message box appears:
(please see the attached file)
The working file Strategy.mdl exceeds the size limit for storing revisions by delta
within an archive.
In order for this check in to proceeed, the archive must be converted to store references to complete
contents of each revision
The check in will be cancelled if the conversion is not allowed to occur.
Do you want to automatically convert the archive into store-by-reference format prior to the check in ?
Yes - Yes to All - No - No to All - Cancel
Solved! Go to Solution.
Hi Amatei,
How large is the Matlab .mdl file? How many MB?
You're seeing this message, because there is a configurable size-limit for storing revisions by "delta" for an archive. The larger these files are, the more memory they consume in trying to calculate and store the delta, and the larger the files are, the less useful those "deltas" become. When the files get big enough, that's why they recommend to store as binary instead.
Here's a relevant knowledge article on this setting:
Hi Amatei,
How large is the Matlab .mdl file? How many MB?
You're seeing this message, because there is a configurable size-limit for storing revisions by "delta" for an archive. The larger these files are, the more memory they consume in trying to calculate and store the delta, and the larger the files are, the less useful those "deltas" become. When the files get big enough, that's why they recommend to store as binary instead.
Here's a relevant knowledge article on this setting:
Hi,
The .mdl file is not big but has 41 revisions in the file member history
Please see the attached file. Does it help to check the [ ] Store by reference checkbox ?
Hi,
I have found the reason why the message box mentioned above appears
It is not related to how numerous the file history is, it doesn't matter that there are 41 revisions with frequent merge operations.
The reason is this:
- the most recent revision has ~ 6 MB, but the file I am trying to check-in has ~ 19 MB.
- because there are too many differences between the two files, MKS will display that message box when a check-in is performed