Transferring Ecosystem Simulation Codes to Supercomputers

Transferring Ecosystem Simulation Codes to Supercomputers

NASA Technical Memorandum 4662 ,'/','.-7"> , . Transferring Ecosystem Simulation Codes to Supercomputers J. W. Skiles and C. H. Schulbach (NASA-TM-46o2) TRANSFERRING N95-24uS2 ECOSYSTEM SIMULATION CODES TO SUPERCOMPUTERS (NASA. Ames Research Center) 40 p Unc|as HII61 0044586 L " .L v. NASA Technical Memorandum 4662 Transferring Ecosystem Simulation Codes to Supercomputers J. W. Skiles, Johnson Controls World Services, Inc., Cape Canaveral, Florida C. H. Schulbach, Ames Research Center, Moffett Field, California February1995 National Aeronautics and Space Administration Ames Research Center Moffett Field, California 94035-1000 CONTENTS Page Summary ................................................................................................................................................................... 1 Introduction ............................................................................................................................................................... Assumptions ...................................................................................................................................................... Computer Platform Description ................................................................................................................................ 3 Parallelism in Computer Architecture ............................................................................................................... 4 Flynn's Classification Scheme .......................................................................................................................... 4 Selecting the Cray Platform ............................................................................................................................... 5 Cray Architecture .............................................................................................................................................. 5 Ecosystem Model Description .................................................................................................................................. 5 Model Validation ............................................................................................................................................... 6 Ecosystem Model Structure ............................................................................................................................... 6 Characteristics of the Simulated Site ................................................................................................................. 7 Baseline Simulations ................................................................................................................................................ 7 Differences in Results and Possible Causes ...................................................................................................... 9 Data representation ..................................................................................................................................... 9 Computer arithmetic ................................................................................................................................... 10 Resolution of Discrepancies .............................................................................................................................. 1t Code Optimization .................................................................................................................................................... 11 Optimization Methodology ................................................................................................................................ 11 Establish Criteria ............................................................................................................................................... 11 Determine Program Bottleneck ......................................................................................................................... 11 Amdahl's Law ............................................................................................................................................ 12 Locate CPU-intensive Code .............................................................................................................................. 12 Restructure Code ............................................................................................................................................... 14 Determine Degree of Optimization ................................................................................................................... 14 Future Plans .............................................................................................................................................................. 15 Summary and Conclusions ....................................................................................................................................... 16 References ................................................................................................................................................................. 17 Appendix 1 Pawnee Plant Production ...................................................................................................................... 21 Appendix 2 SPUR Modules ..................................................................................................................................... 23 Appendix 3 Paranoia Output .................................................................................................................................... 25 IEEE Standard 754 Machine Output from Run of Paranoia, Single Precision ................................................ 25 Cray Output from Run of Paranoia, Single Precision ........................................................................................ 29 VAX Output from Run of Paranoia, Single Precision ...................................................................................... 34 iii PRECEDING PAGE BLANK NOT FILMED Transferring Ecosystem Simulation Codes to Supercomputers J. W. SKILES* AND C. H. SCHULBACH Ames Research Center Summary Introduction Many computer codes have been developed for the simu- Scientists involved in ecosystem studies have used models lation of ecological systems in the last twenty-five years. for many years. Models help explain processes in ecosys- This development took place initially on main-frame tems that cannot be observed or measured explicitly. They computers, then mini-computers, and more recently, on serve to direct study to areas where data and understand- micro-computers and workstations. Recent recognition of ing are missing. Further, models allow manipulation of earth system science as a High Performance Computing simulated ecosystems not feasible with the actual system and Communications Program Grand Challenge area because of time, budget, or conservation constraints. The emphasizes supercomputers (both parallel and distributed tools for ecosystem modeling, especially computing plat- systems) as the next set of tools for ecological simulation. forms, were also evolving simultaneously. Transferring ecosystem simulation codes to such systems Ecosystem model development began with the use of is not a matter of simply compiling and executing existing mainframe computational platforms (ref. 1). Models were code on the supercomputer, since significant differences submitted to a queue in the form of card decks, executed exist between the system architectures of sequential, in batch, and output returned as hardcopy, hours or days scalar computers and parallel and/or vector supercom- later. Mini-computers eased the turnaround time between puters. To more effectively match the application to the job executions because they were more affordable. Since architecture and achieve reasonable performance, the there were more of them, they usually operated in a time- parallelism, if it exists, of the original application must be sharing mode, and they offered greater access to graphic exploited. We discuss our work in transferring a general and peripheral plotting devices. grassland simulation model (developed on a VAX in the FORTRAN computer programming language) to a The advent of the micro-processor brought computing to Cray Y-MP/C-90. We show the Cray shared-memory the individual user. Large facilities were no longer neces- vector architecture and discuss our rationale for selecting sary for computing, and many specialized output devices the Cray. We describe porting the model to the Cray and and applications became available for the display of executing and verifying a baseline version, and we discuss model output. Ecosystem modelers, over this same period the changes we made to exploit the parallelism in the of time, have continued to demand faster and faster rates application and to improve code execution. As a result of of execution and more and more core or random access these efforts, the Cray executed the model 30 times faster memory (RAM). Supercomputing platforms would seem than the VAX 11/785 and 10 times faster than a Sun 4 to meet these continually rising demands. workstation. We achieved an additional speed increase of Though signs of documentation of supercomputer use are approximately 30 percent over the original Cray run by beginning to appear in the ecological literature (refs. 2-4), using the compiler's vectorizing capabilities and the supercomputers, generally located in large facilities, were machine's ability to put subroutines

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    48 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us