Sampling Design Trade-Offs in Occupancy Studies with Imperfect Detection: Examples and Software Author(S): Larissa L

Total Page:16

File Type:pdf, Size:1020Kb

Load more

Sampling Design Trade-Offs in Occupancy Studies with Imperfect Detection: Examples and Software Author(s): Larissa L. Bailey, James E. Hines, James D. Nichols, Darryl I. MacKenzie Source: Ecological Applications, Vol. 17, No. 1 (Jan., 2007), pp. 281-290 Published by: Ecological Society of America Stable URL: http://www.jstor.org/stable/40061993 . Accessed: 28/01/2011 15:07 Your use of the JSTOR archive indicates your acceptance of JSTOR's Terms and Conditions of Use, available at . http://www.jstor.org/page/info/about/policies/terms.jsp. JSTOR's Terms and Conditions of Use provides, in part, that unless you have obtained prior permission, you may not download an entire issue of a journal or multiple copies of articles, and you may use content in the JSTOR archive only for your personal, non-commercial use. Please contact the publisher regarding any further use of this work. Publisher contact information may be obtained at . http://www.jstor.org/action/showPublisher?publisherCode=esa. Each copy of any part of a JSTOR transmission must contain the same copyright notice that appears on the screen or printed page of such transmission. JSTOR is a not-for-profit service that helps scholars, researchers, and students discover, use, and build upon a wide range of content in a trusted digital archive. We use information technology and tools to increase productivity and facilitate new forms of scholarship. For more information about JSTOR, please contact [email protected]. Ecological Society of America is collaborating with JSTOR to digitize, preserve and extend access to Ecological Applications. http://www.jstor.org Ecological Applications, 17(1), 2007, pp. 281-290 © 2007 by the Ecological Society of America SAMPLING DESIGN TRADE-OFFS IN OCCUPANCY STUDIES WITH IMPERFECTDETECTION: EXAMPLES AND SOFTWARE Larissa L. Bailey, James E. Hines, James D. Nichols, and Darryl I. Mackenzie2 1 U.S. Geological Survey, Patuxent WildlifeResearch Center, 12100 Beech Forest Road, Laurel, Maryland 20708-4017 USA 2Proteus Wildlife Research Consultants, PO Box 5193, Dunedin, New Zealand Abstract. Researchers have used occupancy, or probability of occupancy, as a response or state variable in a variety of studies (e.g., habitat modeling), and occupancy is increasingly favored by numerous state, federal, and international agencies engaged in monitoring programs. Recent advances in estimation methods have emphasized that reliable inferences can be made from these types of studies if detection and occupancy probabilities are simultaneously estimated. The need for temporal replication at sampled sites to estimate detection probability creates a trade-off between spatial replication (number of sample sites distributed within the area of interest/inference) and temporal replication (number of repeated surveys at each site). Here, we discuss a suite of questions commonly encountered during the design phase of occupancy studies, and we describe software (program GENPRES) developed to allow investigators to easily explore design trade-offs focused on particularities of their study system and sampling limitations. We illustrate the utility of program GENPRES using an amphibian example from Greater Yellowstone National Park, USA. Key words: Ambystoma tigrinum; detection probability; monitoring; program GENPRES; site occupancy; survey design; tiger salamanders; YellowstoneNational Park. Introduction occupancy studies (also see Field et al. 2005). MacKenzie and three for Various fields of ecology use occupancy, or probability Royle (2005) investigated possible designs studies: "standard design," in which each that a patch is occupied by a species, as a state variable to single-season site is the same number of times; "double- address hypotheses about habitat associations (e.g., surveyed in which a subset of sites is Scott et al. 2002), species distribution (e.g., Fisher and sampling design," surveyed times and the sites are Shaffer 1996, Van Buskirk 2005), and metapopulation multiple remaining sampled only once; and "removal in which sites are dynamics (e.g., Hames et al. 2001, Barbraud et al. 2003, design," surveyed times until the is detected. The Martinez-Solano et al. 2003). Often, occupancy is the multiple target species authors found that there was an number of state variable of interest to wildlife managers assessing optimal for each of whether the impacts of management actions (Mazerolle et al. repeated surveys design, regardless the was to: achieve- a desired level of 2005), and it is commonly the focal variable in long-term objective (1) for minimal total or minimize monitoring programs (Manley et al. 2004). Recent precision survey effort; (2) the variance of the estimator for a papers have emphasized that reliable inferences from occupancy (var(\(/)) total number of and these types of studies require estimating occupancy from given surveys (MacKenzie Royle of on the detection-nondetection (presence-absence) data in a 2005). This optimal number surveys depended manner that deals with detection probabilities <1 study design and the true occupancy and detection for the but was of (Moilanen 2002, MacKenzie et al. 2002, 2003, 2005, probability target species, independent Gu and Swihart 2004). A key feature of these new the number of study sites. In general, the standard design estimation methods is that they generally require both outperformed the double-sampling design, and the spatial and temporal replication. The need for temporal removal design was also promising if detection proba- replication at sampled sites to estimate detection bility was believed to be constant across surveys. probability creates a trade-off between spatial replication MacKenzie and Royle (2005) considered their results (number of sample sites distributed within the area of to be a useful starting point for practitioners planning interest/inference) and temporal replication (number of occupancy studies, but cautioned that their results were repeated surveys at each site). based on a simple model, namely one that assumed that MacKenzie and Royle (2005) presented the first occupancy probability was similar across all sites and investigation of these trade-offs, and their findings that detection probability was constant over both time provide some needed guidance for efficient design of and space (sites). Furthermore, their results were based on asymptotic (large sample) methods and the results may not hold for studies with small sample sizes. These received 31 December 2005; revised 1 May 2006; Manuscript and recommend that be accepted 5 May 2006. Corresponding Editor: J. Van Buskirk. authors, others, study designs 3 E-mail: [email protected] evaluated on a case-by-case basis, tailoring the design to 281 282 LARISSA L. BAILEY ET AL. Ecologica|AppUcations specific scientific goals, the biology of the target species, sites and time, except when differences can be modeled and logistical or economical constraints. with covariates (e.g., habitat features); and (3) the target In this paper, we describe software (program GEN- species is identified correctly. PRES) developed to allow investigators to explore design model and parameter definitions trade-offs focused on the specifics of their study systems Single-season and attendant sampling limitations. The program MacKenzie et al. (2002, 2005, 2006) defined a permits investigation of both single-season and multi- probability-based model that consisted of two kinds of ple-season situations, with one or more groups of sites parameters: v|/ represents the probability that a site is that differ in their sampling intensity, occupancy, or occupied by the target species, and pj is the probability of detection probabilities. Users supply information on the detecting the species at an occupied site during the y'th model type (single- or multiple-season), construct a independent survey of a site. Assuming that detection relevant sampling design using a flexible general frame- histories from all s sites are independent, maximum work, and provide realistic parameter values, based on likelihood methods are used to estimate occupancy and either guesses or, preferably, on analysis of pilot data. detection probability. Additionally, it is possible to model Evaluations can be performed via analytic-numeric either occupancy or detection probability as a function of approximations (based on expected values of sample measured covariates using the logistic equation data) or simulations with either predefined or user- exp(X,-p) defined occupancy models. Detection histories are ' generated and can be saved as input files for multi- l+exp(X,-p) model evaluation other software such as using programs where 9, representsthe parameterof interest for site /, X, is MARK and Burnham or PRES- program (White 1999) the row vector of covariate information for site /, and p is ENCE (MacKenzie et al. 2006). We illustrate the use of the column vector of coefficients to be estimated. GENPRES an from program using amphibian example Occupancy probability may be modeled as a function of the Greater Yellowstone National Park Network. site-specific covariates that do not change during the Background: Occupancy Models season (e.g., habitat type), whereas detection probability and Parameter Estimation may be modeled as a function of either site-specific or survey-specific covariates (e.g., weather conditions or while for Estimating occupancy probability adjusting observer). The same modeling procedure also can be used detection has been the focus of several recent imperfect with a Bayesian
Recommended publications
  • KDE 2.0 Development, Which Is Directly Supported

    KDE 2.0 Development, Which Is Directly Supported

    23 8911 CH18 10/16/00 1:44 PM Page 401 The KDevelop IDE: The CHAPTER Integrated Development Environment for KDE by Ralf Nolden 18 IN THIS CHAPTER • General Issues 402 • Creating KDE 2.0 Applications 409 • Getting Started with the KDE 2.0 API 413 • The Classbrowser and Your Project 416 • The File Viewers—The Windows to Your Project Files 419 • The KDevelop Debugger 421 • KDevelop 2.0—A Preview 425 23 8911 CH18 10/16/00 1:44 PM Page 402 Developer Tools and Support 402 PART IV Although developing applications under UNIX systems can be a lot of fun, until now the pro- grammer was lacking a comfortable environment that takes away the usual standard activities that have to be done over and over in the process of programming. The KDevelop IDE closes this gap and makes it a joy to work within a complete, integrated development environment, combining the use of the GNU standard development tools such as the g++ compiler and the gdb debugger with the advantages of a GUI-based environment that automates all standard actions and allows the developer to concentrate on the work of writing software instead of managing command-line tools. It also offers direct and quick access to source files and docu- mentation. KDevelop primarily aims to provide the best means to rapidly set up and write KDE software; it also supports extended features such as GUI designing and translation in con- junction with other tools available especially for KDE development. The KDevelop IDE itself is published under the GNU Public License (GPL), like KDE, and is therefore publicly avail- able at no cost—including its source code—and it may be used both for free and for commer- cial development.
  • Note on Using the CS+ Integrated Development Environment

    Note on Using the CS+ Integrated Development Environment

    Tool News RENESAS TOOL NEWS on April 16, 2015: 150416/tn2 Note on Using the CS+ Integrated Development Environment When using the CS+ IDE, take note of the problem described in this note regarding the following point. Statements in source code which form a deeply-nested block 1. Products Concerned Products from the following list for which the version number of the CS+ common program is 3.00.00 to 3.01.00. - RX Family C/C++ Compiler Package (with IDE) - RL78 Family C Compiler Package (with IDE) - RH850 Family C Compiler Package (with IDE) - CS+ evaluation edition To check the version number of the product you have, refer to the following URL. https://www.renesas.com/cubesuite+_ver 2. Description CS+ might be terminated forcibly when a program is downloaded to a debugging tool or when an editor panel is opened after downloading a program. 3. Conditions Forced termination may occur when the source code for a project includes code that meets any of the following conditions. (a) { } blocks nested to a depth of 128 or more within a function. (b) 64 or more consecutive "else if" conditions are in sequence. (c) The total of double the number of consecutive "else if" conditions and the depth of the nesting of {} blocks at some point in the sequence of consecutive "else if" conditions is 128 or more. With conditions (b) and (c) above, the problem only arises when the C99 option is designated and the product is the RX family C/C++ compiler package (with IDE). 4. Workaround To avoid this problem, do any of the following.
  • Embrace and Extend Approach (Red Hat, Novell)

    Embrace and Extend Approach (Red Hat, Novell)

    Integrated Development Environments (IDEs) Technology Strategy Chad Heaton Alice Park Charles Zedlewski Table of Contents Market Segmentation.............................................................................................................. 4 When Does the IDE Market Tip? ........................................................................................... 6 Microsoft & IDEs ................................................................................................................... 7 Where is MSFT vulnerable?................................................................................................. 11 Eclipse & Making Money in Open Source........................................................................... 12 Eclipse and the Free Rider Problem ..................................................................................... 20 Making Money in an Eclipse World?................................................................................... 14 Eclipse vs. Microsoft: Handicapping the Current IDE Environment ................................... 16 Requirements for Eclipse success......................................................................................... 18 2 Overview of the Integrated Development Environment (IDE) Market An Integrated Development Environment (IDE) is a programming environment typically consisting of a code editor, a compiler, a debugger, and a graphical user interface (GUI) builder. The IDE may be a standalone application or may be included as part of one or more existing
  • The C Programming Language

    The C Programming Language

    The C programming Language The C programming Language By Brian W. Kernighan and Dennis M. Ritchie. Published by Prentice-Hall in 1988 ISBN 0-13-110362-8 (paperback) ISBN 0-13-110370-9 Contents ● Preface ● Preface to the first edition ● Introduction 1. Chapter 1: A Tutorial Introduction 1. Getting Started 2. Variables and Arithmetic Expressions 3. The for statement 4. Symbolic Constants 5. Character Input and Output 1. File Copying 2. Character Counting 3. Line Counting 4. Word Counting 6. Arrays 7. Functions 8. Arguments - Call by Value 9. Character Arrays 10. External Variables and Scope 2. Chapter 2: Types, Operators and Expressions 1. Variable Names 2. Data Types and Sizes 3. Constants 4. Declarations http://freebooks.by.ru/view/CProgrammingLanguage/kandr.html (1 of 5) [9/6/2002 12:20:42 ] The C programming Language 5. Arithmetic Operators 6. Relational and Logical Operators 7. Type Conversions 8. Increment and Decrement Operators 9. Bitwise Operators 10. Assignment Operators and Expressions 11. Conditional Expressions 12. Precedence and Order of Evaluation 3. Chapter 3: Control Flow 1. Statements and Blocks 2. If-Else 3. Else-If 4. Switch 5. Loops - While and For 6. Loops - Do-While 7. Break and Continue 8. Goto and labels 4. Chapter 4: Functions and Program Structure 1. Basics of Functions 2. Functions Returning Non-integers 3. External Variables 4. Scope Rules 5. Header Files 6. Static Variables 7. Register Variables 8. Block Structure 9. Initialization 10. Recursion 11. The C Preprocessor 1. File Inclusion 2. Macro Substitution 3. Conditional Inclusion 5. Chapter 5: Pointers and Arrays 1.
  • FEI~I&lt;Ts Ltistttute NEWS LETTER

    FEI~I<Ts Ltistttute NEWS LETTER

    NEWS LETTER FEI~I<tS ltiSTtTUTE from l\Yron J. Brophy, President VOL. 1. NO.7 Big Rapids, !.Iichigan July 23, 1951 . BUlmmG ffiOOR,i1SS. Mon~ Progress Meeting was held at the site at 1 p.m. Wednesday, Jul¥ lB. Those present were: For the Institution" . President Brophy, It'. Pattullo" and Mr. DeMOSS; for the Building Division" Mr. J. ~-'angema.n, and 11:r. Arthur Decker, the project Superintendent; for the IJuskegon Construction Company, Mr. Smith and Mr. Mastenbrook; fC1!.' t...~e Distel Heating Company, ur. Holgate; and for the Electric Construction t.; Machiner"J COmpany, ur. Brabon and Mr. Knight,; and for the Architect, l!r'. Roger Allen. Mr. Allen reported that the color scheme for all rooms in the East Wing has been determined. Mr. lD:rnest King, from the architect1s office, conferred With l!r. pattullo Friday to discuss the preparation of similar color schemes for the Vlest Wing. Work on General C~struction is proceeding rapidq and all mechanical contractors are keeping up with the construction. All structural steel roof framing for the one-story sections will be in place by the middle of this 'week and will be ready to receiVe steel roof deck. ];!t'. Smith hB.f3 received word from the Detroit Steel Products Company (sub­ contractors for the steel deck) that this material Will be Shipped some­ time bet\"loon July 30th and August loth. The fin!ll poUring of cement sla.bin the classroom building was completed last l'leck. The stone Window Sills have been received and installation has started. The alllnlinum vlindow frames Bl'e now being in­ stalled and arc ready for the laying of the glass blockS.
  • 2.3.7 80X86 Floating Point

    2.3.7 80X86 Floating Point

    Open Watcom C/C++ Compiler Options data segment. For example, the option "zt100" causes all data objects larger than 100 bytes in size to be implicitly declared as far and grouped in other data segments. The default data threshold value is 32767. Thus, by default, all objects greater than 32767 bytes in size are implicitly declared as far and will be placed in other data segments. If the "zt" option is specified without a size, the data threshold value is 256. The largest value that can be specified is 32767 (a larger value will result in 256 being selected). If the "zt" option is used to compile any module in a program, then you must compile all the other modules in the program with the same option (and value). Care must be exercised when declaring the size of objects in different modules. Consider the following declarations in two different C files. Suppose we define an array in one module as follows: extern int Array[100] = { 0 }; and, suppose we reference the same array in another module as follows: extern int Array[10]; Assuming that these modules were compiled with the option "zt100", we would have a problem. In the first module, the array would be placed in another segment since Array[100] is bigger than the data threshold. In the second module, the array would be placed in the default data segment since Array[10] is smaller than the data threshold. The extra code required to reference the object in another data segment would not be generated. Note that this problem can also occur even when the "zt" option is not used (i.e., for objects greater than 32767 bytes in size).
  • Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers

    Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers

    Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers Garry Bleasdale, QNX Software Systems, [email protected] Andy Gryc, QNX Software Systems, [email protected] Introduction This paper presents a selection of Eclipse IDE tips and tricks gathered from: the QNX® development community: our engineers, techies and trainers Foundry27, the QNX Community Portal for open development, where we have an Eclipse IDE forum Eclipse.org forums public web sites and blogs that offer Eclipse-related expertise The 27 tips described in this paper are the tips that we received from these sources and identified as most interesting and useful to developers. We present them here with the hope that they will help make you more productive when you use the Eclipse IDE. About Eclipse A modern embedded system may employ hundreds of software tasks, all of them sharing system resources and interacting in complex ways. This complexity can undermine reliability, for the simple reason that the more code a system contains, the greater the probability that coding errors will make their way into the field. (By some estimates, a million lines of code will ship with at least 1000 bugs, even if the code is methodically developed and tested.) Coding errors can also compromise security, since they often serve as entry points for malicious hackers. No amount of testing can fully eliminate these bugs and security holes, as no test suite can anticipate every scenario that a complex software system may encounter. Consequently, system designers and software developers must adopt a “mission-critical mindset” and employ software architectures that can contain software errors and recover from them quickly.
  • Using the Java Bridge

    Using the Java Bridge

    Using the Java Bridge In the worlds of Mac OS X, Yellow Box for Windows, and WebObjects programming, there are two languages in common use: Java and Objective-C. This document describes the Java bridge, a technology from Apple that makes communication between these two languages possible. The first section, ÒIntroduction,Ó gives a brief overview of the bridgeÕs capabilities. For a technical overview of the bridge, see ÒHow the Bridge WorksÓ (page 2). To learn how to expose your Objective-C code to Java, see ÒWrapping Objective-C FrameworksÓ (page 9). If you want to write Java code that references Objective-C classes, see ÒUsing Java-Wrapped Objective-C ClassesÓ (page 6). If you are writing Objective-C code that references Java classes, read ÒUsing Java from Objective-CÓ (page 5). Introduction The original OpenStep system developed by NeXT Software contained a number of object-oriented frameworks written in the Objective-C language. Most developers who used these frameworks wrote their code in Objective-C. In recent years, the number of developers writing Java code has increased dramatically. For the benefit of these programmers, Apple Computer has provided Java APIs for these frameworks: Foundation Kit, AppKit, WebObjects, and Enterprise Objects. They were made possible by using techniques described later in Introduction 1 Using the Java Bridge this document. You can use these same techniques to expose your own Objective-C frameworks to Java code. Java and Objective-C are both object-oriented languages, and they have enough similarities that communication between the two is possible. However, there are some differences between the two languages that you need to be aware of in order to use the bridge effectively.
  • GCC Toolchain Eclipse Setup Guide

    GCC Toolchain Eclipse Setup Guide

    !"#$ % '#((#()*!+,-.#)/$01234 GCC Toolchain Eclipse Setup Guide WP0001 Version 5 September 23, 2020 Copyright © 2017-2020 JBLopen Inc. All rights reserved. No part of this document and any associated software may be reproduced, distributed or transmitted in any form or by any means without the prior written consent of JBLopen Inc. Disclaimer While JBLopen Inc. has made every attempt to ensure the accuracy of the information contained in this publication, JBLopen Inc. cannot warrant the accuracy of completeness of such information. JBLopen Inc. may change, add or remove any content in this publication at any time without notice. All the information contained in this publication as well as any associated material, including software, scripts, and examples are provided “as is”. JBLopen Inc. makes no express or implied warranty of any kind, including warranty of merchantability, noninfringement of intellectual property, or fitness for a particular purpose. In no event shall JBLopen Inc. be held liable for any damage resulting from the use or inability to use the information contained therein or any other associated material. Trademark JBLopen, the JBLopen logo, TREEspanTM and BASEplatformTM are trademarks of JBLopen Inc. All other trademarks are trademarks or registered trademarks of their respective owners. Contents 1 Overview 1 1.1 About Eclipse ............................................. 1 2 Eclipse Setup Guide (Windows) 2 2.1 MSYS2 Installation .......................................... 2 2.2 Eclipse Installation .......................................... 11 2.3 Toolchain Installation ......................................... 16 2.4 Environment Variable Setup ..................................... 17 2.4.1 PATH Environnement Variable Setup ........................... 17 3 Eclipse Setup Guide (Linux) 22 3.1 Eclipse Installation .......................................... 22 3.2 Toolchain Installation ......................................... 27 3.3 GNU Make Installation .......................................
  • Pascalabc.NET (Версия 3.0)

    Pascalabc.NET (Версия 3.0)

    К.Ю. Поляков Новые возможности PascalABC.NET (версия 3.0) По материалам С.С. Михалковича (http://pascalabc.net) К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET 2 «Стандартный» Паскаль сегодня . классический учебный язык . популярен в школах России . хватает для сдачи ЕГЭ Тенденции в программировании: . Размер программы и скорость работы не критичны . Важна скорость разработки и надёжность . Нет современных типов данных (словари, списки, стеки и т.д.) . Нет высокоуровневых средств . Нет стандартных библиотек (типа STL) К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET 3 Паскаль сегодня: среды . АЛГО (В. Петрив) Python . Delphi C# • цена ??? • тяжеловесная (4 Гбайт) . Free Pascal • оболочка в стиле 1990-х • по пути Delphi • практически не развивается . PascalABC.NET • поддержка «старого» Паскаля • новые конструкции языка • новые структуры данных (коллекции) • использование библиотек .NET К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET (версия 3.0) Средства на каждый день К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET 5 Внутриблочные переменные begin var x: integer = 1; begin Область var y: integer; действия y y := x + 2; writeln(y); end; end. ! Понадобилась переменная – описал! К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET 6 Внутриблочные переменные в циклах for var i:=1 to 10 do begin writeln(i*i); Область ... действия i end; К.Ю. Поляков, 2015 http://kpolyakov.spb.ru Новые возможности PascalABC.NET 7 Автовывод типов begin var p := 1; // integer var t := 1.234; // real var s := 'Привет!'; // string // чтение с клавиатуры var n := ReadInteger('Введите n:'); var x := ReadReal; ..
  • C Programming Tutorial

    C Programming Tutorial

    C Programming Tutorial C PROGRAMMING TUTORIAL Simply Easy Learning by tutorialspoint.com tutorialspoint.com i COPYRIGHT & DISCLAIMER NOTICE All the content and graphics on this tutorial are the property of tutorialspoint.com. Any content from tutorialspoint.com or this tutorial may not be redistributed or reproduced in any way, shape, or form without the written permission of tutorialspoint.com. Failure to do so is a violation of copyright laws. This tutorial may contain inaccuracies or errors and tutorialspoint provides no guarantee regarding the accuracy of the site or its contents including this tutorial. If you discover that the tutorialspoint.com site or this tutorial content contains some errors, please contact us at [email protected] ii Table of Contents C Language Overview .............................................................. 1 Facts about C ............................................................................................... 1 Why to use C ? ............................................................................................. 2 C Programs .................................................................................................. 2 C Environment Setup ............................................................... 3 Text Editor ................................................................................................... 3 The C Compiler ............................................................................................ 3 Installation on Unix/Linux ............................................................................
  • Open WATCOM User's Guide

    Open WATCOM User's Guide

    this document downloaded from... Use of this document the wings of subject to the terms and conditions as flight in an age stated on the website. of adventure for more downloads visit our other sites Positive Infinity and vulcanhammer.net chet-aero.com Open Watcom FORTRAN 77 User's Guide Version 1.8 Notice of Copyright Copyright 2002-2008 the Open Watcom Contributors. Portions Copyright 1984-2002 Sybase, Inc. and its subsidiaries. All rights reserved. Any part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of anyone. For more information please visit http://www.openwatcom.org/ ii Preface The Open Watcom FORTRAN 77 Optimizing Compiler (Open Watcom F77) is an implementation of the American National Standard programming language FORTRAN, ANSI X3.9-1978, commonly referred to as FORTRAN 77. The language level supported by this compiler includes the full language definition as well as significant extensions to the language. Open Watcom F77 evolved out of the demands of our users for a companion optimizing compiler to Open Watcom's WATFOR-77 "load-and-go" compiler. The "load-and-go" approach to processing FORTRAN programs emphasizes fast compilation rates and quick placement into execution of FORTRAN applications. This type of compiler is used heavily during the debugging phase of the application. At this stage of application development, the "load-and-go" compiler optimizes the programmer's time ... not the program's time. However, once parts of the application have been thoroughly debugged, it may be advantageous to turn to a compiler which will optimize the execution time of the executable code.