Frequently Asked Questions (FAQ)

Q: Running or debugging a model gives validation errors, but they are not shown in the editor.
A: If the editor reports no validation errors, but running or debugging the model reports errors, then there might be a problem with the line endings of the files. To solve this problem, save the file with windows line endings. This problem is often caused by Linux line endings.

Q: Why does the type system produce warnings instead of errors?
A: In POOSL models, the types of variables and parameters have no formal meaning; basically they are just pieces of documentation. When invoking a data method or operation, at simulation time the types of variables are determined. This means that it is impossible to perform a 100% correct type check while editing; therefore any data type related issues are reported while editing as warnings.

Q: Why does a certain quick-fix have no effect?
A: Executing a quick-fix sometimes has no effect on the model. This can be caused by other errors that are still present in the model that are related to applied quick-fix. Solve these errors before executing the quick-fix.

Q: What can I do about "OutOfMemoryError: Java heap space" or "GC overhead limit exceeded" ?
A: The Eclipse installation folder contains a file eclipse.ini, which most likely contains a fragment like "-Xmx512m". This indicates that the maximum Java heap size is 512 megabyte. Increasing this amount (e.g., doubling it) should solve this problem.