DOCSLIB.ORG

Readthedocs-Breathe Documentation Release 1.0.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Readthedocs-Breathe Documentation Release 1.0.0 ReadTheDocs-Breathe Documentation Release 1.0.0 Thomas Edvalson Jan 23, 2019 Contents 1 Going to 11: Amping Up the Programming-Language Run-Time Foundation3 2 Solid Compilation Foundation and Language Support5 2.1 Quick Start Guide............................................5 2.1.1 Current Release Notes.....................................5 2.1.2 Installation Guide........................................5 2.1.3 Programming Guide......................................6 2.1.4 ROCm GPU Tunning Guides..................................7 2.1.5 GCN ISA Manuals.......................................7 2.1.6 ROCm API References.....................................7 2.1.7 ROCm Tools..........................................8 2.1.8 ROCm Libraries........................................9 2.1.9 ROCm Compiler SDK..................................... 10 2.1.10 ROCm System Management.................................. 10 2.1.11 ROCm Virtualization & Containers.............................. 10 2.1.12 Remote Device Programming................................. 11 2.1.13 Deep Learning on ROCm.................................... 11 2.1.14 System Level Debug...................................... 11 2.1.15 Tutorial............................................. 11 2.1.16 ROCm Glossary......................................... 12 2.2 Current Release Notes.......................................... 12 2.2.1 New features and enhancements in ROCm 2.0......................... 12 2.2.1.1 Adds support for RHEL 7.6 / CentOS 7.6 and Ubuntu 18.04.1............ 12 2.2.1.2 Adds support for Vega 7nm.............................. 12 2.2.1.3 Introduces MIVisionX................................. 12 2.2.1.4 Improvements to ROCm Libraries.......................... 12 2.2.1.5 MIOpen........................................ 12 2.2.1.6 Tensorflow multi-gpu and Tensorflow FP16 support for Vega 7nm.......... 12 2.2.1.7 PyTorch/Caffe2 with Vega 7nm Support....................... 12 2.2.1.8 Improvements to ROCProfiler tool.......................... 12 2.2.1.9 Support for hipStreamCreateWithPriority....................... 13 2.2.1.10 OpenCL 2.0 support.................................. 13 2.2.1.11 Improved Virtual Addressing (48 bit VA) management for Vega 10 and later GPUs. 13 2.2.1.12 Kubernetes support.................................. 13 2.2.1.13 Removed features................................... 13 2.2.2 New features and enhancements in ROCm 1.9.2........................ 13 i 2.2.2.1 RDMA(MPI) support on Vega 7nm.......................... 13 2.2.2.2 Improvements to HCC................................. 13 2.2.2.3 Improvements to ROCProfiler tool.......................... 13 2.2.2.4 Critical bug fixes.................................... 13 2.2.3 New features and enhancements in ROCm 1.9.1........................ 13 2.2.3.1 Added DPM support to Vega 7nm........................... 13 2.2.3.2 Fix for ‘ROCm profiling’ “Version mismatch between HSA runtime and libhsa- runtime-tools64.so.1” error.............................. 14 2.2.4 New features and enhancements in ROCm 1.9.0........................ 14 2.2.4.1 Preview for Vega 7nm................................. 14 2.2.4.2 System Management Interface............................ 14 2.2.4.3 Improvements to HIP/HCC.............................. 14 2.2.4.4 Preview for rocprof Profiling Tool........................... 14 2.2.4.5 Preview for rocr Debug Agent rocr_debug_agent................... 14 2.2.4.6 New distribution support............................... 14 2.2.4.7 ROCm 1.9 is ABI compatible with KFD in upstream Linux kernels.......... 15 2.3 ROCm Installation Guide........................................ 15 2.3.1 Current ROCm Version: 2.0.................................. 15 2.3.2 Hardware Support........................................ 15 2.3.2.1 Supported GPUs.................................... 15 2.3.2.2 Supported CPUs.................................... 16 2.3.2.3 Not supported or limited support under ROCm.................... 17 2.3.2.3.1 Limited support............................... 17 2.3.2.3.2 Not supported................................ 17 2.3.3 The latest ROCm platform - ROCm 2.0............................ 17 2.3.3.1 Supported Operating Systems - New operating systems available.......... 19 2.3.3.2 ROCm support in upstream Linux kernels...................... 19 2.3.4 Installing from AMD ROCm repositories........................... 20 2.3.4.1 ROCm Binary Package Structure........................... 20 2.3.4.2 Ubuntu Support - installing from a Debian repository................ 22 2.3.4.2.1 First make sure your system is up to date.................. 22 2.3.4.2.2 Add the ROCm apt repository....................... 22 2.3.4.2.3 Install.................................... 22 2.3.4.2.4 Next set your permissions.......................... 22 2.3.4.2.5 Test basic ROCm installation........................ 23 2.3.4.2.6 Performing an OpenCL-only Installation of ROCm............ 23 2.3.4.2.7 How to uninstall from Ubuntu 16.04 or Ubuntu 18.04........... 23 2.3.4.2.8 Installing development packages for cross compilation.......... 23 2.3.4.2.9 Using Debian-based ROCm with upstream kernel drivers......... 24 2.3.4.3 CentOS/RHEL 7 (7.4, 7.5, 7.6) Support........................ 24 2.3.4.3.1 Preparing RHEL 7 (7.4, 7.5, 7.6) for installation.............. 24 2.3.4.3.2 Install and setup Devtoolset-7........................ 24 2.3.4.3.3 Prepare CentOS/RHEL (7.4, 7.5, 7.6) for DKMS Install.......... 25 2.3.4.3.4 Installing ROCm on the system....................... 25 2.3.4.3.5 Set up permissions............................. 25 2.3.4.3.6 Compiling applications using HCC, HIP, and other ROCm software... 26 2.3.4.3.7 How to uninstall ROCm from CentOS/RHEL 7.4, 7.5 and 7.6....... 26 2.3.4.3.8 Installing development packages for cross compilation.......... 26 2.3.4.3.9 Using ROCm with upstream kernel drivers................. 26 2.3.5 Known issues / workarounds.................................. 27 2.3.5.1 HCC: removed support for C++AMP in ROCm 2.0................. 27 2.3.5.2 HipCaffe is supported on single GPU configurations................. 27 ii 2.3.5.3 The ROCm SMI library calls to rsmi_dev_power_cap_set() and rsmi_dev_power_profile_set() will not work for all but the first gpu in multi- gpu set ups....................................... 27 2.3.6 Closed source components................................... 27 2.3.7 Getting ROCm source code................................... 27 2.3.7.1 Installing repo..................................... 27 2.3.7.2 Downloading the ROCm source code......................... 27 2.3.7.3 Building the ROCm source code........................... 28 2.3.8 Final notes........................................... 28 2.4 Programming Guide........................................... 28 2.4.1 ROCm Languages........................................ 28 2.4.1.1 ROCm, Lingua Franca, C++, OpenCL and Python.................. 28 2.4.1.2 HCC: Heterogeneous Compute Compiler....................... 28 2.4.1.3 When to Use HC.................................... 29 2.4.1.4 HIP: Heterogeneous-Computing Interface for Portability.............. 29 2.4.1.5 When to Use HIP................................... 29 2.4.1.6 OpenCL™: Open Compute Language........................ 29 2.4.1.7 When to Use OpenCL................................. 29 2.4.1.8 Anaconda Python With Numba............................ 29 2.4.1.9 Numba......................................... 30 2.4.1.10 When to Use Anaconda................................ 30 2.4.1.11 Wrap-Up........................................ 30 2.4.1.12 Table Comparing Syntax for Different Compute APIs................ 32 2.4.1.13 Notes.......................................... 33 2.4.2 HC Programming Guide.................................... 33 2.4.2.1 Platform Requirements................................ 33 2.4.2.2 Compiler Backends.................................. 34 2.4.2.3 Installation....................................... 34 2.4.2.4 Ubuntu......................................... 34 2.4.2.5 Download HCC.................................... 34 2.4.2.6 Build HCC from source................................ 35 2.4.2.7 Use HCC........................................ 36 2.4.2.8 Multiple ISA...................................... 36 2.4.2.9 CodeXL Activity Logger............................... 37 2.4.3 HC Best Practices........................................ 37 2.4.3.1 HCC built-in macros.................................. 38 2.4.3.2 HC-specific features.................................. 38 2.4.3.3 Differences between HC API and C++ AMP..................... 39 2.4.3.4 HCC Profile Mode................................... 40 2.4.3.4.1 Kernel Commands............................. 40 2.4.3.4.2 Memory Copy Commands......................... 41 2.4.3.4.3 Barrier Commands............................. 42 2.4.3.4.4 Overhead.................................. 43 2.4.3.4.5 Additional Details and tips......................... 43 2.4.3.5 API documentation.................................. 43 2.4.4 HIP Programing Guide..................................... 43 2.4.5 HIP Best Practices....................................... 44 2.4.6 OpenCL Programing Guide................................... 44 2.4.7 OpenCL Best Practices..................................... 44 2.5 ROCm GPU Tuning Guides....................................... 44 2.5.1 GFX7 Tuning Guide...................................... 44 2.5.2 GFX8 Tuning Guide...................................... 44 2.5.3 Vega Tuning Guide....................................... 44 2.6 GCN ISA Manuals...........................................
Load more

Recommended publications
  • Visual Development Environment for Openvx
    ______________________________________________________PROCEEDING OF THE 20TH CONFERENCE OF FRUCT ASSOCIATION Visual Development Environment for OpenVX Alexey Syschikov, Boris Sedov, Konstantin Nedovodeev, Sergey Pakharev Saint Petersburg State University of Aerospace Instrumentation Saint Petersburg, Russia {alexey.syschikov, boris.sedov, konstantin.nedovodeev, sergey.pakharev}@guap.ru Abstract—OpenVX standard has appeared as an answer II. STATE OF THE ART from the computer vision community to the challenge of accelerating vision applications on embedded heterogeneous OpenVX is intended to increase performance and reduce platforms. It is designed as a low-level programming framework power consumption of machine vision applications. It is that enables software developers to leverage the computer vision focused on embedded systems with real-time use cases such as hardware potential with functional and performance portability. face, body and gesture tracking, video surveillance, advanced In this paper, we present the visual environment for OpenVX driver assistance systems (ADAS), object and scene programs development. To the best of our knowledge, this is the reconstruction, augmented reality, visual inspection etc. first time the graphical notation is used for OpenVX programming. Our environment addresses the need to design The using of OpenVX standard functions is a way to ensure OpenVX graphs in a natural visual form with automatic functional portability of the developed software to all hardware generation of a full-fledged program, saving the programmer platforms that support OpenVX. from writing a bunch of a boilerplate code. Using the VIPE visual IDE to develop OpenVX programs also makes it possible to work Since the OpenVX API is based on opaque data types, with our performance analysis tools.
    [Show full text]
  • GLSL 4.50 Spec
    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Small Form Factor 3D Graphics for Your Pc
    VisionTek Part# 900701 PRODUCTIVITY SERIES: SMALL FORM FACTOR 3D GRAPHICS FOR YOUR PC The VisionTek Radeon R7 240SFF graphics card offers a perfect balance of performance, features, and affordability for the gamer seeking a complete solution. It offers support for the DIRECTX® 11.2 graphics standard and 4K Ultra HD for stunning 3D visual effects, realistic lighting, and lifelike imagery. Its Short Form Factor design enables it to fit into the latest Low Profile desktops and workstations, yet the R7 240SFF can be converted to a standard ATX design with the included tall bracket. With 2GB of DDR3 memory and award-winning Graphics Core Next (GCN) architecture, and DVI-D/HDMI outputs, the VisionTek Radeon R7 240SFF is big on features and light on your wallet. RADEON R7 240 SPECS • Graphics Engine: RADEON R7 240 • Video Memory: 2GB DDR3 • Memory Interface: 128bit • DirectX® Support: 11.2 • Bus Standard: PCI Express 3.0 • Core Speed: 780MHz • Memory Speed: 800MHz x2 • VGA Output: VGA* • DVI Output: SL DVI-D • HDMI Output: HDMI (Video/Audio) • UEFI Ready: Support SYSTEM REQUIREMENTS • PCI Express® based PC is required with one X16 lane graphics slot available on the motherboard. • 400W (or greater) power supply GCN Architecture: A new design for AMD’s unified graphics processing and compute cores that allows recommended. 500 Watt for AMD them to achieve higher utilization for improved performance and efficiency. CrossFire™ technology in dual mode. • Minimum 1GB of system memory. 4K Ultra HD Support: Experience what you’ve been missing even at 1080P! With support for 3840 x • Installation software requires CD-ROM 2160 output via the HDMI port, textures and other detail normally compressed for lower resolutions drive.
    [Show full text]
  • The Importance of Data
    The landscape of Parallel Programing Models Part 2: The importance of Data Michael Wong and Rod Burns Codeplay Software Ltd. Distiguished Engineer, Vice President of Ecosystem IXPUG 2020 2 © 2020 Codeplay Software Ltd. Distinguished Engineer Michael Wong ● Chair of SYCL Heterogeneous Programming Language ● C++ Directions Group ● ISOCPP.org Director, VP http://isocpp.org/wiki/faq/wg21#michael-wong ● [email protected] ● [email protected] Ported ● Head of Delegation for C++ Standard for Canada Build LLVM- TensorFlow to based ● Chair of Programming Languages for Standards open compilers for Council of Canada standards accelerators Chair of WG21 SG19 Machine Learning using SYCL Chair of WG21 SG14 Games Dev/Low Latency/Financial Trading/Embedded Implement Releasing open- ● Editor: C++ SG5 Transactional Memory Technical source, open- OpenCL and Specification standards based AI SYCL for acceleration tools: ● Editor: C++ SG1 Concurrency Technical Specification SYCL-BLAS, SYCL-ML, accelerator ● MISRA C++ and AUTOSAR VisionCpp processors ● Chair of Standards Council Canada TC22/SC32 Electrical and electronic components (SOTIF) ● Chair of UL4600 Object Tracking ● http://wongmichael.com/about We build GPU compilers for semiconductor companies ● C++11 book in Chinese: Now working to make AI/ML heterogeneous acceleration safe for https://www.amazon.cn/dp/B00ETOV2OQ autonomous vehicle 3 © 2020 Codeplay Software Ltd. Acknowledgement and Disclaimer Numerous people internal and external to the original C++/Khronos group, in industry and academia, have made contributions, influenced ideas, written part of this presentations, and offered feedbacks to form part of this talk. But I claim all credit for errors, and stupid mistakes. These are mine, all mine! You can’t have them.
    [Show full text]
  • Nvidia Graphics Card Release Dates
    Nvidia Graphics Card Release Dates Energising and factitive Verne impropriated ablins and doss his microgametes competitively and professorially. Hall misterms false if roomier Hans winterized or commoves. Worldly and antigenic Han never bunglings leastways when Doyle coft his daylight. Now, penalty can calculate the peak performance of a GPU without even plugging it in using math as splendid as those know has many streaming processors the GPU has and our clock speed. Thank father for posting this response. The graphics card industry is only going under grow and expand, to people will star to tight for more options with improved technology. Nvidia should be providing us with details in the phone couple of days. Some elements, such as against link embeds, images, loading indicators, and error messages may get inserted into the editor. There however also been second GPU whose benchmark was leaked, but which appeared to procure a slightly less powerful version. Average feature size of components of the processor. This time it is very important details may result in graphics card. You blew up the Internet. The price will exercise in accordance with that. There always seems to dispense something January. The joys of competition. As profit goes missing, they date more about concrete. Now late you flop a child of writing better understanding of what makes a graphics card so expensive, it is thinking good idea and understand a legitimate more air these cards before intercourse make you purchase. For make, I ignore marketing and please look at architectures. This is pure pretty sizable jump in performance.
    [Show full text]
  • SID Khronos Open Standards for AR May17
    Open Standards for AR Neil Trevett | Khronos President NVIDIA VP Developer Ecosystem [email protected] | @neilt3d LA, May 2017 © Copyright Khronos Group 2017 - Page 1 Khronos Mission Software Silicon Khronos is an International Industry Consortium of over 100 companies creating royalty-free, open standard APIs to enable software to access hardware acceleration for 3D graphics, Virtual and Augmented Reality, Parallel Computing, Neural Networks and Vision Processing © Copyright Khronos Group 2017 - Page 2 Khronos Standards Ecosystem 3D for the Web Real-time 2D/3D - Real-time apps and games in-browser - Cross-platform gaming and UI - Efficiently delivering runtime 3D assets - VR and AR Displays - CAD and Product Design - Safety-critical displays VR, Vision, Neural Networks Parallel Computation - VR/AR system portability - Tracking and odometry - Machine Learning acceleration - Embedded vision processing - Scene analysis/understanding - High Performance Computing (HPC) - Neural Network inferencing © Copyright Khronos Group 2017 - Page 3 Why AR Needs Standard Acceleration APIs Without API Standards With API Standards Platform Application Fragmentation Portability Everything Silicon runs on CPU Acceleration Standard Acceleration APIs provide PERFORMANCE, POWER AND PORTABILITY © Copyright Khronos Group 2017 - Page 4 AR Processing Flow Download 3D augmentation object and scene data Tracking and Positioning Generate Low Latency Vision Geometric scene 3D Augmentations for sensor(s) reconstruction display by optical system Semantic scene understanding
    [Show full text]
  • SAPPHIRE HD 6950 2GB GDDR5 Dirt3 Edition
    SAPPHIRE HD 6950 2GB GDDR5 Dirt3 Edition The SAPPHIRE HD 6950 Dirt3 Special Edition is a new SAPPHIRE original model with a special cooler using a new dual fan configuration. Based on the latest high end AMD GPU architecture, it boasts true DX 11 capability and the powerful configuration of 1408 stream processors and 88 texture processing units. With its clock speed of 800MHz for the core and 2GB of the latest GDDR5 memory running at 1250Mhz (5 Gb/sec effective), this model speeds through even the most demanding applications for a smooth and detail packed experience. A Dual BIOS feature allows enthusiasts to experiment with alternative BIOS settings and performance can be further enhanced with the SAPPHIRE overclocking tool, TriXX, available as a free download from http://www.sapphiretech.com/ssc/TriXX/ System Overview Awards News Requirements Specification 1 x Dual-Link DVI 1 x HDMI 1.4a Output 1 x DisplayPort 1 x Single-Link DVI-D DisplayPort 1.2 800 MHz Core Clock GPU 40 nm Chip 1408 x Stream Processors 2048 MB Size Memory 256 -bit GDDR5 5000 MHz Effective Dimension 260(L)x110(W)x35(H) mm Size. Driver CD Software SAPPHIRE TriXX Utility 1 x Dirt®3 Coupon CrossFire™ Bridge Interconnect Cable DVI to VGA Adapter Accessory 6 PIN to 4 PIN Power Cable x 2 HDMI 1.4a high speed 1.8 meter cable(Full Retail SKU only) All specifications and accessories are subject to change without notice. Please check with your supplier for exact offers. Products may not be available in all markets.
    [Show full text]
  • Standards for Vision Processing and Neural Networks
    Standards for Vision Processing and Neural Networks Radhakrishna Giduthuri, AMD [email protected] © Copyright Khronos Group 2017 - Page 1 Agenda • Why we need a standard? • Khronos NNEF • Khronos OpenVX dog Network Architecture Pre-trained Network Model (weights, …) © Copyright Khronos Group 2017 - Page 2 Neural Network End-to-End Workflow Neural Network Third Vision/AI Party Applications Training Frameworks Tools Datasets Trained Vision and Neural Network Network Inferencing Runtime Network Model Architecture Desktop and Cloud Hardware Embedded/Mobile Embedded/MobileEmbedded/Mobile Embedded/Mobile/Desktop/CloudVision/InferencingVision/Inferencing Hardware Hardware cuDNN MIOpen MKL-DNN Vision/InferencingVision/Inferencing Hardware Hardware GPU DSP CPU Custom FPGA © Copyright Khronos Group 2017 - Page 3 Problem: Neural Network Fragmentation Neural Network Training and Inferencing Fragmentation NN Authoring Framework 1 Inference Engine 1 NN Authoring Framework 2 Inference Engine 2 NN Authoring Framework 3 Inference Engine 3 Every Tool Needs an Exporter to Every Accelerator Neural Network Inferencing Fragmentation toll on Applications Inference Engine 1 Hardware 1 Vision/AI Inference Engine 2 Hardware 2 Application Inference Engine 3 Hardware 3 Every Application Needs know about Every Accelerator API © Copyright Khronos Group 2017 - Page 4 Khronos APIs Connect Software to Silicon Software Silicon Khronos is an International Industry Consortium of over 100 companies creating royalty-free, open standard APIs to enable software to access
    [Show full text]
  • Khronos Template 2015
    Ecosystem Overview Neil Trevett | Khronos President NVIDIA Vice President Developer Ecosystem [email protected] | @neilt3d © Copyright Khronos Group 2016 - Page 1 Khronos Mission Software Silicon Khronos is an Industry Consortium of over 100 companies creating royalty-free, open standard APIs to enable software to access hardware acceleration for graphics, parallel compute and vision © Copyright Khronos Group 2016 - Page 2 http://accelerateyourworld.org/ © Copyright Khronos Group 2016 - Page 3 Vision Pipeline Challenges and Opportunities Growing Camera Diversity Diverse Vision Processors Sensor Proliferation 22 Flexible sensor and camera Use efficient acceleration to Combine vision output control to GENERATE PROCESS with other sensor data an image stream the image stream on device © Copyright Khronos Group 2016 - Page 4 OpenVX – Low Power Vision Acceleration • Higher level abstraction API - Targeted at real-time mobile and embedded platforms • Performance portability across diverse architectures - Multi-core CPUs, GPUs, DSPs and DSP arrays, ISPs, Dedicated hardware… • Extends portable vision acceleration to very low power domains - Doesn’t require high-power CPU/GPU Complex - Lower precision requirements than OpenCL - Low-power host can setup and manage frame-rate graph Vision Engine Middleware Application X100 Dedicated Vision Processing Hardware Efficiency Vision DSPs X10 GPU Compute Accelerator Multi-core Accelerator Power Efficiency Power X1 CPU Accelerator Computation Flexibility © Copyright Khronos Group 2016 - Page 5 OpenVX Graphs
    [Show full text]
  • Real-Time Computer Vision with Opencv Khanh Vo Duc, Mobile Vision Team, NVIDIA
    Real-time Computer Vision with OpenCV Khanh Vo Duc, Mobile Vision Team, NVIDIA Outline . What is OpenCV? . OpenCV Example – CPU vs. GPU with CUDA . OpenCV CUDA functions . Future of OpenCV . Summary OpenCV Introduction . Open source library for computer vision, image processing and machine learning . Permissible BSD license . Freely available (www.opencv.org) Portability . Real-time computer vision (x86 MMX/SSE, ARM NEON, CUDA) . C (11 years), now C++ (3 years since v2.0), Python and Java . Windows, OS X, Linux, Android and iOS 3 Functionality Desktop . x86 single-core (Intel started, now Itseez.com) - v2.4.5 >2500 functions (multiple algorithm options, data types) . CUDA GPU (Nvidia) - 250 functions (5x – 100x speed-up) http://docs.opencv.org/modules/gpu/doc/gpu.html . OpenCL GPU (3rd parties) - 100 functions (launch times ~7x slower than CUDA*) Mobile (Nvidia): . Android (not optimized) . Tegra – 50 functions NEON, GLSL, multi-core (1.6–32x speed-up) 4 Functionality Image/video I/O, processing, display (core, imgproc, highgui) Object/feature detection (objdetect, features2d, nonfree) Geometry-based monocular or stereo computer vision (calib3d, stitching, videostab) Computational photography (photo, video, superres) Machine learning & clustering (ml, flann) CUDA and OpenCL GPU acceleration (gpu, ocl) 5 Outline . What is OpenCV? . OpenCV Example – CPU vs. GPU with CUDA . OpenCV CUDA functions . Future of OpenCV . Summary OpenCV CPU example #include <opencv2/opencv.hpp> OpenCV header files using namespace cv; OpenCV C++ namespace int
    [Show full text]
  • SAPPHIRE R9 285 2GB GDDR5 ITX COMPACT OC Edition (UEFI)
    Specification Display Support 4 x Maximum Display Monitor(s) support 1 x HDMI (with 3D) Output 2 x Mini-DisplayPort 1 x Dual-Link DVI-I 928 MHz Core Clock GPU 28 nm Chip 1792 x Stream Processors 2048 MB Size Video Memory 256 -bit GDDR5 5500 MHz Effective 171(L)X110(W)X35(H) mm Size. Dimension 2 x slot Driver CD Software SAPPHIRE TriXX Utility DVI to VGA Adapter Mini-DP to DP Cable Accessory HDMI 1.4a high speed 1.8 meter cable(Full Retail SKU only) 1 x 8 Pin to 6 Pin x2 Power adaptor Overview HDMI (with 3D) Support for Deep Color, 7.1 High Bitrate Audio, and 3D Stereoscopic, ensuring the highest quality Blu-ray and video experience possible from your PC. Mini-DisplayPort Enjoy the benefits of the latest generation display interface, DisplayPort. With the ultra high HD resolution, the graphics card ensures that you are able to support the latest generation of LCD monitors. Dual-Link DVI-I Equipped with the most popular Dual Link DVI (Digital Visual Interface), this card is able to display ultra high resolutions of up to 2560 x 1600 at 60Hz. Advanced GDDR5 Memory Technology GDDR5 memory provides twice the bandwidth per pin of GDDR3 memory, delivering more speed and higher bandwidth. Advanced GDDR5 Memory Technology GDDR5 memory provides twice the bandwidth per pin of GDDR3 memory, delivering more speed and higher bandwidth. AMD Stream Technology Accelerate the most demanding applications with AMD Stream technology and do more with your PC. AMD Stream Technology allows you to use the teraflops of compute power locked up in your graphics processer on tasks other than traditional graphics such as video encoding, at which the graphics processor is many, many times faster than using the CPU alone.
    [Show full text]
  • The Openvx™ Specification
    The OpenVX™ Specification Editor: Radhakrishna Giduthuri, Intel, The Khronos® OpenVX Working Group Version 1.3, Thu, 10 Sep 2020 07:04:36 +0000: Git branch information not available Table of Contents 1. Introduction . 2 1.1. Abstract . 2 1.2. Purpose . 2 1.3. Scope of Specification . 2 1.4. Normative References . 2 1.5. Version/Change History . 3 1.6. Deprecation . 3 1.7. Normative Requirements . 3 1.8. Typographical Conventions . 3 1.8.1. Naming Conventions . 4 1.8.2. Vendor Naming Conventions . 4 1.9. Glossary and Acronyms . 5 1.10. Acknowledgements . 5 2. Design Overview . 8 2.1. Software Landscape . 8 2.2. Design Objectives . 8 2.2.1. Hardware Optimizations . 8 2.2.2. Hardware Limitations . 9 2.3. Assumptions . 9 2.3.1. Portability. 9 2.3.2. Opaqueness . 9 2.4. Object-Oriented Behaviors . 9 2.5. OpenVX Framework Objects . 9 2.6. OpenVX Data Objects . 10 2.7. Error Objects . 11 2.8. Graphs Concepts . 11 2.8.1. Linking Nodes . 11 2.8.2. Virtual Data Objects . 11 2.8.3. Node Parameters . 14 2.8.4. Graph Parameters . 15 2.8.5. Execution Model . 15 Asynchronous Mode . 15 2.8.6. Graph Formalisms . 15 Contained & Overlapping Data Objects . 16 2.8.7. Node Execution Independence . 18 2.8.8. Verification. 20 2.9. Callbacks . 21 2.10. User Kernels. 21 2.10.1. Parameter Validation. 23 The Meta Format Object. 23 2.10.2. User Kernels Naming Conventions . 23 2.11. Immediate Mode Functions . 24 2.12. Targets . ..
    [Show full text]