DOCSLIB.ORG

XL Fortran: Optimization and Programming Guide F Pthread Rwlockattr Getpshared(Rwattr, How XL Fortran I/O Interacts with Pipes, Special Pshared)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
XL Fortran: Optimization and Programming Guide F Pthread Rwlockattr Getpshared(Rwattr, How XL Fortran I/O Interacts with Pipes, Special Pshared) IBM XL Fortran for AIX, V16.1 IBM Optimization and Programming Guide Version 16.1 SC27-8064-00 IBM XL Fortran for AIX, V16.1 IBM Optimization and Programming Guide Version 16.1 SC27-8064-00 Note Before using this information and the product it supports, read the information in “Notices” on page 339. First edition This edition applies to IBM XL Fortran for AIX, V16.1 (Program 5765-J14, 5725-C74) and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product. © Copyright IBM Corporation 1990, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document ........ vii Chapter 4. Managing code size .... 51 Who should read this document ....... vii Steps for reducing code size ......... 52 How to use this document ......... vii Compiler option influences on code size..... 52 How this document is organized ....... vii The -qipa compiler option ........ 52 Conventions .............. viii The -qinline inlining option ........ 52 Related information ........... xii The -qhot compiler option ........ 53 Available help information ........ xii The -qcompact compiler option....... 53 Standards and specifications ....... xiv Other influences on code size ........ 53 Technical support ............ xiv High activity areas ........... 53 How to send your comments ........ xv Computed GOTOs and CASE constructs ... 54 Code size with dynamic or static linking ... 54 Chapter 1. Optimizing your applications 1 Distinguishing between optimization and tuning .. 1 Chapter 5. Debugging optimized code 57 Steps in the optimization process ....... 2 Understanding different results in optimized Basic optimization ............ 2 programs ............... 58 Optimizing at level 0 .......... 3 Debugging in the presence of optimization .... 58 Optimizing at level 2 .......... 3 Using -qoptdebug to help debug optimized Advanced optimization ........... 4 programs ............... 60 Optimizing at level 3 .......... 5 An intermediate step: adding -qhot suboptions at Chapter 6. Compiler-friendly level 3 ............... 6 programming techniques ....... 63 Optimizing at level 4 .......... 7 General practices ............ 63 Optimizing at level 5 .......... 8 Variables and pointers ........... 63 Specialized optimization techniques ...... 8 Arrays ................ 64 High-order transformation (HOT) ...... 9 Choosing appropriate variable sizes ...... 64 Interprocedural analysis (IPA) ....... 11 Submodules (Fortran 2008) ......... 65 Profile-directed feedback ......... 15 Handling table of contents (TOC) overflow ... 22 Vector technology ........... 25 Chapter 7. Exploiting POWER9 Using compiler reports to diagnose optimization technology ............. 69 opportunities ............. 29 POWER9 compiler options ......... 69 Tracing procedures in your code ....... 31 High-performance libraries that are tuned for Getting more performance ......... 35 POWER9 ............... 69 Beyond performance: effective programming POWER9 intrinsic procedures ........ 69 techniques ............... 36 Chapter 8. High performance libraries 73 Chapter 2. Tuning XL compiler Using the Mathematical Acceleration Subsystem applications ............ 37 (MASS) libraries ............. 73 Tuning for your target architecture ...... 37 Using the scalar library ......... 74 Using -qarch ............. 38 Using the vector libraries ......... 76 Using -qtune ............. 40 Using the SIMD libraries ......... 81 Using -qcache ............ 40 Compiling and linking a program with MASS .. 86 Before you finish tuning ......... 41 Using the Basic Linear Algebra Subprograms - BLAS 87 Further option driven tuning ........ 41 BLAS function syntax .......... 88 Options for providing application characteristics 41 Linking the libxlopt library ........ 90 Options to control optimization transformations 44 Options to assist with performance analysis .. 45 Chapter 9. Parallel programming with Options that can inhibit performance ..... 46 XL Fortran ............. 91 Compiling your parallelized code ....... 91 Chapter 3. Advanced optimization The _OPENMP C preprocessor macro and concepts .............. 47 conditional compilation ......... 91 Aliasing ............... 47 Setting runtime options .......... 92 Inlining................ 47 XLSMPOPTS ............. 92 Finding the right level of inlining ...... 48 Environment variables for OpenMP ..... 99 Optimizing your SMP code......... 106 © Copyright IBM Corp. 1990, 2018 iii Developing and running SMP applications .. 107 f_pthread_attr_t ........... 224 Parallelization directives.......... 107 f_pthread_cancel(thread) ........ 225 Summary of supported parallelization directives 108 f_pthread_cleanup_pop(exec) ....... 225 Detailed descriptions of parallelization directives 110 f_pthread_cleanup_push(cleanup, flag, arg) .. 226 Data sharing attribute rules........ 161 f_pthread_cond_broadcast(cond) ...... 227 Directive clauses ........... 163 f_pthread_cond_destroy(cond)....... 228 Routines for OpenMP .......... 187 f_pthread_cond_init(cond, cattr) ...... 228 omp_destroy_lock(svar) ......... 188 f_pthread_cond_signal(cond) ....... 229 omp_destroy_nest_lock(nvar) ....... 189 f_pthread_cond_t ........... 229 omp_get_active_level() ......... 189 f_pthread_cond_timedwait(cond, mutex, omp_get_ancestor_thread_num(level) .... 190 timeout) .............. 230 omp_get_dynamic() .......... 190 f_pthread_cond_wait(cond, mutex) ..... 230 omp_get_level() ........... 191 f_pthread_condattr_destroy(cattr)...... 231 omp_get_max_active_levels() ....... 191 f_pthread_condattr_getpshared(cattr, pshared) 232 omp_get_max_threads() ......... 191 f_pthread_condattr_init(cattr) ....... 232 omp_get_nested() ........... 192 f_pthread_condattr_setpshared(cattr, pshared) 233 omp_get_num_procs() ......... 192 f_pthread_condattr_t .......... 234 omp_get_num_threads() ......... 193 f_pthread_create(thread, attr, flag, ent, arg) .. 234 omp_get_schedule(kind, modifier) ..... 194 f_pthread_detach(thread) ........ 235 omp_get_team_size(level) ........ 194 f_pthread_equal(thread1, thread2) ..... 236 omp_get_thread_limit() ......... 195 f_pthread_exit(ret) ........... 236 omp_get_thread_num() ......... 195 f_pthread_getconcurrency() ........ 237 omp_get_wtick() ........... 196 f_pthread_getschedparam(thread, policy, param) 237 omp_get_wtime() ........... 197 f_pthread_getspecific(key, arg)....... 238 omp_in_final() ............ 198 f_pthread_join(thread, ret) ........ 239 omp_in_parallel() ........... 198 f_pthread_key_create(key, dtr) ....... 239 omp_init_lock(svar) .......... 199 f_pthread_key_delete(key) ........ 240 omp_init_nest_lock(nvar) ........ 200 f_pthread_key_t ........... 241 omp_set_dynamic(enable_expr) ...... 201 f_pthread_kill(thread, sig) ........ 241 omp_set_lock(svar) .......... 201 f_pthread_mutex_destroy(mutex) ...... 242 omp_set_max_active_levels(max_levels) ... 202 f_pthread_mutex_getprioceiling(mutex, old) .. 242 omp_set_nested(enable_expr) ....... 203 f_pthread_mutex_init(mutex, mattr) ..... 243 omp_set_nest_lock(nvar) ........ 204 f_pthread_mutex_lock(mutex) ....... 243 omp_set_num_threads(number_of_threads_expr) 204 f_pthread_mutex_setprioceiling(mutex, new, old) 244 omp_set_schedule(kind, modifier) ..... 205 f_pthread_mutex_t .......... 244 omp_test_lock(svar) .......... 206 f_pthread_mutex_trylock(mutex) ...... 245 omp_test_nest_lock(nvar) ........ 207 f_pthread_mutex_unlock(mutex) ...... 245 omp_unset_lock(svar) ......... 207 f_pthread_mutexattr_destroy(mattr) ..... 246 omp_unset_nest_lock(nvar)........ 208 f_pthread_mutexattr_getprioceiling(mattr, Pthreads Library Module ......... 209 ceiling) .............. 246 Pthreads data structures, functions, and f_pthread_mutexattr_getprotocol(mattr, proto) 247 subroutines ............. 210 f_pthread_mutexattr_getpshared(mattr, pshared) 247 f_maketime(delay)........... 212 f_pthread_mutexattr_gettype(mattr, type) ... 248 f_pthread_attr_destroy(attr)........ 213 f_pthread_mutexattr_init(mattr) ...... 249 f_pthread_attr_getdetachstate(attr, detach) ... 213 f_pthread_mutexattr_setprioceiling(mattr, f_pthread_attr_getguardsize(attr, guardsize) .. 214 ceiling) .............. 250 f_pthread_attr_getinheritsched(attr, inherit) .. 215 f_pthread_mutexattr_setprotocol(mattr, proto) 250 f_pthread_attr_getschedparam(attr, param) .. 215 f_pthread_mutexattr_setpshared(mattr, pshared) 251 f_pthread_attr_getschedpolicy(attr, policy) ... 216 f_pthread_mutexattr_settype(mattr, type) ... 251 f_pthread_attr_getscope(attr, scope) ..... 217 f_pthread_mutexattr_t ......... 252 f_pthread_attr_getstackaddr(attr, stackaddr) .. 217 f_pthread_once(once, initr) ........ 253 f_pthread_attr_getstacksize(attr, ssize) .... 218 f_pthread_once_t ........... 253 f_pthread_attr_init(attr) ......... 218 f_pthread_rwlock_destroy(rwlock) ..... 253 f_pthread_attr_setdetachstate(attr, detach) ... 219 f_pthread_rwlock_init(rwlock, rwattr) .... 254 f_pthread_attr_setguardsize(attr, guardsize) .. 220 f_pthread_rwlock_rdlock(rwlock) ...... 255 f_pthread_attr_setinheritsched(attr, inherit) .. 220 f_pthread_rwlock_t .......... 255 f_pthread_attr_setschedparam(attr, param) .. 221 f_pthread_rwlock_tryrdlock(rwlock) ..... 256 f_pthread_attr_setschedpolicy(attr, policy) ... 222 f_pthread_rwlock_trywrlock(rwlock) .... 256 f_pthread_attr_setscope(attr, scope) ..... 223 f_pthread_rwlock_unlock(rwlock) ..... 257 f_pthread_attr_setstackaddr(attr, stackaddr) .. 223 f_pthread_rwlock_wrlock(rwlock) ....
Load more

Recommended publications
  • Program Analysis and Optimization for Embedded Systems
    Program Analysis and Optimization for Embedded Systems Mike Jochen and Amie Souter jochen, souter ¡ @cis.udel.edu Computer and Information Sciences University of Delaware Newark, DE 19716 (302) 831-6339 1 Introduction ¢ have low cost A proliferation in use of embedded systems is giving cause ¢ have low power consumption for a rethinking of traditional methods and effects of pro- ¢ require as little physical space as possible gram optimization and how these methods and optimizations can be adapted for these highly specialized systems. This pa- ¢ meet rigid time constraints for computation completion per attempts to raise some of the issues unique to program These requirements place constraints on the underlying analysis and optimization for embedded system design and architecture’s design, which together affect compiler design to address some of the solutions that have been proposed to and program optimization techniques. Each of these crite- address these specialized issues. ria must be balanced against the other, as each will have an This paper is organized as follows: section 2 provides effect on the other (e.g. making a system smaller and faster pertinent background information on embedded systems, de- will typically increase its cost and power consumption). A lineating the special needs and problems inherent with em- typical embedded system, as illustrated in figure 1, consists bedded system design; section 3 addresses one such inherent of a processor core, a program ROM (Read Only Memory), problem, namely limited space for program code; section 4 RAM (Random Access Memory), and an ASIC (Applica- discusses current approaches and open issues for code min- tion Specific Integrated Circuit).
    [Show full text]
  • Fortran Reference Guide
    FORTRAN REFERENCE GUIDE Version 2018 TABLE OF CONTENTS Preface............................................................................................................ xv Audience Description......................................................................................... xv Compatibility and Conformance to Standards............................................................ xv Organization................................................................................................... xvi Hardware and Software Constraints...................................................................... xvii Conventions................................................................................................... xvii Related Publications........................................................................................ xviii Chapter 1. Language Overview............................................................................... 1 1.1. Elements of a Fortran Program Unit.................................................................. 1 1.1.1. Fortran Statements................................................................................. 1 1.1.2. Free and Fixed Source............................................................................. 2 1.1.3. Statement Ordering................................................................................. 2 1.2. The Fortran Character Set.............................................................................. 3 1.3. Free Form Formatting..................................................................................
    [Show full text]
  • SPSS to Orthosim File Conversion Utility Helpfile V.1.4
    SPSS to Orthosim File Conversion Utility Helpfile v.1.4 Paul Barrett Advanced Projects R&D Ltd. Auckland New Zealand email: [email protected] Web: www.pbarrett.net 30th December, 2019 Contents 3 Table of Contents Part I Introduction 5 1 Installation Details ................................................................................................................................... 7 2 Extracting Matrices from SPSS - Cut and Paste ................................................................................................................................... 8 3 Extracting Matrices from SPSS: Orthogonal Factors - E.x..c..e..l. .E..x..p..o..r.t................................................................................................................. 17 4 Extracting Matrices from SPSS: Oblique Factors - Exce.l. .E..x..p..o..r..t...................................................................................................................... 24 5 Creating Orthogonal Factor Orthosim Files ................................................................................................................................... 32 6 Creating Oblique Factor Orthosim Files ................................................................................................................................... 41 3 Paul Barrett Part I 6 SPSS to Orthosim File Conversion Utility Helpfile v.1.4 1 Introduction SPSS-to-Orthosim converts SPSS 11/12/13/14 factor loading and factor correlation matrices into the fixed-format .vf (simple ASCII text) files
    [Show full text]
  • IBM Power® Systems for SAS® Empowers Advanced Analytics Harry Seifert, Laurent Montaron, IBM Corporation
    Paper 4695-2020 IBM Power® Systems for SAS® Empowers Advanced Analytics Harry Seifert, Laurent Montaron, IBM Corporation ABSTRACT For over 40+ years of partnership between IBM and SAS®, clients have been benefiting from the added value brought by IBM’s infrastructure platforms to deploy SAS analytics, and now SAS Viya’s evolution of modern analytics. IBM Power® Systems and IBM Storage empower SAS environments with infrastructure that does not make tradeoffs among performance, cost, and reliability. The unified solution stack, comprising server, storage, and services, reduces the compute time, controls costs, and maximizes resilience of SAS environment with ultra-high bandwidth and highest availability. INTRODUCTION We will explore how to deploy SAS on IBM Power Systems platforms and unleash the full potential of the infrastructure, to reduce deployment risk, maximize flexibility and accelerate insights. We will start by reviewing IBM and SAS’s technology relationship and the current state of SAS products on IBM Power Systems. Then we will look at some of the infrastructure options to deploy SAS 9.4 on IBM Power Systems and IBM Storage, while maximizing resiliency & throughput by leveraging best practices. Next, we will look at SAS Viya, which introduces changes to the underlying infrastructure requirements while remaining able to be deployed alongside a traditional SAS 9.4 operation. We’ll explore the various deployment modes available. Finally, we’ll look at tuning practices and reference materials available for a deeper dive in deploying SAS on IBM platforms. SAS: 40 YEARS OF PARTNERSHIP WITH IBM IBM and SAS have been partners since the founding of SAS.
    [Show full text]
  • POWER® Processor-Based Systems
    IBM® Power® Systems RAS Introduction to IBM® Power® Reliability, Availability, and Serviceability for POWER9® processor-based systems using IBM PowerVM™ With Updates covering the latest 4+ Socket Power10 processor-based systems IBM Systems Group Daniel Henderson, Irving Baysah Trademarks, Copyrights, Notices and Acknowledgements Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Active AIX® POWER® POWER Power Power Systems Memory™ Hypervisor™ Systems™ Software™ Power® POWER POWER7 POWER8™ POWER® PowerLinux™ 7® +™ POWER® PowerHA® POWER6 ® PowerVM System System PowerVC™ POWER Power Architecture™ ® x® z® Hypervisor™ Additional Trademarks may be identified in the body of this document. Other company, product, or service names may be trademarks or service marks of others. Notices The last page of this document contains copyright information, important notices, and other information. Acknowledgements While this whitepaper has two principal authors/editors it is the culmination of the work of a number of different subject matter experts within IBM who contributed ideas, detailed technical information, and the occasional photograph and section of description.
    [Show full text]
  • IBM AIX Version 6.1 Differences Guide
    Front cover IBM AIX Version 6.1 Differences Guide AIX - The industrial strength UNIX operating system AIX Version 6.1 enhancements explained An expert’s guide to the new release Roman Aleksic Ismael "Numi" Castillo Rosa Fernandez Armin Röll Nobuhiko Watanabe ibm.com/redbooks International Technical Support Organization IBM AIX Version 6.1 Differences Guide March 2008 SG24-7559-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (March 2008) This edition applies to AIX Version 6.1, program number 5765-G62. © Copyright International Business Machines Corporation 2007, 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xiii Notices . xvii Trademarks . xviii Preface . xix The team that wrote this book . xix Become a published author . xxi Comments welcome. xxi Chapter 1. Application development and system debug. 1 1.1 Transport independent RPC library. 2 1.2 AIX tracing facilities review . 3 1.3 POSIX threads tracing. 5 1.3.1 POSIX tracing overview . 6 1.3.2 Trace event definition . 8 1.3.3 Trace stream definition . 13 1.3.4 AIX implementation overview . 20 1.4 ProbeVue . 21 1.4.1 ProbeVue terminology. 23 1.4.2 Vue programming language . 24 1.4.3 The probevue command . 25 1.4.4 The probevctrl command . 25 1.4.5 Vue: an overview. 25 1.4.6 ProbeVue dynamic tracing example . 31 Chapter 2. File systems and storage. 35 2.1 Disabling JFS2 logging .
    [Show full text]
  • Raiffeisenbank Speeds Data Warehouse, Cuts Costs with Red Hat Enterprise Linux
    CUSTOMER CASE STUDY RAIFFEISENBANK SPEEDS DATA WAREHOUSE, CUTS COSTS WITH RED HAT ENTERPRISE LINUX Raiffeisenbank, a banking institution that provides a wide range of services to private and corporate clients in the Czech Republic, needed to replace the aging hardware and IBM AIX operating system that supported its data warehouse. By migrating to Red Hat Enterprise Linux running on cost-effective Hitachi servers with Intel processors, the bank has tripled system performance speed and maintained stability — while cutting total cost SOFTWARE AND of ownership (TCO) by 50%. SERVICES Red Hat® Enterprise Linux® HARDWARE Hitachi Unified Compute Platform for Oracle Database Hitachi Compute Blade 2500 Prague, Czech Republic FINANCIAL SERVICES (CB 2500) Hitachi Virtual Storage HEADQUARTERS 3,000 EMPLOYEES Platform G600 (VSP G600) 120 BRANCHES PARTNER “There are many benefits to using Red Hat MHM computer a.s. and Oracle solutions together, and also BENEFITS from moving from IBM to Intel. We feel • Achieved three times faster a combination of Red Hat and Oracle on system performance an Intel platform is a preferred solution • Anticipates 50% decrease for any company.” in total cost of ownership over five years JIŘÍ KOUTNÍK HEAD OF SYSTEM ADMINISTRATION, • Gained greater flexibility by RAIFFEISENBANK eliminating vendor lock-in facebook.com/redhatinc @redhatnews linkedin.com/company/red-hat redhat.com AGING UNIX SYSTEM TOO SLOW FOR MODERN BUSINESS Raiffeisenbank a.s. provides a wide range of banking services to private and corporate clients in the Czech Republic at more than 120 branches and business client centers. The bank offers corpo- rate and personal finance products and services related to savings, insurance, and leasing, including specialized mortgage centers and business advisors.
    [Show full text]
  • ILE C/C++ Programmer's Guide
    IBM i 7.2 Programming IBM Rational Development Studio for i ILE C/C++ Programmer's Guide IBM SC09-2712-07 Note Before using this information and the product it supports, read the information in “Notices” on page 441. This edition applies to version 7, release 2, modification 0 of IBM Rational Development Studio for i (product number 5770-WDS) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1993, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents ILE C/C++ Programmer’s Guide..............................................................................1 PDF file for ILE C/C++ Programmer’s Guide............................................................................................... 3 About ILE C/C++ Programmer's Guide........................................................................................................5 Install Licensed Program Information................................................................................................... 5 Notes About Examples..........................................................................................................................
    [Show full text]
  • Developing Embedded SQL Applications
    IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 Note Before using this information and the product it supports, read the general information under Appendix B, “Notices,” on page 209. Edition Notice This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at http://www.ibm.com/shop/publications/ order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/ planetwide/ To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1993, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Introduction to embedded Include files for COBOL embedded SQL SQL................1 applications .............29 Embedding SQL statements
    [Show full text]
  • The UCSD P-System STATUT ORIL Y EX E:M PT
    DOCfi!D(ov~ by NSA on 12-01-2011, Transparency Case# 5335]UNCLASSIFIED The UCSD p-System STATUT ORIL Y EX E:M PT This paper discusses the UCSD p-System, an operating system for small computers developed at the University of California at San Diego. The discussion includes the overall system, file managing, editing, and programming in Pascal on the system. INTRODUCTION The UCSD p-System was developed at the University of California at San Diego to support Pascal programming on microcomputers. Similar to MS-DOS, the p-System is an operating system for small computers but is, in many ways, very different. The p-System is written in Pascal and now supports not only Pascal, but also FORTRAN, COBOL, BASIC, and Modula-2. The concept was to have an operating system that, once it was implemented on a machine, allowed any program written under that operating system to be truly transportable from computer to computer. That is to say, the p-System compiler would not actually translate the program into a language that was specific for, say, an 8088 chip on the IBM-PC, but rather would translate it into a "pseudo" language that, when used with an operating system designed for the PC, would run correctly. Similarly, if the operating system were implemented on a Digital Equipment Corporation (DEC) computer, this same pseudo code would still work properly with no modifications. The particular version of UCSD p-System tested was written for the IBM-PC and requires two single-sided double-density disk drives and at least 128K of memory.
    [Show full text]
  • GSI Local Guide
    UNIX Primer GSI Local Guide GSI Computing Center Version 2.0 This is draft version !!! Preface: More than one year ago, we published our ®rst version of the Unix primer, which has been used in the meantime by many people at GSI and even in the outside HEP community. Nowadays, as more and more physicists have access to a Unix computer either via a X-terminal or use their own workstation, and as the installed computing power has increased by a large factor, we have revised the ®rst version of our Unix primer. We tried to re¯ect the changes in the installedhardware, like the installationof the 11 machine AIX cluster, and the installationof new software products, as the batch system for job submission, new backup and restore products and the graphics system IDL. Almost all chapters have been revised, and some have undergone substantial changes like the introduction, the section about experimental data and tape handling and the chapter about the editors, where more editors are described in detail. Although many topics are still missing or could be improved, we decided to publishthe second edition of the Unix primer now in order to give a guide to the rapidly increasing Unix user community at GSI. As for the ®rst edition, many people again have contributed to this document: Wolfgang Ahner, Eliete Bertulani, Michael Dahlinger, Matthias Feyerabend, Ingo Giese, Horst GÈoringer, Eva Hocks, Peter Malzacher, Udo Meyer, Kerstin Schiebel, Kay Winkler and Heiko Weber. Preface for Version 1.0: In early summer 1991 the GSI Computing Center started a Unix Pilot Project investigating the hardware and software possibilities of centrally operated unix workstation systems.
    [Show full text]
  • A FORTRAN 77 Program for a Nonparametric Item Response Model: the Mokken Scale Analysis
    BehaviorResearch Methods, Instruments, & Computers 1988, 20 (5), 471-480 A FORTRAN 77 program for a nonparametric item response model: The Mokken scale analysis JOHANNES KINGMA University of Utah, Salt Lake City, Utah and TERRY TAERUM University ofAlberta, Edmonton, Alberta, Canada A nonparametric item response theory model-the Mokken scale analysis (a stochastic elabo­ ration of the deterministic Guttman scale}-and a computer program that performs this analysis are described. Three procedures of scaling are distinguished: a search procedure, an evaluation of the whole set of items, and an extension of an existing scale. All procedures provide a coeffi­ cient of scalability for all items that meet the criteria of the Mokken model and an item coeffi­ cient of scalability for every item. Four different types of reliability coefficient are computed both for the entire set of items and for the scalable items. A test of robustness of the found scale can be performed to analyze whether the scale is invariant across different subgroups or samples. This robustness test serves as a goodness offit test for the established scale. The program is writ­ ten in FORTRAN 77. Two versions are available, an SPSS-X procedure program (which can be used with the SPSS-X mainframe package) and a stand-alone program suitable for both main­ frame and microcomputers. The Mokken scale model is a stochastic elaboration of which both mainframe and MS-DOS versions are avail­ the well-known deterministic Guttman scale (Mokken, able. These programs, both named Mokscal, perform the 1971; Mokken & Lewis, 1982; Mokken, Lewis, & Mokken scale analysis. Before presenting a review of the Sytsma, 1986).
    [Show full text]