Back to company website

You are not logged in. Please login or register.

Forum updated

We have recently updated our forums system, and we have cleared all spam topics and users. In case we accidentally deleted your account, please register again. If you miss a topic you have posted before, please let us know.

Post new reply

Post new reply

Compose and post your new reply

You may use: BBCode Smilies

All fields with bold label must be completed before the form is submitted.

Required information for guests


Required information

Topic review (newest first)

4 Post by dpryl

Hello, using shells for the elastic loading/support plates usually does NOT make much sense. Normal volume brick or tetrahedra are typically the best choice there.

3 Post by amgqp4

Ok, I noticed that the girder failed at the one the supports, and that two of the 4 convergence criteria didn't converge.  I'm assuming the error occurred due to the failure at the support.  However, this type of failure didn't occur during the physical test. Would you suggest enlarging the support?  Currently I'm using a shell element for the steel plate supports.

Alex

2 Post by dpryl

Hello, have you already checked the convergence and results for the calculated steps? Is the deformed shape as expected? Are there any surprising cracks or plastic strains?

1 Post by amgqp4

Hi,

I am modeling a prestressed concrete I girder, and get the error "internal analysis error: floating point overflow" halfway through the analysis.  I have altered the displacement increment that is applied to the girder and the error always occurs at the same analysis step. The construction case and load cases before and after this load step are identical.

I have read through 2.4.2 in the trouble shooting manual, and have not found any obvious errors.

What does floating point overflow mean and how could I resolve this issue?

Thanks in advance,
Alex