DOCSLIB.ORG

Dspic DSC Speex Speech Encoding/Decoding Library As a Development Tool to Emulate and Debug Firmware on a Target Board

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dspic DSC Speex Speech Encoding/Decoding Library As a Development Tool to Emulate and Debug Firmware on a Target Board dsPIC® DSC Speex Speech Encoding/Decoding Library User’s Guide © 2008-2011 Microchip Technology Inc. DS70328C Note the following details of the code protection feature on Microchip devices: • Microchip products meet the specification contained in their particular Microchip Data Sheet. • Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. • There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property. • Microchip is willing to work with the customer who is concerned about the integrity of their code. • Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.” Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act. Information contained in this publication regarding device Trademarks applications and the like is provided only for your convenience The Microchip name and logo, the Microchip logo, dsPIC, and may be superseded by updates. It is your responsibility to KEELOQ, KEELOQ logo, MPLAB, PIC, PICmicro, PICSTART, ensure that your application meets with your specifications. PIC32 logo, rfPIC and UNI/O are registered trademarks of MICROCHIP MAKES NO REPRESENTATIONS OR Microchip Technology Incorporated in the U.S.A. and other WARRANTIES OF ANY KIND WHETHER EXPRESS OR countries. IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, FilterLab, Hampshire, HI-TECH C, Linear Active Thermistor, INCLUDING BUT NOT LIMITED TO ITS CONDITION, MXDEV, MXLAB, SEEVAL and The Embedded Control QUALITY, PERFORMANCE, MERCHANTABILITY OR Solutions Company are registered trademarks of Microchip FITNESS FOR PURPOSE. Microchip disclaims all liability Technology Incorporated in the U.S.A. arising from this information and its use. Use of Microchip Analog-for-the-Digital Age, Application Maestro, chipKIT, devices in life support and/or safety applications is entirely at chipKIT logo, CodeGuard, dsPICDEM, dsPICDEM.net, the buyer’s risk, and the buyer agrees to defend, indemnify and dsPICworks, dsSPEAK, ECAN, ECONOMONITOR, hold harmless Microchip from any and all damages, claims, FanSense, HI-TIDE, In-Circuit Serial Programming, ICSP, suits, or expenses resulting from such use. No licenses are Mindi, MiWi, MPASM, MPLAB Certified logo, MPLIB, conveyed, implicitly or otherwise, under any Microchip MPLINK, mTouch, Omniscient Code Generation, PICC, intellectual property rights. PICC-18, PICDEM, PICDEM.net, PICkit, PICtail, REAL ICE, rfLAB, Select Mode, Total Endurance, TSHARC, UniWinDriver, WiperLock and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. All other trademarks mentioned herein are property of their respective companies. © 2008-2011, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved. Printed on recycled paper. ISBN: 978-1-61341-297-8 Microchip received ISO/TS-16949:2002 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition, Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified. DS70328C-page 2 © 2008-2011 Microchip Technology Inc. dsPIC® DSC SPEEX SPEECH ENCODING/DECODING LIBRARY USER’S GUIDE Table of Contents Preface ........................................................................................................................... 5 Chapter 1. Introduction 1.1 Library Overview .......................................................................................... 11 1.2 Features ....................................................................................................... 14 1.3 System Requirements .................................................................................. 14 Chapter 2. Installation 2.1 Installation Procedure ................................................................................... 15 2.2 Library Files .................................................................................................. 16 Chapter 3. Quick Start Demonstration 3.1 Quick Start Demonstration for dsPIC33F Device Family ............................. 21 3.2 Quick Start Demonstration for dsPIC33E Device Family ............................. 30 Chapter 4. Application Programming Interface 4.1 Adding the Library to an Application ............................................................. 37 4.2 Memory Model Compile Options .................................................................. 38 4.3 Using the Library .......................................................................................... 40 4.4 Register Usage ............................................................................................. 43 4.5 Packet Loss and Corruption ......................................................................... 43 4.6 PC Encoder Utility (PCEU) Output Files ...................................................... 43 4.7 Resource Requirements ............................................................................... 44 4.8 API Functions ............................................................................................... 47 4.9 Application Tips ............................................................................................ 61 Index ............................................................................................................................. 63 Worldwide Sales and Service .................................................................................... 64 © 2008-2011 Microchip Technology Inc. DS70328C-page 3 dsPIC® DSC Speex Speech Encoding/Decoding Library User’s Guide NOTES: DS70328C-page 4 © 2008-2011 Microchip Technology Inc. dsPIC® DSC SPEEX SPEECH ENCODING/DECODING LIBRARY USER’S GUIDE Preface NOTICE TO CUSTOMERS All documentation becomes dated, and this manual is no exception. Microchip tools and documentation are constantly evolving to meet customer needs, so some actual dialogs and/or tool descriptions may differ from those in this document. Please refer to our web site (www.microchip.com) to obtain the latest documentation available. Documents are identified with a “DS” number. This number is located on the bottom of each page, in front of the page number. The numbering convention for the DS number is “DSXXXXXA”, where “XXXXX” is the document number and “A” is the revision level of the document. For the most up-to-date information on development tools, see the MPLAB® IDE on-line help. Select the Help menu, and then Topics to open a list of available on-line help files. INTRODUCTION This chapter contains general information that will be useful to know before using the dsPIC® DSC Speex Speech Encoding/Decoding Library User’s Guide. Items discussed in this preface include: • Document Layout • Conventions Used in this Guide • Warranty Registration • Recommended Reading • The Microchip Web Site • Development Systems Customer Change Notification Service • Customer Support • Document Revision History DOCUMENT LAYOUT This document describes how to use the dsPIC DSC Speex Speech Encoding/Decoding Library as a development tool to emulate and debug firmware on a target board. The document layout is as follows: • Chapter 1. “Introduction”– This chapter describes the dsPIC DSC Speex Speech Encoding/Decoding Library. • Chapter 2. “Installation” – This chapter provides detailed information needed to install the dsPIC DSC Speex Speech Encoding/Decoding Library on a PC. • Chapter 3. “Quick Start Demonstration” – This chapter describes the demonstrations available for the dsPIC DSC Speex Speech Encoding/Decoding Library. • Chapter 4. “Application Programming Interface” – This chapter outlines how the API functions provided in the dsPIC DSC Speex Speech Encoding/Decoding Library can be included in your application software through the Application Programming Interface. © 2008-2011 Microchip Technology Inc. DS70328C-page 5 dsPIC® DSC Speex Speech Encoding/Decoding Library User’s Guide CONVENTIONS USED IN THIS GUIDE This manual uses the following documentation conventions: DOCUMENTATION CONVENTIONS Description Represents Examples Arial font: Italic characters Referenced books MPLAB® IDE User’s Guide Emphasized text ...is the only compiler... Initial caps A window the Output window A dialog the Settings dialog A menu selection select Enable Programmer Quotes A field name in a window or “Save project before build” dialog Underlined, italic text with A menu path File>Save right angle
Load more

Recommended publications
  • Lossless Audio Codec Comparison
    Contents Introduction 3 1 CD-audio test 4 1.1 CD's used . .4 1.2 Results all CD's together . .4 1.3 Interesting quirks . .7 1.3.1 Mono encoded as stereo (Dan Browns Angels and Demons) . .7 1.3.2 Compressibility . .9 1.4 Convergence of the results . 10 2 High-resolution audio 13 2.1 Nine Inch Nails' The Slip . 13 2.2 Howard Shore's soundtrack for The Lord of the Rings: The Return of the King . 16 2.3 Wasted bits . 18 3 Multichannel audio 20 3.1 Howard Shore's soundtrack for The Lord of the Rings: The Return of the King . 20 A Motivation for choosing these CDs 23 B Test setup 27 B.1 Scripting and graphing . 27 B.2 Codecs and parameters used . 27 B.3 MD5 checksumming . 28 C Revision history 30 Bibliography 31 2 Introduction While testing the efficiency of lossy codecs can be quite cumbersome (as results differ for each person), comparing lossless codecs is much easier. As the last well documented and comprehensive test available on the internet has been a few years ago, I thought it would be a good idea to update. Beside comparing with CD-audio (which is often done to assess codec performance) and spitting out a grand total, this comparison also looks at extremes that occurred during the test and takes a look at 'high-resolution audio' and multichannel/surround audio. While the comparison was made to update the comparison-page on the FLAC website, it aims to be fair and unbiased.
    [Show full text]
  • Cluster-Based Delta Compression of a Collection of Files Department of Computer and Information Science
    Cluster-Based Delta Compression of a Collection of Files Zan Ouyang Nasir Memon Torsten Suel Dimitre Trendafilov Department of Computer and Information Science Technical Report TR-CIS-2002-05 12/27/2002 Cluster-Based Delta Compression of a Collection of Files Zan Ouyang Nasir Memon Torsten Suel Dimitre Trendafilov CIS Department Polytechnic University Brooklyn, NY 11201 Abstract Delta compression techniques are commonly used to succinctly represent an updated ver- sion of a file with respect to an earlier one. In this paper, we study the use of delta compression in a somewhat different scenario, where we wish to compress a large collection of (more or less) related files by performing a sequence of pairwise delta compressions. The problem of finding an optimal delta encoding for a collection of files by taking pairwise deltas can be re- duced to the problem of computing a branching of maximum weight in a weighted directed graph, but this solution is inefficient and thus does not scale to larger file collections. This motivates us to propose a framework for cluster-based delta compression that uses text clus- tering techniques to prune the graph of possible pairwise delta encodings. To demonstrate the efficacy of our approach, we present experimental results on collections of web pages. Our experiments show that cluster-based delta compression of collections provides significant im- provements in compression ratio as compared to individually compressing each file or using tar+gzip, at a moderate cost in efficiency. A shorter version of this paper appears in the Proceedings of the 3rd International Con- ference on Web Information Systems Engineering (WISE), December 2002.
    [Show full text]
  • Multimedia Compression Techniques for Streaming
    International Journal of Innovative Technology and Exploring Engineering (IJITEE) ISSN: 2278-3075, Volume-8 Issue-12, October 2019 Multimedia Compression Techniques for Streaming Preethal Rao, Krishna Prakasha K, Vasundhara Acharya most of the audio codes like MP3, AAC etc., are lossy as Abstract: With the growing popularity of streaming content, audio files are originally small in size and thus need not have streaming platforms have emerged that offer content in more compression. In lossless technique, the file size will be resolutions of 4k, 2k, HD etc. Some regions of the world face a reduced to the maximum possibility and thus quality might be terrible network reception. Delivering content and a pleasant compromised more when compared to lossless technique. viewing experience to the users of such locations becomes a The popular codecs like MPEG-2, H.264, H.265 etc., make challenge. audio/video streaming at available network speeds is just not feasible for people at those locations. The only way is to use of this. FLAC, ALAC are some audio codecs which use reduce the data footprint of the concerned audio/video without lossy technique for compression of large audio files. The goal compromising the quality. For this purpose, there exists of this paper is to identify existing techniques in audio-video algorithms and techniques that attempt to realize the same. compression for transmission and carry out a comparative Fortunately, the field of compression is an active one when it analysis of the techniques based on certain parameters. The comes to content delivering. With a lot of algorithms in the play, side outcome would be a program that would stream the which one actually delivers content while putting less strain on the audio/video file of our choice while the main outcome is users' network bandwidth? This paper carries out an extensive finding out the compression technique that performs the best analysis of present popular algorithms to come to the conclusion of the best algorithm for streaming data.
    [Show full text]
  • User Commands GZIP ( 1 ) Gzip, Gunzip, Gzcat – Compress Or Expand Files Gzip [ –Acdfhllnnrtvv19 ] [–S Suffix] [ Name ... ]
    User Commands GZIP ( 1 ) NAME gzip, gunzip, gzcat – compress or expand files SYNOPSIS gzip [–acdfhlLnNrtvV19 ] [– S suffix] [ name ... ] gunzip [–acfhlLnNrtvV ] [– S suffix] [ name ... ] gzcat [–fhLV ] [ name ... ] DESCRIPTION Gzip reduces the size of the named files using Lempel-Ziv coding (LZ77). Whenever possible, each file is replaced by one with the extension .gz, while keeping the same ownership modes, access and modification times. (The default extension is – gz for VMS, z for MSDOS, OS/2 FAT, Windows NT FAT and Atari.) If no files are specified, or if a file name is "-", the standard input is compressed to the standard output. Gzip will only attempt to compress regular files. In particular, it will ignore symbolic links. If the compressed file name is too long for its file system, gzip truncates it. Gzip attempts to truncate only the parts of the file name longer than 3 characters. (A part is delimited by dots.) If the name con- sists of small parts only, the longest parts are truncated. For example, if file names are limited to 14 characters, gzip.msdos.exe is compressed to gzi.msd.exe.gz. Names are not truncated on systems which do not have a limit on file name length. By default, gzip keeps the original file name and timestamp in the compressed file. These are used when decompressing the file with the – N option. This is useful when the compressed file name was truncated or when the time stamp was not preserved after a file transfer. Compressed files can be restored to their original form using gzip -d or gunzip or gzcat.
    [Show full text]
  • Software Development Kits Comparison Matrix
    Software Development Kits > Comparison Matrix Software Development Kits Comparison Matrix DATA COMPRESSION TOOLKIT FOR TOOLKIT FOR TOOLKIT FOR LIBRARY (DCL) WINDOWS WINDOWS JAVA Compression Method DEFLATE DEFLATE64 DCL Implode BZIP2 LZMA PPMd Extraction Method DEFLATE DEFLATE64 DCL Implode BZIP2 LZMA PPMd Wavpack Creation Formats Supported ZIP BZIP2 GZIP TAR UUENCODE, XXENCODE Large Archive Creation Support (ZIP64) Archive Extraction Formats Supported ZIP BZIP2 GZIP, TAR, AND .Z (UNIX COMPRESS) UUENCODE, XXENCODE CAB, BinHex, ARJ, LZH, RAR, 7z, and ISO/DVD Integration Format Static Dynamic Link Libraries (DLL) Pure Java Class Library (JAR) Programming Interface C C/C++ Objects C#, .NET interface Java Support for X.509-Compliant Digital Certificates Apply digital signatures Verify digital signatures Encrypt archives www.pkware.com Software Development Kits > Comparison Matrix DATA COMPRESSION TOOLKIT FOR TOOLKIT FOR TOOLKIT FOR LIBRARY (DCL) WINDOWS WINDOWS JAVA Signing Methods SHA-1 MD5 SHA-256, SHA-384 and SHA-512 Message Digest Timestamp .ZIP file signatures ENTERPRISE ONLY Encryption Formats ZIP OpenPGP ENTERPRISE ONLY Encryption Methods AES (256, 192, 128-bit) 3DES (168, 112-bit) 168 ONLY DES (56-bit) RC4 (128, 64, 40-bit), RC2 (128, 64, 40-bit) CAST5 and IDEA Decryption Methods AES (256, 192, 128-bit) 3DES (168, 112-bit) 168 ONLY DES (56-bit) RC4 (128, 64, 40-bit), RC2 (128, 64, 40-bit) CAST5 and IDEA Additional Features Supports file, memory and streaming operations Immediate archive operation Deferred archive operation Multi-Thread
    [Show full text]
  • Backing up Data
    Backing up data On LINUX and UNIX Logical backup • Why? Job security • For user data. • Remember endian order, character set issues. • Full backup + incremental = backup set No differential (see find command). • Backup without a restore test is just a tape • mt or rmt used for generic tape management. See mt, rmt manpage. See /dev/rmt0 • See text for CD/DVD procedures • Use commercial products for business. Why? Tape catalog management. Backup Commands • cp (duh) • ftp (eh) • rcp (no, no, no) • scp • rsync • tar • cpio • pax (see cpio, tar) • dump/restore – the standard The usual suspects • cp –rp source destination • ftp hostname user name cd source or destination lcd destination/source put/get filename quit • scp source user@destination:/pathtofile scp user@source:/pathtofile /destination • rcp source user@destination:/pathtofile rcp user@ source:/pathtofile /destination uses .rhosts see manpage on hosts.equiv rsync • Support from rsync.samba.org • rsync copies files either to or from a remote host, or locally on the current host but does not support copying files between two remote hosts. • rsync can reduce the amount of data sent over the network by sending only the differences between the source files and the existing files in the destination. • There are two different ways for rsync to contact a remote system: using a remote- shell program as the transport (such as ssh or rsh) or contacting an rsync daemon directly via TCP. See the manpage on rsyncd.conf. • rsync –avh /source /destination • rsync -avze ssh /home/user/directory/ user@remotehost:home/user/directory/ • Other Options -a, --archive archive mode; equals -r, --recursive recurse into directories -u, --update skip files that are newer on the receiver Tape ARchive • Most portable backup utility between systems.
    [Show full text]
  • I/O of Sound with R
    I/O of sound with R J´er^ome Sueur Mus´eum national d'Histoire naturelle CNRS UMR 7205 ISYEB, Paris, France July 14, 2021 This document shortly details how to import and export sound with Rusing the packages seewave, tuneR and audio1. Contents 1 In 2 1.1 Non specific classes...................................2 1.1.1 Vector......................................2 1.1.2 Matrix......................................2 1.2 Time series.......................................3 1.3 Specific sound classes..................................3 1.3.1 Wave class (package tuneR)..........................4 1.3.2 audioSample class (package audio)......................5 2 Out 5 2.1 .txt format.......................................5 2.2 .wav format.......................................6 2.3 .flac format.......................................6 3 Mono and stereo6 4 Play sound 7 4.1 Specific functions....................................7 4.1.1 Wave class...................................7 4.1.2 audioSample class...............................7 4.1.3 Other classes..................................7 4.2 System command....................................8 5 Summary 8 1The package sound is no more maintained. 1 Import and export of sound with R > options(warn=-1) 1 In The main functions of seewave (>1.5.0) can use different classes of objects to analyse sound: usual classes (numeric vector, numeric matrix), time series classes (ts, mts), sound-specific classes (Wave and audioSample). 1.1 Non specific classes 1.1.1 Vector Any muneric vector can be treated as a sound if a sampling frequency is provided in the f argument of seewave functions. For instance, a 440 Hz sine sound (A note) sampled at 8000 Hz during one second can be generated and plot following: > s1<-sin(2*pi*440*seq(0,1,length.out=8000)) > is.vector(s1) [1] TRUE > mode(s1) [1] "numeric" > library(seewave) > oscillo(s1,f=8000) 1.1.2 Matrix Any single column matrix can be read but the sampling frequency has to be specified in the seewave functions.
    [Show full text]
  • Improving Opus Low Bit Rate Quality with Neural Speech Synthesis
    Improving Opus Low Bit Rate Quality with Neural Speech Synthesis Jan Skoglund1, Jean-Marc Valin2∗ 1Google, San Francisco, CA, USA 2Amazon, Palo Alto, CA, USA [email protected], [email protected] Abstract learned representation set [11]. A typical WaveNet configura- The voice mode of the Opus audio coder can compress wide- tion requires a very high algorithmic complexity, in the order band speech at bit rates ranging from 6 kb/s to 40 kb/s. How- of hundreds of GFLOPS, along with a high memory usage to ever, Opus is at its core a waveform matching coder, and as the hold the millions of model parameters. Combined with the high rate drops below 10 kb/s, quality degrades quickly. As the rate latency, in the hundreds of milliseconds, this renders WaveNet reduces even further, parametric coders tend to perform better impractical for a real-time implementation. Replacing the di- than waveform coders. In this paper we propose a backward- lated convolutional networks with recurrent networks improved compatible way of improving low bit rate Opus quality by re- memory efficiency in SampleRNN [12], which was shown to be synthesizing speech from the decoded parameters. We compare useful for speech coding in [13]. WaveRNN [14] also demon- two different neural generative models, WaveNet and LPCNet. strated possibilities for synthesizing at lower complexities com- WaveNet is a powerful, high-complexity, and high-latency ar- pared to WaveNet. Even lower complexity and real-time opera- chitecture that is not feasible for a practical system, yet pro- tion was recently reported using LPCNet [15]. vides a best known achievable quality with generative models.
    [Show full text]
  • 12.1 Introduction 12.2 Tar Command
    12.1 Introduction Linux distributions provide several different sets of commands for compressing and archiving files and directories. This chapter will describe their advantages and disadvantages as well as their usefulness in making backup copies of files and directories efficiently. More sophisticated types of copying, using the dd and cpio commands, will also be covered. These commands, while more complex, offer powerful features. 12.2 tar Command An archive is a single file, which consists of many files, though not necessarily compressed. The tar command is typically used to make archives within Linux. These tar archive files, sometimes called tarballs, were originally used to backup data onto magnetic tape. Tar is derived from the words "tape archive". While the primary purpose of the tar command is to merge multiple files into a single file, it is capable of many different operations and there are numerous options. The functionality of the tar command can be broken down into three basic functions: creating, viewing and extracting archives. The tar command accepts all three styles of options (x, -x, --extract) as parameters. Do not be surprised to see it used with options that have no hyphens (BSD style), a single hyphen (UNIX style) or two hyphens (GNU style). The tar command originally did not support compression, but a newer version that was developed by the GNU project supports both gzip and bzip2compression. Both of these compression schemes will be presented later in this chapter. To use gzip compression with the tar command, use the -z option. To use bzip2 compression, use the -j option.
    [Show full text]
  • Freebsd General Commands Manual BSDCPIO (1)
    BSDCPIO (1) FreeBSD General Commands Manual BSDCPIO (1) NAME cpio —copyfiles to and from archives SYNOPSIS cpio { −i}[options][pattern . ..][<archive] cpio { −o}[options] <name-list [>archive] cpio { −p}[options] dest-dir < name-list DESCRIPTION cpio copies files between archivesand directories. This implementation can extract from tar,pax, cpio, zip, jar,ar, and ISO 9660 cdrom images and can create tar,pax, cpio, ar,and shar archives. The first option to cpio is a mode indicator from the following list: −i Input. Read an archive from standard input (unless overriden) and extract the contents to disk or (if the −t option is specified) list the contents to standard output. If one or more file patterns are specified, only files matching one of the patterns will be extracted. −o Output. Read alist of filenames from standard input and produce a newarchive onstandard output (unless overriden) containing the specified items. −p Pass-through. Read alist of filenames from standard input and copythe files to the specified direc- tory. OPTIONS Unless specifically stated otherwise, options are applicable in all operating modes. −0 Read filenames separated by NUL characters instead of newlines. This is necessary if anyofthe filenames being read might contain newlines. −A (o mode only) Append to the specified archive.(Not yet implemented.) −a (o and p modes) Reset access times on files after theyare read. −B (o mode only) Block output to records of 5120 bytes. −C size (o mode only) Block output to records of size bytes. −c (o mode only) Use the old POSIX portable character format. Equivalent to −-format odc.
    [Show full text]
  • Real-Time Data Compression for Data Acquisition Systems Applied to the Iter Radial Neutron Camera 1
    504 REAL-TIME DATA COMPRESSION FOR DATA ACQUISITION SYSTEMS APPLIED TO THE ITER RADIAL NEUTRON CAMERA 1 Real-time data compression for data acquisition systems applied to the ITER Radial Neutron Camera B. Santos, N. Cruz, A. Fernandes, P.F. Carvalho, J. Sousa, B. Gonc¸alves, M. Riva, F. Pollastrone, C. Centioli, D. Marocco, B. Esposito, C.M.B.A. Correia and R.C. Pereira Abstract—To achieve the aim of the ITER Radial Neutron processed using IPFN FPGA Mezzanine Cards (FMC-AD2- Camera Diagnostic, the data acquisition prototype must be 1600) with 2 digitizer channels of 12-bit resolution sampling compliant with a sustained 2 MHz peak event for each channel up to 1.6 GSamples/s. These in-house developed cards are with 128 samples of 16 bits per event. The data is acquired and processed using an IPFN FPGA Mezzanine Card (FMC- mounted in PCIe evaluation boards from Xilinx (KC705) [5]. AD2-1600) with 2 digitizer channels of 12-bit resolution and a The prototype architecture comprises one host PC with two sampling rate up to 1.6 GSamples/s mounted in a PCIe evaluation installed KC705 modules and four channels, producing up to board from Xilinx (KC705) installed in the host PC. 2 GB/s in event mode and up to 3.2 GB/s in continuous mode The acquired data in the event-based data-path is streamed [5]. to the host through the PCIe x8 Direct Memory Access (DMA) The LZ4 is a lossless compression algorithm, providing with a maximum data throughput per channel ≈0.5 GB/s of raw data (event base), ≈1 GB/s per digitizer and up to 1.6 GB/s in compression speed at 400 MB/s per core, scalable with multi- continuous mode.
    [Show full text]
  • GNU Gzip the Data Compression Program for Gzip Version 1.11 2 January 2021
    GNU gzip The data compression program for Gzip version 1.11 2 January 2021 by Jean-loup Gailly This manual is for GNU Gzip (version 1.11, 2 January 2021), and documents commands for compressing and decompressing data. Copyright c 1998{1999, 2001{2002, 2006{2007, 2009{2021 Free Software Foundation, Inc. Copyright c 1992, 1993 Jean-loup Gailly Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents 1 Overview ::::::::::::::::::::::::::::::::::::::::: 1 2 Sample output ::::::::::::::::::::::::::::::::::: 3 3 Invoking gzip :::::::::::::::::::::::::::::::::::: 5 4 Advanced usage ::::::::::::::::::::::::::::::::: 9 5 Environment:::::::::::::::::::::::::::::::::::: 11 6 Using gzip on tapes :::::::::::::::::::::::::::: 13 7 Reporting Bugs :::::::::::::::::::::::::::::::: 15 Appendix A GNU Free Documentation License :: 17 Appendix B Concept index:::::::::::::::::::::: 25 1 1 Overview gzip reduces the size of the named files using Lempel{Ziv coding (LZ77). Whenever possi- ble, each file is replaced by one with the extension.gz ` ', while keeping the same ownership modes, access and modification times. (The default extension is`z' for MSDOS, OS/2 FAT and Atari.) If no files are specified or if a file nameis -, the standard input is compressed to the standard output. gzip will only attempt to compress regular files. In particular, it will ignore symbolic links. If the new file name is too long for its file system, gzip truncates it.
    [Show full text]