Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
RAM | STAAD | ADINA
  • Product Communities
RAM | STAAD | ADINA
RAM | STAAD | ADINA Wiki In Memory Member Splitting and Node Merging
    • Sign In
    • -RAM | STAAD | ADINA Wiki
      • +ADINA
      • +iTwin Analytical Synchronizer_
      • +Structural Analysis Support Solutions
      • +RAM Concept
      • +RAM Connection
      • +RAM Elements
      • +RAM SBeam
      • +RAM Structural System
      • -STAAD.Pro
        • +How is STAAD.Pro licensed
        • +Installation Requirements
        • +(+) Revision History
        • -(+) STAAD.Pro Support Solutions
          • +STAAD.Pro General [FAQ]
          • +STAAD.Pro Verification Documents
          • STAAD.Pro Safety Related Features
          • STAAD Product Releases in December 2018 and Associated Licensing Changes
          • +Procedure for Downloading STAAD.Pro CE
          • +STAAD.Pro Developing The Model [FAQ]
          • +STAAD.Pro Import/Export [FAQ]
          • +STAAD.Pro Installation/Licensing Solutions
          • +STAAD.Pro Miscellaneous Solutions
          • +STAAD.Pro Miscellaneous [FAQ]
          • +STAAD.Pro Postprocessing FAQ's
          • +STAAD.Pro Postprocessing Solutions
          • +STAAD.Pro TechNotes [TN]
          • What is panel in physical modeler? How to model the panel and how to add loading on it?
          • -(+) Analytical Modeling workflow
            • +STAAD.Pro Analysis Solutions
            • +STAAD.Pro Design Solutions
            • +STAAD.Pro General Solutions
            • -STAAD.Pro Import/Export Solutions
              • Design Parameters
              • Export a Solid Slab or Wall
              • Getting beams generated in STAAD.Pro to come into Tekla at top of steel
              • Import Model in STAAD.Pro
              • Importing AutoPIPE files into STAAD.Pro CONNECT Edition through Pipelink
              • In Memory Member Splitting and Node Merging
              • ISM No STAAD filename provided Error
              • Mapping Structural Modeler/Power Structural Modeler Code Names To STAAD Section .MDB Files
              • STAAD.Pro ISM Import Error from Network Drive
              • Structural Modeler MVBA STAAD/RAM Data Exchange does not Work
              • When a .UPT file is imported to STAAD.Pro user table manager, the below pop-up message appears. Why the error is coming and how to rectify it?
            • +STAAD.Pro Modeling Solutions
            • +STAAD.Pro OpenSTAAD
          • +(+) Connection Design workflow
          • (+) Physical Modeling workflow
          • (+) Postprocessing workflow
          • +(+) Steel AutoDrafter worfklow
        • +STAAD.Pro CONNECT Edition - Tips & Tricks
        • +(+) STAAD.Pro Download/Installation/Security/Performance
        • +(+) STAAD.Pro Known Issues
        • +(+) STAAD.Pro Licensing Solutions
        • +(+) STAAD.Pro Webinars/Videos//Events
      • +STAAD Foundation Advanced
      • +STAAD Advanced Concrete Design (RCDC)
      • +STAAD.building
      • +STAAD RCDC FE
      • +Scenario Services
      • +STAAD.offshore
      • +Limcon
      • +Microstran
      • +MStower
      • +Structural Dashboard
      • +Structural WorkSuite
    • +RAM | STAAD Learning Resources
    • Simplifications to Bentley's Engineering Simulation Software Licenses

     
     Questions about this article, topic, or product? Click here. 

    In Memory Member Splitting and Node Merging

       
      Applies To 
       
      Product(s): STAAD.Pro
      Version(s): All
      Environment:  N/A
      Area:  Import Export Solutions
      Subarea:  Import/Export
      Original Author: Jason Chickneas
    Bentley Technical Support Group
       

    In Memory Member Splitting and Node Merging


    Description:


    In Bentley Structural V8i, the ability to export to STAAD.Pro without creating an analysis model in Bentley Structural was introduced.  This is achieved with the new "Physical Only" option on the export dialog.  The analysis model is said to be created "in memory" upon export to STAAD.  This topic describes how the analytical elements are split and nodes merged "in memory".


    To correctly model connections between the end of one member and the end of another it is necessary to connect the respective analytical elements by a common node. Similarly, to correctly model connections between the end of one member and another at some arbitrary point along its length where no node exists, it is necessary to divide a segment into two by inserting a node. When synthesizing an analysis model from a physical model, differences in member cross-sections cause the ends of the resulting wireframe elements to be disconnected. To determine where connections should exist in the wireframe analysis model, a tolerance value is used. Any two member ends (nodes) which have a distance less than the tolerance value will be merged. Similarly, any node, within the tolerance distance from a member, will be projected onto the member and the member will be split into two.


    Advantages to the "Physical Only" option:

    • Ability to roundtrip structural objects in reference file attachments.

    • It is no longer necessary to maintain the analysis model in Structural Modeler


    Disadvantages:

    • The analysis model: loads, supports, member end releases, element and node ids are not persisted and therefore re-generated for each subsequent export

    Terminology:

    Member Splitting - The process of dividing a member's analytical representation in multiple segments by inserting nodes between the two end nodes.

    Node Merging - The process of replacing the end node of a member with a nearby node which is connected by another member such that a common joint is created and the total number of nodes is reduced.

    Use Cases:


    Figure 1 - Node Merging


    Figure 2 - Member Splitting


    Figure 3 - Combined Merging and Splitting


    Figure 4 - Setting the node tolerance

    Example:

     


    Figure 5 - Small building model with node tolerance set to zero; members 5 and 6 are NOT split and there are disconnected nodes at the tops of columns


    Figure 6 - Same small building model as in Figure 5 above exported with node tolerance set to three (3) inches; members five(5) and six (6) have been split and all members connect to a single node at the top of each column.

     

    • import
    • AECOsim Building Designer (ABD)
    • Share
    • History
    • More
    • Cancel
    • Steve Crabtree Created by Steve Crabtree
    • When: Tue, Jun 21 2016 10:53 AM
    • Seth Guthrie Last revision by Bentley Colleague Seth Guthrie
    • When: Fri, Jan 6 2017 6:59 PM
    • Revisions: 7
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies