CFD General Notation System
|
||
|
||
All CGNS files are stored on
GitHub (https://github.com/CGNS).
Issue tracking is located at:
https://cgnsorg.atlassian.net.
If you have not done so already, please REGISTER by e-mailing to the CGNS REGISTRAR the following information:
We also strongly recommend that you join the Discussion Group. This forum is the primary method used to keep CGNS users current with release and other important information updates. It is also used for discussing important problems/issues and for obtaining help from other CGNS users. What to DownloadFirst and most importantly, we recommend that you read the CGNS User Guide. This guide also includes sample code (UserGuideCode) for helping to get started with CGNS. For the up-to-date development source, visit GitHub Development.
git clone https://github.com/CGNS/CGNS.git
For the stable source, visit GitHub Stable.
git clone -b master https://github.com/CGNS/CGNS.git
As a minimum, you will need to download and compile the CGNS library code. Compilation requires an ANSI compliant C compiler. The source code may downloaded as a gzipped, tar file:
Historical Stable Releases: Patched version v4.1.2 addressed backward compatibility issues. Patched version v4.1.1 addressed backward compatibility and tools compilation errors.
This version implements: - CPEX42 (Storing bounding box of a grid, CGNS-149) - CPEX43 (Family hierarchy as a tree, CGNS-180) CGNS switched to using HDF5 compact storage for smaller datasets. The following APIs were removed: cgio_read_all_data, cgio_read_data, cgio_read_block_data cgio_read_all_data_f, cgio_read_data_f, cgio_read_block_data_f These APIs should be used instead: cgio_read_all_data_type, cgio_read_data_type, cgio_read_block_data_type cgio_read_all_data_type_f, cgio_read_data_type_f, cgio_read_block_data_type_f See RELEASE.txt for additional bug fixes.
Background [1]: The CGNS versions are currently numbered as follows: "Version x.y, Revision z", or "Version x.y-z".The first number represents the "major" version number. Within this number, the library maintains forward compatibility. Issue: With the introduction of CPEX 0041 "NGON modification proposal", CGNS 3.4.0 broke the convention of maintaining forward compatibility with-in the major versioning of CGNS. Version 4.0.0 was released with CPEX 0041 implemented, (essentially this is CGNS 3.4.0 released as version 4.0.0). Patched version v3.4.1 removed CPEX 0041.
In addition to numerous bug fixes, this version added new features: CPEX 40 Rind Plane Indexing, CPEX 41 NGON modification proposal, added support for NAG Fortran compilers, enforce the HDF5 version >= 1.8 is used in building HDF5, automatic detection and linking of szip and zlib if required by HDF5.
This Version implements CPEX 0038 and 0039, adds new functionality to the parallel capability, and makes extensive changes related to the Fortran library. Important note for Fortran users: V3.3 removes the usage of "include cgnslib_f.h". Instead, from this release forward, one must now employ the module "use CGNS". Also, if making use of 64-bit integers, Fortran programs must declare the relevant 64-bit integers via, e.g.: integer(cgsize_t) integername. This Version 3.2 release provides partial integration of parallel I/O using HDF5 with MPI. It also implements the Hierarchy of families (CPEX 0033), Multiple families (CPEX 0034), and Cubic elements (CPEX 0036). Conversion programs to and from AFLR3, FAST, and TetGen have also been added to CGNStools. Release 3.2.1 implements the suggestions by Cambridge Flow Solutions to the CMake scripts and adds routines to set the MPI communicator for parallel I/O. There are also numerous updates and fixes to the test cases, tools and CGNStools utilities. Note: CGNStools is no longer built automatically, you need to set the configure flag, --enable-cgnstools if using configure. Includes 64-bit integer capability and updated Tools for viewing and editing CGNS files. HDF5 is now the default file type, when CGNS is built with HDF5 version 1.8 or later. (CGNS can always read or write both HDF5 and ADF file types.) Older recent release versions are also available from https://github.com/CGNS/CGNS/releases. Even earlier releases can be found in the archives: https://github.com/CGNS/CGNS_archives. Also available:
NOTE: CGNS has switched from SourceForge (http://sourceforge.net/projects/cgns) to GitHub (https://github.com/CGNS). Issue tracking is located at: https://cgnsorg.atlassian.net. NOTE: if building CGNS with an HDF5 version earlier than 1.8, then links will not work when using HDF5 file type. Note about Linking CGNS with HDF5When using HDF5, it is currently recommended that CGNS be compiled using the newest HDF5 release. The following figure shows the typical performance of CGNS "make check" for various versions of HDF5 for serial I/O. It is recommended to NOT link with HDF5 versions 1.10.0-patch1, 1.10.1 or 1.10.2. Note about CompilersUsers should be aware that many new features in CGNS require the use of up-to-date compilers. For example, older FORTRAN compilers that are not FORTRAN 2003 compliant (such as g77) will not work for many CGNS features, and are not recommended or supported. Note to Users of Version 2.5 CGNSCurrent users of Version 2.5 should read the following short guide: which describes some of the reasons for upgrading to the latest version 3 software as well as how to handle portability issues between versions. Known Bugs/Issues in Latest Official (Stable) Release
|