DOCSLIB.ORG

Study for the Validation of Code Saturne for Turbulent Flow Simulations Appendices

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Study for the Validation of Code Saturne for Turbulent Flow Simulations Appendices Study for the Validation of Code Saturne for Turbulent Flow Simulations Appendices Jordi Amat Foraster June 2017 Study for the Validation of Code Saturne for Turbulent Flow Simulations Appendices by Jordi Amat Foraster to obtain the degree of Bachelor of Science in Aerospace Technology Engineering, Escola Superior d’Enginyeries Industrial, Aeronàutica i Audiovisual de Terrassa (ESEIAAT) Universitat Politècnica de Catalunya Student name: Jordi Amat Foraster Project duration: February 15, 2017 – June 10, 2017 Thesis supervisor/s: Prof. Arnau Miró Jané, ESEIAAT (DFIS), director Prof. Dr. Manel Soria Guerrero, ESEIAAT (DFIS), director An electronic version of this thesis is available at http://upcommons.upc.edu. Contents Contents i List of Figures ii A An introduction to Code_Saturne 1 A.1 Workflow ................................... 1 A.1.1 Meshes ................................ 2 A.1.2 Preprocessor ............................. 2 A.1.3 Graphical User Interface ....................... 3 A.1.4 User Subrutines ........................... 3 A.1.5 Kernel ................................. 4 A.1.6 Postprocessing ............................ 4 A.2 Directory Hierarchy .............................. 5 A.3 Setting Up and Running a Calculation ................... 6 A.4 Spatial Discretization ............................. 7 A.4.1 Gradient Calculation ......................... 8 A.4.2 Convective Scheme ......................... 8 A.5 Time Discretization .............................. 9 A.5.1 Pressure-based velocity-pressure solver .............. 9 A.6 Turbulence Models .............................. 10 A.7 Linear System Resolution .......................... 11 B Rates of Strain 12 C Mathematical Proofs 14 C.1 Global Kinetic Energy Equation ....................... 14 C.2 Velocity-Pressure Coupling of the Taylor-Green Vortex Flow ....... 16 References 18 i List of Figures A.1 Code_Saturne workflow diagram (inspired by Code_Saturne user’s man- ual[1]). ..................................... 1 A.2 Code_Saturne structure diagram. ...................... 5 A.3 Collocated arrangement of discrete variables. ............... 7 ii A An introduction to Code_Saturne The purpose of this appendix is to review the main features of Code_Saturne CFD software, as well as to serve as a simple and summarized guide to start using Code_Saturne. A.1 Workflow Code_Saturne workflow is represented in Fig. A.1. Figure A.1: Code_Saturne workflow diagram (inspired by Code_Saturne user’s man- ual[1]). 1 Appendix A. An introduction to Code_Saturne 2 A.1.1 Meshes Code_Saturne does not include a mesh generator, however, it supports multiple mesh formats. All of these formats have advantages and disadvantages (in terms of simplicity, functionality, longevity and popularity) when compared to each other. The following formats are currently supported by Code_Saturne : − .des from SIMAIL package. − .unv from I-deas universal tool. − .med from Salomé platform. − .cgns is a generic format. − .msh from the Gmsh tool. − .case from Ensight 6 or Ensight Gold tools. − .neu from Ansys FLUENT’s GAMBIT meshing tool. − .ccm from STAR-CCm+ tool. All these formats are described in greater detail in Code_Saturne user’s manual[1]. A.1.2 Preprocessor Mesh operations are handled by the Preprocessor, which works independently from the Kernel. The main interesting operations are: − Mesh import and read. − Mesh modification operations such as joining, periodicity and smoothing. − Mesh quality criteria computation to check the mesh consistency. The resulting data is transferred to the Kernel through specific files, named mesh_input, or placed in a directory of that name when multiple meshes are imported. In Code_Saturne user’s manual[1] it is encouraged to separate the preprocessing and cal- culation runs, as this not only speeds up calculations, but also ensures that the mesh is identical, regardless of the architecture or number of processors it is run on. Appendix A. An introduction to Code_Saturne 3 A.1.3 Graphical User Interface An optional Graphical User Interface (GUI) is available with Code_Saturne for config- uring the main parameters of the simulation (in .xml file). The GUI manages calcu- lation parameters, standard initialization values and boundary conditions for standard physics, pulverized fuel combustion, gas combustion, atmospheric flows, Lagrangian module, electrical model, compressible model and radiative transfers. If needed, the reader is encouraged to follow the Code_Saturne tutorial[2] to get used to the GUI. A.1.4 User Subrutines Code_Saturne provides great capabilities and user customization via C and Fortran subroutines. The running script runcase will compile all files in the SRC directory and link them with the existing libraries. Subroutines will have precedence to any settings on the .xml files from the GUI. The user’s subroutines are in the REFERENCE directory inside SRC and among others, some of the most important are: − cs_user_parameters.f90. Set physical and numerical calculation parameters. − cs_user_boundary_conditions.f90. Boundary conditions definitions (e.g., slid- ing or non-slip walls). − cs_user_physical_properties.f90. Definition of physical properties (e.g., vari- able viscosity or density). − cs_user_initialization.f90. Initialization of variables (e.g., velocity field). − cs_user_extra_operations.f90. Extra operations, i.e., computation of forces, profiles or probes. − cs_user_postprocess.f90. Post-processing of extra variables (e.g., vorticity). − cs_user_periodicity.c. Definition of periodicity conditions. If the reader wants to program his own subroutines is a must to refer to the Code_Saturne user’s manual[1]. Appendix A. An introduction to Code_Saturne 4 A.1.5 Kernel The Kernel module is the main program that recompiles the subroutines, reads the .xml and launches the case. A.1.6 Postprocessing Code_Saturne generally saves two output meshes: − Volume: for fluid variables such as pressure, velocity, etc. − Boundary: for wall defined variables such as efforts, fluxes, etc. They can all be set through the GUI. Additional output can be achieved through subrou- tines. All the this post-processing output in the .case format (both volume and boundary) is saved on the postprocessing directory and can be opened using Paraview open- source for its visualization. For visualizing the part, the Extract Block filter must be applied and the Fluid domain part must be selected. As Code_Saturne is a finite vol- ume collocated code, the information is on the cell centers. To interpolate the data to the nodes (for a smoother visualization), the celldata2pointdata filter must be used. Monitoring points can be defined whether in the GUI or in cs_user_parameters.f90. The monitoring points saved in the monitoring directory can be visualized via Matlab or Paraview. Appendix A. An introduction to Code_Saturne 5 A.2 Directory Hierarchy Code_Saturne is structured into studies that compress several cases as shown in Fig. A.2: Figure A.2: Code_Saturne structure diagram. The STUDY directory contains: − A directory MESH containing the mesh(es) necessary for the study. − A directory POST for the potential post-processing scripts (not used directly by the code). − One or several CASE directories for the calculations. Every CASE directory contains: − A directory DATA for the calculation data, the user script and the .xml file. − A directory SRC for the potential user subroutines necessary for the calculation. − A directory SCRIPTS for the runcase script to launch the calculation. − A directory RESU for saving the results after the simulation has finished. The case preparer command code_saturne create automatically creates a study di- rectory according to the typical architecture when typing: code_saturne create -s STUDY -c CASE_NAME1 CASE_NAME2 Appendix A. An introduction to Code_Saturne 6 This syntax creates a study directory STUDY with case subdirectories CASE_NAME1 and CASE_NAME2. If no case name is given, a default case directory called CASE1 is created. To improve the calculation traceability, the files and directories sent to RESU after a calculation are placed in a subdirectory named after that run’s ”id”, which is by default based on the run date and time, using the format: STUDY/CASE/RESU/YYYYMMDD- hhmm. See Code_Saturne user’s manual[1] for specific information about all the files sent to RESU. A.3 Setting Up and Running a Calculation This paragraph summarises the basic steps which are necessary to prepare and run a standard case: − Open a new terminal and prepare the directories using the code_saturne create command (see Section A.2). − Place the mesh(es) in the directory MESH. Make sure they are in a format com- pliant with Code_Saturne (see section A.1). − Go to the directory DATA and launch the GUI using the command ./SaturneGUI. − If not using the GUI, copy the DATA/REFERENCE/cs_user_scripts.py file to DATA and edit it, so that the correct run options and mesh paths may be set. Just as with user subroutines, settings defined in this file have priority over those defined in the GUI. − Place the necessary user subroutines in the directory SRC. When not using the Interface, some subroutines are compulsory (see the list in Code_Saturne user’s manual[1]). − Run the code_saturne run --initialize command to generate a folder in the RESU directory with the solver and the mesh files (it is highly recommended to rename this folder as a mesh folder). − Go into the directory src_saturne and edit the user subroutines to prepare the calculation. Then, compile them through code_saturne compile and substitute the
Load more

Recommended publications
  • Introduction CFD General Notation System (CGNS)
    CGNS Tutorial Introduction CFD General Notation System (CGNS) Christopher L. Rumsey NASA Langley Research Center Outline • Introduction • Overview of CGNS – What it is – History – How it works, and how it can help – The future • Basic usage – Getting it and making it work for you – Simple example – Aspects for data longevity 2 Introduction • CGNS provides a general, portable, and extensible standard for the description, storage, and retrieval of CFD analysis data • Principal target is data normally associated with computed solutions of the Navier-Stokes equations & its derivatives • But applicable to computational field physics in general (with augmentation of data definitions and storage conventions) 3 What is CGNS? • Standard for defining & storing CFD data – Self-descriptive – Machine-independent – Very general and extendable – Administered by international steering committee • AIAA recommended practice (AIAA R-101A-2005) • Free and open software • Well-documented • Discussion forum: [email protected] • Website: http://www.cgns.org 4 History • CGNS was started in the mid-1990s as a joint effort between NASA, Boeing, and McDonnell Douglas – Under NASA’s Advanced Subsonic Technology (AST) program • Arose from need for common CFD data format for improved collaborative analyses between multiple organizations – Existing formats, such as PLOT3D, were incomplete, cumbersome to share between different platforms, and not self-descriptive (poor for archival purposes) • Initial development was heavily influenced by McDonnell Douglas’ “Common
    [Show full text]
  • Development of a Coupling Approach for Multi-Physics Analyses of Fusion Reactors
    Development of a coupling approach for multi-physics analyses of fusion reactors Zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften (Dr.-Ing.) bei der Fakultat¨ fur¨ Maschinenbau des Karlsruher Instituts fur¨ Technologie (KIT) genehmigte DISSERTATION von Yuefeng Qiu Datum der mundlichen¨ Prufung:¨ 12. 05. 2016 Referent: Prof. Dr. Stieglitz Korreferent: Prof. Dr. Moslang¨ This document is licensed under the Creative Commons Attribution – Share Alike 3.0 DE License (CC BY-SA 3.0 DE): http://creativecommons.org/licenses/by-sa/3.0/de/ Abstract Fusion reactors are complex systems which are built of many complex components and sub-systems with irregular geometries. Their design involves many interdependent multi- physics problems which require coupled neutronic, thermal hydraulic (TH) and structural mechanical (SM) analyses. In this work, an integrated system has been developed to achieve coupled multi-physics analyses of complex fusion reactor systems. An advanced Monte Carlo (MC) modeling approach has been first developed for converting complex models to MC models with hybrid constructive solid and unstructured mesh geometries. A Tessellation-Tetrahedralization approach has been proposed for generating accurate and efficient unstructured meshes for describing MC models. For coupled multi-physics analyses, a high-fidelity coupling approach has been developed for the physical conservative data mapping from MC meshes to TH and SM meshes. Interfaces have been implemented for the MC codes MCNP5/6, TRIPOLI-4 and Geant4, the CFD codes CFX and Fluent, and the FE analysis platform ANSYS Workbench. Furthermore, these approaches have been implemented and integrated into the SALOME simulation platform. Therefore, a coupling system has been developed, which covers the entire analysis cycle of CAD design, neutronic, TH and SM analyses.
    [Show full text]
  • Integrated Tool Development for Used Fuel Disposition Natural System Evaluation –
    Integrated Tool Development for Used Fuel Disposition Natural System Evaluation – Phase I Report Prepared for U.S. Department of Energy Used Fuel Disposition Yifeng Wang & Teklu Hadgu Sandia National Laboratories Scott Painter, Dylan R. Harp & Shaoping Chu Los Alamos National Laboratory Thomas Wolery Lawrence Livermore National Laboratory Jim Houseworth Lawrence Berkeley National Laboratory September 28, 2012 FCRD-UFD-2012-000229 SAND2012-7073P DISCLAIMER This information was prepared as an account of work sponsored by an agency of the U.S. Government. Neither the U.S. Government nor any agency thereof, nor any of their employees, makes any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness, of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. References herein to any specific commercial product, process, or service by trade name, trade mark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the U.S. Government or any agency thereof. The views and opinions of authors expressed herein do not necessarily state or reflect those of the U.S. Government or any agency thereof. Sandia National Laboratories is a multi-program laboratory managed and operated by Sandia Corporation, a wholly owned subsidiary of Lockheed Martin Corporation, for the U.S. Department of Energy‘s National Nuclear Security Administration under contract DE-AC04-94AL85000. Integrated Tool Development for UFD Natural System Evaluation 9/1/2012 iii Integrated Tool Development for UFD Natural System Evaluation iv 9/1/2012 Integrated Tool Development for UFD Natural System Evaluation 9/1/2012 v Executive Summary The natural barrier system (NBS) is an integral part of a geologic nuclear waste repository.
    [Show full text]
  • Seven Keys for Practical Understanding and Use of CGNS
    Seven keys for practical understanding and use of CGNS Marc Poinot∗ Christopher L. Rumseyy SAFRAN NASA Langley Research Center [email protected] [email protected] We present key features of the CGNS standard, focusing on its two main elements, the data model (CGNS/SIDS) and its implementations (CGNS/HDF5 and CGNS/Python). The data model is detailed to emphasize how the topological user oriented information, such as families, are separated from the actual meshing that could be split or modified during the CFD workflow, and how this topological information is traced during the meshing process. We also explain why the same information can be described in multiple ways and how to handle such alternatives in an application. Two implementations, using HDF5 and Python, are illustrated in several use examples, both for archival and interoperability purposes. The CPEX extension formalized process is explained to show how to add new features to the standard in a consensual way; we present some of the next extensions to come. Finally we conclude by showing how powerful a consensual public approach like CGNS can be, as opposed to a stand-alone private one. All throughout the paper, we demonstrate how the use of CGNS could be of great benefit for both the meshing and CFD solver communities. I. Introduction The CFD General Notation System12 (CGNS) is a public standard for the CFD community. It has had more than 20 years of feedback from users throughout the world in industry, universities, and government research labs. The CGNS name is now well known in the CFD community, but it is often only associated with the CGNS library (CGNS/MLL) used by CFD tools.
    [Show full text]
  • Summary of Software Using HDF5 by Name (December 2017)
    Summary of Software Using HDF5 by Name (December 2017) Name (with Product Open Source URL) Application Type / Commercial Platforms Languages Short Description ActivePapers (http://www.activepapers File format for storing .org) General Problem Solving Open Source computations. Freely available SZIP implementation available from Adaptive Entropy the German Climate Encoding Library Special Purpose Open Source Computing Center IO componentization of ADIOS Special Purpose Open Source different IO transport methods Software for the display and Linux, Mac, analysis of X-Ray diffraction Adxv Visualization/Analysis Open Source Windows images Computer graphics interchange Alembic Visualization Open Source framework API to provide standard for working with electromagnetic Amelet-HDF Special Purpose Open Source data Bathymetric Attributed File format for storing Grid Data Format Special Purpose Open Source Linux, Win32 bathymetric data Basic ENVISAT Toolbox for BEAM Special Purpose Open Source (A)ATSR and MERIS data Bers slices and holomy Bear Special Purpose Open Source representations Unix, Toolkit for working BEAT Visualization/Analysis Open Source Windows,Mac w/atmospheric data Cactus General Problem Solving Problem solving environment Rapid C++ technical computing environment,with built-in HDF Ceemple Special Purpose Commercial C++ support Software for working with CFD CGNS Special Purpose Open Source Analysis data Tools for working with partial Chombo Special Purpose Open Source differential equations Command-line tool to convert/plot a Perkin
    [Show full text]
  • Getting Data Into Visit
    LLNL-SM-446033 Getting Data Into VisIt July 2010 Version 2.0.0 Brad Whitlock wrence La Livermore National Laboratory ii DISCLAIMER This document was prepared as an account of work sponsored by an agency of the United States government. Neither the United States government nor Lawrence Livermore National Security, LLC, nor any of their employees makes any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trade- mark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States government or Lawrence Livermore National Security, LLC. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States government or Lawrence Liver- more National Security, LLC, and shall not be used for advertising or product endorsement purposes. This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory in part under Contract W-7405-Eng-48 and in part under Contract DE-AC52-07NA27344. iii iv Table of Contents Introduction Manual chapters . 2 Manual conventions . 2 Strategies . 2 Picking a strategy . 3 Definition of terms . 4 Creating compatible files Creating a conversion utility or extending a simulation . 7 Survey of database reader plug-ins. 9 BOV file format . 9 X-Y Curve file format. 12 Plain text ASCII files .
    [Show full text]
  • AIAA Paper 2012-1264
    AIAA-2012-1264 50th AIAA Aerospace Sciences Meeting, January 9 – 12, 2012, Nashville, TN Recent Updates to the CFD General Notation System (CGNS) Christopher L. Rumsey∗ NASA Langley Research Center, Hampton, VA 23681 Bruce Wedan† Computational Engineering Solutions, San Ramon, CA 94582 Thomas Hauser‡ University of Colorado Boulder, Boulder, CO 80309 Marc Poinot§ ONERA - The French Aerospace Lab, F-92322 Chatillon, FRANCE The CFD General Notation System (CGNS)—a general, portable, and extensible standard for the storage and retrieval of computational fluid dynamics (CFD) analysis data—has been in existence for more than a decade (Version 1.0 was released in May 1998). Both structured and unstructured CFD data are covered by the standard, and CGNS can be easily extended to cover any sort of data imaginable, while retaining backward compatibility with existing CGNS data files and software. Although originally designed for CFD, it is readily extendable to any field of computational analysis. In early 2011, CGNS Version 3.1 was released, which added significant capabilities. This paper describes these recent enhancements and highlights the continued usefulness of the CGNS methodology. Glossary of Terms ADF CGNS Advanced Data Format, www.grc.nasa.gov/www/cgns/CGNS docs current/adf API Application Programming Interface CGIO CGNS low-level library, www.grc.nasa.gov/www/cgns/CGNS docs current/cgio CHLone CGNS special purpose C library (for HDF5 files only), chlone.sourceforge.net CGNS CFD General Notation System, cgns.org CGNSTalk CGNS user forum,
    [Show full text]
  • BASEMENT Reference Manual
    BASEMENT System Manuals VAW - ETH Zurich v2.8.1 BASEMENT System Manuals VAW - ETH Zurich v2.8.1 Contents Preamble 5 Credits . 5 License ......................................... 7 1 Pre-Processing in QGIS with BASEmesh 11 1.1 Introduction . 11 1.2 Tutorial 1: Mesh Generation based on Pointwise Elevation Data . 12 1.2.1 Project Settings . 13 1.2.2 Coordinate Reference System Configuration . 14 1.2.3 Loading Input Data for Elevation Model . 14 1.2.4 Saving Layer as Shape File . 15 1.2.5 Loading the Model Boundary . 15 1.2.6 Editing the Model Boundary . 17 1.2.7 Loading Breakline Data . 19 1.2.8 Creation of the Elevation Model as TIN . 20 1.2.9 Adaption of the Breaklines for Quality Meshing . 21 1.2.10 Creation of Region Marker Points . 22 1.2.11 Creation of Quality Mesh . 24 1.2.12 Interpolating elevation data from elevation mesh (TIN) . 25 1.2.13 3D view of the mesh . 26 1.2.14 Export of mesh to 2dm . 27 1.3 Tutorial 2: Import/Modify an existing Mesh and use Raster Data as Elevation Model . 28 1.3.1 Importing a .2dm mesh file . 29 1.3.2 Modifying the material indices of elements . 29 1.3.3 Manual editing of mesh elements . 33 1.3.4 Renumbering the mesh . 34 1.3.5 Interpolating elevations from raster data . 35 1.4 Tutorial 3: Using dividing constraints along boundary cross sections and setting up a BASEMENT simulation with a mesh from BASEmesh . 35 1.4.1 Using dividing constraints for Quality meshing .
    [Show full text]
  • About Pycgns 3 1.1 CGNS Standard
    pyCGNS.intro/Manual Release 4.2.0 Marc Poinot August 27, 2007 CONTENTS 1 About pyCGNS 3 1.1 CGNS Standard...........................................3 1.2 Package contents...........................................4 1.3 Quick start..............................................5 2 Build and Install 7 2.1 Required libraries..........................................7 2.2 Optional libraries...........................................7 2.3 Installation process..........................................8 2.4 Single module installation......................................8 2.5 Configuration file contents......................................8 2.6 NAV depends.............................................9 2.7 MAP depends............................................9 2.8 WRA depends............................................9 3 Glossary 11 4 PDF Docs 13 i ii pyCGNS.intro/Manual, Release 4.2.0 Release 4.2 • CGNS.MAP is now a wrapper to CHLone python module • CGNS.WRA reborn, re-coding using Cython • CGNS.VAL reborn • completely new CGNS.NAV using Qt, VTK and Cython • YouTube demos here The package gathers various tools and libraries for CGNS end-users and Python application developpers. The main object of pyCGNS is to provide the application developpers with a Python interface to CGNS/SIDS, the data model. The MAP and PAT modules are dedicated to this goal: map the CGNS/SIDS data model the CGNS/Python implementation. The WRA module contains wrapper on CGNS/MLL and a MLL-like set of functions that uses the CGNS/Python mapping as implementation. The NAV module supports the CGNS.NAV graphical browser, with nice features about tree exploration, copy/paste and even global node changes. Then, the VAL module is a parser engine for CGNS/Python tree compliance checking. The CGNS.VAL tool can analyze your CGNS/HDF5 file and returns you a large panel of diagnostics.
    [Show full text]
  • MASS2, Modular Aquatic Simulation System in Two Dimensions, User
    PNNL-14820-2 MASS2 Modular Aquatic Simulation System in Two Dimensions User Guide and Reference W. A. Perkins M. C. Richmond September 2004 Prepared for the U.S. Department of Energy under Contract DE-AC06-76RL01830 DISCLAIMER United States Government. Neither the United States Government nor any agency thereof, nor Battelle Memorial Institute, nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof, or Battelle Memorial Institute. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. PACIFIC NORTHWEST NATIONAL LABORATORY operated by BATTELLE for the UNITED STATES DEPARTMENT OF ENERGY under Contract DE-AC06-76RLO1830 Printed in the United States of America Available to DOE and DOE contractors from the Office of Scientific and Technical Information, P.O. Box 62, Oak Ridge, TN 37831-0062; ph: (865) 576-8401 fax: (865) 576-5728 email: [email protected] Available to the public from the National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Rd., Springfield, VA 22161 ph: (800) 553-6847 fax: (703) 605-6900 email: [email protected] online ordering: http://www.ntis.gov/ordering.htm This document was printed on recycled paper.
    [Show full text]
  • Data Formats for Visualization and I T Bilit Interoperability
    Data Formats for Visualization and Int eroperabilit y Steve Lantz Senior Research Associate 10/27/2008 www.cac.cornell.edu 1 How will you store your data? • Raw binary is compact but not portable – “Unformatted,” machine-specific representation – Byte-order issues: big endian (IBM) vs. little endian (Intel) • Formatted text is portable but not compact – Need to know all the details of formatting just to read the data – 1 byyygg()te of ASCII text stores only a single decimal digit (~3 bits) – Most of the fat can be knocked out by compression (gzip, bzip, etc.) – However, compression is impractical and slow for large files • Need to consider how data will ultimately be used – Are you trying to ensure future portability? – Will your favored analysis tools be able to read the data? – What storage constraints are there? 10/27/2008 www.cac.cornell.edu 2 Issues beyond the scope of this talk… • Provenance – The record of the origin or source of data – The history of the ownership or location of data – Purpose: to confirm the time and place of, and perhaps the person responsible for, the creation, production or discovery of the data • Curation – Collecting, cataloging, organizing, and preserving data • Ontology – Assigning t ypes and pro perties to data ob jects – Determining relationships among data objects – Associating concepts and meanings with data (semantics) •Portab le data fo rmats can an d do addr ess som e of th ese i ssues… 10/27/2008 www.cac.cornell.edu 3 Portable data formats: the HDF5 technology suite • Versatile data model that
    [Show full text]
  • Tutorial Session Agenda
    CFD General Notation System (CGNS) Tutorial Session Agenda • 7:00-7:30 Introduction, overview, and basic usage C. Rumsey (NASA Langley) • 7:30-7:50 Usage for structured grids B. Wedan (ANSYS – ICEM) • 7:50-8:10 Usage for unstructured grids E. van der Weide (Stanford University) • 8:20-8:40 HDF5 usage and parallel implementation T. Hauser (Utah State University) • 8:40-9:00 Python and in-memory CGNS trees M. Poinot (ONERA) • 9:00-9:30 Discussion and question/answer period 2 CFD General Notation System (CGNS) Introduction, overview, and basic usage Christopher L. Rumsey NASA Langley Research Center Chair, CGNS Steering Committee Outline • Introduction • Overview of CGNS – What it is – History – How it works, and how it can help – The future • Basic usage – Getting it and making it work for you – Simple example – Aspects for data longevity 4 Introduction • CGNS provides a general, portable, and extensible standard for the storage and retrieval of CFD analysis data • Principal target is data normally associated with computed solutions of the Navier-Stokes equations & its derivatives • But applicable to computational field physics in general (with augmentation of data definitions and storage conventions) 5 What is CGNS? • Standard for defining & storing CFD data – Self-descriptive – Machine-independent – Very general and extendable – Administered by international steering committee • AIAA recommended practice (AIAA R-101-2002) • In process of becoming part of international ISO standard • Free and open software • Well-documented • Discussion
    [Show full text]