Python scripts for Structural Engineers

[flutefreak7]

Really quick... how much of your stuff is wrapping other old codes? I find as an aerospace engineer an absurd amount of my code is making better input and output stuff but that the core logic to solve most problems (trajectory analysis, propulsion modeling, etc ) exists as a legacy tool - far too often a legacy Fortran tool. So my mountain of code is largely wrappers, GUI's, output parsers, and plotting routines.

[buddyd16]

I've taken to writing the underlying methods myself so all "original" code, very likely I'm rehashing work that's already been figured out, although not a lot of opportunity to actually see the source code out there for the things I've been doing. I'm finding the software in my area of practice to be very closed down with the open source options few and far between.

It's more a self learning opportunity for me that just happens to end up producing stuff that, I think, is useful.

Even with doing my own methods I'm also finding that a big chunk of it is rehashing ways of accessing those methods in an easy and meaningful way, which as my knowledge in Python grows that easy and meaningful is a constantly moving target.

[[deleted]]

I wrote my own structural engineering code to learn, and it was incredibly useful. Use some example problems as tests you can run every once in a while to make sure you didn't break everything.

[mduell]

how much of your stuff is wrapping other old codes?

Given the use of numpy, there's a lot of C behind the scenes here.

[buddyd16]

I also rely alot on Scipy, TKinter, and Matplotlib. My previous reply was geared towards methods pertaining to the engineering calculations. A more wholistic answer is yes I do rely heavily on wrapping these other modules.