Disk Drive Operations Storage Access Methods

Total Page:16

File Type:pdf, Size:1020Kb

Disk Drive Operations Storage Access Methods Disk Drive Operations Storage Access Methods Lecture 2 September 19, 2006 NEU csg389 Information Storage Technologies, Fall 2006 Plan for today • Questions from last time • On-disk data organization • what they’re all about • Storage access methods • Block-based access • File-based access • Object-based access NEU csg389 Fall 2006, Jiri Schindler 2 Disk Drive Firmware Algorithms NEU csg389 Information Storage Technologies, Fall 2006 Outline • Mapping LBNs to physical sectors • zones • defect management • track and cylinder skew • Bus and buffer management • optimizing storage subsystem resources • Advanced buffer space usage • prefetching and caching • read/write-on-arrival NEU csg389 Fall 2006, Jiri Schindler 4 How functionality is implemented • Some of it is in ASIC logic • error detection and correction • signal/servo processing • motor/seek control • cache hits (often) • Some of it is in firmware running on control processor • request processing • request queueing and scheduling • LBN-to-PBN mapping • Key considerations: cost and performance and cost • optimize common cases • keep things simple and space-conscious NEU csg389 Fall 2006, Jiri Schindler 5 Recall the storage device interface • Linear address space of equal-sized blocks • each identified by logical block number (LBN) … 5 6 7 12 23 … • Common block size: 512 bytes • Number of blocks: device capacity / block size NEU csg389 Fall 2006, Jiri Schindler 6 Recall the physical disk storage reality Cylinder Track Sector NEU csg389 Fall 2006, Jiri Schindler 7 Physical sectors of a single-surface disk NEU csg389 Fall 2006, Jiri Schindler 8 LBN-to-physical for a single-surface disk 4 5 16 17 3 6 15 28 29 18 27 30 40 41 7 2 14 39 42 19 26 38 43 31 37 25 44 32 13 1 36 45 20 8 4 46 24 33 12 35 34 21 9 0 23 22 11 10 NEU csg389 Fall 2006, Jiri Schindler 9 Extending mapping to a multi-surface disk NEU csg389 Fall 2006, Jiri Schindler 10 Some real numbers for modern disks • # of platters: 1-4 • 2-8 surfaces for data • # of tracks per surface: 10s of 1000s • same thing as # of cylinders • # sectors per track: 500-900 • so, 250-450KB • # of bytes per sector: usually 512 • can be chosen by OS for some disks • disk manufactures want to make it bigger NEU csg389 Fall 2006, Jiri Schindler 11 Clarification of Cylinder Numbering NEU csg389 Fall 2006, Jiri Schindler 12 First Complication: Zones • Outer tracks are longer than inner ones • so, they can hold more data • benefits: increased capacity and higher bandwidth • Issues • increased bookkeeping for LBN-to-physical mapping • more complex signal processing logic – because of variable bit rate timing • Compromise: zones • all tracks in each zone hold same number of sectors NEU csg389 Fall 2006, Jiri Schindler 13 Constant number of sectors per track NEU csg389 Fall 2006, Jiri Schindler 14 Multiple “zones” NEU csg389 Fall 2006, Jiri Schindler 15 A real zone breakdown • IBM Ultrastar 18ES (1998) Zone Start cylinder End cylinder SPT 0 0 377 390 1 378 1263 374 2 1264 2247 364 3 2248 3466 351 4 3466 4504 338 5 4505 5526 325 6 5527 7044 312 7 7045 8761 286 8 8762 9815 273 9 9816 10682 260 10 10683 11473 247 NEU csg389 Fall 2006, Jiri Schindler 16 Second Complication: Defects • Portions of the media can become unusable • both before installation and during use – former is MUCH more common than latter • Need to set aside physical space as spares • simplicity dictates having no holes in LBN space • many different organizations of spare space – e.g., sectors per track, cylinder, group of cylinders, zone • Two schemes for using spare space to handle defects • remapping – leave everything else alone and just remap the disturbed LBNs • slipping – change mapping to skip over defective regions NEU csg389 Fall 2006, Jiri Schindler 17 One spare sector per track 4 5 15 16 3 6 14 26 27 17 25 28 37 38 7 2 13 36 39 18 24 35 40 29 34 23 41 30 12 1 33 42 19 8 43 22 31 11 32 20 0 22 9 10 NEU csg389 Fall 2006, Jiri Schindler 18 Remapping from defective sector to spare 4 5 15 16 3 6 14 26 27 17 28 37 38 7 2 13 36 39 18 24 35 40 29 34 23 41 30 12 1 33 42 19 8 43 22 31 11 25 32 20 0 22 9 10 NEU csg389 Fall 2006, Jiri Schindler 19 LBN mapping slipped past defective sector 4 5 15 16 3 6 14 25 26 17 27 37 38 7 2 13 36 39 18 24 35 40 28 34 23 41 29 12 1 33 42 19 8 43 22 30 11 32 31 20 0 22 9 10 NEU csg389 Fall 2006, Jiri Schindler 20 Some Real Defect Management Schemes • High level facts • percentage of space: < 1% • always slip if possible – much more efficient for streaming data • One real scheme: Seagate Cheetah 4LP • 108 spare sectors every 12 cylinders – located on the last track of the 12-cylinder group – used only for remapped sectors grown during usage • many spare sectors on innermost cylinders – used to provide backstop for all slipped sectors NEU csg389 Fall 2006, Jiri Schindler 21 Computing physical location from LBN • First, check list of remapped LBNs • usually identifies exact physical location of replacement • If no match, do the steps from before • but, also account for slipped sectors that affect desired LBN • About 10 different management schemes • For any given scheme, the computations can be fairly straightforward. However, it is quite complex to discuss them all at once concretely NEU csg389 Fall 2006, Jiri Schindler 22 When defects “grow” during operation • First, try ECC • it can recover from many problems • Next, try to read the sector again • often, failure to read the sector is transient • cost is a full rotation added to access time • Last resort, report failure and remap sector • this means that the stored data has been lost • until next write to this LBN, reads get error response – new data allows the location change to take effect NEU csg389 Fall 2006, Jiri Schindler 23 Error Recovery Algorithm for READs READ SELECTOR typically tries 3 times ECC COMPARE NO RETRY YES ECC SYMBOL OR NO RETRY RETRY THRESHOLD LIMIT SECTOR REACHED? REACHED? READ NO YES REPLACE BLOCK ERROR NO INCREASE OR SIGNAL HOST TO RECOVERY LEVELS ERROR RECOVERY PERFORM EXHAUSTED? REPLACEMENT LEVEL YES DELIVER SIGNAL DATA TO DATA ERROR HOST TO HOST NEU csg389 Fall 2006, Jiri Schindler 24 Third Complication: Skew • Switching from one track to another takes time • sequential transfers would suffer full rotation • Solution: skew • offset physical location of first sector to avoid extra rotation – selection of skew value made from switch time statistics • Track skew • for when switching to next surface within a cylinder • Cylinder skew • for when switching from last surface of one cylinder to first surface of next cylinder NEU csg389 Fall 2006, Jiri Schindler 25 What happens to requests that span tracks? 1 2 11 0 0 1 0 13 14 3 10 23 12 1 11 12 13 2 12 25 26 15 22 35 24 13 23 24 25 14 24 27 34 25 35 26 11 4 9 2 10 3 23 35 28 16 21 33 26 14 22 34 27 15 34 29 32 27 33 28 10 22 17 5 8 20 15 3 9 21 16 4 33 30 31 28 32 29 21 32 31 18 19 30 29 16 20 31 30 17 9 20 19 6 7 18 17 4 8 19 18 5 8 7 6 5 7 6 Request spans 2 tracks After reading first part After track switch NEU csg389 Fall 2006, Jiri Schindler 26 What happens to requests that span tracks? 1 2 11 0 0 1 0 13 14 3 10 23 12 1 11 12 13 2 12 25 26 15 22 35 24 13 23 24 25 14 24 27 34 25 35 26 11 4 9 2 10 3 23 35 28 16 21 33 26 14 22 34 27 15 34 29 32 27 33 28 10 22 17 5 8 20 15 3 9 21 16 4 33 30 31 28 32 29 21 32 31 18 19 30 29 16 20 31 30 17 9 20 19 6 7 18 17 4 8 19 18 5 8 7 6 5 7 6 Request spans 2 tracks After reading first part After track switch Sector 12 rotates past during track switch, so full rotation needed NEU csg389 Fall 2006, Jiri Schindler 27 Same request with track skew of one sector 1 2 11 0 0 1 0 12 13 3 10 22 23 1 11 23 12 2 23 35 24 14 21 33 34 12 22 34 35 13 34 25 32 35 33 24 11 4 9 2 10 3 22 33 26 15 20 31 24 13 21 32 25 14 32 27 30 25 31 26 10 21 16 5 8 19 14 3 9 20 15 4 31 28 29 26 30 27 20 30 29 17 18 28 27 15 19 29 28 16 9 19 18 6 7 17 16 4 8 18 17 5 8 7 6 5 7 6 Request spans 2 tracks After reading first part After track switch Track skew prevents unnecessary rotation NEU csg389 Fall 2006, Jiri Schindler 28 Examples of Track and Cylinder Skews Quantum IBM Atlas 10k Ultrastar 18ES S ke Z w o n SPT Track Cylinder SPT Track Cylinder e 1 334 64 101 390 58 102 2 324 62 98 374 56 97 3 306 56 93 364 55 95 NEU csg389 Fall 2006, Jiri Schindler 29 Computing Physical Location from LBN Figure out cylno, surfaceno, and sectno • using algorithms indicated previously Compute total skew for first mapped physical sector on this track • totalskew = (cylno * cylskew) + (surfaceno + (cylno * (surfaces-1)) * trackskew) Compute rotational offset on given track • offset = (totalskew + sectno) % sectspertrack NEU csg389 Fall 2006, Jiri Schindler 30 Basic On-disk Caching NEU csg389 Information Storage Technologies, Fall 2006 On-disk RAM • RAM on disk drive controllers sector • firmware • speed matching buffer • prefetching buffer one $ segment • cache • Canonical disk drive buffers • several fixed-size “segments” • latest thing: variable-size segments • down the road: OS style management NEU csg389 Fall 2006, Jiri Schindler 32 Prefetching and Caching • Prefetching • sequential prefetch essentially free until next request arrives – and until track boundary • Note: physically sequential sectors are prefetched – usefulness depends on access patterns • Example algorithms – prefetch until buffer is full or next request arrives – MIN and MAX values for prefetching – if track n-1 and n have been READ, prefetch track n+1 • Caching • data in buffer segments retained as cache • most of the benefit comes from prefetching NEU csg389 Fall
Recommended publications
  • Sequence Listings Webinar Suzannah K. Sundby Carl Oppedahl
    Suzannah K. Sundby Canady + Lortz LLP Sequence Listings Webinar January 9, 2018 – Updated Version Carl Oppedahl Oppedahl Patent Law Firm LLC DISCLAIMER These materials and views expressed today reflect only the personal views of the author and do not necessarily represent the views of other members and clients of the author’s organizations. These materials are public information and have been prepared solely for educational purposes to contribute to the understanding of U.S. intellectual property law. While every attempt was made to ensure that these materials are accurate, errors or omissions may be contained therein, for which any liability is disclaimed. These materials and views are not a source of legal advice and do not establish any form of attorney-client relationship with the authors and their law firms. Why are some sequence errors not identified by Checker? Is “SEQ ID NO” required before sequences in Specifications? Do you recommend using the PatentIn Software? How do you correct sequence listing errors in PCTs? What about the new WIPO ST.26 Standard? Is Checker worthwhile? How can I easily edit sequence listings generated by others? Can I use other software to generate sequence listings? How do I file sequence listings using EFS-Web and ePCT? How long does it take the USPTO to review and approve? Any risk TYFNIL of using certain sequence descriptors? Help! IT locked down my computer… what do I do? Any sequence listing tips? Why Practitioners Should Know and Do Usually lack of time to send to outside vendors Last minute changes to applications (apps) containing sequences (seqs) Particularly, changes to claims Not hostage to staff/vendors, overtime, etc.
    [Show full text]
  • BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions
    BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions BEA TUXEDO Release 6.5 Document Edition 6.5 February 1999 Copyright Copyright © 1999 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
    [Show full text]
  • The AWK Programming Language
    The Programming ~" ·. Language PolyAWK- The Toolbox Language· Auru:o V. AHo BRIAN W.I<ERNIGHAN PETER J. WEINBERGER TheAWK4 Programming~ Language TheAWI(. Programming~ Language ALFRED V. AHo BRIAN w. KERNIGHAN PETER J. WEINBERGER AT& T Bell Laboratories Murray Hill, New Jersey A ADDISON-WESLEY•• PUBLISHING COMPANY Reading, Massachusetts • Menlo Park, California • New York Don Mills, Ontario • Wokingham, England • Amsterdam • Bonn Sydney • Singapore • Tokyo • Madrid • Bogota Santiago • San Juan This book is in the Addison-Wesley Series in Computer Science Michael A. Harrison Consulting Editor Library of Congress Cataloging-in-Publication Data Aho, Alfred V. The AWK programming language. Includes index. I. AWK (Computer program language) I. Kernighan, Brian W. II. Weinberger, Peter J. III. Title. QA76.73.A95A35 1988 005.13'3 87-17566 ISBN 0-201-07981-X This book was typeset in Times Roman and Courier by the authors, using an Autologic APS-5 phototypesetter and a DEC VAX 8550 running the 9th Edition of the UNIX~ operating system. -~- ATs.T Copyright c 1988 by Bell Telephone Laboratories, Incorporated. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopy­ ing, recording, or otherwise, without the prior written permission of the publisher. Printed in the United States of America. Published simultaneously in Canada. UNIX is a registered trademark of AT&T. DEFGHIJ-AL-898 PREFACE Computer users spend a lot of time doing simple, mechanical data manipula­ tion - changing the format of data, checking its validity, finding items with some property, adding up numbers, printing reports, and the like.
    [Show full text]
  • IBM VM/370 (Ems) Terminal User's Guide for FORTRAN IV Program Product Program Products
    SC28-6891-1 IBM VM/370 (eMS) Terminal User's Guide for FORTRAN IV Program Product Program Products Program Numbers 5734-F01 5734-F02 5734-F03 5734-LM1 5734-LM3 Page of SC28-6891-0,-1 Revised May 13, 1977 By TNL SN20-922S Second Edition (April 1975) This edition, as amended by technical newsletters SN20-9201 and SN20-9225, applies to Release 1.0 of the IBM Virtual Machine Facility/370 (VM/370) (CMS). This edition is a reprint of SC28-6891-0 incorporating changes released in Technical Newsletters SN28-0609 (dated March 1, 1973) and SN28-0620 (dated January 3, 1974). Changes are listed in the Summary of Amendments, Number 3, on the facing page. Information in this publication is subject to significant change. Any such changes will be published in new editions or technical newsletters. Before using the publication, consult the latest IBM System/360 Bibliography, GC20-0360, or IBM System/370 Bibliography, GC20-0001, and the technical newsletters that amend the particular bibliography, to learn which editions are applicable and current. Requests for copies of IBM publications shou'ld be made to your IBM representative or to the IBM branch office that serves your locality. Forms for readers' comments are provided at the back of this publication. If the forms have been removed, address comments to IBM Corporation, P. O. Box 50020, Programming Publishing, San Jose, California 95150. Comments and suggesti~ns become the property of IBM. © Copyright International Business Machines Corporation 1972 Summary of Amendments Number 1 Date of Publication: March 1, 1973 Form of Publication: TNL SN28-0609 to SC28-6891-0 CP and CMS Command Abbreviations Maintenance: Documentation Only Valid abbreviations have been added to the summary descriptions of significant CP and CMS commands.
    [Show full text]
  • Journal Import Requirements and Technical Guidance
    Journal Import Requirements and Technical Guidance Document Purpose The purpose of this document is to provide technical requirements information regarding the Journal Import process for those involved in the remediation of systems impacted by Workday Release 4 functionality. Prior to Workday Release 4 in July 2017, journal import utilizes the Journal Staging Area (JSA). This document provides information about the design that will be used to replace the JSA process of uploading files into Oracle with the new process for loading files into Workday. The process covers both non-Internal Service Provider (non-ISP) and Internal Service Provider (ISP) Journal Imports. Process Due to the large number of JSA sources, one of the guiding principles for the new Journal Import process has been that the overall process should feel familiar and require minimal training for end-users. In order to accomplish this goal, the design(s) utilizes the existing Managed File Transfer (MFT) source directories; the file formats, while different, utilize a file format that contains a Header (GLH) record and multiple Detail (GLD) records. The formats can be viewed in the template file - ISP and non-ISP journal file layouts. The designers of the process are aware that there are use cases that will require some sources to submit both JSA files to be routed to EBS at the same time that they are submitting Journal Import files to be imported into Workday. This use case is very constrained and will only last for a very short period of time. If you think this may apply to you, the team would like to hear from you.
    [Show full text]
  • Streampix 5 Tech Support:[email protected]
    Norpix Inc - www.norpix.com StreamPix 5 Tech Support:[email protected] STREAMPIX 5 Copyright Norpix Inc. (C) 2009-2013 StreamPix5 - Copyright Norpix Inc. (C) 2013 (1/187) Norpix Inc - www.norpix.com StreamPix 5 Tech Support:[email protected] Table of Contents About StreamPix 5...................................................................................................................................8 Minimum system requirements................................................................................................................9 Installing StreamPix...............................................................................................................................10 Authorization codes...............................................................................................................................11 StreamPix 5 Basics................................................................................................................................12 Ribbon Interface overview.................................................................................................................12 Faster !..........................................................................................................................................14 Default list of Keyboard Shortcuts.................................................................................................15 The Sequence slider ....................................................................................................................16
    [Show full text]
  • The UNIX Time- Sharing System
    1. Introduction There have been three versions of UNIX. The earliest version (circa 1969–70) ran on the Digital Equipment Cor- poration PDP-7 and -9 computers. The second version ran on the unprotected PDP-11/20 computer. This paper describes only the PDP-11/40 and /45 [l] system since it is The UNIX Time- more modern and many of the differences between it and older UNIX systems result from redesign of features found Sharing System to be deficient or lacking. Since PDP-11 UNIX became operational in February Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; they Bell Laboratories are generally smaller than the system described here. Most of them are engaged in applications such as the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from various switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly for research in operating sys- tems, languages, computer networks, and other topics in computer science, and also for document preparation. UNIX is a general-purpose, multi-user, interactive Perhaps the most important achievement of UNIX is to operating system for the Digital Equipment Corpora- demonstrate that a powerful operating system for interac- tion PDP-11/40 and 11/45 computers. It offers a number tive use need not be expensive either in equipment or in of features seldom found even in larger operating sys- human effort: UNIX can run on hardware costing as little as tems, including: (1) a hierarchical file system incorpo- $40,000, and less than two man years were spent on the rating demountable volumes; (2) compatible file, device, main system software.
    [Show full text]
  • K-Watch & K-Manager Pro Application Software User
    K-Watch & K-Manager Pro Application Software User Manual K-Watch & K-Manager Pro Patent Information This product may be protected by one or more patents. For further information, please visit: www.grassvalley.com/patents/ Copyright and Trademark Notice Grass Valley®, GV® and the Grass Valley logo and/or any of the Grass Valley products listed in this document are trademarks or registered trademarks of GVBB Holdings SARL, Grass Valley USA, LLC, or one of its affiliates or subsidiaries. All other intellectual property rights are owned by GVBB Holdings SARL, Grass Valley USA, LLC, or one of its affiliates or subsidiaries. All third party intellectual property rights (including logos or icons) remain the property of their respective owners. Copyright © 2021 GVBB Holdings SARL and Grass Valley USA, LLC. All rights reserved. Specifications are subject to change without notice. Terms and Conditions Please read the following terms and conditions carefully. By using K-Watch and K- Manager Pro documentation, you agree to the following terms and conditions. Grass Valley hereby grants permission and license to owners of K-Watch and K- Manager Pro to use their product manuals for their own internal business use. Manuals for Grass Valley products may not be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose unless specifically authorized in writing by Grass Valley. A Grass Valley manual may have been revised to reflect changes made to the product during its manufacturing life. Thus, different versions of a manual may exist for any given product.
    [Show full text]
  • User's Guide to Seqninja™ (Command-Line Edition)
    User's Guide to SeqNinja™ (Command-Line Edition) DNASTAR, Inc. 2014 Contents Before You Begin ...........................................................................................................................4 Overview .........................................................................................................................................5 Getting Started with SeqNinja ......................................................................................................6 Editing in the SeqNinja Shell ........................................................................................................8 Command-Line Options ................................................................................................................8 Supported File Formats .................................................................................................................9 The SeqNinja Language ..............................................................................................................10 Language Overview .................................................................................................................10 Escape Codes ...........................................................................................................................11 File Patterns .............................................................................................................................12 Settings .....................................................................................................................................13
    [Show full text]
  • Distributed Metadata Management for Post-Production Environments
    Distributed Metadata Management for Post-production Environments Werner Bailer1, Konstantin Schinas2, Georg Thallinger1, Wolfgang Schmidt2, Werner Haas1 1 JOANNEUM RESEARCH Forschungsgesellschaft mbH Institute of Information Systems & Information Management Steyrergasse 17, 8010 Graz, Austria 2 DVS Digital Video Systems GmbH Krepenstraße 8, 30165 Hannover, Germany Abstract: Efficient and flexible management of digital essence and associated metadata is of critical relevance in post-production. We describe a distributed content management system, which uses a peer-to-peer architecture in order to support the dynamic nature of post-production setups. Each peer indexes content on storage under its control by extracting relevant metadata from the headers of essence files as well as by performing automatic content analysis in a background process. The extracted metadata are indexed in a lightweight database at each peer and stored on disk in MPEG-7 XML format in order to provide a standard compliant interface for metadata exchange. The client tool running on a peer allows to edit the metadata in the data base, in the MPEG-7 file and in the file headers (e.g. to adjust timecodes). Moreover, the software provides tools for essence management (copying, moving, defragmentation). The system allows searching for content across all peers in the network. A visual keyframe-based browsing interface allows exploring the indexed content based on the extracted metadata. 1 Introduction Digital media technology resulted in a lasting change in post-production workflows. In digital post-production physical “storage media” such as film rolls and video tapes recede in importance. Instead, uncompressed image sequences in high resolution (e.g.
    [Show full text]
  • Guide to Openvms File Applications
    Guide to OpenVMS File Applications Order Number: AA-PV6PD-TK April 2001 This document is intended for application programmers and designers who write programs that use OpenVMS RMS files. Revision/Update Information: This manual supersedes the Guide to OpenVMS File Applications, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. and Patent and Trademark Office. Alpha, OpenVMS, PATHWORKS, DECnet, and DEC are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. ZK4506 The Compaq OpenVMS documentation set is available on CD-ROM.
    [Show full text]
  • Introduction to NGS
    Introduction to NGS Dr Torsten Seemann Peter MacCallum Cancer Centre - Fri 27 July 2012 What we will cover today ● High throughput sequencing ● Read sequences ● Base quality values ● FASTQ and FASTA files ● Sequence alignment ● BAM files ● Visualising alignments Sequencing In an ideal world... ● Collect a human genomic DNA sample ● Run it through the lab sequencing machine ● Get back 46 files ○ phased, haplotype chromosomes ○ each one a single contiguous sequence of AGTC ○ maybe some extra files if cancer sample Reality bites ● Unfortunately, no such instrument exists ○ can't read long stretches of DNA (yet) ● But we can read short pieces of DNA ○ shred DNA into ~500 bp fragments ○ we can read these reliably ● High-throughput sequencing ○ sequence millions of different fragments in parallel ○ various technologies to do this Technologies Instrument Method Read Length Yield Quality Value synthesis + Illumina fluorescence 250 ++++ +++++ ++++ ligation + SOLiD fluorescence 75 ++++ +++ +++ non-term NTP + Ion Torrent pH wells 300 ++ +++ +++ non-term NTP + Roche 454 luminescence 600 + ++++ ++ PacBio synthesis + ZMW 12000 +++ + ++ Illumina ● HiSeq 2000 ○ 1 week run ○ 300 Gb ○ 3 billion reads (100bp) ○ "big jobs" ● MiSeq ○ 1 day run ○ 1.5 Gb ○ 5 million reads (150bp) ○ "benchtop sequencer" What you get back Millions to billions of reads (big files): ATGCTTCTCCGCCTTTAATTAAAATTCCATTTCGTGCACCAACACCCGTTCCTACCATAATAGCTGTTGGAGTCGCTAAACCTAATGCACATGGACACGC <- 1st read CTAAGATACTGCCATCTTCTTCCAACGTAAATTGTACGTGATTTTCGATCCATTTTCTTCGAGGTTCTACTTTGTCACCCATTAGTGTGGTTACTCGACG
    [Show full text]