Author Topic: A bug in stress output?  (Read 4678 times)

K.Li

  • Full Member
  • ***
  • Posts: 191
A bug in stress output?
« on: May 29, 2015, 06:44:52 AM »
Dear FEAP users:

When I was using the FEAP built-in solid element, I found my stress output is zero. Then I checked routine fld3d2() in which it seems the stresses were written to the output file (iow) around line 655. But in this write command 'sigl(i,l)' array was used, here 'l' must be the a number for Gauss point. The second do loop through all the Gauss points was end around line 628, so all the elements of this array and 'xxm' are zero outside of that loop. That must be the reason I got zero stresses in my output file. Could anyone please verify whether it is  a bug or I am using a old version of FEAP? It says I am using 8.4.

Thanks a lot!

Prof. R.L. Taylor

  • Administrator
  • FEAP Guru
  • *****
  • Posts: 2649
Re: A bug in stress output?
« Reply #1 on: May 29, 2015, 08:06:02 AM »
This is a bug which will be corrected for the next release.

The correction is:

Before statements in stress output

                do i = 1,3
                  bpra(i) = 0.5d0*log(bpr(i))
                  xxm(i)  = 0.0d0

add
               do l = 1,lint

close loop after write of results.

K.Li

  • Full Member
  • ***
  • Posts: 191
Re: A bug in stress output?
« Reply #2 on: May 29, 2015, 08:58:04 AM »
Thank you so much for your promptly reply, Prof Taylor! Now it outputs all the stresses on all the Gauss points together for one element.

I look forward to the next release.

K.Li

  • Full Member
  • ***
  • Posts: 191
Re: A bug in stress output?
« Reply #3 on: May 30, 2015, 03:06:27 AM »
Dear Prof Taylor:

I was thinking about maybe we could put all the known bugs of current release of FEAP together in one post so that other users could just avoid investigating time on those bugs (I spent a lot time on this bug, I thought it was a mistake with my user material model at first, then I thought it was a interface problem with our use element). In this post, we should at least point out where the bug is located on which file. If available, the solution could be also posted or a link to the post where the solution is located. I am sure such a post will benefit the FEAP community.

Thanks!