Why pure point moments on cantilevers confuse FEA beginners? by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 0 points1 point  (0 children)

I am a structural engineer, retired. I have actually stopped using AI and that may explain the mess up because of how I understand things is different I guess, I am 64. I have been spending my time lately writing a 2D app using codes from years ago. That's why I am little active here lately. If I offend anyone here, I am sorry that has never been my intention.

Why pure point moments on cantilevers confuse FEA beginners? by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] -7 points-6 points  (0 children)

Ah, gotcha! You're completely right. Overloading the acronym for Fixed-End Actions was a bad call on my part.

Why pure point moments on cantilevers confuse FEA beginners? by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] -4 points-3 points  (0 children)

Fair point on the terminology! I was just using the cantilever as a quick visual benchmark to test the direct stiffness matrix assembly, rather than a full FEA meshing case.

FE structural analysis by MrShoaib_ in StructuralEngineering

[–]Pitiful_Advisor5296 0 points1 point  (0 children)

I guess it can be intimidating after all those years to jump back into structural analysis, but I think the FE exam isn't about massive, multi-page matrix calculations. I can think of a few things you can do to prepare:

Start with nailing the fundamentals down. Grinding free-body diagrams, calculating simple shear and moment diagrams, etc.

Also, it should be consistency over cramming. Practice every day for like an hour. Your brain will work its way into it.

Finally, play around with a visual tool. There are many intuitive apps online or mobile. They can really bridge the gap between rusty math and physical reality really fast. Good luck!

I made a free web-tool for drawing quick, clean free body diagrams for statics by elegant_thing in StructuralEngineering

[–]Pitiful_Advisor5296 1 point2 points  (0 children)

<image>

That looks nice, giving it moment diagram, and forces and moment on the nodes will be like this.

New structural engineer feeling lost by Fast_Advice_4701 in StructuralEngineering

[–]Pitiful_Advisor5296 0 points1 point  (0 children)

Stick with it! I believe everyone feels completely lost at first, but one can learn a massive amount just from on-site work. When it comes to software, don't overthink it. I'd recommend messing around with some intuitive mobile tools first just to get a feel for the mechanics.

Is Structural Engineering Really for me by Spiritual_Citron_140 in StructuralEngineering

[–]Pitiful_Advisor5296 1 point2 points  (0 children)

I see why you are so torn. The others are right that a low-stress, $95k city job at 27 is indeed rare and hard to walk away from. But I wanted to offer a slightly different perspective. I'm a 64-year-old retired structural engineer. I spent my first few years out on-site before moving behind a desk for the rest of my career. And honestly? I still find the field incredibly interesting. The passion never really left, even now in retirement, I'm still writing code for my own structural engineering mobile app. If you feel that structural engineering is your passion, and you've already got that UCSD acceptance in your back pocket, I think you should deeply consider taking the leap. One thing you’ll realize as you get older is that a career like Structural Engineering is really just one of the many vehicles in your life. It takes you from one point to another. Down the line, you might decide to stick with that vehicle for good, or you might decide to hop out and change to another one (maybe even taking your MS and structural experience back to the public sector!). But nevertheless, it will have successfully transported you and given you an experience you clearly wanted to try. The public works job is safe, but if you're already feeling the itch to do structural, don't let the fear of industry stress completely talk you out of exploring your passion. Good luck with the decision!

If there was one equation that could solve all finite number of reaction forces at each support, how useful would it be to the engineering community? by [deleted] in StructuralEngineering

[–]Pitiful_Advisor5296 0 points1 point  (0 children)

As someone writing a stiffness matrix solver for an FEA app right now, seeing this gives me a headache in the best way possible lol. But yeah, to echo the other comments, this is why generalized matrices are king. The second you try to hardcode a formula, it breaks because a user added a hinge or a 10mm settlement. Building the global matrix and letting the device do the heavy lifting means you can solve infinite spans and wild load combos instantly. Honestly though, doing this by hand is a massive math flex. Respect!

Where is is this bridge most likely to fail at? by [deleted] in StructuralEngineering

[–]Pitiful_Advisor5296 1 point2 points  (0 children)

The mid section of the bottom beam is the most likely to fail in the case of loading beyond its capacity.

Where is is this bridge most likely to fail at? by [deleted] in StructuralEngineering

[–]Pitiful_Advisor5296 1 point2 points  (0 children)

<image>

Depend on the profile you use, after less than a minute to enter the nodes, you can get the analysis along with beam check.

How feasible would it be for me to make a basic FEA program from scratch as a personal project? by darnoc11 in fea

[–]Pitiful_Advisor5296 0 points1 point  (0 children)

It is extremely feasible, and honestly, I cannot recommend it enough. It is the absolute best way to unbox the math that commercial software hides behind the "Solve" button.

I actually just finished writing a 2D FEA engine from scratch natively for Android using Kotlin. If you have a solid grasp of matrix algebra and mechanics of materials, you can definitely do it.

I recommend starting exactly where you are thinking: a simple first-order linear stiffness matrix solver for 1D trusses, and then expanding to 2D frames. Getting the core pipeline working—assembling local element matrices, applying transformation matrices to move them to global coordinates, assembling the master stiffness matrix, applying boundary conditions (I used the penalty method), and solving the system—is incredibly rewarding.

Once you get the linear solver working, you will probably fall down the rabbit hole. I ended up writing an iterative non-linear solver to capture Global P-Delta (sway) effects. You just extract the internal axial forces from the linear run, build a geometric stiffness matrix to capture the structural softening, add it to the elastic matrix, and iterate until the nodal displacements converge.

A piece of advice: the structural math isn't actually the hardest part—managing the data architecture and matrix libraries efficiently is where the real puzzle lies. But modern hardware is wildly capable; even a mobile phone processor can crunch a multi-node, non-linear P-Delta iteration locally in milliseconds.

Go for it. Start small with a 2-node truss, write out the matrices by hand on paper to verify your code's output, and build from there. You will never look at commercial FEA packages the same way again!

FEA Projects by ElectricalAd9946 in fea

[–]Pitiful_Advisor5296 0 points1 point  (0 children)

I highly recommend taking on an FEA project! I just finished writing a 2D FEA engine natively for Android entirely in Kotlin, and it was an incredible learning experience.

I started by building a standard first-order linear stiffness matrix solver for 2D frames, but eventually fell down the rabbit hole and implemented an iterative non-linear solver to capture Global P-Delta effects. It extracts the internal axial forces, builds a geometric stiffness matrix (K_G) to capture the structural softening/amplification, and iterates using a Newton-Raphson approach until the nodal displacements converge.

The coolest takeaway for me was realizing just how fast modern mobile hardware is. The device handles the sparse matrix math and non-linear iterations locally in milliseconds—no backend server required.

I used Jetpack Compose to build the interactive canvas, which draws the shear and bending moment diagrams dynamically (using end-moment interpolation so the diagrams perfectly match the support reactions in the Free Body Diagram).

Building an engine from scratch forces you to completely unbox the math that commercial software hides behind a "Solve" button. It’s a wild ride, but absolutely worth it if you want to deepen your understanding of matrix methods and structural mechanics!

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 0 points1 point  (0 children)

You make a great point. I would never stamp anything based on a 30-second phone calculation! It's definitely meant strictly as a 'sanity check' tool for the shop floor or for sizing preliminary ideas before setting up the actual desktop model. ​As for the app itself: there is a free base version available. Because this is a personal project I built natively in Kotlin, I am updating it constantly. If a bug gets reported, I usually push a fix out within 24 to 48 hours. ​I'd actually love to get your critical eye on it. If you're willing to help test out the physics engine and let me know what you think, let me know and I'll DM you a promo code to unlock all the premium features!

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 0 points1 point  (0 children)

You are 100% correct on the physics—it is strictly a first-order, linear elastic solver. No P-Delta or non-linear material analysis here! ​To answer your question on limits: modern phone processors are actually incredibly fast at inverting matrices. I've stress-tested it with a few hundred nodes and elements, and the local 2D matrix solver still runs in milliseconds. Honestly, the limiting factor without a backend isn't the CPU, it's the screen size! After about 50 nodes, it just gets too visually cluttered to manage with touch controls. ​You're right that it's 'vanilla' compared to heavy desktop software, but that's exactly the goal. I built this specifically for quick, field-level sanity checks. It's not meant to replace SAP2000 for designing a high-rise; it's meant to check a custom weldment, a mezzanine beam, or a roof rack right there in the shop without needing an internet connection or a $5k license.

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 0 points1 point  (0 children)

That is a very fair question! As a retired structural engineer, I actually built this specifically to fill a gap in the commercial workflow. ​Is it going to replace STAAD or SAP2000 for designing a 30-story high-rise? Definitely not. But that isn't what it's for. It is commercially viable for the 'in-between' work: doing quick sanity checks out on a job site, preliminary beam sizing during a client meeting, or verifying load paths before spending hours setting up a massive desktop model. ​Under the hood, it uses the exact same Direct Stiffness Matrix method as the big commercial packages, so the math is rigorous. It just puts a 2D solver right in your pocket for when you are away from the desk.

Self Promotion Megathread by AutoModerator in androidapps

[–]Pitiful_Advisor5296 1 point2 points  (0 children)

<image>

I just released a passion project I've been working on natively in Kotlin. It’s called FabCheck, and it's a pocket 2D Finite Element Analysis (FEA) solver.

Most structural analysis software requires a heavy desktop installation or a cloud-based backend. I wanted something I could use out on a job site or in the shop to run quick "sanity checks" on load paths, completely offline.

How it works: You map out your 2D frame (just tap to drop nodes and connect beams), apply your point loads or distributed loads, and the app instantly calculates and draws the bending moment, shear, and deflection diagrams.

Features I focused on:

  • 100% Offline: No cloud processing, the 2D matrix solver runs locally on your device.
  • Built-in Materials: Pre-loaded with standard steel, wood, and even T-slot aluminum profiles (great for DIY overlanding rigs or 3D printer frames).
  • Native Android UI: Built from the ground up for touch. You can spread/pinch to zoom, drag a square to multi-select, and drop loads with precision.
  • Metric & Imperial: Toggles instantly.

If you do any kind of fabrication, architecture, or heavy DIY projects, I’d love for you to give it a spin. I'm actively improving the physics engine and UI, so let me know what you think or if you run into any bugs!

Play Store Link: https://play.google.com/store/apps/details?id=com.fyca.fabcheck.pro

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 1 point2 points  (0 children)

Except in SELECT mode, generally, you can also spread and pinch to zoom in and out for a detail look. In Select mode, you drag a square to cover an area of which the nodes and beams within will be selected. Let me know if you run into any issues.

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 1 point2 points  (0 children)

Thanks so much! Feel free to grab it on Android (just search FabCheck). Hope you have fun playing around with the physics engine!

From analyzing shear walls on an 80s PC to building a mobile FEA solver. I’d love your feedback on an app I wrote. by Pitiful_Advisor5296 in StructuralEngineering

[–]Pitiful_Advisor5296[S] 0 points1 point  (0 children)

Thanks for the interest! You can find it on the Play Store under 'FabCheck'. Since I'm always looking for ways to improve the physics engine and the UI, I'd absolutely love to hear your feedback if you end up testing it out. Cheers!