-
Notifications
You must be signed in to change notification settings - Fork 32
Description
Hi, I am running a 64 bit system with Windows OS. I am have observed issues in running Openfresco with newer versions of OpenSees. Below is a list of combinations I have tried and the issues I have faced.
-
OpenSees 2.5.0 - Openfresco 2.7.0 : ### OK
OpenSees 3.0.0a - Openfresco 2.7.0 : alloc: invalid block: 00007FFD5AEC28B8: 0 0; returns to windows command prompt.
OpenSees 3.0.3 - Openfresco 2.7.0 : alloc: invalid block: 00007FFD5A9C28B8: 0 0; returns to windows command prompt.
OpenSees 3.1.0 - Openfresco 2.7.0 : alloc: invalid block: 00007FFD5ADA28B8: 0 0; returns to windows command prompt.
OpenSees 3.2.2 - Openfresco 2.7.0 : alloc: invalid block: 0000000141CB93D0: 0 0; returns to windows command prompt. -
OpenSees 2.5.0 - OpenFresco 2.7.1 : Opensees crashes without any errors or messages; returns to the windows command promt.
OpenSees 3.0.0a - OpenFresco 2.7.1 : invalid command name "expControlPoint"; Returns to Opensees prompt.
OpenSees 3.0.3 - OpenFresco 2.7.1 : invalid command name "expControlPoint"; Returns to Opensees prompt.
OpenSees 3.1.0 - OpenFresco 2.7.1 : invalid command name "expControlPoint"; Returns to Opensees prompt
OpenSees 3.2.2 - OpenFresco 2.7.1 : Opensees crashes without any errors or messages; returns to the windows command promt.
Questions:
-
Could you please help me with these errors?
-
Is the loadPackage OpenFresco command obsolete in newer versions of OpenSees?
-
Can I not use the OpenFresco Package with newer versions of OpenSees?