Eighty Years of the Finite Element Method
link.springer.com
Eighty Years of the Finite Element Method
1–10 of 47 posts
Re: Eighty Years of the Finite Element Method
#2Re: Eighty Years of the Finite Element Method
#3Very nice summary paper on FEM! FEM has now become a key part of any physical product development process. I used to work in FEM area and few years back switched to unrelated software domains - so felt a bit of nostalgia reading the paper. Thanks for posting !
Re: Eighty Years of the Finite Element Method
#4Re: Eighty Years of the Finite Element Method
#5Very nice summary paper on FEM! FEM has now become a key part of any physical product development process. I used to work in FEM area and few years back switched to unrelated software domains - so felt a bit of nostalgia reading the paper. Thanks for posting !
I just skimmed this and I never worked in FEM but this really brought me back. I had the pleasure of meeting several of the people in the article (Hughes, Oden, Babuska, Demkowicz) and couldn’t help feeling some nostalgia as well.
Re: Eighty Years of the Finite Element Method
#6Re: Eighty Years of the Finite Element Method
#7Re: Eighty Years of the Finite Element Method
#8The lead developer (at the time) once said that the biggest software failure we can have is not incorrect results, but incorrect results without the user knowing. This is probably why I am so bothered by silent failures in my big company role now.
Re: Eighty Years of the Finite Element Method
#9My first programming role was on the back of work by an engineer in this article. The core of the solver was a FORTRAN implementation of a paper on p-convergence. It was really amazing seeing our software predict how a small crack in a part of an aircraft would propagate. The 3D model produced matched the photograph shared later. The lead developer (at the time) once said that the biggest software failure we can have…
Re: Eighty Years of the Finite Element Method
#10I'm not sure if there's a simple implementation of FEM (might be < 50 lines of code) to understand the virtual of the algorithm then.