You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is regarding current state of the develop branch:
I suddenly started to get this error.
AttributeError: 'Meta' object has no attribute 'model_dimension'
This happened when I tried to export an .xml file that was generated earlier (with my backend-otf branch).
Do you have an idea what this could be related to? Did the 'model_dimension' property got moved from meta to somewhere else?
Some extra info:
As far I know, everything is consistent if you generate the .xml, export and run with the same code snapshot... I.e. regenerating the .xml from the render script solves the issue.
I had previously exported the .xml I mentioned first (with code from my backend-otf branch). I could run this model with the current state of the develop branch (but, as I said before, could not export it again).
The text was updated successfully, but these errors were encountered:
I installed 'amos' in my Mac running El Capitan. When I execute the line kmos.cli.main('export myfirst_kmc.xml') inside my ipython (invoked as sudo ipython), then I get the same error as above :
AttributeError: 'Meta' object has no attribute 'model_dimension'
Hi,
In my experience this error occurs when there is some discrepancy among different Python versions. I have experienced it for example if I installed kmos using one version of Python and then tries to run a model using another version of Python.
It could also be the case that the xml file you are trying to export has been created using a different Python version than what you have installed.
Hey Max,
This is regarding current state of the develop branch:
I suddenly started to get this error.
AttributeError: 'Meta' object has no attribute 'model_dimension'
This happened when I tried to export an .xml file that was generated earlier (with my backend-otf branch).
Do you have an idea what this could be related to? Did the 'model_dimension' property got moved from meta to somewhere else?
Some extra info:
As far I know, everything is consistent if you generate the .xml, export and run with the same code snapshot... I.e. regenerating the .xml from the render script solves the issue.
I had previously exported the .xml I mentioned first (with code from my backend-otf branch). I could run this model with the current state of the develop branch (but, as I said before, could not export it again).
The text was updated successfully, but these errors were encountered: