{"id":1272,"date":"2026-03-05T15:09:25","date_gmt":"2026-03-05T15:09:25","guid":{"rendered":"https:\/\/inventorics.com\/?post_type=portfolio&p=1272"},"modified":"2026-06-24T15:11:01","modified_gmt":"2026-06-24T15:11:01","slug":"bike-frame-pattern-4-manual","status":"publish","type":"portfolio","link":"https:\/\/inventorics.com\/?portfolio=bike-frame-pattern-4-manual","title":{"rendered":"Bike frame pattern 4 – manual"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

The definition is structured into 5 sections: <\/p>\n\n\n\n

    \n
  1. Wasp aggregation <\/li>\n\n\n\n
  2. Inventory sorting<\/li>\n\n\n\n
  3. Part placement<\/li>\n\n\n\n
  4. Kangaroo simulation<\/li>\n\n\n\n
  5. Postproduction, evaluation, and labeling <\/li>\n<\/ol>\n\n\n\n
    \"\"
    Geometries in Rhino workspace that are referenced in the definition<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n
    \"\"
    Section 1 in detail<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    In section 1, a Wasp aggregation is set up with a standard proto-part. When you open the associated rhino file, the part geometry is automatically loaded from rhino model space (a).
    At section b) points and lines to define part connections are referenced in the containers inside the purple group, and then\u2014together with geometry\u2014compiled as a wasp part.
    In section c) connection rules are defined inside the white panels, together with the positions of connection points and lines these rules are critical for and finally all components are combined to construct a stochastic aggregation (d) with a bounding volume from rhino workspace set as global constraint.<\/p>\n\n\n\n

    When you switch visible the component highlighted in the screenshot above, the preliminary aggregation of identical proto-parts is previewed in Rhino model space.<\/p>\n\n\n\n

    \"\"
    Wasp <\/sup><\/em>proto-part aggregation<\/em><\/sup><\/figcaption><\/figure>\n\n\n\n

    By altering the bounding box volume in Rhino workspace, the extents of the aggregation can be changed. For the pattern to remain a flat interconnected mesh, it is important to keep the height of the box volume the same and only modify length and width (Non-rectangular geometries would also work). Parts from the inventory are automatically duplicated when the bounding box is larger and the number of parts in the pattern exceeds the amount of inventory parts. When you go very large, the number of parts set at the wasp aggregation in section 1 may also be adjusted.<\/p>\n\n\n\n

    \"\"
    Section 2 in detail<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    In section 2, the inventory of 3D scanned bicycle frames is mapped to the Wasp proto-part aggregation to replace the uniform placeholders.
    In section a), you find a catalog of bicycle frames as curves (center-line axes) and meshes internalized in two separate containers.
    in section b) the inventory is split in two lists, separating diamond frame type and step-through frames.
    At c only those center-line axes are picked that are required for connections in the predefined aggregation pattern (“pattern4”) saved with this file, the selected axes are modified to exactly fit within intersections with other axes (e) and offset to define the distance between connected pipes in the aggregation (f).
    In section d) parts in the inventory are randomly jittered using the slider highlighted in blue, at g) parts are mapped to each the positions of each proto-part.<\/p>\n\n\n\n

    \"\"
    Section 3 in detail<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    In section 3, data from the wasp aggregation graph is used to set up connections and alignment constraints for the Kangaroo physics simulation in section 4.
    A graph defines a topology of connections, each node in the graph represents a part, and lines between nodes represent connections. Besides a graphical representation of connectivity as lines and vertices (screenshot below), the output of the graph components are synchronous lists. Each list contains entries for each connection in the graph, listing part indices at start and end, as well as connection indices at start and end of connections. This information is used to assign relationships between geometries that are later translated into constraints for a Kangaroo simulation, this determines which parts are connected and eg. which frame profiles should co-align. <\/p>\n\n\n\n

    \"\"
    Parts with preview of connection graph in green<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    At the beginning in section a), different instances of the aggregation graph component output different sub-sets of the graph dependent on which connections are called (specified by Wasp rules) at the connection filter input “CR”.
    At b) parts along the pattern edge are selected to place step-through frames (because in this frame type, the top tube is missing, they can only be placed at the boundary).
    At the other end (c) preconfigured part geometries (axes and points) are sorted according to the connection graph and fed into Kangaroo constraints.<\/p>\n\n\n\n

    \"\"
    Section 4 in detail<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    In section 4 a physics simulation with Kangaroo 3D is set up. First, parts as rigid bodies and constraints for connections and co-alignment are defined (a) based on the connection graph information from the previous section 3.
    These are compiled and fed into a Kangaroo simulation component (“Kangaroo Solver”) (b). The simulation can be started and stopped by switching the toggle, and it is reset with the button above.
    Alternatively, the “Zombie Solver” above can be activated for simulation. Be careful, the model will freeze until the simulation is resolved, you will not see the form finding process in real time, and dependent on the size of your model this can take a few seconds! It is recommended to disable the standard solver before you try the Zombie.
    Dependent on which solver you use, the output is channeled for further processing (c).<\/p>\n\n\n\n

    \"\"
    Section 5 in detail<\/sup><\/em><\/figcaption><\/figure>\n\n\n\n

    Finally, in section 5 results are visualized. At first the preview of the component highlighted in section a) needs to be activated to visualize the 3D scanned bicycle frame parts after simulation colored by instance. The component inside the red group next to “scan names” displays part names.
    In section b) below, co-alignment axes, deviation angle tags at each connection, and global deviation values can be displayed.(highlighted from left to right).
    In section c), connection overlap can be displayed as aligned dimensions and with the component inside the red group markings for placing connectors are created (leave this disabled during Kangaroo simulation for calculation speed).<\/p>\n\n\n\n

    This is what it looks like when you switch on all the display items mentioned above:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    If you want to play with modifications of the overall form, you could drag parts with left mouse button while the simulation is active and running (does not work nicely with MacOS). The aggregation will behave like a fabric that can be bent and shaped, as a reference see also this entry on our blog<\/a><\/p>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    The definition is structured into 5 sections: In section 1, a Wasp aggregation is set up with a standard proto-part. When you open the associated rhino file, the part geometry is automatically loaded from rhino model space (a). At section b) points and lines to define part connections are referenced in the containers inside the […]<\/p>\n","protected":false},"featured_media":1274,"comment_status":"closed","ping_status":"closed","template":"","portfolio_cat":[51],"portfolio_skill":[],"class_list":["post-1272","portfolio","type-portfolio","status-publish","has-post-thumbnail","hentry","portfolio_cat-manuals"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/portfolio\/1272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/portfolio"}],"about":[{"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/types\/portfolio"}],"replies":[{"embeddable":true,"href":"https:\/\/inventorics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1272"}],"version-history":[{"count":7,"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/portfolio\/1272\/revisions"}],"predecessor-version":[{"id":1344,"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/portfolio\/1272\/revisions\/1344"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/inventorics.com\/index.php?rest_route=\/wp\/v2\/media\/1274"}],"wp:attachment":[{"href":"https:\/\/inventorics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1272"}],"wp:term":[{"taxonomy":"portfolio_cat","embeddable":true,"href":"https:\/\/inventorics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fportfolio_cat&post=1272"},{"taxonomy":"portfolio_skill","embeddable":true,"href":"https:\/\/inventorics.com\/index.php?rest_route=%2Fwp%2Fv2%2Fportfolio_skill&post=1272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}