180 likes | 320 Views
January 2009. MAST – Multi Agent System for Structural Design. Cherif Branki - UWS. Introduction Structural Optimisation Multi-Agent Systems Case Study Conclusion Future Work. Content. Agent Technology + Structural Design Optimisation = fun. Introduction. Best “possible” design
E N D
January 2009 MAST – Multi Agent System for Structural Design Cherif Branki - UWS
Introduction • Structural Optimisation • Multi-Agent Systems • Case Study • Conclusion • Future Work Content
Agent Technology • + • Structural Design Optimisation • = • fun Introduction
Best “possible” design • Given criteria and constraints • Transferral in mathematical domain • Powerful search strategy • Area of project collaborators Optimisation and Design
Search for optimum properties of structural components • Geometrical Optimisation • Topological Optimisation Structural Optimisation
Deformable Body • Volume V • Surface S • Traction t at St • Su Fixed • Sf Free Structural Design
Two alternatives • Shape • Given material, best surface configuration • Topology • Single: Material variable density • Multiple: Cavities in V • Discrete: structural elements Structure of problem
Topology • Set of components (Vocabulary) • Connections (Grammar) • Geometry • Coordinates • Components • Attributes Three Level Optimum Design
Multi-Agent System • Graph transformations • Structural Optimum Design • Evolutionary Computing Technologies
Graph-based description of the structure • Agents optimising each level • Agent collaboration strategy • Testing the prototype software • Prepare final release of the MAST • Published in journals • Mobile Adaptation Status so far
Most abstract to least • Topology to Geometry to Components • Influence in both directions • Expensive to solve • Ignore dependencies • Solve sequentially Mutual coupling Agent Agent
Composite Knowledge Representation • Composition graph for structure • Solutions generated by Graph Grammar • Layout of Structure • Hierarchical composition graphs Graph-based representation
Influenced by internal hCP structure • Monolithic prototype software • No connection between the three levels • Easily extendable for future additions • bottom‑up approach Agent Architecture
Agent server • Factory registration • Clients connection • Multiple factories and multiple clients Design
SD and MAS work well • Promising approach • Implementation done • Mobile implementation • Performance optimisation Conclusion
Questions? Thank You