integration command for "forceBeamColumn"

[ttt]

Hi,

Although the following commands were correctly run in the old version of Opensees, it does not now run in opensees v2.5. How can I adapt these commands to the current version v.2.5?
For now, thanks for any support

set locations “0.0 1.0 0.2 0.5 0.8”
set weights “0.2 0.2”
set secTags “1 1 2 2 2”
set integration “LowOrder $N $secTags $locations $weights”
element forceBeamColumn $tag $ndI $ndJ $transfTag $integration

[asmith]

You have 5 locations and only two weights. The number of inputs for locations, weights and secTags must be the same. That's how I have used that command in the past. There is a pdf that weights 5 integration points for you on the forcebeamcolumn page

[ttt]

Hi asmith,

Thanks for your reply.

You are right about the lack data in the command "set weights “0.2 0.2”".
However, altough I correct this mistake as

set locations “0.0 1.0 0.2 0.5 0.8”
set weights “0.2 0.2 0.2 0.2 0.2”
set secTags “1 1 2 2 2”
set integration “LowOrder $N $secTags $locations $weights”
element forceBeamColumn $tag $ndI $ndJ $transfTag $integration

and put the corrected data for the opensees interface, I unfortunetly get an error again.
After your reply, I fastly consider the source code of "forcebeamcolumn" coded in version 2.4 and see that this input is not valid for this version. However, there exists a definition for the input as "userdefined...".
Now,, I strive to solve how this input is introduced into opensees platform.

wishes

[ttt]

Hi asmith,

Today, when I re-consider my input data, I notice that one of the material definitions is not correctly defined. Thus, after I correct it, this command runs for both "userDefined ...." and "LowOrder..."

wishes,