11–20 of 47 posts
I'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.
https://www.math.hu-berlin.de/~cc/cc_homepage/download/1999-...
My 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…
I know it's not a simple answer, but how would you embed checks to flag or highlight potentially incorrect results to the user?
http://hplgit.github.io/num-methods-for-PDEs/doc/web/index.h...
http://hplgit.github.io/num-methods-for-PDEs/doc/pub/index.h...
My favourite resources for FEM were the book and courses that Hans Petter Langtangen (RIP) wrote at Simula. FEniCs made FEM so easy, it’s truly an excellent software project that is unfortunately not as well known as it should be within the community. http://hplgit.github.io/num-methods-for-PDEs/doc/web/index.h... http://hplgit.github.io/num-methods-for-PDEs/doc/pub/index.h...
Earlier quoted context omitted.
I know it's not a simple answer, but how would you embed checks to flag or highlight potentially incorrect results to the user?
For physical processes, you can sometimes lean on conservation laws. Financial, no-arbitrage "laws". Sometimes it can help to run two different models, or different numerical methods, and compare their results. More generally, it's very, very hard. I am fairly sure there are multiple published results in computational fluid dynamics that are subtly wrong.
This is great. I studied FEM in school and got my first job in industry as a structural analyst. I started my own firm when I was 25 and employed 22 analysts that I contracted to Pontiac Motors.
Earlier quoted context omitted.
I know it's not a simple answer, but how would you embed checks to flag or highlight potentially incorrect results to the user?
For physical processes, you can sometimes lean on conservation laws. Financial, no-arbitrage "laws". Sometimes it can help to run two different models, or different numerical methods, and compare their results. More generally, it's very, very hard. I am fairly sure there are multiple published results in computational fluid dynamics that are subtly wrong.
I wonder what that means for the accuraccy of the climate models...
This is great. I studied FEM in school and got my first job in industry as a structural analyst. I started my own firm when I was 25 and employed 22 analysts that I contracted to Pontiac Motors.
Former structural analyst here. :waves: If you worked on consumer products there (aka cars and their components), do you happen to remember what the design-to fatigue life was? I talked with another analyst several years ago who had worked at Chrysler, and he told me they had used 125,000 miles. (I was in aerospace so not sure how many miles comprised a fatigue cycle, etc.)
I worked as a structural analyst on passenger train cars (metros, LRVs, etc) for a while, as my first job after grad school actually.
Depending on the project (client requirements), we designed for 25-35 year lifetimes, with 12-24h operation typical. That usually amounted to millions of kilometers.
We had load cases with varying numbers of cycles. Eg curves with light loading might have been millions of cycles, but max (or even over max) loading might have been 10s or 100s of thousands of cycles.
All load cases were determined based on on usage stats from the operator and testing conducted to measure accelerations on the operator's infrastructure.