1 / 33

The Philosophy and Physics of the CEM Framework

The Philosophy and Physics of the CEM Framework. Build EM models, construct modeling scenarios, run codes, and visualize results. Factors Driving the Philosophy. Paradigm shifts in the workplace Computational software  Top-level toolkits, approximate methods

Download Presentation

The Philosophy and Physics of the CEM Framework

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. The Philosophy and Physics of the CEM Framework Build EM models, construct modeling scenarios, run codes, and visualize results.

  2. Factors Driving the Philosophy • Paradigm shifts in the workplace • Computational software  Top-level toolkits, approximate methods • Seasoned analysts  Entry-level analysts • Code developers  Code users • Independent workforce  Collaborative workforce • Parochial focus  Inter-department, inter-agency, international focus • Technology shifts in the workplace • Computational ability has outpaced our “understanding” • Easier to generate gigabytes of data, harder to make sense of it • Most analyses now require multiple methods, multiple codes, varying levels of detail, inclusion of measured data, multiple participants • Collaboration is no longer optional; collaborative tools are needed • Data re-use, higher levels of abstraction are required • Pace of change is faster than ever • Management issues in the workplace • Necessary to manage projects, models, data, and engineers • Verification, validation and accreditation require “audit trails” • Decision-makers need to see results differently from engineers

  3. The “Old” Way of Doing Things • A “code-centric” view of CEM • Not conducive to collaboration

  4. Project Manager Maintains overall control of analysis, receives reports on progress and results, retrieves top-level data for decision making and conclusions Configuration Control Verification/validation, accreditation, maintains control over codes, models, and data CAD Modeler Import geometry data, “strip” data to retain EM features, establishes system-level parameters EM Modeler Generates valid, rule-based EM models from CAD data. Builds models of other EM components. Adds EM-specific parameters to models EM Analyst Creates “scenes” from geometrical and EM components. Defines observables, parameter values. Manipulates EM results to obtain engineering quantities Code Developer Conceives, creates, and writes the tools used by the other participants. Stakeholders in a CEM Analysis

  5. All Participants View Problem Differently Collaboration Tools EM Analyst Database Expertise End User Project Manager Toolkit Developer Code Developer CAD Modeler T&E Expertise EM Modeler

  6. The Computational EM FrameworkThe New Way of Doing Things Scenario Design Post Processing & Visualization Model Building Data Repository • Models & Scenarios • Parameters & Observables Users Users Developers Developers Modeling Rules and Guidelines EM to Engr Translation CEM Code Suite Expert Advice Customer Requirements

  7. Framework Design Philosophy • Design tools around roles of the participants. • Let the usersprogram the Framework. • Let the usersextend the Framework’s capability. • Integrate the tools via a data repository. (The “elephant” is the data in all its shapes, sizes, and forms.) • Achieve transparency in running computational tools and other codes. • Provide multiple ways for users to view results. • Satisfy needs of all users, including supervisors, management, and higher level decision makers. • Provide intra-organizational and inter-organizational infrastructure for analysis. • Provide a “place” for a user community.

  8. Quick Tour of the Framework • Model Builder – AutoGridder • Master model, family of models concept • Parameterize geometry at high level • Application Builder – Scene generator • Consistent interface across all tools • Parameterize scenario values • Component View – Post processing • Data manipulation at all levels of detail • Extract “meaning” from the data • SmartView – Graphical Editing and Visualization • Multi-level, multi-view visualizer • Modeling error analyzer • Help Assistant • Place to find information on all the tools • Includes tutorials and how-to’s

  9. Model Builder – BRL-CAD Example Taken from an existing BRL-CAD input file

  10. Master Model Generates Specific Models Master Model - CSG Coarse Mesh – Physical Optics Fine Mesh – Method of Moments Finite Difference Mesh – Interior Analysis

  11. Model Top-Level Parameterization

  12. Application Builder – Create Scenario

  13. App Builder Creates Multiple Scenes Radiation Pattern EM Coupling Near-Field Rad Hazard Communications Range Plot

  14. Export and Launch the Code

  15. Raw CEM Code Output is Non-Intuitive

  16. Component View – Post-processing Data

  17. Typical EM Applications and Observables

  18. SmartView: A 3D Graphical Editor/Visualizer

  19. SmartView: Displaying Surface Currents

  20. SmartView: Analyzing Modeling Errors

  21. SmartView: Selecting Patches for Editing

  22. More Examples – ACAD File Format

  23. SmartView Imports From BYU and STL

  24. SmartView Import from X3D/VRML

  25. SmartView Export to GEMACS

  26. Antenna Pattern Centered on Vehicle

  27. Quickly Execute Component View Again

  28. Help Assistant Contains all Documentation(extensible by user to other codes and other topics)

  29. Putting It All Together (1)(End-to-end use of the CEM Framework) Geometry Data Source • Build EM model • Tweak model • Check for errors • Validate model Validated EM Geometry Model SmartView AutoGridder BRL-to-SV Other Converters Direct Input SmartView

  30. Putting It All Together (2) User Scenario - Sources - Observables • Combine models into “scenes.” • Add sources, ground plane. • Request EM results. • Generate CEM code inputs. • Execute CEM code(s). • Save the EM results. Application Builder Geometry Models EM Results CEM Codes

  31. Putting It All Together (3) User-Requested Engineering Results Geometry Models Engineering Results Component View – Data Post-Processing EM Results

  32. Putting It All Together (4) Engineering Results Geometry Model Presentation Results SmartView

  33. With the CEM Framework, you will be able to … • Perform all aspects of a CEM analysis • Build and mesh models • Construct EM scenarios and run CEM codes • Process data to obtain engineering output • Visualize that data in a variety of ways • Save and re-use models, scenarios, maps, and data • Share/exchange data with other Framework users • Extend/expand the Framework to your needs • Work with engineering quantities, not just raw EM • Become 5x to 10x more productive

More Related