The OpenSees Community

Check the connectivity of the elements in your model. You likely have a mechanism.

Here is a video: https://youtu.be/BLcY1w7a5Ec

1. Yes, you can compile libraries from OpenSees source code, without Tcl or Python
2. There is not a way to block spam as far as I know

That's always possible. There is a quickMain project in the OpenSees/Win64/proj directory that compiles OpenSees\EXAMPLES\Example1\main.cpp as a stand alone main function.

Thanks! I ran into similar issues recently with the OpenSees.exe compilation. I recorded the process, but haven't edited the video yet.

But here's a video on compiling openseespy.pyd https://youtu.be/l5-vJDZR_hA

Yeah, even with a linear model, it's still always a good idea to use the Newton algorithm.

Same kind of thing happens with member loads on force-based beam-column elements where you need the second iteration for the loads to have an effect.

That can be done. Would you create an issue for this on GitHub? https://github.com/OpenSees/OpenSees/issues

Change your project architecture from Debug.DLL to Debug (or Release.DLL to Release)

Do you have beam elements mixed with quad elements in your model? That error may be due to using elements that require more DOFs/node than what you define in the 'model' command.

Here's a video of me compiling OpenSeesPy in Visual Studio: https://youtu.be/l5-vJDZR_hA

You can use quad with plane strain, either way should work

Yes, the material will compute shear modules G=E/(2(1+v))

I'm working on the same thing myself. Will let you know when I get it compiled.

You may have to ops.wipe() your model before doing the animate??

I think it's the same issue as with recorders: https://wp.me/pbejzW-Si

Try putting the str around the non-string arguments, e.g., '-val',str(0.3),...

You can use rigid joint offsets in the geomTransf command.