nonlinearBeamColumn problem

hrodrigues · Post by **hrodrigues** » Thu Oct 30, 2008 2:01 pm

Hello,
I have a OS code and it have the next sentence in the definition of the nonlinearBeamColumn element:

element nonlinearBeamColumn $elemTag $no_e $$no_d 5 -sections 111 112 113 112 111 $transfTag

OS is not running with these code. The problem is in “-sections 111 112 113 112 111”.
in my point of view the previous user associate different section types to the different integration points. However now it’s not working. Anyone knows why ?
these properties is very useful for the definition of the beams with different types of reinforcement.
thanks in advanced.
Hugo

hrodrigues · Post by **hrodrigues** » Sun Nov 02, 2008 4:20 pm

Anyone can help me ??

silvia · Post by **silvia** » Mon Nov 03, 2008 5:22 am

you need to use the integration points not the section tags.

hrodrigues · Post by **hrodrigues** » Mon Nov 03, 2008 9:24 am

Sorry,
I can’t understand what you mean.

hrodrigues · Post by **hrodrigues** » Mon Nov 03, 2008 9:57 am

solved!

silvia · Post by **silvia** » Mon Nov 03, 2008 12:02 pm

hanjun009 · Post by **hanjun009** » Tue Nov 04, 2008 12:25 am

Hi hrodrigues;
i have encountered the some question. When i use opensees1.7.3,the "sections" work well, but not work using opensees 2.0 version. how did you solve it?

hrodrigues · Post by **hrodrigues** » Tue Nov 11, 2008 10:43 am

hanjun009 wrote:Hi hrodrigues;
i have encountered the some question. When i use opensees1.7.3,the "sections" work well, but not work using opensees 2.0 version. how did you solve it?

It Works in OS 2.0
Please see the example:
element nonlinearBeamColumn 101 51 11 3 UserDefined $numSec 111 112 113 112 111 0 0.327326835 0 0.327326835 1 0.05 0.272222222 0.355555556 0.272222222 0.05

element nonlinearBeamColumn $elem_tag $left_node $right_node $Geotranf UserDefined $numSec $sectype1 $sectype2 $sectype3 $sectype4 $sectype4 $posi1 $posi2 $posi3 $posi4 $posi5 $weight1 $weight2 $weight3 $weight4 $weight5

to see and adequate to you model please see the integration points location and weight in the OS code at:
http://opensees.berkeley.edu/cgi-bin/cv ... ration.cpp

tell me if you need anything.
Best regards
Hugo

arbarbosa · Post by **arbarbosa** » Thu Nov 20, 2008 10:09 pm

The syntax is now (at least since v1.6.2.f):

element beamType? eleTag? iNode? jNode? transfTag? UserDefined nIP?
secTag1? secTag2? .. secTagN pt1? pt2? .. ptN? wt1? wt2? .. wtN?

where beamType can be forceBeamColumn or dispBeamColumn