slab girder?

[ae-ox]

Hi,

I am trying to do a moment-curvature analysis of a slab girder cross section (Precast double-tee element).
Therefore I took example2.tcl and redefined the material properties and the cross section. If I run the girder only, everything is fine, but as soon as I define the slab Opensees will return this error:

WARNING SuperLU::solve(void)- Error 1 returned in factorization dgstrf()
WARNING NewtonRaphson::solveCurrentStep() -the LinearSysOfEqn failed in solve()
Static Analysis::analyze - the Algorithm failed at iteration: 0 with domain at load factor 0
Opensees > analyze failed, returned: -3 error flag

What is wrong? The girder is 19-23cm wide, the width of the slab is 150cm. -Is this discontinuity a problem?

Thanks,
Andreas

[ae-ox]

I found my mistake (I didn't define the slab anti-clockwise...)

SORRY!!

[from tongji]

how to define the contact between the new and the old concrete?

[silvia]

i don't think you can in opensees, yet.

[mgs]

Hi,

I have got a similar error as the one on the top in OpenSeesNavigator:

WARNING SuperLU::solve(void)- Error 4 returned in factorization dgstrf()
WARNING NewtonRaphson::solveCurrentStep() -the LinearSysOfEqn failed in solve()

Would please give me an idea what may be wrong? I have read some where that it means the solution is not converged.

[mgs]

ae-ox wrote:
> I found my mistake (I didn't define the slab anti-clockwise...)
>
> SORRY!!
Hi,
Would you please share your finding about the reason of the error you got and how you fixed it? Mine is the same as yours:

WARNING SuperLU::solve(void)- Error 1 returned in factorization dgstrf()
WARNING NewtonRaphson::solveCurrentStep() -the LinearSysOfEqn failed in solve()
StaticAnalysis::analyze() - the Algorithm failed at iteration: 0 with domain at load factor 0.1
OpenSees > analyze failed, returned: -3 error flag

I am modelling an RC bridge using dispbeamcolumn and elasticbeamcolumn elements and RigidLinks (MP constraints).

[fmk]

that error is due to the fact that you have either incorrect properties or your model has not enough constraints. the original problem was the former, as the section was defined incorrectly. yours could be anything. given your model i would hazard to guess the latter is your problem.