Hosted by CU logo University of Colorado
Boulder
Powered by ESGF-CoG logo
Welcome, Guest. | Login | Create Account
ESMF logo
You are at the CoG-CU node
 

Releases: 4* Series

Public releases have an "r" after the release name, e.g. 5_2_0r. Public releases that have been patched are labeled with their patch number e.g. "rp1", "rp2".

Click on the link for any release to download the code.

Release Release notes Known bugs

ESMF_4_0_0rp2

5/11/10

Reference Manual
(html) (pdf) 

User's Guide
(html) (pdf) 

Supported Platforms

  • Added support for the Intel compiler suite on the Cray XT platform.
  • Added support for the PGI 10.x compiler version.
  • The same as ESMF_4_0_0rp1 with the following exceptions:
    • Negative whole numbers specified as 8-byte floating point values for *_r8 time units in ESMF_TimeSet() and ESMF_TimeIntervalSet() methods now retain their sign, remaining negative.
    • Proxy Field objects, internally created during ESMF_StateReconcile(), now return the correct dimCount.
    • Also see SourceForge bugs list.
Platform-specific bugs:
  • Windows/Cygwin g95: ESMF_MeshUTest.F90 fails with what appears to be an incompatibility between C++ exceptions and the g95 driver on Cygwin.

ESMF_4_0_0rp1

3/23/10 

Reference Manual
(html) (pdf) 

User's Guide
(html) (pdf) 

Supported Platforms

  • List of ESMF interface changes since ESMF_4_0_0r.
  • The performance of ESMF_StateReconcile() for large processor counts has been improved dramatically.
  • During ESMF_FieldRegridStore() pole elements are no longer created if the source Grid extends all the way to the pole. Previously degenerate zero-sized elements were erroneously created around the pole for this case. 
  • Added ESMF_LocStreamCreate() that allows a user to create a LocStream from a background Grid or Mesh. This call creates a new LocStream that is a redistribution of an existing LocStream. The new LocStream is created so that an element with a given set of coordinates is located on the PET with the piece of background Grid (or Mesh) that contains those coordinates.
  • Added support for replicated dimensions in Field along all Grid dimensions. A gridToFieldMap argument containing all zeros in ESMF_FieldCreate() and ESMF_FieldSetCommit() indicates that no Grid dimensions are part of the Field. Instead the Field is replicated across all the DEs along all the Grid dimensions.
  • An "advice to installers" paragraph has been added to the Installation section of the User Guide. The paragraph recommends that a standard environment variable named ESMFMKFILE be set by the system to point to the "esmf.mk" file of the ESMF installation. Standardizing this aspect of the ESMF installation process promotes the design of portable ESMF application build systems.
  • The linker flags that are provided to the user through "esmf.mk" on the ORNL Cray XT systems are now portable between jaguar (XT4) and jaguarpf (XT5).
  • The "mvapich2" option was added to build environment variable ESMF_COMM. Please refer to the second table in the Supported Platforms section of the User Guide to see where it can be used.
  • A number of known bugs have been fixed, including issues with repeating sticky and non-sticky Alarms. Please see the known bugs list for more information.
  • The same as ESMF_4_0_0r with the following exceptions:
    • The problem that caused segmentation faults in ESMF_StateReconcile() has been fixed.
    • Repeating sticky Alarms whose ringInterval is less than or equal to the Clock's timeStep now ring properly.
    • Repeating sticky Alarms that are not turned off during a waiting period of a Clock run now ring properly after the waiting period is over, Alarms are cleared, and turning off of subsequent Alarms resumes.
    • Repeating non-sticky Alarms now ring properly for a Clock that goes into ESMF_MODE_REVERSE at the Clock's stopTime, while an Alarm is ringing.
    • Windows/Cygwin gfortran and g95 no longer require the setting of environment variables ESMF_F90LINKOPTS, ESMF_CXXLINKOPTS and ESMF_F90LINKLIBS.
    • The build issue with GCC 4.4.1 has been resolved.
    • The problem that caused segmentation faults on a user's Linux system with Intel compilers and OpenMPI has been identified and corrected in the ESMF library code.
  • Also see SourceForge bugs list.
  • Platform-specific bugs:
    • Windows/Cygwin g95: ESMF_LogErrUTest.F90 fails intermittently.

ESMF_4_0_0r

10/30/09 

Reference Manual
(html) (pdf) 

User's Guide
(html) (pdf) 

Supported Platforms

  • List of ESMF interface changes since ESMF_4_0_0.
  • Component methods necessary to support user-level threading were added. These methods (such as ESMF_GridCompSetMaxPEs(); see the list of interface changes for others) allow a Component to set the characteristics of its VM before it is started up. One application of these additional methods is to share the Processing Elements (PEs), provided by the Persistent Execution Threads (PETs) of the parent Component, across a lesser number of child PETs. These PEs can then be used in user-level OpenMP threading during Component method execution.
  • Implemented the underpinnings of a Component-level automatic garbage collection scheme. An initial effect is that ESMF objects that were created within a Component will be destroyed when the Component is destroyed. Additional garbage collection features will be finished and documented in future releases.
  • Corrected ESMF_StateReconcile() code to correctly handle nested States.
  • Removed the (previously undocumented) restriction that prevented States, originating from partially overlapping Components, from being reconciled with ESMF_StateReconcile().
  • The internal buffer in ESMF_StateReconcile() is now dynamically allocated. Applications with a large number of objects contained in a State should no longer run up against internal buffer size limitations.
  • Added ESMF_StateRead() and ESMF_StateWrite() methods to read and write undistributed Arrays serially from a NetCDF file. See example in the State section of the ESMF Reference Manual.
  • The Internal State implementation has been changed so that ESMF_GridCompGetInternalState() always returns the Internal State set by the last ESMF_GridCompSetInternalState() call. The previous behavior was that it would always return the Internal State set by the first ESMF_GridCompSetInternalState() call. The same is true with equivalent CplComp methods.
  • FieldBundles can now be created from Fields built on LocStreams or Meshes.
  • Fields built on LocStreams and Meshes now work with ESMF_StateReconcile() and can therefore be transferred between Components running on different sets of PETs.
  • The farray argument in ESMF_FieldGet() method has been renamed to farrayPtr to better reflect the nature of the returned parameter, and to be consistent with the ESMF_ArrayGet() method.
  • Regrid weight generation can be performed either through an offline application or through an online interface. The offline application is a separate executable which takes in two NetCDF grid files and outputs a NetCDF interpolation weight file. The online interface (ESMF_FieldRegridStore()) takes ESMF Field descriptions and generate weights. The weights can either be returned to the user through Fortran arrays, or can be applied with a parallel sparse matrix multiply in an ESMF_FieldRegrid() call.
  • The ESMF offline weight generation application supports:
    • Regridding between a pair of 2D logically rectangular Grids mapped to a sphere.
    • Multiple pole options: 1) Pole value is an average of source values around pole, 2) Pole value is an average of n-point stencil of source values, or 3) No pole.
    • Higher-order patch recovery interpolation.
  • For details please see the "File Based Regrid Weight Application" section in the "Infrastructure: Fields and Grids" part of the ESMF reference manual.
  • The ESMF online weight generation interface supports:
    • Regridding between any combination of 2D Meshes composed of triangles and quadrilaterals, and 2D Grids composed of a single logically rectangular tile with no edge connections.
    • Regridding between any combination of 3D Meshes composed of hexahedrons, and 3D Grids composed of a single logically rectangular region.
    • Regridding between a pair of 2D logically rectangular Grids mapped to a sphere.
    • One pole option: Pole value is an average of source values around pole.
    • Source and destination point masking of Grids.
    • The ability to choose what happens to unmapped destination points: either 1) return an error if any are found, or 2) ignore and don't interpolate them.
    • Two interpolation options, 1) bilinear or 2) higher order.
    For details please see the "Field Regrid" section in the "Infrastructure: Fields and Grids" part of the ESMF reference manual.
  • A more efficient tree-based search has been added to the ESMF_FieldRegridStore() method which improves its average running time by an order of magnitude.
  • A zeroflag and a checkflag have been added to the ESMF_FieldRegrid() call. The zeroflag allows the user to control how the destination Field should be initialized before regrid, and the checkflag allows the user to turn on more extensive error checking.
  • Optimized performance of ESMF_ArraySparseMatMulStore() for cases where the sparse matrix elements (i.e. factorList and factorIndexList arguments) are provided in parallel across the calling PETs.
  • Added an overloaded method for ESMF_GridCreate() to read the specification for a 2D regularly distributed rectilinear Grid from an XML file. See example in the Grid section of the ESMF Reference Manual.
  • The Grid class now contains a DistGrid per stagger location. This change allows the memory within a Field to exactly match the size of the exclusive region (the DE local portion) of the DistGrid associated with each stagger location. Previously the exclusive region of every stagger location needed to be sized to contain the exclusive region of all the stagger locations. This change affects some interfaces, such as ESMF_GridGet(), which now can return a DistGrid per stagger location.
  • Methods in the Mesh class now generate error messages through the standard ESMF LogErr system.
  • Mesh methods can now operate correctly in child Components which are running on fewer PETs than their parents.
  • The documentation for Meshes, and Fields created on Meshes, has been vastly improved, including multiple examples of Mesh creation and improved method descriptions. In addition, more extensive input checking has been added to Mesh to make its use easier.
  • Added bounds checking to the defaultvalueList argument in ESMF_AttributeGet().
  • Added a standard Attribute package to Array.
  • Added Attribute hierarchy linking to Array and ArrayBundle.
  • Time Manager interfaces have been made more robust to gracefully handle uninitialized objects and to eliminate memory leaks.
  • Two additional system tests were added to demonstrate the sparse matrix multiply operation for Fields based on LocStreams and Meshes.
  • A new system test, ESMF_ArrayRedistOpenMP, was added to demonstrate support for user-implemented OpenMP parallelism in ESMF Components.
  • Expanded the ESMF_CompFortranAndC system test to demonstrate the inter-language usage of Mesh and Field objects through States.
  • Reworked the VM documentation section in the Reference Manual to be more user oriented.
  • Removed the remaining dependency on explicit knowledge of the shape of the Fortran dope vector. This makes the library more portable across platforms, and more robust with compiler upgrades.
  • Implemented a clearer OpenMP support strategy. Two new environment variables were introduced that can be set to ON/OFF. ESMF_OPENMP, when set to ON during the library build, will compile all library sources using OpenMP compiler flags. In this case the OpenMP compiler flags automatically become part of the compiler flags exported by esmf.mk. If the ESMF library was compiled with ESMF_OPENMP set to OFF, a second environment variable, ESMF_TESTFORCEOPENMP, can be set to force the test and example codes to build with OpenMP compiler flags.
  • A new Windows option, intelcl, has been added. This allows building ESMF with the Intel Fortran compiler and the Microsoft cl (Visual C++) compiler, using the MinGW toolchain.
C interfaces:
  • Added to the C interface the ability to add and retrieve Field objects from a State.
  • Added C interfaces for the Field class. These enable a Field to be created on a Mesh, and allow the Mesh to be retrieved.
  • Segmentation faults have been reported for ESMF_StateReconcile().
  • ESMF_FieldRegridStore() doesn't currently work on Fields created on Meshes which contain tetrahedra.
  • ESMF_FieldRegridStore() doesn't currently work on Fields created on Grids which contain a DE of width less than 2 elements.
  • ESMF_FieldRegridStore() doesn't currently work on Fields created on Grids of arbitrary distribution.
  • ESMF_FieldRegridStore() only works on Fields created on Grids with indexflag equal to ESMF_INDEX_GLOBAL. This is not the default.
  • Grid edge connections don't work in this release and will have no effect on the actions of ESMF_FieldRegridStore().
  • FieldBundles don't currently enforce that every contained Field is built on the same Grid, although the documentation says that this should be so.
  • Proxy Field objects, internally created during ESMF_StateReconcile(), return the wrong dimCount.
  • Repeating sticky Alarms whose ringInterval is less than or equal to the Clock's timeStep do not ring properly.
  • Repeating sticky Alarms that are not turned off during a waiting period of a Clock run do not ring properly after the waiting period is over, Alarms are cleared, or turning off of subsequent Alarms resumes.
  • Repeating non-sticky Alarms do not ring properly for a Clock that goes into ESMF_MODE_REVERSE at the Clock's stopTime, while an Alarm is ringing.
  • Negative whole numbers specified as 8-byte floating point values for *_r8 time units in ESMF_TimeSet() and ESMF_TimeIntervalSet() methods incorrectly lose their sign, becoming positive.
  • ESMF_AttributeWrite() only works for ESMF standard Attribute packages.
  • Also see SourceForge bugs list.
Platform-specific bugs:
  • IBM Bluefire: all the ArrayHarness unit tests fail with ESMF_ABI=32.
  • Discover: ESMF_ArrayRedistOpenMPSTest.F90 fails with intelmpi when run by an automatic test script, but runs correctly when executed manually.
  • Linux ia32 test platform: ESMF_ConfigOverviewEx.F90 and ESMF_ConfigUTest.F90 fail with PGI.
  • Linux ia32 test platform: ESMF_MeshUTest.F90 fails with PGIGCC configuration.
  • Linux x86_64 test platform: Fails 15 system tests with ESMF_ABI=x86_64_medium.
  • SunOS test platform: the C interfaces do not work (seg fault).
  • SunOS test platform: the ESMF_AttributeSTest.F90 and ESMF_AttributeUpdateEx.F90 fail.
  • SunOS test platform: the ESMF_FieldRegridDisjointSTest.F90 system test fails.
  • Windows/MinGW test platform: the ESMF_ArrayRedistOpenMPSTest.F90 and ESMF_FieldArbGridUTest.F90 fail, using the intel configuration.
  • Windows/MinGW test platform: the ESMF_ArrayRedistOpenMPSTest.F90, ESMF_FieldArbGridUTest.F90, and ESMF_FieldCreateGetUTest.F90 fail, using the intelcl configuration.
  • Windows/Cygwin gfortran: the following environment variables may need to be set on some systems in order to properly link applications:
    • export ESMF_F90LINKOPTS=-Wl,--enable-auto-import
    • export ESMF_CXXLINKOPTS=-Wl,--enable-auto-import
  • Windows/Cygwin g95: the ESMF_MeshUTest.F90 fails.
  • Windows/Cygwin g95: the following environment variables may need to be set on some systems in order to properly link applications:
    • export ESMF_F90LINKLIBS=-lgcc_s
    • export ESMF_F90LINKOPTS=-Wl,--enable-auto-import
    • export ESMF_CXXLINKOPTS=-Wl,--enable-auto-import
  • The ESMF build has been reported failing for GCC 4.4.1.
  • Segmentation faults have been reported for some of the bundled test codes on a user's Linux system with Intel compilers and OpenMPI.

ESMF_4_0_0

5/15/09

Reference Manual
(html) (pdf) 

User's Guide
(html) (pdf) 

Supported Platforms

  • List of ESMF interface changes since ESMF_3_1_1.
  • Added public C interfaces for select methods of the Mesh class. The prefix for these methods is ESMC. We do not yet have a Reference Manual that describes these interfaces.
  • Modifications were made to selected GridComp and CplComp methods that enable use of keyword syntax for procedure arguments. This was not permitted before because they did not have explicit interfaces. Using keyword syntax ensures that the compiler will check argument types.We strongly recommend that users take advantage of this feature. All of the ESMF calls that take dummy procedure arguments, or call into previously registered user procedures, now provide explicit interfaces: ESMF_GridCompSetVM(), ESMF_GridCompSetServices(), ESMF_GridCompSetEntryPoint(), ESMF_GridCompInitialize(), ESMF_GridCompRun(), ESMF_GridCompFinalize(), ESMF_GridCompReadRestart(), ESMF_GridCompWriteRestart(), ESMF_CplCompSetVM(), ESMF_CplCompSetServices(), ESMF_CplCompSetEntryPoint(), ESMF_CplCompInitialize(), ESMF_CplCompRun(), ESMF_CplCompFinalize(), ESMF_CplCompReadRestart(), ESMF_CplCompWriteRestart().
  • Those methods that call into a user supplied routine provide two separate (optional) return codes - the standard "rc" return code for the ESMF library, and the "userRc" return code set by the user routine. If keyword syntax is not used, the two return codes can get confused, with dire results. Specifically, using the old interface argument order, without keyword syntax, would lead to incorrect rc association. Users are strongly encouraged to make appropriate changes to their codes. See the API changes page for details.
  • ESMF_GridCompSetServices() and ESMF_CplCompSetServices() now support runtime loading of ESMF components via shared objects. This allows users to maintain separate build systems for individual components in the same application. The newly added ESMF_ArrayRedistSharedObj system test demonstrates this feature.
  • Changed the behavior of ESMF_GridCompSetServices() and ESMF_CplCompSetServices() to support the MAPL/GEOS-5 Component hierarchy paradigm. For most user code the SetServices change is expected to be completely transparent. All previous versions of ESMF executed the specified SetServices routine in the context of the parent VM. Now, the specified public child routine is executed within the context of the child VM. This means that calls that would affect the child VM must be issued before the child SetServices routine is called. Two new interfaces, ESMF_GridCompSetVM() and ESMF_CplCompSetVM(), have been added that allow child component code to be called and executed from within the context of the parent VM. The benefit of the SetServices change is that the child SetServices routine may now contain calls that require execution from within the context of the child VM, e.g. creation of sub-components.
  • Added standard ReadRestart and WriteRestart methods to the ESMF_GridComp and ESMF_CplComp interfaces.
  • The ESMF_GridCompGet() and ESMF_CplCompGet() interfaces now offer access to the current method (for example, initialize, run, ...) and current phase of a Component.
  • Added "attachable methods" to ESMF States. User supplied methods can be attached, executed and removed. Currently attached user methods are ignored during ESMF_StateReconcile(), and attached methods cannot be copied or moved between States. For details see the new "Attachable Methods" section in the "Infrastructure: Utilities" part of the ESMF Reference Manual.
  • The InternalState documentation in the Reference Manual has been reworked to be more applicable to real world situations.
  • Added support in ESMF_FieldCreate() methods for Fields on arbitrarily distributed Grids. ESMF_FieldRegrid() does not yet work for arbitrarily distributed Grids. Overall, communications using Fields on arbitrarily distributed Grids have not been well tested.
  • The ESMF_FieldRegridStore() call now supports source and destination masking. The user can use this masking to tell the regrid to ignore source and/or destination points.
  • The ESMF_FieldRegridStore() call now has an unmappedDstAction flag. This allows the user to choose if they want unmapped destination points to cause an error or to be ignored.
  • A number of bug fixes and tweaks have improved the accuracy and stability of ESMF_FieldRegridStore(). This is in particular true of the higher-order interpolation weight generation.
  • Added a new public method ESMF_FieldGetBounds() to allow a user to query localDe specific data bounds.
  • Grids now have the capability to store other types of data besides coordinates. This data is referred to as Grid items. A set of new interfaces which mirror the ESMF_GridCoord interfaces has been added to Grid to support this functionality. The Grid currently supports four items and a set of new flags (ESMF_GRIDITEM_MASK, ESMF_GRIDITEM_AREA, ESMF_GRIDITEM_AREAM, ESMF_GRIDITEM_FRAC) has been added to be used in the interface to indicate the item being accessed. The ESMF_GRIDITEM_MASK item is used to store mask information for use by ESMF_FieldRegridStore().
  • Added support to create arbitrarily distributed Grids using ESMF_GridCreateShapeTile(), ESMF_GridCreate(), and ESMF_GridSetCommitShapeTile(). Other Grid interfaces have been modified as needed. Grid items do not work for arbitrarily distributed Grids.
  • Changed ESMF_GridGet() interface to get the information defined for the arbitrarily distributed Grid, including arbDim (the dimension in the DistGrid that represents the arbitrarily distributed dimension(s)), localCount (the number of PET-local arbitrarily distributed index locations), and localIndices (a list of PET-local arbitrarily distributed index locations). The names of these arguments are likely to change in future releases.
  • Added ability to read Attributes from an XML file via new method ESMF_AttributeRead(), which then attaches the Attributes to a Component, Field, or Grid.
  • XML Attribute file reading is done with the open source third party Xerces C++ library. ESMF must be built against the Xerces library, which requires the setting of additional ESMF environment variables. See the "Third Party Libraries" section in the ESMF User's Guide for details.
  • Implemented ability to specify time units as 8-byte floating point values in Time Manager methods.
  • Implemented ESMF standard Attribute packages for Components, State, Field, and Grid.
  • Added Attributes to ArrayBundle and DistGrid.
  • Allow Field Attribute hierarchy to connect to Grid Attribute hierarchy.
  • Allow ESMF_AttributeWrite() to be called from Components, State, FieldBundle, and Field.
  • Allow ESMF_AttributeCopy() to locally copy Attribute values between Components.
  • Added ESMF_AttributeUpdate() routine to build consistent Attribute structure and values for objects defined across a VM. One use of this feature is to use it in conjunction with ESMF_AttributeCopy() during the CplComp run method in order to transfer Attributes between GridComps defined on mutually exclusive sets of PETs.
  • Overloaded ESMF_AttributeRemove() to remove entire Attribute packages, Attributes in an Attribute package, or just single Attributes.
  • Added the ability to nest Attribute packages inside of each other.
  • ESMF_StateReconcile() now has a flag to allow optional Attribute reconciliation. The default is currently that Attribute reconciliation is off, due to concerns about performance and robustness.
  • Added a set of overloaded ESMF_AttributeLinkRemove() interfaces. These detach an object's Attribute hierarchy from that of another object.
  • Modified the ESMF_Attribute system test to use ESMF_AttributeUpdate(), ESMF_AttributeCopy(), and ESMF_StateReconcile() on both States and Components where appropriate.
  • The range of Fortran unit numbers used within ESMF can be overridden via the ESMF_Initialize() call by using the new IOUnitLower and IOUnitUpper optional arguments. A new ESMF_IOUnitGet() method to find an unused unit number within the ESMF unit number range is provided as a service to application developers.
  • ESMF_IOUnitFlush() is provided as a common method to flush Fortran unit numbers. This is intended for use as a service to application developers.
  • Added ESMF_ConcurrentEnsemble system test demonstrating an ensemble in which different ensemble members, which are distinctly different components, run concurrently on distinct sets of PETs.
  • Added ESMF_InternalStateEnsemble system test demonstrating how different ensemble members representing the same Component can be written using a single Component object which indexes different elements of an ESMF internal State.
  • Activated TestHarness for Array and Field testing.
  • Added support for Windows MinGW/MSYS, using the Intel Fortran and C++ compiler and Microsoft MPI. This was developed and tested under Windows Compute Cluster Server (CCS) 2003.
  • Standardized 3rd party library support (NETCDF, PNETCDF, LAPACK, XERCES).
  • An offline file-to-file regridding application has been developed as part of ESMF. This application takes two netcdf grid files and outputs interpolation weights generated using ESMF's higher-order interpolation. This application supports a number of options for handling the pole: no pole, treating the pole as the average of the values surrounding the pole, and an n-point stencil average of the points surrounding the pole. The format of the files makes this application a suitable replacement for SCRIP. For details see the new "File Based Regrid Weight Application" section in the "Infrastructure: Fields and Grids" part of the ESMF Reference Manual.
  • Furthermore, all the features listed in the release notes for ESMF_3_1_0rp2 apply to this release.
  • The ESMF_StateReconcile() call, generally used by couplers dealing with Components running on exclusive petLists, has an internal size limit (which will be addressed in a subsequent release). There is no hard-coded limit to how many elements, i.e. States, Bundles, Fields, Arrays can be added to the State. However, there is a limit, roughly 20, on the maximum number of sub-elements contained by any element in the State passed into ESMF_StateReconcile()
  • The ESMF_StateReconcile() call fails for nested States.
  • ESMF_LOG_SINGLE is known to be broken. The symptoms are platform dependent and may appear non-deterministic.
  • Fields built on LocStreams and Meshes will not work with ESMF_StateReconcile() and therefore cannot be transfered between Components running concurrently.
  • ESMF_FieldRegrid() is only implemented for Fields created on Grids with indexflag equal to ESMF_INDEX_GLOBAL. This is not the default.
  • Proxy Field objects, internally created during ESMF_StateReconcile(), return the wrong dimCount.
  • Grid connections don't work in this release and will have no effect on the actions of ESMF_FieldRegridStore().
  • Repeating sticky Alarms whose ringInterval is less than or equal to the Clock's timeStep do not ring properly.
  • Repeating sticky Alarms that are not turned off during a waiting period of a Clock run do not ring properly after the waiting period is over, Alarms are cleared, or turning off of subsequent Alarms resumes.
  • Repeating non-sticky Alarms do not ring properly for a Clock that goes into ESMF_MODE_REVERSE at the Clock's stopTime, while an Alarm is ringing.
  • Negative whole numbers specified as 8-byte floating point values for *_r8 time units in ESMF_TimeSet() and ESMF_TimeIntervalSet( ) methods incorrectly lose their sign, becoming positive.
  • Array and ArrayBundle Attribute hierarchies are not implemented yet.
  • ESMF_AttributeWrite() only works for ESMF standard Attribute packages.
  • In the Reference Manual, "Figure 29: The structure of the Attribute class" shows an attrCount variable which is no longer present, and does not show two vectors of Attribute pointers called packList and linkList.
  • In the API description of ESMF_AttributeLink() and ESMF_AttributeLinkRemove(), in the ESMF Reference Manual, the argument keyword should be "comp1" instead of "comp".
  • Also see SourceForge bugs list.
Platform-specific bugs:
  • The Mesh and ESMF_FieldRegrid() code is unstable when compiled with PGI.
  • ESMF_DistGridCreateGetUTest.F90 fails on IBM Lightning with PGI.
  • ESMF_ClockUTest.F90 fails on IBM/AIX in ESMF_BOPT=O mode.
  • ESMF_ClockUTest.F90 fails on Linux with NAG.
  • All the ArrayHarness unit tests fail on IBM Bluefire with ESMF_ABI=32 and ESMF_BOPT=g.
  • ESMC_ConfigUTest.C fails on IBM Bluefire with ESMF_ABI=64 and ESMF_BOPT=O.
  • ESMF_GridCoordUTest.F90 fails on Darwin with Absoft and with ESMF_BOPT=O.
  • The Attribute unit tests fail with Lahey and ESMF_BOPT=O.
  • ESMF_ConfigOverviewEx.F90 and ESMF_ConfigUTest.F90 fail on ia32 with PGI.
  • Examples ESMF_LogErrEx.F90, ESMF_AttReadGridCompEx.F90, ESMF_AttReadGridEx.F90, and ESMF_AttributePackageEx.F90 fail on Linux with the g95 v0.5 compiler.
  • The C unit tests and examples fail to link on wJet with the Intel compiler.

 

Last Update: Feb. 24, 2015, 2:12 p.m. by deleted user