DOCSLIB.ORG

Powerhouse(R) 4GL Migration Planning Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Powerhouse(R) 4GL Migration Planning Guide COGNOS(R) APPLICATION DEVELOPMENT TOOLS POWERHOUSE(R) 4GL FOR MPE/IX MIGRATION PLANNING GUIDE Migration Planning Guide 15-02-2005 PowerHouse 8.4 Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the Title Bar text for online help PowerHouse(R) 4GL version 8.4 USER GUIDE (DRAFT) THE NEXT LEVEL OF PERFORMANCETM Product Information This document applies to PowerHouse(R) 4GL version 8.4 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site (http://support.cognos.com). Copyright Copyright © 2005, Cognos Incorporated. All Rights Reserved Printed in Canada. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos, the Cognos logo, Axiant, PowerHouse, QUICK, and QUIZ are registered trademarks of Cognos Incorporated. QDESIGN, QTP, PDL, QUTIL, and QSHOW are trademarks of Cognos Incorporated. OpenVMS is a trademark or registered trademark of HP and/or its subsidiaries. UNIX is a registered trademark of The Open Group. Microsoft is a registered trademark, and Windows is a trademark of Microsoft Corporation. FLEXlm is a trademark of Macrovision Corporation. All other names mentioned herein are trademarks or registered trademarks of their respective companies. All Internet URLs included in this publication were current at time of printing. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical or technical errors may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of the information contained in this document. This page shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the publication will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. Information about Cognos Products and Accessibility can be found at www.Cognos.com. Table of Contents About this Book 5 Cognos PowerHouse 4GL, Axiant 4GL, and PowerHouse Web Documentation Set 6 Chapter 1: Migration Choices 11 Key Migration Decisions 11 Choosing the Target Platform 11 Choosing the Target File Systems 12 Choosing the End-User UI 13 Choosing the Migration Method 13 Choosing the Migration Timing 14 Moving Forward 14 Chapter 2: The Target Platform: UNIX 15 Platform Differences 15 Groups and Accounts vs. Directory Paths 15 File Names 15 Operating System Commands 16 System Management 18 PowerHouse Differences 19 PowerHouse File Extensions 19 Subfiles 20 Designated Files and Environment Variables 20 Case Sensitivity 21 Interrupt Control 21 PDL 21 QDESIGN/QUICK 22 QTP 23 QUIZ 23 After the Migration 24 PDL 24 QDESIGN/QUICK 24 QTP 25 QUIZ 25 Moving Forward 25 Chapter 3: The Target Platform: Windows 27 Platform Differences 27 Groups and Accounts vs. Folders 27 File Names 27 Operating System Commands 28 System Management 30 PowerHouse Differences 30 The Command Prompt Window 30 PowerHouse File Extensions 31 Paths in File Names 31 Subfiles 32 Designated Files and Environment Variables 32 Interrupt Control 33 PDL 33 QDESIGN/QUICK 33 QTP 35 Migration Planning Guide 3 QUIZ 35 After the Migration 36 PDL 36 QDESIGN/QUICK 37 QTP 37 QUIZ 37 Moving Forward 37 Chapter 4: The File Systems 39 Migrating from IMAGE 39 IMAGE to An IMAGE Emulator 39 IMAGE to Relational 40 IMAGE to Indexed 48 Migrating from KSAM (Indexed) 49 KSAM to Indexed 49 KSAM to Relational 51 Migrating from MPE Files (Direct, Relative, Sequential) 57 Direct and Sequential Files 57 Relative Files 58 Migrating from Allbase or Oracle (Relational) 59 Datatype Mappings 60 Moving Forward 61 Chapter 5: The Migration Plan 63 Overview 63 The Twelve Step Plan 63 Step 1: Define the Application 63 Step 2: Learn 63 Step 3: Take Inventory 64 Step 4: Identify What Will Be Migrated 64 Step 5: Develop a Plan 65 Step 6: Migrate The Pilot Application 65 Migrate with the Axiant Migration Tools 65 Migrate without the Axiant Migration Tools 68 Step 7: Assemble the Pilot Application 70 Step 8: Assess Steps 2 through 7 71 Step 9: Have Users Evaluate the Pilot 71 Step 10: Assess Steps 2 through 9 71 Step 11: Plan the Complete Migration 71 Step 12: Do the Complete Migration 71 In Conclusion 71 Index 73 4 PowerHouse(R) 4GL for MPE/iX About this Book Overview This book describes how to plan your migration of PowerHouse applications from MPE/iX to a UNIX or Windows platform. It is intended for system managers and developers who are familiar with the MPE/iX environment and have a basic knowledge of UNIX or Windows. Unless otherwise indicated, where "Windows" appears in the documentation, it applies to the Microsoft Windows operating systems. And unless otherwise indicated, where "relational database" appears in the documentation, it refers to a relational database management system (RDBMS). Chapter 1, "Migration Choices", gives an overview of the types of migration covered in this guide. It also identifies the factors which will influence your choices for each type of migration. Chapter 2, "The Target Platform: UNIX", discusses differences between MPE/iX and UNIX that will have to be addressed during the migration. Chapter 3, "The Target Platform: Windows", discusses differences between MPE/iX and Windows that will have to be addressed during the migration. Chapter 4, "The File Systems", contains a separate section for each of the MPE/iX file systems: IMAGE, KSAM, MPE, and relational. In each section, we identify the target file systems available for the given source file system, and then discuss the work involved in migrating between the two file systems. Chapter 5, "The Migration Plan", describes the 12-step plan to actually perform the migration. This identifies everything from identifying training needs to editing data definitions. We'll show two ways of doing this, with and without the Axiant 4GL migration tools. Migration Planning Guide 5 About this Book Cognos PowerHouse 4GL, Axiant 4GL, and PowerHouse Web Documentation Set PowerHouse 4GL, Axiant 4GL, and PowerHouse Web documentation includes planning and configuration advice, detailed information about statements and procedures, installation instructions, and last minute product information. Objective Document Get detailed Cognos PowerHouse 4GL Reference documents reference on the documentation CD. They provide detailed information for information about PowerHouse rules and each PowerHouse 4GL PowerHouse component. and PowerHouse The documents are: Web • Cognos PowerHouse 4GL PowerHouse Rules (PHRules.pdf) • Cognos PowerHouse 4GL PDL and Utilities Reference (PDL.pdf) • Cognos PowerHouse 4GL QDESIGN Reference (QD.pdf) • Cognos PowerHouse 4GL PowerHouse and Relational Databases (PHRDB.pdf) • Cognos PowerHouse 4GL PHD Reference (PHD.pdf) • Cognos PowerHouse 4GL QUIZ Reference (QZ.pdf) • Cognos PowerHouse 4GL QTP Reference (QTP.pdf) Available from the PowerHouse 4GL documentation CD or from: http://support.cognos.com and http://powerhouse.cognos.com Get an Cognos PowerHouse 4GL Primer. This document introduction to provides an overview of the PowerHouse language PowerHouse 4GL and a hands-on demonstration of how to use PowerHouse. Available from the PowerHouse 4GL documentation CD or from: http://www.cognos.com/products/powerhouse/ download.html Install Cognos PowerHouse 4GL & PowerHouse Web PowerHouse 4GL Getting Started books. These documents provide step-by-step instructions on installing PowerHouse 4GL on each supported platform. 6 PowerHouse(R) 4GL for MPE/iX About this Book Objective Document Get a summary of PowerHouse 4GL New Features. This document what’s new in contains a summary of new features in this release PowerHouse 4GL of PowerHouse. It also contains documentation for features specific to PowerHouse for Windows Available from: http://support.cognos.com and http://powerhouse.cognos.com Attend training Instructor-led classes are available for courses PowerHouse 4GL, Axiant 4GL, and PowerHouse Web. They provide hands-on education about these products. Available courses include: • PowerHouse 4GL - Introduction • PowerHouse 4GL - QUIZ Reporting By Users • PowerHouse 4GL - QUIZ Advanced Reporting • PowerHouse 4GL - Advanced Part I • PowerHouse 4GL - Advanced Part 2 • PowerHouse 4GL - Relational Interface Part I • PowerHouse 4GL - Relational Interface Part II • PowerHouse 4GL - Moving to Relational: Understanding Relational Databases • PowerHouse 4GL - Moving to Relational: Porting PowerHouse Applications • Axiant 4GL - Building Applications • Migrating Applications with Axiant 4GL • PowerHouse Web - Developing Applications Course descriptions and schedules are available from: http://support.cognos.com and http://powerhouse.cognos.com
Load more

Recommended publications
  • Bag-Of-Features Image Indexing and Classification in Microsoft SQL Server Relational Database
    Bag-of-Features Image Indexing and Classification in Microsoft SQL Server Relational Database Marcin Korytkowski, Rafał Scherer, Paweł Staszewski, Piotr Woldan Institute of Computational Intelligence Cze¸stochowa University of Technology al. Armii Krajowej 36, 42-200 Cze¸stochowa, Poland Email: [email protected], [email protected] Abstract—This paper presents a novel relational database ar- data directly in the database files. The example of such an chitecture aimed to visual objects classification and retrieval. The approach can be Microsoft SQL Server where binary data is framework is based on the bag-of-features image representation stored outside the RDBMS and only the information about model combined with the Support Vector Machine classification the data location is stored in the database tables. MS SQL and is integrated in a Microsoft SQL Server database. Server utilizes a special field type called FileStream which Keywords—content-based image processing, relational integrates SQL Server database engine with NTFS file system databases, image classification by storing binary large object (BLOB) data as files in the file system. Microsoft SQL dialect (Transact-SQL) statements I. INTRODUCTION can insert, update, query, search, and back up FileStream data. Application Programming Interface provides streaming Thanks to content-based image retrieval (CBIR) access to the data. FileStream uses operating system cache for [1][2][3][4][5][6][7][8] we are able to search for similar caching file data. This helps to reduce any negative effects images and classify them [9][10][11][12][13]. Images can be that FileStream data might have on the RDBMS performance.
    [Show full text]
  • Read and Write Images from a Database Using SQL Server
    HOWTO: Read and write images from a database using SQL Server Atalasoft is an imaging SDK and we do not directly have any dependencies on, or specific functionality for Database access (with the single exception of our DbImageSource class). However, since the typical means of image storage in a database is a BLOB (Binary Long Object), developers can take advantage of the AtalaImage.ToByteArray and AtalaImage.FromByteArray methods to use in their own code to store and retrieve image data to and from databases respectively. Atalasoft dotImage has streaming capabilities that can be used jointly with ADO.NET to read and write images directly to a database without saving to a temporary file. The following code snippets demonstrates this in C# and VB.NET. Please note that the code examples below are provided as a courtesy/convenience only and are not meant to be production code or represent the only way to access a database. The code is provided as is as but an example of how to get the needed data in a byte array suitable for use in storing to a database and how to take binary data containing an image back into an AtalaImage to use in our SDK. Write to a Database C# rivate void SaveToSqlDatabase(AtalaImage image) { SqlConnection myConnection = null; try { // Save image to byte array. // we will be storing this image as a Jpeg using our JpegEncoder with 75 quality // you could use any of our ImageEncoder classes to store as the respective image types byte[] imagedata = image.ToByteArray(new Atalasoft.Imaging.Codec.JpegEncoder(75)); // Create the SQL statement to add the image data.
    [Show full text]
  • Peoplesoft Financials/Supply Chain Management 9.2 (Through Update Image 40) Hardware and Software Requirements
    PeopleSoft Financials/Supply Chain Management 9.2 (through Update Image 40) Hardware and Software Requirements July 2021 PeopleSoft Financials/Supply Chain Management 9.2 (through Update Image 40) Hardware and Software Requirements Copyright © 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software
    [Show full text]
  • Eloquence: HP 3000 IMAGE Migration by Michael Marxmeier, Marxmeier Software AG
    Eloquence: HP 3000 IMAGE Migration By Michael Marxmeier, Marxmeier Software AG Michael Marxmeier is the founder and President of Marxmeier Software AG (www.marxmeier.com), as well as a fine C programmer. He created Eloquence in 1989 as a migration solution to move HP250/HP260 applications to HP-UX. Michael sold the package to Hewlett-Packard, but has always been responsible for Eloquence development and support. The Eloquence product was transferred back to Marxmeier Software AG in 2002. This chapter is excerpted from a tutorial that Michael wrote for HPWorld 2003. Email: [email protected] Eloquence is a TurboIMAGE compatible database that runs on HP-UX, Linux and Windows.Eloquence supports all the TurboIMAGE intrinsics, almost all modes, and they behave identically. HP 3000 applications can usually be ported with no or only minor changes. Compatibility goes beyond intrinsic calls (and also includes a performance profile.) Applications are built on assumptions and take advantage of specific behavior. If those assumptions are no longer true, the application may still work, but no longer be useful. For example, an IMAGE application can reasonably expect that a DBFIND or DBGET execute fast, independently of the chain length and that DBGET performance does not differ substantially between modes. If this is no longer true, the application may need to be rewritten, even though all intrinsic calls are available. Applications may also depend on external utilities or third party tools. If your application relies on a specific tool (let’s say, Robelle’s SUPRTOOL), you want it available (Suprtool already works with Eloquence). If a tool is not available, significant changes to the application would be required.
    [Show full text]
  • Turboimage/XL Database Management System Reference Manual
    TurboIMAGE/XL Database Management System Reference Manual HP e3000 MPE/iX Computer Systems Edition 8 Manufacturing Part Number: 30391-90012 E0701 U.S.A. July 2001 Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19 (c) (1,2). Acknowledgments UNIX is a registered trademark of The Open Group. Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U.S.A. © Copyright 1985, 1987, 1989, 1990, 1992, 1994, 1997, 2000, 2001 by Hewlett-Packard Company 2 Contents 1. Introduction Data Security . 27 Rapid Data Retrieval and Formatting . 28 Program Development .
    [Show full text]
  • Oracle Multimedia Image PL/SQL API Quick Start
    Oracle Multimedia Image PL/SQL API Quick Start Introduction Oracle Multimedia is a feature that enables Oracle Database to store, manage, and retrieve images, audio, video, and other heterogeneous media data in an integrated fashion with other enterprise information. Oracle Multimedia extends Oracle Database reliability, availability, and data management to multimedia content in media-rich applications. This article provides simple PL/SQL examples that upload, store, manipulate, and export image data inside a database using Oracle Multimedia’s PL/SQL packages. Some common pitfalls are also highlighted. The PL/SQL package used here is available in Oracle Database release 12c Release 2 or later with Oracle Multimedia installed (the default configuration provided by Oracle Universal Installer). The functionality in this PL/SQL package is the same as the functionality available with the Oracle Multimedia relational interface and object interface. For more details refer to Oracle Multimedia Reference and Oracle Multimedia User’s Guide. The following examples will show how to store images within the database in BLOB columns so that the image data is stored in database tablespaces. Oracle Multimedia image also supports BFILEs (pointers to files that reside on the filesystem), but this article will not demonstrate the use of BFILEs. Note that BFILEs are read -only so they can only be used as the source for image processing operations (i.e. you can process from a BFILE but you can’t process into a BFILE). NOTE: Access to an administrative account is required in order to grant the necessary file system privileges. In the following examples, you should change the command connect sys as sysdba to the appropriate one for your system: connect sys as sysdba Enter password: password The following examples also connect to the database using connect ron Enter password: password which you should change to an actual user name and password on your system.
    [Show full text]
  • A 10 Million Image Database for Scene Recognition
    This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TPAMI.2017.2723009, IEEE Transactions on Pattern Analysis and Machine Intelligence 1 Places: A 10 million Image Database for Scene Recognition Bolei Zhou, Agata Lapedriza, Aditya Khosla, Aude Oliva, and Antonio Torralba Abstract—The rise of multi-million-item dataset initiatives has enabled data-hungry machine learning algorithms to reach near- human semantic classification performance at tasks such as visual object and scene recognition. Here we describe the Places Database, a repository of 10 million scene photographs, labeled with scene semantic categories, comprising a large and diverse list of the types of environments encountered in the world. Using the state-of-the-art Convolutional Neural Networks (CNNs), we provide scene classification CNNs (Places-CNNs) as baselines, that significantly outperform the previous approaches. Visualization of the CNNs trained on Places shows that object detectors emerge as an intermediate representation of scene classification. With its high-coverage and high-diversity of exemplars, the Places Database along with the Places-CNNs offer a novel resource to guide future progress on scene recognition problems. Index Terms—Scene classification, visual recognition, deep learning, deep feature, image dataset. F 1 INTRODUCTION Whereas most datasets have focused on object categories If a current state-of-the-art visual recognition system would (providing labels, bounding boxes or segmentations), here send you a text to describe what it sees, the text might read we describe the Places database, a quasi-exhaustive repos- something like: “There is a sofa facing a TV set.
    [Show full text]
  • Using Free Pascal to Create Android Applications
    Using Free Pascal to create Android applications Michaël Van Canneyt January 19, 2015 Abstract Since several years, Free pascal can be used to create Android applications. There are a number of ways to do this, each with it’s advantages and disadvantages. In this article, one of the ways to program for Android is explored. 1 Introduction Programming for Android using Free Pascal and Lazarus has been possible since many years, long before Delphi unveiled its Android module. However, it is not as simple a process as creating a traditional Desktop application, and to complicate matters, there are several ways to do it: 1. Using the Android NDK. Google makes the NDK available for tasks that are CPU- intensive (a typical example are opengl apps), but warns that this should not be the standard way of developing Android apps. This is the way Delphi made it’s Android port: Using Firemonkey – which uses OpenGL to draw controls – this is the easiest approach. There is a Lazarus project that aims to do things in a similar manner (using the native-drawn widget set approach). 2. Using the Android SDK: a Java SDK. This is the Google recommended way to create Android applications. This article shows how to create an Android application using the Java SDK. 2 FPC : A Java bytecode compiler The Android SDK is a Java SDK: Android applications are usually written in Java. How- ever, the Free Pascal compiler can compile a pascal program to Java Bytecode. This is done with the help of the JVM cross-compiler. Free Pascal does not distribute this cross-compiler by default (yet), so it must be built from sources.
    [Show full text]
  • COMMUNICATOR 3000 MPE/Ix-Powerpatch 5 (Powerpatch Tape C.55.05) Based on Release 5.5
    COMMUNICATOR 3000 MPE/iX-PowerPatch 5 (PowerPatch Tape C.55.05) Based on Release 5.5 HP 3000 MPE/iX Computer Systems Volume 9, Issue 4 Customer Order Number 30216-90257 30216-90257 E0798 Printed in: U.S.A. July 1998 Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Acknowledgements Microsoft Windows ™, Windows 95 ™, Windows NT ™, Microsoft Access ™, Visual Basic ™, Visual C ++ ™, Visual FoxPro ™, and MS-Query ™are U.S. registered trademarks of Microsoft Corporation. ODBCLink/SE ™is a registered trademark of M. B. Foster Software Labs, Inc. Dr. DeeBeeSpy© 1995 Syware, Inc., all rights reserved. Axiant ™ and Impromptu ™ are registered trademarks of Cognos. Foxbase ™ is a registered trademark of Fox Software. Lotus ™ is a registered trademark of Lotus Development Corporation. Jetform is a registered trademark of Jetform Corporation. Paradox ™ is a registered trademark of Borland International Inc. PowerBuilder ™ is a registered trademark of Powersoft Corporation.
    [Show full text]
  • Decision Support and Data Warehousing in an HP 3000 Environment
    Paper# : 3011 Decision Support and Data Warehousing in an HP 3000 Environment. Christophe Jacquet Hewlett-Packard Co. 19447 Pruneridge Ave Cupertino, CA, 94087 Email: [email protected] Decision Support and Data Warehousing in an HP 3000 Environment. 3011 - 1 As corporate downsizing continues, flatter organizational structures give end users more decision making responsibilities. HP 3000 users can take advantage of powerful tools such as Image/SQL and ODBC drivers to gain direct access to the data in the databases. While these tools provide real benefits, the limitations of directly accessing operational data, in terms of performance, concurrency, ease of use and data quality, are rapidly becoming apparent. A current approach to Decision Support is the consolidation of company-wide data into a separately designed environment, commonly called a Data Warehouse. This paper covers the benefits and history of Data Warehouses and examines a variety of approaches available within the HP 3000 marketplace to implement such a Decision Support environment. It describes the elements needed to create a Data Warehouse environment from the Decision Support data store to the end user desktop, including extraction and cleansing tools. Data Warehousing is just one example of how enhancements to the MPE/iX operating environment permit HP 3000 customers to take full advantage of the many new technologies and approaches emerging in the Information Technology marketplace. Why is decision support important. In today’s world, companies have to be able to make decisions much faster than before. Making the right decisions at the right time can provide significant competitive advantage for a company.
    [Show full text]
  • Free Pascal and Lazarus Programming Textbook
    This page deliberately left blank. In the series: ALT Linux library Free Pascal and Lazarus Programming Textbook E. R. Alekseev O. V. Chesnokova T. V. Kucher Moscow ALT Linux; DMK-Press Publishers 2010 i UDC 004.432 BBK 22.1 A47 Alekseev E.R., Chesnokova O.V., Kucher T.V. A47 Free Pascal and Lazarus: A Programming Textbook / E. R. Alekseev, O. V. Chesnokova, T. V. Kucher M.: ALTLinux; Publishing house DMK-Press, 2010. 440 p.: illustrated.(ALT Linux library). ISBN 978-5-94074-611-9 Free Pascal is a free implementation of the Pascal programming language that is compatible with Borland Pascal and Object Pascal / Delphi, but with additional features. The Free Pascal compiler is a free cross-platform product implemented on Linux and Windows, and other operating systems. This book is a textbook on algorithms and programming, using Free Pascal. The reader will also be introduced to the principles of creating graphical user interface applications with Lazarus. Each topic is accompanied by 25 exercise problems, which will make this textbook useful not only for those studying programming independently, but also for teachers in the education system. The book’s website is: http://books.altlinux.ru/freepascal/ This textbook is intended for teachers and students of junior colleges and universities, and the wider audience of readers who may be interested in programming. UDC 004.432 BBK 22.1 This book is available from: The <<Alt Linux>> company: (495) 662-3883. E-mail: [email protected] Internet store: http://shop.altlinux.ru From the publishers <<Alians-kniga>>: Wholesale purchases: (495) 258-91-94, 258-91-95.
    [Show full text]
  • A Large-Scale Hierarchical Image Database
    ImageNet: A Large-Scale Hierarchical Image Database Jia Deng, Wei Dong, Richard Socher, Li-Jia Li, Kai Li and Li Fei-Fei Dept. of Computer Science, Princeton University, USA fjiadeng, wdong, rsocher, jial, li, [email protected] Abstract content-based image search and image understanding algo- rithms, as well as for providing critical training and bench- The explosion of image data on the Internet has the po- marking data for such algorithms. tential to foster more sophisticated and robust models and ImageNet uses the hierarchical structure of WordNet [9]. algorithms to index, retrieve, organize and interact with im- Each meaningful concept in WordNet, possibly described ages and multimedia data. But exactly how such data can by multiple words or word phrases, is called a “synonym be harnessed and organized remains a critical problem. We set” or “synset”. There are around 80; 000 noun synsets introduce here a new database called “ImageNet”, a large- in WordNet. In ImageNet, we aim to provide on aver- scale ontology of images built upon the backbone of the age 500-1000 images to illustrate each synset. Images of WordNet structure. ImageNet aims to populate the majority each concept are quality-controlled and human-annotated of the 80,000 synsets of WordNet with an average of 500- as described in Sec. 3.2. ImageNet, therefore, will offer 1000 clean and full resolution images. This will result in tens of millions of cleanly sorted images. In this paper, tens of millions of annotated images organized by the se- we report the current version of ImageNet, consisting of 12 mantic hierarchy of WordNet.
    [Show full text]