using artificial intelligence and transprecision
play

Using Artificial Intelligence and Transprecision Computing for - PowerPoint PPT Presentation

1 st R-CCS International Symposium @ Kobe, Japan Feb. 18, 2019 Using Artificial Intelligence and Transprecision Computing for Accelerating Finite-Element Urban Earthquake Simulation Tsuyoshi Ichimura, Kohei Fujita, Takuma Yamaguchi, Akira


  1. 1 st R-CCS International Symposium @ Kobe, Japan Feb. 18, 2019 Using Artificial Intelligence and Transprecision Computing for Accelerating Finite-Element Urban Earthquake Simulation Tsuyoshi Ichimura, Kohei Fujita, Takuma Yamaguchi, Akira Naruse, Jack C. Wells, Thomas C. Schulthess, Tjerk P. Straatsma, Christopher J. Zimmer, Maxime Martinasso, Kengo Nakajima, Muneo Hori, Lalith Maddegedara

  2. Smart cities • Controlling cities based on real-time data for higher efficiency • Computer modeling via high-performance computing is expected as key enabling tool • Disaster resiliency is requirement; however, not established yet Example of highly dense city: Tokyo Station district 2

  3. Fully coupled aboveground/underground earthquake simulation required for resilient smart city 3

  4. Earthquake modeling of smart cities • Unstructured mesh with implicit solvers required for urban earthquake modeling • We have been developing high-performance implicit unstructured finite-element solvers (SC14 & SC15 Gordon Bell Prize Finalist, SC16 best poster) • However, simulation for smart cities requires full coupling in super-fine resolution • Traditional physics-based modeling too costly • Can we combine use of data analytics to solve this problem? SC14, SC15 & SC16 solvers: Fully coupled ground-structure simulation with underground structures ground simulation only 4

  5. Data analytics and equation based modeling • Equation based modeling • Highly precise, but costly • Data analytics • Fast inferencing, but accuracy not as high • Use both methods to complement each other Phenomena Data analytics Equation based modeling 5

  6. Integration of data analytics and equation based modeling • First step: use data generated by equation based modeling for data analytics training • Use of high-performance computing in equation based modeling enables generating very large amounts of high quality data • We developed earthquake intensity prediction method using this approach (SC17 Best Poster) • SC17 SC14: equation based modeling • SC15: equation based modeling Phenomena • SC16: equation based modeling • SC17: equation based modeling for AI Data analytics Equation based Simulated (with better modeling data for prediction) training 6

  7. Integration of data analytics and equation based modeling • We extend this concept in this paper: train AI to accelerate equation based modeling SC18 Phenomena • SC14: equation based modeling • SC15: equation based modeling • SC16: equation based modeling Data Equation based • SC17: equation based modeling for AI analytics AI for accelerating modeling • SC18: AI for equation based modeling equation based (25-fold speedup solver from without AI) 7

  8. Earthquake modeling for smart cities • By using AI-enhanced solver, we enabled fully coupled ground- structure simulation on Summit a) Overview of city model c) Close up view of city model e) Displacement response 8 d) Displacement response of city of underground structure b) Location of underground structure

  9. Difficulties of using data analytics to accelerate equation based modeling • Target: Solve A x = f • Difficulty in using data analytics in solver • Data analytics results are not always accurate • We need to design solver algorithm that enables robust and cost effective use of data analytics, together with uniformity for scalability on large-scale systems • Candidates: Guess A -1 for use in preconditioner • For example, we can use data analytics to determine the fill-in of matrix; however, challenging for unstructured mesh where sparseness of matrix A is nonuniform (difficult for load balancing and robustness) ➡ Manipulation of A without additional information may be difficult… 9

  10. Designing solver suitable for use with AI • Use information of underlying governing equation • Governing equation’s characteristics with discretization conditions should include information about the difficulty of convergence in solver • Extract parts with bad convergence using AI and extensively solve extracted part Phenomena Equation based modeling Governing equation Data analytics Discretization A x = f 10

  11. Solver suitable for use with AI AI preconditioner – use to roughly solve A z = r • Transform solver such PreCG c (1 st order tetrahedral mesh) that AI can be used Approximately solve A c z c = r c robustly Loop until converged Use z c as initial solution • Select part of domain to be extensively solved in part (1 st order tetrahedral mesh) PreCG c adaptive conjugate Approximately solve A cp z cp = r cp gradient solver Use z cp as initial solution • Based on the governing PreCG (2 nd order tetrahedral mesh) equation’s properties, Approximately solve A z = r part of problem with bad convergence is selected Use z for search direction using AI Adaptive Conjugate Gradient iteration (2 nd order tetrahedral mesh) 11

  12. How to select part of problem using AI • In discretized form, governing equation becomes function of material property, element and node connectivity and coordinates • Train an Artificial Neural Network (ANN) to guess the degree of difficulty of convergence from these data Extracted part by AI (about 1/10 of whole model) Whole city model 12 12

  13. Performance of AI-enhanced solver on K computer • FLOP count decreased by 5.56-times from PCGE (standard solver; Conjugate Gradient solver with block Jacobi preconditioning) and 1.32-times from SC14 Gordon Bell Prize finalist solver (with multi-grid & mixed-precision arithmetic) Strong scaling Weak scaling 1,951.2 65536 576 3,774.1 36,389.1 # of MPI processes (# nodes) 36,389.1 32768 1152 18,908.7 16384 2304 9,508.8 Elapsed time (s) 8192 4608 4,773.3 3,774.1 4096 9216 1,951.2 1,867.7 2048 12288 1,065.7 1,025.6 1024 24576 521.9 531.4 36,275.6 2,195.9 (17.2% of FP64 peak) 512 49152 4,093.4 271.7 256 0 10000 20000 30000 40000 256 2048 Elapsed time (s) # of MPI processes (# of nodes) ■ Developed ■ SC14 ■ PCGE (Standard) 13

  14. Porting to Piz Daint/Summit • Communication & memory bandwidth relatively lower than K computer • Reducing data transfer required for performance • We have been using FP32-FP64 variables • Transprecision computing is available due to adaptive preconditioning K computer Piz Daint Summit 1 × SPARC64 VIIIfx 1 × Intel Xeon E5-2690 v3 2 × IBM POWER 9 CPU/node 1 × NVIDIA P100 GPU 6 × NVIDIA V100 GPU GPU/node - Peak FP32 0.128 TFLOPS 9.4 TFLOPS 93.6 TFLOPS performance/node Memory bandwidth 512 GB/s 720 GB/s 5400 GB/s Inter-node throughput 5 GB/s 10.2 GB/s 25 GB/s in each direction

  15. Introduction of FP16 variables • Half precision can be used for reduction of data transfer size Single precision S e x p o n e n t f r a c t i o n (FP32, 32 bits) 1bit sign + 8bits exponent + 23bits fraction Half precision S e x p f r a c t i o n (FP16, 16 bits) 1bit sign + 5bits exponent + 10bits fraction • Using FP16 for whole matrix or vector causes overflow/underflow or fails to converge • Smaller exponent bits → small dynamic range • Smaller fraction bits → no more than 4-digit accuracy

  16. FP16 computation in Element-by-Element method • Matrix-free matrix-vector multiplication • Compute element-wise multiplication • Add into the global vector • Normalization of variables per element can be performed • Enables use of doubled width FP16 variables in element wise computation • Achieved 71.9% peak FP64 performance on V100 GPU • Similar normalization used in communication between MPI partitions for FP16 communication Element #0 Element-by-Element += (EBE) method FP32 FP16 FP16 T u f = Σ e P e A e P e Element #1 += [ A e is generated on-the-fly] … u f … A e Element #N-1

  17. Introduction of custom data type: FP21 • Most computation in CG loop is memory bound • However, exponent of FP16 is too small for use in global vectors • Use FP21 variables for memory bound computation • Only used for storing data (FP21 × 3 are stored into 64bit array) • Bit operations used to convert FP21 to FP32 variables for computation Single precision S e x p o n e n t f r a c t i o n (FP32, 32 bits) 1bit sign + 8bits exponent + 23bits fraction S e x p o n e n t f r a c t i o n (FP21, 21 bits) 1bit sign + 8bits exponent + 12bits fraction Half precision S e x p f r a c t i o n (FP16, 16 bits) 1bit sign + 5bits exponent + 10bits fraction

  18. Performance on Piz Daint/Summit • Developed solver demonstrates higher scalability compared to previous solvers • Leads to 19.8% (nearly full Piz Daint) & 14.7% (nearly full Summit) peak FP64 performance 75.8 110.7 288 302.5 1,923.7 # of MPI processes (# GPUs) 288 # of MPI processes (# GPUs) 373.2 2,759.3 77.6 576 311.7 1,939.5 117.8 80.4 576 378.5 1152 327.3 1,927.5 3,065.1 82.9 2304 349.8 121.1 1,912.2 1152 399.5 84.3 3,034.6 4608 374.6 2,033.8 120.8 83.7 6144 380.2 2304 401.0 1,922.1 2,999.8 90.0 12288 415.1 2,082.9 123.7 4608 393.3 100.4 24576 454.2 2,867.1 0 1000 2000 3000 4000 0 500 1000 1500 2000 2500 Elapsed time (s) Elapsed time (s) Piz Daint Summit ■ Developed ■ SC14 ■ PCGE (Standard) 18

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend