1 / 19

Distributed Testing at CU-NEES Using OpenFresco and SIMCOR

Gary Haussmann. Distributed Testing at CU-NEES Using OpenFresco and SIMCOR. Outline. Distributed Testing Who's in charge? Issues and limitations OpenFresco In analysis In testing SIMCOR Connecting to a test site Sample Testing Configurations. Distributed Testing.

halona
Télécharger la présentation

Distributed Testing at CU-NEES Using OpenFresco and SIMCOR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gary Haussmann Distributed Testing at CU-NEESUsing OpenFresco and SIMCOR CU-NEES 2008 FHT Workshop

  2. Outline • Distributed Testing • Who's in charge? • Issues and limitations • OpenFresco • In analysis • In testing • SIMCOR • Connecting to a test site • Sample Testing Configurations CU-NEES 2008 FHT Workshop

  3. Distributed Testing • Physically distant sites cooperate to perform a test • Combine resources and equipment • Relevant position/force data sent over Internet CU-NEES 2008 FHT Workshop

  4. Who's In Charge? • Someone has to be “in charge” • Start/stop the test at a single site • Send requests, get data from “satellite” locations • Typically the primary analysis site is in charge • But analysis may be “subcontracted” • Satellite sites only perform physical manipulation CU-NEES 2008 FHT Workshop

  5. Issues and Limitations • Timing of overall test • Typically implicit in data transfer • Usually not real-time (speed of light)‏ • Software and Protocols • One protocol is enough • Software versioning • Check the Network • Firewalls, filters, can cause problems • Bandwidth usually not an issue CU-NEES 2008 FHT Workshop

  6. OpenFresco: A Summary • No analysis in OpenFresco • Mostly networking and Some Instrumentation • Designed to be used with analysis tool (OpenSEES etc.)‏ • Combine various objects to achieve the behavior you want • Remote or local hybrid test • Various element types • Various actuator configurations CU-NEES 2008 FHT Workshop

  7. OpenFresco Components • Site • Local or Client & Server • Element • Truss, Frame, TwoNode • Setup • OneActuator or multi-DOF • Handles transforms • Control • Talk to your equipment CU-NEES 2008 FHT Workshop

  8. SIMCORSimulation Coordinator • Built using MATLAB • Inherent access to MATLAB functionality • MATLAB-based GUI during test • Not analysis tool • Embed analysis as a module • ABAQUS, FE-DEAS, OpenSEES, etc. • Configure Modules for Various Protocols • LabView module • OpenFresco1D module • OpenSEES analysis module CU-NEES 2008 FHT Workshop

  9. SIMCOR Modules • Analysis Modules • ABAQUS, FE-DEAS, etc. • Control Modules • LabView • OpenFresco1D • MATLAB CU-NEES 2008 FHT Workshop

  10. OpenFresco or SIMCOR? • Previous software experience • OpenSEES or TCL: OpenFresco • MATLAB: SIMCOR • Legacy analysis results • MATLAB: SIMCOR • OpenSEES: OpenFresco • ABAQUS, FE-DEAS: SIMCOR • CU NEES Site • Both SIMCOR and OpenFresco installed • OpenFresco controller “default” • Access with either tool CU-NEES 2008 FHT Workshop

  11. A Series of Tests • Perform tests of ever-increasing complexity • Local-only with simulated specimen • Local-only with actual specimen • Distributed with simulated specimen(s)‏ • Distributed with actual specimen(s)‏ CU-NEES 2008 FHT Workshop

  12. Local-Only Test • “Server” and “Client” are the same machine • Use a fake specimen with SimUniaxialMaterial CU-NEES 2008 FHT Workshop

  13. Local-Only Hybrid Test • Client/Server on Same Machine • Live Actuator Movement CU-NEES 2008 FHT Workshop

  14. Distributed Dry Run • Analysis at one site, specimen at another • Specimen is simulated with SimUniaxialMaterial CU-NEES 2008 FHT Workshop

  15. Distributed Hybrid Test • Multi-site • Live Actuators • UIUC, SIMCOR • Berkeley, OpenFresco CU-NEES 2008 FHT Workshop

  16. Multi-Site Testing • Three sites • CU, LeHigh, U. of Connecticut • U-Conn performs analysis • CU, LeHigh drive “specimens” CU-NEES 2008 FHT Workshop

  17. Multi-Site Testing • U-Conn runs OpenSEES 1.7.4/OpenFresco 2.5 client • CU runs OpenFresco/xPC Module server • LeHigh run OpenFresco/SCRAMnet Module server • Network Transfer and Campus Firewalls • Manually open a port via paperwork • Find an open port to use CU-NEES 2008 FHT Workshop

  18. Multi-Site Testing • Test Results • Two Specimen Errors CU-NEES 2008 FHT Workshop

  19. Conclusion • Use OpenFresco or SIMCOR for distributed Hybrid Tests • CU-NEES Support Distributed Tests via OpenFresco Server • Testing Process • Start simple, local • Check network connections • Switch to live specimens CU-NEES 2008 FHT Workshop

More Related