Simulate Early, Simulate Often... In Rhino
Contributed by anonymous user from Korea.
Of course information about "linear structural (elasticity) problem" is correct. All is o.k., honest and fair (without any marketing promises). I need to read all carefully.
I would like to explain, that (for example) shield i.e. tall beam have very complicated work, another than usual low beam. Fat plate is more complicated than thin plate etc. Of course You know about this complex theories, but users of Rhino3D can be designers or form creators and other people.
My message was not ideal, sorry. I think about this important "provissions" for every user, with big letter, bold latters, is safety "guard", because I see users! Software is great, but users only people.
Dear Tomasz, I think that your comments are misplaced -- please see the product documentation, which of course includes known limitations of the software.
More generally, your modest opinion is duly noted, and of course as you pointed out, your comments are applicable to any FEA program or any engineering software that matter. The subject of who should be "allowed" using engineering analysis softwrae widely debated on the internet and in the professional literature. But it is really besides the point, because it reminds of the time when driving cars was too dangerous (still is), or draftsmen were not allowed to use CAD systems, etc. So declaring mechanics to be very complicated/complex problem is not very helpful. Of course it is complicated. So is geometry. So is algebra. A more relevant question is how to raise the level of education, skill, and awareness -- broadly, for an average reasonably educated user -- and which tools are helpful in this pursuit. This is what Scan&Solve is all about.
Scan&Solve computes numerical approximation to linear structural (elasticity) problem. It's validity has been established both theoretically and experimentally. Like all software packages, it has some limitations and like all software packages, it can be misused. It is not really helpful to tell me people that their simulations are wrong ... particularly since all simulations are wr0ng, by definition. If you have specific constructive suggestions on how to solve the same problems better, or if you want to share some of your professional wisdom with other users, I am sure that it would be much appreciated and would be very helpful.
Of course tool/software is o.k. but simplicity of software operating is not the same with simplicity of analysis, but "soft is good", exciting. We need to buy it for exploration and deep testing. Good luck!
© 2023 Created by Michael Freytag. Powered by
You need to be a member of Scan-and-Solve for Rhino to add comments!
Join Scan-and-Solve for Rhino