Known issues

When loading an Aspect Model, the Aspect Model Editor freezes in a blurry mode.

This can be caused by previously generated TTL with certain syntax errors. This can be caused by renaming an Entity.

When loading a TTL file to edit an Aspect Model, an Error when loading RDF is shown.

This is caused by fundamental syntax errors in the TTL being loaded. Potential underlying root cause: The used BAMM version is not supported by this version of the Aspect Model Editor.

Check that you have not missed parts of the TTL file. Also check against syntax errors consulting Namespaces and versions (BAMM 1.0.0).

"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:bamm:com.your.example.namespace:aspect-model:AngularVelocityHistory:1.1.1#AngularVelocityTimeSeries"

"resultPath":"urn:bamm:com.your.example.namespace:meta-model:1.2.0#dataType" "resultSeverity":"http://www.w3.org/ns/shacl#Violation"

"value":"urn:bamm:com.your.example.namespace:aspect-model:AngularVelocityHistory:1.1.1#AngularVelocityTimeSeriesEntity"

This can happen if a namespace version is not supported anymore or when setting an unsupported dataType.

Wrong data type

Check that the data types you are using are correct, see Datatypes (BAMM 1.0.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. Display the Movement Example by clicking the New/Load icon > Create/Upload Aspect Model > Models > Movement Example.

When loading a TTL file, units are not loaded correctly. After triggering a validation, this validation does not stop and the user cannot continue to edit the Aspect Model.

The backend validation does not complete successfully. One reason can be that the backend service is not running.

Restart the Aspect Model Editor.

Fixed for Aspect Model Editor 2.1.0 and higher: If the backend is not available, a message is shown to the user.

After triggering a validation, the validation runs into a timeout.

The backend validation does not complete successfully. One reason can be that the backend service is not running.

Restart the Aspect Model Editor.

During installation, some files cannot be written. Popup allows retry or abort.

File path restriction does not allow writing a file.

Install on C:\AME or similar without going deeper in hierarchy

Trying to add entity / relate entity with Characteristic does not work.

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.

Should you need to relate this Characteristic with an Entity, change your Characteristic class first and modify your own Entity as suitable.

During usage, a key press (e.g. delete to delete an element) is not recognized. Instead, no action happens.

The Aspect Model Editor does not support keystrokes like "del". See Get started.

Use mouse actions instead, e.g. the toolbar on the top with the Delete icon. You can also change your focus back and forth to try again pressing the delete key.

After loading an Aspect Model or after auto-format, some elements seem to be missing

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)

The "Aspect Model Editor Uninstaller" is not available when searching via Windows search bar, see

Unknown root cause.

Uninstall via context menu which will lead to add/remove programs

Error message when starting the Aspect Model Editor on MacOS.

If your MacOS version is running Apple’s new security feature, it could happen that the application is started in a kind of sandbox. You can easily detect this by reading the following in the JavaScript error message: Uncaught Exception: Error: spawn /private/var…​ (see image below).

The keyword here is /private/var, which means that your application is in a kind of quarantine and can only be unlocked by you. For this you must open your terminal and execute the following command:

xattr -r -d com.apple.quarantine /Applications/AspectModelEditor/Aspect-Model-Editor.app

Please note that the path to the application can change and this is only the default path.

Please keep in mind that this is not an official Apple version, and it must be confirmed in the security settings first. You may be asked several times before the app opens.

If your security settings are enabled to launch unverified applications, the following error messages may pop up. These must be pre-approved in the security settings of your system.

The following should be considered when approving: