-
Notifications
You must be signed in to change notification settings - Fork 115
Description
Totally respect that the application itself is trying to be unit agnostic - even though it does reference metric/SI in a few places...
I've been trying to use anaStruct for the last few hours, but have been finding myself sifting through source, and the couple of examples there are to reconcile what the relationship between my input/output units are....
For example, if my coordinate system is in mm, do I put my forces in as kN? If my Young's Modulus is 210GPa, do I have to convert my EI? How do I convert my EI to match the input coordinate system units?
If the program is unitless/unit agnostic, which is totally fair, maybe a page in the docs laying out - here are recommended input units for parameters so that all the calcs under the hood are aligning in orders of magnitude(in imperial and/or metric).
Ironically, it's the metric notes (hea/ipe, sectionbase/properties.py and Ritchie Vink's nonlinear water example) that have allowed me to reconcile what the input/output units are/should be. It isn't necessarily clear, it's taken a good amount of reverse engineering to figure out what should be what and conversions that need to happen.