The OpenSees Community

transformation should work if no dof is constrained more than once, e.g no equalDOF and sp. we don't yet follow the path. for the lagrange you probably have to change the convergence test, disp increments for penalty and unbalance for lagrange. as for the penalty it should give you the correct respo...

i have fixed the visualstudio.net and vc6.0++ project files .. both now assume tcl8.4 or greater .. the current files can be obtained from cvs .. the tarball source code distribution of the new 1.6.0 release will be at the website shortly.

i have fixed the code for these .. avail with 1.6.0 and higher.

if anybody notices any other things that fail when the save/restore commands are used please post them in this thread.

thanks.

the material can themselves keep track of their previous stress state ..
remember this is an object-oriented code and not a procedural one .. objects can keep track of whatever other info they need themselves.

you are probably using the dispBeamColumn .. use the (forceBeamColumn) nonlinearBeamColumn instead .. given nodal disp the force based element iterates to get a displacement field which exatcly satisfies force equi of element (force field known exactly for force based element) .. the displacement ba...

you are correct .. it is dof at the jnode - the dof at the inode .. we do need to make this clearer in the manual.

you can use the corotational transformation with the force (nonlinearBeamColumn) and displlacement beam column elements.

the problem is tcl/tk .. they have tightened up their api betwen versions 8.3 and 8.4 .. a lot of procedures now take const char * instead of char * .. as we have developers trying to compile with both versions we have defined TCL_Char in OPS_Globals.h .. if you look at the OpenSees files that call ...

i have just placed a new executable on the website .. version 1.5.3 .. it does not appear
to have the problem you describe .. maybe you could test it, if problem persists .. could
you try and post the script so i can run it and see what's up.

i don't see this message with my current windows .exe version 1.5.3 .. i will put
a tarball of the latest source code online shortly.

you can't .. i could not bring the old message board back up on new server .. there was not that many messages anyway.

can you be a bit more specific. you could for example use loadControl and in 1 pattern place the loads which use one path and in another specify the displacements which follow some other path .. this is IMPOSED DISPLACEMENTS and NOT DISPLACEMENT CONTROL :twisted: Most people want displacement cotrol...

truss and zeroLength elements determine their own damping .. all other elements use the default provided by the Element classial will work .. that is why providing eta for the material will work .. it is something that obviously needs to be clearly documented and i apologise that it is not

did you look to see if you have the header and library files?? .. they will be in
C:\Program Files\tcl\include and C:\Program Files\lib

ansewrs to your questions: 1. nodes and elements DO NOT have to be continuous. 2. you just have to enter 2 DIFFERENT nodes, remember the material for the ZeroLength will define the force-deformation and not stress-strain relationship. the 'strain' sent to the material at each step will be the differ...