Finished physical members

Author: JWock82

README.md

@@ -18,6 +18,7 @@ An easy to use elastic 3D structural engineering finite element analysis library
 * Member point loads, linearly varying distributed loads, and nodal loads are supported.
 * Classify loads by load case and create load combinations from load cases.
 * Produces shear, moment, and deflection results and diagrams for each member.
+* Automatic handling of internal nodes on frame members (physical members).
 * Tension-only and compression-only elements.
 * Spring elements: two-way, tension-only, and compression-only.
 * Spring supports: two-way and one-way.
@@ -33,11 +34,11 @@ As I've gotten into the structural engineering profession, I've found there's a
 
 1. Accuracy: There are no guarantees PyNite is error free, but accuracy and correctness are a priority. When bugs or errors are identified, top priority will be given to eliminate them. PyNite's code is frequently reviewed, and its output is tested against a suite of textbook problems with known solutions using continuous integration (CI) anytime a change to the code base is made. If you do happen to find an error, please report it as an issue.
 
-2. Simplicity: There are other finite element alternatives out there with many more capabilities, but they are often lacking in documentation, written in outdated languages, or require extensive knowledge of finite element theory and/or element formulations to use. PyNite is not intended to be the most technically advanced solver out there. Rather, the goal is to provide a robust yet simple general purpose package.
+2. Simplicity: There are other finite element alternatives out there with many more capabilities, but they are often lacking in documentation, written in difficult languages, or require extensive knowledge of finite element theory and/or element formulations to use. PyNite is not intended to be the most technically advanced solver out there. Rather, the goal is to provide a robust yet simple general purpose package.
 
-4. Improvement: I plan to continue supporting PyNite for many years to come. There are a lot of pieces I'd like to add to PyNite going forward. There's a lot of potential to create extensions as well to solve all kinds of engineering problems. There are more problems to solve than I have time for, so some priorities will have to be made. The plan is to keep PyNite mainstream, adding core functionality first. Occasionally however I may just add what interests me at the time.
+4. Improvement: I plan to continue supporting PyNite for many years to come. There are a lot of pieces I'd like to add to PyNite going forward. There's a lot of potential to create extensions as well to solve all kinds of engineering problems. There are more problems to solve than I have time for, so some priorities will have to be made. The plan is to keep PyNite mainstream, adding core functionality first.
 
-5. Collaboration: The intent is to keep PyNite free and open source. This will encourage future development and contributions. Keeping it open source will allow anyone to inspect and improve the code it runs on. If you see an area you think you can help PyNite improve in you are encouraged to contribute. I'd like to get PyNite doing a lot more. Don't be offended if I'm a little slow to accept your contributions. FEA is a very technical subject and accuracy is extremely important to me. Sometimes I'm a little slow understanding both FEA and Python and it takes some time for me to comprehend what's being proposed. I also have a young family to take care of that takes first priority.
+5. Collaboration: The intent is to keep PyNite free and open source. This will encourage future development and contributions. Keeping it open source will allow anyone to inspect and improve the code it runs on. If you see an area you can help PyNite improve in you are encouraged to contribute.
 
 # Support
 Whether you just need help getting started with PyNite, or are looking to build something more complex, there are a few resources available:
@@ -64,7 +65,7 @@ PyNite depends on the following packages:
 # What's New?
 
 v0.0.67
-* Added physical members. Members now automatically detect internal nodes.
+* Added physical members. Members now automatically detect internal nodes and subdivide themselves and their loads.
 * Refactoring: deprecated old method names for member results. You may now have some errors show up if you still try to get member results using the old method names.
 * Bug fix for P-Delta analysis. Global displacements were correct, but member internal forces were neglecting the geometric stiffness matrix. The impact of this bug was minimal, since the strain induced by correct global displacements was still being considered prior to this update. You should see a slight change to member P-Delta results.
 * Code simplification for P-Delta analysis.

Testing/__init__.py

@@ -11,7 +11,7 @@
 # Use warnings flag to suppress the PendingDeprecationWarning 
 # from numpy.matrix
 # unittest.main(warnings='ignore')
-test_suite = unittest.TestLoader().discover("Testing", pattern='test_AISC*.py')
+test_suite = unittest.TestLoader().discover("Testing", pattern='test_*.py')
 
 # `TextTestRunner` does not exit the module. CI will get confused unless we save the result
 # and send the proper exit code.

Testing/test_AISC_PDelta_benchmarks.py

@@ -13,8 +13,8 @@
 
 class Test_AISC_Benchmark(unittest.TestCase):
     """
-    AISC's benchmark problems used to determine if a second order analysis 
-    procedure is rigorous enough.
+    AISC's benchmark problems used to determine if a second order analysis procedure is rigorous
+    enough.
     """
 
     def setUp(self):
@@ -27,7 +27,7 @@ def tearDown(self):
         # Reset the print function to normal
         sys.stdout = sys.__stdout__
 
-    def test_AISC_Benchmark_PhysMember(self):
+    def test_AISC_Benchmark(self):
 
         # Create the cantilever model
         cantilever = FEModel3D()
@@ -44,7 +44,7 @@ def test_AISC_Benchmark_PhysMember(self):
         num_nodes = 6
         for i in range(num_nodes):
             # Add nodes
-            cantilever.add_node('N' + str(i+1), 0, i*L/6, 0)
+            cantilever.add_node('N' + str(i+1), 0, i*L/(num_nodes - 1), 0)
 
         # Add the member
         cantilever.add_member('M1', 'N1', 'N6', E, G, I, I, 200/12**4, 10/12**2)
@@ -61,13 +61,13 @@ def test_AISC_Benchmark_PhysMember(self):
         # Perform 2nd order analysis
         cantilever.analyze_PDelta()
 
-        from PyNite.Visualization import Renderer
-        renderer = Renderer(cantilever)
-        renderer.annotation_size = 0.5
-        renderer.window_width = 750
-        renderer.window_height = 750
-        renderer.deformed_shape = True
-        renderer.render_model()
+        # from PyNite.Visualization import Renderer
+        # renderer = Renderer(cantilever)
+        # renderer.annotation_size = 0.5
+        # renderer.window_width = 750
+        # renderer.window_height = 750
+        # renderer.deformed_shape = True
+        # renderer.render_model()
 
         # The moment at the base of the column
         calculated_moment = cantilever.Nodes['N1'].RxnMZ['Combo 1']
@@ -80,56 +80,6 @@ def test_AISC_Benchmark_PhysMember(self):
         Mmax = H*L*(math.tan(alpha)/alpha)
         ymax = H*L**3/(3*E*I)*(3*(math.tan(alpha)-alpha)/alpha**3)
 
-        # Compare the calculation results
-        # self.assertAlmostEqual(calculated_moment/Mmax, 1.0, 1)
-        # self.assertAlmostEqual(calculated_displacement/(ymax*12), 1.0, 1)
-    
-    def test_AISC_Benckmark_Segments(self):
-        # Create the cantilever model
-        cantilever = FEModel3D()
-
-        # Define the column and its properties
-        L = 20 # ft
-        H = 5 # kips lateral load
-        P = 100 # kips axial load
-        G = 11200*12**2 # shear modulus (ksf)
-        E = 29000*12**2 # modulus of elasticity (ksf)
-        I = 100/12**4 # moment of inertia (ft^4)
-
-        # Break the column into several segments in order to capture P-little-delta effects
-        num_segs = 5
-        num_nodes = num_segs + 1
-        for i in range(num_nodes):
-            # Add nodes
-            cantilever.add_node(str(i+1), 0, i*L/(num_segs), 0)
-
-        for i in range(num_segs):
-            # Add members between nodes
-            cantilever.add_member(str(i+1), str(i+1), str(i+2), E, G, I, I, 200/12**4, 10/12**2)
-
-        # Add a fixed support at the base of the column
-        cantilever.def_support('1', True, True, True, True, True, True)
-
-        # Add a -10 kip axial load to the top of the column
-        cantilever.add_node_load(str(num_nodes), 'FY', -P)
-
-        # Add a 5 kip lateral load to the top of the column
-        cantilever.add_node_load(str(num_nodes), 'FX', H)
-
-        # Perform 2nd order analysis
-        cantilever.analyze_PDelta()
-
-        # The moment at the base of the column
-        calculated_moment = cantilever.Nodes['1'].RxnMZ['Combo 1']
-
-        # the deflection at the top of the column
-        calculated_displacement = cantilever.Nodes[str(num_nodes)].DX['Combo 1']*12
-
-        # Calculate the AISC benchmark problem solution:
-        alpha = (P*L**2/(E*I))**0.5
-        Mmax = H*L*(math.tan(alpha)/alpha)
-        ymax = H*L**3/(3*E*I)*(3*(math.tan(alpha)-alpha)/alpha**3)
-        
         # Compare the calculation results
         self.assertAlmostEqual(calculated_moment/Mmax, 1.0, 1)
         self.assertAlmostEqual(calculated_displacement/(ymax*12), 1.0, 1)