Known issues
All known issues with the Aspect Model Editor are listed here.
See also known limitations.
Issues with validating, loading, and saving Aspect Models (TTL files)
Aspect Model Editor freezes when loading model
Error |
When loading an Aspect Model, the Aspect Model Editor freezes in a blurry mode. |
|---|---|
Explanation |
This can be caused by previously generated TTL with certain syntax errors. This can be caused by renaming an Entity. |
Error when loading RDF
Error |
When loading a TTL file to edit an Aspect Model, an |
|---|---|
Explanation |
This is caused by fundamental syntax errors in the TTL being loaded. Potential underlying root cause: The used SAMM version is not supported by this version of the Aspect Model Editor. |
Workaround |
Check that you have not missed parts of the TTL file. Also check against syntax errors consulting Namespaces and versions (SAMM 2.2.0). |
The dataType (see value) that is used as dataType on the Characteristic (see focusNode) is neither an allowed XSD or RDF type, nor a type that is defined as rdfs:Class.
Error |
"resultMessage":"The dataType (see value) that is used as dataType on the Characteristic (see focusNode) is neither an allowed XSD or RDF type nor a type that is defined as rdfs:Class." "focusNode":"urn:samm:com.your.example.namespace:aspect-model:AngularVelocityHistory:1.1.1#AngularVelocityTimeSeries" "resultPath":"urn:samm:com.your.example.namespace:meta-model:1.2.0#dataType" "resultSeverity":"http://www.w3.org/ns/shacl#Violation" "value":"urn:samm:com.your.example.namespace:aspect-model:AngularVelocityHistory:1.1.1#AngularVelocityTimeSeriesEntity" |
|---|---|
Explanation |
This can happen if a namespace version is not supported anymore or when setting an unsupported dataType. |
Workaround |
Wrong data type Check that the data types you are using are correct, see Datatypes (SAMM 2.2.0) Unsupported Namespaces Check that your currently used namespaces in the TTL file are up to date. Hint: You can check the current default namespaces via looking at the Movement Example code. Load the Movement Example via File > New… > Examples > Movement.ttl. |
Validation timeout
Error |
After triggering a validation, the validation runs into a timeout. |
|---|---|
Explanation |
The backend validation does not complete successfully. One reason can be that the backend service is not running. If the backend is not available, a corresponding message is shown. |
Workaround |
Restart the Aspect Model Editor. |
Other known issues
Aspect Model Editor installation cannot write all files
Error |
During installation, some files cannot be written. Popup allows retry or abort. |
|---|---|
Explanation |
File path restriction does not allow writing a file. |
Workaround |
Install on C:\AME or similar without going deeper in hierarchy. |
Cannot add Entity or relate Entity with Characteristic
Error |
Trying to add entity / relate entity with Characteristic does not work. |
|---|---|
Explanation |
This is the intended behavior. If your Characteristic is a predefined instance, its data type is immutable. In this case you cannot relate it with an Entity. |
Workaround |
Should you need to relate this Characteristic with an Entity, change your Characteristic class first and modify your own Entity as suitable. |
Some elements seem missing when loading or auto-formatting
Error |
After loading an Aspect Model or after auto-format, some elements seem to be missing |
|---|---|
Explanation |
Elements may in some cases be moved on top of each other or far away. This can for example happen when there are elements in the Aspect Model that are not connected to the Aspect (directly or via other elements) |
Workaround |
|
Imported elements may overlap
Error |
After importing elements from the workspace, the element subtree overlaps the present model. |
|---|---|
Explanation |
This happens due to autoformat not being enabled and/or the hierarchical layout being disabled. When you move elements manually, the Aspect Model Editor prevents them from being dropped on top of other elements. |
Workaround |
One of the following options can be used to fix the problem:
|
macOS: Application cannot be opened or backend does not start
| This issue is caused by the Aspect Model Editor not being notarized or signed with an Apple Developer certificate. See Current limitations on macOS for background information. |
Error |
When starting the Aspect Model Editor on macOS, one of the following happens:
|
|---|---|
Explanation |
macOS Gatekeeper quarantines applications downloaded from the internet.
Quarantined applications are blocked or started from a randomized, read-only location ( |
Workaround |
Remove the quarantine attribute in Terminal:
Please note that the path to the application can differ from the default path used above. Alternatively, approve the application in the security settings:
|