next up previous contents
Next: About this document ... Up: ESMF_refdoc Previous: Bibliography   Contents

Subsections

7 Appendices


50 Appendix A: Master List of Constants

50.1 ESMF_ALARMLIST

This flag is documented in section 44.2.1.


50.2 ESMF_DIM_ARB

DESCRIPTION:
An integer named constant which is used to indicate that a particular dimension is arbitrarily distributed.

50.3 ESMF_ATTGETCOUNT

This flag is documented in section 38.6.1.


50.4 ESMF_ATTRECONCILE

DESCRIPTION:
Indicate whether or not to handle metadata (Attributes) in ESMF_StateReconcile().

The type of this flag is:

type(ESMF_AttReconcileFlag)

The valid values are:

ESMF_ATTRECONCILE_ON
Attribute reconciliation will be turned on.
ESMF_ATTRECONCILE_OFF
Attribute reconciliation will be turned off.

50.5 ESMF_ATTTREE

This flag is documented in section 38.6.2.

50.6 ESMF_ATTWRITE

This flag is documented in section 38.6.3.

50.7 ESMF_CALKIND

This flag is documented in section 40.2.1.


50.8 ESMF_COMPTYPE

DESCRIPTION:
Indicate the type of a Component.

The type of this flag is:

type(ESMF_CompType_Flag)

The valid values are:

ESMF_COMPTYPE_GRID
A ESMF_GridComp object.
ESMF_COMPTYPE_CPL
A ESMF_CplComp objects.
ESMF_COMPTYPE_SCI
A ESMF_SciComp objects.


50.9 ESMF_CONTEXT

DESCRIPTION:
Indicates the type of VM context in which a Component will be executing its standard methods.

The type of this flag is:

type(ESMF_Context_Flag)

The valid values are:

ESMF_CONTEXT_OWN_VM
The component is running in its own, separate VM context. Resources are inherited from the parent but can be arranged to fit the component's requirements.
ESMF_CONTEXT_PARENT_VM
The component uses the parent's VM for resource management. Compared to components that use their own VM context components that run in the parent's VM context are more light-weight with respect to the overhead of calling into their initialize, run and finalize methods. Furthermore, VM-specific properties remain unchanged when going from the parent component to the child component. These properties include the MPI communicator, the number of PETs, the PET labeling, communication attributes, threading-level.


50.10 ESMF_COORDSYS

DESCRIPTION:
A set of values which indicates in which system the coordinates in a class (e.g. Grid) are. This type is useful both to indicate to other users the type of the coordinates, but also to control how the coordinates are interpreted in ESMF methods which depend on the coordinates (e.g. regridding methods like ESMF_FieldRegridStore()).

The type of this flag is:

type(ESMF_CoordSys_Flag)

The valid values are:

ESMF_COORDSYS_CART
Cartesian coordinate system. In this system, the cartesian coordinates are mapped to the Grid coordinate dimensions in the following order: x,y,z. (E.g. using coordDim=2 in ESMF_GridGetCoord() references the y dimension)

ESMF_COORDSYS_SPH_DEG
Spherical coordinates in degrees. In this system, the spherical coordinates are mapped to the Grid coordinate dimensions in the following order: longitude, latitude, radius. (E.g. using coordDim=2 in ESMF_GridGetCoord() references the latitude dimension) Note, however, that ESMF_FieldRegridStore() currently just supports longitude and latitude (i.e. with this system, only Grids of dimension 2 are supported in the regridding).

ESMF_COORDSYS_SPH_RAD
Spherical coordinates in radians. In this system, the spherical coordinates are mapped to the Grid coordinate dimensions in the following order: longitude, latitude, radius. (E.g. using coordDim=2 in ESMF_GridGetCoord() references the latitude dimension) Note, however, that ESMF_FieldRegridStore() currently just supports longitude and latitude (i.e. with this system, only Grids of dimension 2 are supported in the regridding).

This flag is documented in section 50.10.


50.11 ESMF_COPY

DESCRIPTION:
Indicates which type of copy behavior is used when copying ESMF objects.

The type of this flag is:

type(ESMF_Copy_Flag)

The valid values are:

ESMF_COPY_ALIAS
The destination of the copy becomes an alias of the source object.
ESMF_COPY_REFERENCE
All local data of the object is coped by value, and pointer valued data is referenced.
ESMF_COPY_VALUE
All data and pointers are copied to the destination object, nothing is referenced.


50.12 ESMF_DATACOPY

DESCRIPTION:
Indicates whether to reference a data item or make a copy of it.

The type of this flag is:

type(ESMF_DataCopy_Flag)

The valid values are:

ESMF_DATACOPY_VALUE
Copy the data item to another buffer.
ESMF_DATACOPY_REFERENCE
Reference the data item.


50.13 ESMF_DECOMP

DESCRIPTION:
Indicates how DistGrid elements are decomposed over DEs.

The type of this flag is:

type(ESMF_Decomp_Flag)

The valid values are:

ESMF_DECOMP_BALANCED
Decompose elements as balanced as possible across DEs. The maximum difference in number of elements per DE is 1, with the extra elements on the lower DEs.
ESMF_DECOMP_CYCLIC
Decompose elements cyclically across DEs.
ESMF_DECOMP_RESTFIRST
Divide elements over DEs. Assign the rest of this division to the first DE.
ESMF_DECOMP_RESTLAST
Divide elements over DEs. Assign the rest of this division to the last DE.

50.14 ESMF_DIRECTION

This flag is documented in section 43.2.1.

50.15 ESMF_DISTGRIDMATCH

This flag is documented in section 34.2.1.

50.16 ESMF_END

This flag is documented in section 15.2.1.

50.17 ESMF_FIELDSTATUS

This flag is documented in section 25.2.1.

50.18 ESMF_FILEFORMAT

This flag is documented in section 30.2.7.


50.19 ESMF_FILESTATUS

DESCRIPTION:
This flag is used in ESMF I/O functions. It's use is similar to the status keyword in the Fortran open statement.

The type of this flag is:

type(ESMF_FileStatus_Flag)

The valid values are:

ESMF_FILESTATUS_NEW
The file must not exist, it will be created.
ESMF_FILESTATUS_OLD
The file must exist.
ESMF_FILESTATUS_REPLACE
If the file exists, all of its contents will be deleted before writing. If the file does not exist, it will be created.
ESMF_FILESTATUS_UNKNOWN
The value is treated as if it were ESMF_FILESTATUS_OLD if the corresponding file already exists. Otherwise, the value is treated as if it were ESMF_FILESTATUS_NEW.


50.20 ESMF_GEOMTYPE

DESCRIPTION:
Different types of geometries upon which an ESMF Field or ESMF Fieldbundle may be built.

The type of this flag is:

type(ESMF_GeomType_Flag)

The valid values are:

ESMF_GEOMTYPE_GRID
An ESMF_Grid, a structured grid composed of one or more logically rectangular tiles
ESMF_GEOMTYPE_MESH
An ESMF_Mesh, an unstructured grid
ESMF_GEOMTYPE_XGRID
An ESMF_XGrid, an exchange grid
ESMF_TYPEKIND_LOCSTREAM
An ESMF_LocStream, a disconnected series of points with associated key values

50.21 ESMF_GRIDCONN

This flag is documented in section 30.2.1.

50.22 ESMF_GRIDITEM

This flag is documented in section 30.2.2.

50.23 ESMF_GRIDMATCH

This flag is documented in section 30.2.3.

50.24 ESMF_GRIDSTATUS

This flag is documented in section 30.2.4.


50.25 ESMF_INDEX

DESCRIPTION:
Indicates whether index is local (per DE) or global (per object).

The type of this flag is:

type(ESMF_Index_Flag)

The valid values are:

ESMF_INDEX_DELOCAL
Indicates that DE-local index space starts at lower bound 1 for each DE.
ESMF_INDEX_GLOBAL
Indicates that global indices are used. This means that DE-local index space starts at the global lower bound for each DE.
ESMF_INDEX_USER
Indicates that the DE-local index bounds are explicitly set by the user.


50.26 ESMF_IOFMT

DESCRIPTION:
Indicates IO format options that are currently supported.

The type of this flag is:

type(ESMF_IOFmt_Flag)

The valid values are:

ESMF_IOFMT_BIN
Binary format.
ESMF_IOFMT_NETCDF
NETCDF and PNETCDF format.


50.27 ESMF_IO_NETCDF_PRESENT

DESCRIPTION:
Indicates whether netcdf feature support has been enabled within the current ESMF build.

The type of this flag is:

logical

The valid values are:

.true.
Netcdf features are enabled.
.false.
Netcdf features are not enabled.


50.28 ESMF_IO_PIO_PRESENT

DESCRIPTION:
Indicates whether PIO (parallel IO) feature support has been enabled within the current ESMF build.

The type of this flag is:

logical

The valid values are:

.true.
PIO features are enabled..
.false.
PIO features are not enabled.


50.29 ESMF_IO_PNETCDF_PRESENT

DESCRIPTION:
Indicates whether parallel netcdf feature support has been enabled within the current ESMF build.

The type of this flag is:

logical

The valid values are:

.true.
Parallel netcdf features are enabled.
.false.
Parallel netcdf features are not enabled.


50.30 ESMF_ITEMORDER

DESCRIPTION:
Specifies the order of items in a list.

The type of this flag is:

type(ESMF_ItemOrder_Flag)

The valid values are:

ESMF_ITEMORDER_ABC
The items are in alphabetical order, according to their names.
ESMF_ITEMORDER_ADDORDER
The items are in the order in which they were added to the container.


50.31 ESMF_KIND

DESCRIPTION:
Named constants to be used as kind-parameter in Fortran variable declarations. For example:

  integer(ESMF_KIND_I4)       :: integerVariable
  integer(kind=ESMF_KIND_I4)  :: integerVariable
  real(ESMF_KIND_R4)          :: realVariable
  real(kind=ESMF_KIND_R4)     :: realVariable
The Fortran standard does not mandate what numeric values correspond to actual number of bytes allocated for the various kinds. The following constants are defined by ESMF to be correct across the supported Fortran compilers. Note that not all compilers support every kind listed below; in particular 1 and 2 byte integers can be problematic.

The type of these named constants is:

integer

The named constants are:

ESMF_KIND_I1
Kind-parameter for 1 byte integer.
ESMF_KIND_I2
Kind-parameter for 2 byte integer.
ESMF_KIND_I4
Kind-parameter for 4 byte integer.
ESMF_KIND_I8
Kind-parameter for 8 byte integer.
ESMF_KIND_R4
Kind-parameter for 4 byte real.
ESMF_KIND_R8
Kind-parameter for 8 byte real.


50.32 ESMF_LINETYPE

DESCRIPTION:
This argument allows the user to select the path of the line which connects two points on the surface of a sphere. This in turn controls the path along which distances are calculated and the shape of the edges that make up a cell.

The type of this flag is:

type(ESMF_LineType_Flag)

The valid values are:

ESMF_LINETYPE_CART
Cartesian line. When this option is specified distances are calculated in a straight line through the 3D Cartesian space in which the sphere is embedded. Cells are approximated by 3D planes bounded by 3D Cartesian lines between their corner vertices. When calculating regrid weights, this line type is currently the default for the following regrid methods: ESMF_REGRIDMETHOD_BILINEAR, ESMF_REGRIDMETHOD_PATCH, ESMF_REGRIDMETHOD_NEAREST_STOD, and ESMF_REGRIDMETHOD_NEAREST_DTOS.
ESMF_LINETYPE_GREAT_CIRCLE
Great circle line. When this option is specified distances are calculated along a great circle path (the shortest distance between two points on a sphere surface). Cells are bounded by great circle paths between their corner vertices. When calculating regrid weights, this line type is currently the default for the following regrid method: ESMF_REGRIDMETHOD_CONSERVE.

50.33 ESMF_LOGERR

This flag is documented in section 46.2.1.

50.34 ESMF_LOGKIND

This flag is documented in section 46.2.2.

50.35 ESMF_LOGMSG

This flag is documented in section 46.2.3.

50.36 ESMF_MESHELEMTYPE

This flag is documented in section 32.2.1.


50.37 ESMF_MESHLOC

DESCRIPTION:
Used to indicate a specific part of a Mesh. This is commonly used to specify the part of the Mesh to create a Field on.

The type of this flag is:

type(ESMF_MeshLoc)

The valid values are:

ESMF_MESHLOC_NODE
The nodes (also known as corners or vertices) of a Mesh.

ESMF_MESHLOC_ELEMENT
The elements (also known as cells) of a Mesh.


50.38 ESMF_MESHOP

DESCRIPTION:
Specifies the spatial operation with two source Meshes, treating the Meshes as point sets.

The type of this flag is:

type(ESMF_MeshOp_Flag)

The valid values are:

ESMF_MESHOP_DIFFERENCE
Calculate the difference of the two point sets from the source Meshes.


50.39 ESMF_METHOD

DESCRIPTION:
Specify standard ESMF Component method.

The type of this flag is:

type(ESMF_Method_Flag)

The valid values are:

ESMF_METHOD_FINALIZE
Finalize method.
ESMF_METHOD_INITIALIZE
Initialize method.
ESMF_METHOD_READRESTART
ReadRestart method.
ESMF_METHOD_RUN
Run method.
ESMF_METHOD_WRITERESTART
WriteRestart method.

50.40 ESMF_PIN

This flag is documented in section 47.2.1.

50.41 ESMF_POLEKIND

This flag is documented in section 30.2.5.


50.41.1 ESMF_POLEMETHOD

DESCRIPTION:
When interpolating between two Grids which have been mapped to a sphere these can be used to specify the type of artificial pole to create on the source Grid during interpolation. Creating the pole allows destination points above the top row or below the bottom row of the source Grid to still be mapped.

The type of this flag is:

type(ESMF_PoleMethod_Flag)

The valid values are:

ESMF_POLEMETHOD_NONE
No pole. Destination points which lie above the top or below the bottom row of the source Grid won't be mapped.
ESMF_POLEMETHOD_ALLAVG
Construct an artificial pole placed in the center of the top (or bottom) row of nodes, but projected onto the sphere formed by the rest of the grid. The value at this pole is the average of all the source values surrounding the pole.
ESMF_POLEMETHOD_NPNTAVG
Construct an artificial pole placed in the center of the top (or bottom) row of nodes, but projected onto the sphere formed by the rest of the grid. The value at this pole is the average of the N source nodes next to the pole and surrounding the destination point (i.e. the value may differ for each destination point). Here N is set by using the regridPoleNPnts parameter and ranges from 1 to the number of nodes around the pole. This option is useful for interpolating values which may be zeroed out by averaging around the entire pole (e.g. vector components).
ESMF_POLEMETHOD_TEETH
No new pole point is constructed, instead the holes at the poles are filled by constructing triangles across the top and bottom row of the source Grid. This can be useful because no averaging occurs, however, because the top and bottom of the sphere are now flat, for a big enough mismatch between the size of the destination and source pole holes, some destination points may still not be able to be mapped to the source Grid.


50.42 ESMF_REDUCE

DESCRIPTION:
Indicates reduce operation

The type of this flag is:

type(ESMF_Reduce_Flag)

The valid values are:

ESMF_REDUCE_SUM
Use arithmetic sum to add all data elements.
ESMF_REDUCE_MIN
Determine the minimum of all data elements.
ESMF_REDUCE_MAX
Determine the maximum of all data elements.


50.43 ESMF_REGION

DESCRIPTION:
Specifies various regions in the data layout of an Array or Field object.

The type of this flag is:

type(ESMF_Region_Flag)

The valid values are:

ESMF_REGION_TOTAL
Total allocated memory.
ESMF_REGION_SELECT
Region of operation-specific elements.
ESMF_REGION_EMPTY
The empty region contains no elements.


50.43.1 ESMF_REGRIDMETHOD

DESCRIPTION:
Specify which interpolation method to use during regridding. For a more detailed discussion of these methods, as well as ESMF regridding in general, see Section 23.2.

The type of this flag is:

type(ESMF_RegridMethod_Flag)

The valid values are:

ESMF_REGRIDMETHOD_BILINEAR
Bilinear interpolation. Destination value is a linear combination of the source values in the cell which contains the destination point. The weights for the linear combination are based on the distance of destination point from each source value.
ESMF_REGRIDMETHOD_PATCH
Higher-order patch recovery interpolation. Destination value is a weighted average of 2D polynomial patches constructed from cells surrounding the source cell which contains the destination point. This method typically results in better approximations to values and derivatives than bilinear. However, because of its larger stencil, it also results in a much larger interpolation matrix (and thus routeHandle) than the bilinear.
ESMF_REGRIDMETHOD_NEAREST_STOD
In this version of nearest neighbor interpolation each destination point is mapped to the closest source point. A given source point may go to multiple destination points, but no destination point will receive input from more than one source point.
ESMF_REGRIDMETHOD_NEAREST_DTOS
In this version of nearest neighbor interpolation each source point is mapped to the closest destination point. A given destination point may receive input from multiple source points, but no source point will go to more than one destination point.
ESMF_REGRIDMETHOD_CONSERVE
First order conservative interpolation. Value of a destination cell is the weighted sum of the values of the source cells that it overlaps. The weights are determined by the amount the source cell overlaps the destination cell. Will typically give less accurate approximations to values than the other interpolation methods, however, will do a much better job preserving the integral of the value between the source and destination. Needs corner coordinate values to be provided in the Grid. Currently only works for Fields created on the Grid center stagger (or the Mesh element location).


50.44 ESMF_ROUTESYNC

DESCRIPTION:
Switch between blocking and non-blocking execution of RouteHandle based communication calls. Every RouteHandle based communication method contains an optional argument routesyncflag that is of type ESMF_RouteSync_Flag.

The type of this flag is:

type(ESMF_RouteSync_Flag)

The valid values are:

ESMF_ROUTESYNC_BLOCKING
Execute a precomputed communication pattern in blocking mode. This mode guarantees that when the method returns all PET-local data transfers, both in-bound and out-bound, have finished.
ESMF_ROUTESYNC_NBSTART
Start executing a precomputed communication pattern in non-blocking mode. When a method returns from being called in this mode, it guarantees that all PET-local out-bound data has been transferred. It is now safe for the user to overwrite out-bound data elements. No guarantees are made for in-bound data elements at this stage. It is unsafe to access these elements until a call in ESMF_ROUTESYNC_NBTESTFINISH mode has been issued and has returned with finishedflag equal to .true., or a call in ESMF_ROUTESYNC_NBWAITFINISH mode has been issued and has returned.
ESMF_ROUTESYNC_NBTESTFINISH
Test whether the transfer of data of a precomputed communication pattern, started with ESMF_ROUTESYNC_NBSTART, has completed. Finish up as much as possible and set the finishedflag to .true. if all data operations have completed, or .false. if there are still outstanding transfers. Only after a finishedflag equal to .true. has been returned is it safe to access any of the in-bound data elements.
ESMF_ROUTESYNC_NBWAITFINISH
Wait (i.e. block) until the transfer of data of a precomputed communication pattern, started with ESMF_ROUTESYNC_NBSTART, has completed. Finish up all data operations and set the returned finishedflag to .true.. It is safe to access any of the in-bound data elements once the call has returned.
ESMF_ROUTESYNC_CANCEL
Cancel outstanding transfers for a precomputed communication pattern.

50.45 ESMF_SERVICEREPLY

This flag is documented in section 47.2.2.

50.46 ESMF_STAGGERLOC

This flag is documented in section 30.2.6.


50.47 ESMF_STARTREGION

DESCRIPTION:
Specifies the start of the effective halo region of an Array or Field object.

The type of this flag is:

type(ESMF_StartRegion_Flag)

The valid values are:

ESMF_STARTREGION_EXCLUSIVE
Region of elements that are exclusively owned by the local DE.
ESMF_STARTREGION_COMPUTATIONAL
User defined region, greater or equal to the exclusive region.

50.48 ESMF_STATEINTENT

This flag is documented in section 20.2.1.

50.49 ESMF_STATEITEM

This flag is documented in section 20.2.2.


50.50 ESMF_SYNC

DESCRIPTION:
Indicates method blocking behavior and PET synchronization for VM communication methods, as well as for standard Component methods, such as Initialize(), Run() and Finalize().

For VM communication calls the ESMF_SYNC_BLOCKING and ESMF_SYNC_NONBLOCKING modes provide behavior that is practically identical to the blocking and non-blocking communication calls familiar from MPI.

The details of how the blocking mode setting affects Component methods are more complex. This is a consequence of the fact that ESMF Components can be executed in threaded or non-threaded mode. However, in the default, non-threaded case, where an ESMF application runs as a pure MPI or mpiuni program, most of the complexity is removed.

See the VM item in 6.5 for an explanation of the PET and VAS concepts used in the following descriptions.

The type of this flag is:

type(ESMF_Sync_Flag)

The valid values are:

ESMF_SYNC_BLOCKING
Communication calls: The called method will block until all (PET-)local operations are complete. After the return of a blocking communication method it is safe to modify or use all participating local data.

Component calls: The called method will block until all PETs of the VM have completed the operation.

For a non-threaded, pure MPI component the behavior is identical to calling a barrier before returning from the method. Generally this kind of rigid synchronization is not the desirable mode of operation for an MPI application, but may be useful for application debugging. In the opposite case, where all PETs of the component are running as threads in shared memory, i.e. in a single VAS, strict synchronization of all PETs is required to prevent race conditions.

ESMF_SYNC_VASBLOCKING
Communication calls: Not available for communication calls.

Component calls: The called method will block each PET until all operations in the PET-local VAS have completed.

This mode is a combination of ESMF_SYNC_BLOCKING and ESMF_SYNC_NONBLOCKING modes. It provides a default setting that leads to the typically desirable behavior for pure MPI components as well as those that share address spaces between PETs.

For a non-threaded, pure MPI component each PET returns independent of the other PETs. This is generally the expected behavior in the pure MPI case where calling into a component method is practically identical to a subroutine call without extra synchronization between the processes.

In the case where some PETs of the component are running as threads in shared memory ESMF_SYNC_VASBLOCKING becomes identical to ESMF_SYNC_BLOCKING within thread groups, to prevent race conditions, while there is no synchronization between the thread groups.

ESMF_SYNC_NONBLOCKING
Communication calls: The called method will not block but returns immediately after initiating the requested operation. It is unsafe to modify or use participating local data before all local operations have completed. Use the ESMF_VMCommWait() or ESMF_VMCommQueueWait() method to block the local PET until local data access is safe again.

Component calls: The behavior of this mode is fundamentally different for threaded and non-threaded components, independent on whether the components use shared memory or not. The ESMF_SYNC_NONBLOCKING mode is the most complex mode for calling component methods and should only be used if the extra control, described below, is absolutely necessary.

For non-threaded components (the ESMF default) calling a component method with ESMF_SYNC_NONBLOCKING is identical to calling it with ESMF_SYNC_VASBLOCKING. However, different than for ESMF_SYNC_VASBLOCKING, a call to ESMF_GridCompWait() or ESMF_CplCompWait() is required in order to deallocate memory internally allocated for the ESMF_SYNC_NONBLOCKING mode.

For threaded components the calling PETs of the parent component will not be blocked and return immediately after initiating the requested child component method. In this scenario parent and child components will run concurrently in identical VASs. This is the most complex mode of operation. It is unsafe to modify or use VAS local data that may be accessed by concurrently running components until the child component method has completed. Use the appropriate ESMF_GridCompWait() or ESMF_CplCompWait() method to block the local parent PET until the child component method has completed in the local VAS.


50.51 ESMF_TERMORDER

DESCRIPTION:
Specifies the order of source terms in a destination sum, e.g. during sparse matrix multiplication.

The type of this flag is:

type(ESMF_TermOrder_Flag)

The valid values are:

ESMF_TERMORDER_SRCSEQ
The source terms are in strict ascending order according to their source sequence index.
ESMF_TERMORDER_SRCPET
The source terms are first ordered according to their distribution across the source side PETs: for each destination PET the source PET order starts with the localPet and decrements from there, modulo petCount, until all petCount PETs are accounted for. The term order within each source PET is given by the source term sequence index.
ESMF_TERMORDER_FREE
There is no prescribed term order. The source terms may be summed in any order that optimizes performance.


50.52 ESMF_TYPEKIND

DESCRIPTION:
Named constants used to indicate type and kind combinations supported by the overloaded ESMF interfaces. The corresponding Fortran kind-parameter constants are described in section 50.31.

The type of these named constants is:

type(ESMF_TypeKind_Flag)

The named constants are:

ESMF_TYPEKIND_I1
Indicates 1 byte integer.
ESMF_TYPEKIND_I2
Indicates 2 byte integer.
ESMF_TYPEKIND_I4
Indicates 4 byte integer.
ESMF_TYPEKIND_I8
Indicates 8 byte integer.
ESMF_TYPEKIND_R4
Indicates 4 byte real.
ESMF_TYPEKIND_R8
Indicates 8 byte real.


50.53 ESMF_UNMAPPEDACTION

DESCRIPTION:
Indicates what action to take with respect to unmapped destination points and the entries of the sparse matrix that correspond to these points.

The type of this flag is:

type(ESMF_UnmappedAction_Flag)

The valid values are:

ESMF_UNMAPPEDACTION_ERROR
An error is issued when there exist destination points in a regridding operation that are not mapped by corresponding source points.
ESMF_UNMAPPEDACTION_IGNORE
Destination points which do not have corresponding source points are ignored and zeros are used for the entries of the sparse matrix that is generated.


50.54 ESMF_VERSION

DESCRIPTION:
The following named constants define the precise version of ESMF in use.

ESMF_VERSION_BETASNAPSHOT
Constant of type logical indicating beta snapshot phase (.true. for any version during the pre-release development phase, .false. for any released version of the software).
ESMF_VERSION_MAJOR
Constant of type integer indicating the major version number (e.g. 5 for v5.2.0r).
ESMF_VERSION_MINOR
Constant of type integer indicating the minor version number (e.g. 2 for v5.2.0r).
ESMF_VERSION_PATCHLEVEL
Constant of type integer indicating the patch level of a specific revision (e.g. 0 for v5.2.0r, or 1 for v5.2.0rp1).
ESMF_VERSION_PUBLIC
Constant of type logical indicating public vs. internal release status (e.g. .true. for v5.2.0r, or .false. for v5.2.0).
ESMF_VERSION_REVISION
Constant of type integer indicating the revision number (e.g. 0 for v5.2.0r).
ESMF_VERSION_STRING
Constant of type character holding the exact release version string (e.g. "5.2.0r").

50.55 ESMF_XGRIDSIDE

This flag is documented in section 33.2.1.

51 Appendix B: A Brief Introduction to UML

The schematic below shows the Unified Modeling Language (UML) notation for the class diagrams presented in this Reference Manual. For more on UML, see references such as The Unified Modeling Language Reference Manual, Rumbaugh et al, [23].

\scalebox{0.8}{\includegraphics{Appendix_uml}}

52 Appendix C: ESMF Error Return Codes

The tables below show the possible error return codes for Fortran and C methods.

 
 =====================================
 Fortran Symmetric Return Codes 1-500
 =====================================
 
  ESMF_SUCCESS               0 
  ESMF_RC_OBJ_BAD            1 
  ESMF_RC_OBJ_INIT           2
  ESMF_RC_OBJ_CREATE         3
  ESMF_RC_OBJ_COR            4
  ESMF_RC_OBJ_WRONG          5
  ESMF_RC_ARG_BAD            6
  ESMF_RC_ARG_RANK           7
  ESMF_RC_ARG_SIZE           8
  ESMF_RC_ARG_VALUE          9
  ESMF_RC_ARG_DUP           10
  ESMF_RC_ARG_SAMETYPE      11
  ESMF_RC_ARG_SAMECOMM      12
  ESMF_RC_ARG_INCOMP        13
  ESMF_RC_ARG_CORRUPT       14
  ESMF_RC_ARG_WRONG         15
  ESMF_RC_ARG_OUTOFRANGE    16
  ESMF_RC_ARG_OPT           17
  ESMF_RC_NOT_IMPL          18
  ESMF_RC_FILE_OPEN         19
  ESMF_RC_FILE_CREATE       20
  ESMF_RC_FILE_READ         21
  ESMF_RC_FILE_WRITE        22
  ESMF_RC_FILE_UNEXPECTED   23
  ESMF_RC_FILE_CLOSE        24
  ESMF_RC_FILE_ACTIVE       25
  ESMF_RC_PTR_NULL          26
  ESMF_RC_PTR_BAD           27
  ESMF_RC_PTR_NOTALLOC      28
  ESMF_RC_PTR_ISALLOC       29
  ESMF_RC_MEM               30
  ESMF_RC_MEM_ALLOCATE      31
  ESMF_RC_MEM_DEALLOCATE    32
  ESMF_RC_MEMC              33
  ESMF_RC_DUP_NAME          34
  ESMF_RC_LONG_NAME         35
  ESMF_RC_LONG_STR          36
  ESMF_RC_COPY_FAIL         37
  ESMF_RC_DIV_ZERO          38
  ESMF_RC_CANNOT_GET        39
  ESMF_RC_CANNOT_SET        40
  ESMF_RC_NOT_FOUND         41
  ESMF_RC_NOT_VALID         42
  ESMF_RC_INTNRL_LIST       43
  ESMF_RC_INTNRL_INCONS     44
  ESMF_RC_INTNRL_BAD        45
  ESMF_RC_SYS               46
  ESMF_RC_BUSY              47
  ESMF_RC_LIB               48
  ESMF_RC_LIB_NOT_PRESENT   49
  ESMF_RC_ATTR_UNUSED       50
  ESMF_RC_OBJ_NOT_CREATED   51
  ESMF_RC_OBJ_DELETED       52
  ESMF_RC_NOT_SET           53
  ESMF_RC_VAL_WRONG         54
  ESMF_RC_VAL_ERRBOUND      55  
  ESMF_RC_VAL_OUTOFRANGE    56
  ESMF_RC_ATTR_NOTSET       57
  ESMF_RC_ATTR_WRONGTYPE    58
  ESMF_RC_ATTR_ITEMSOFF     59
  ESMF_RC_ATTR_LINK         60
  ESMF_RC_BUFFER_SHORT      61
  ESMF_RC_TIMEOUT           62
  ESMF_RC_FILE_EXISTS       63
  ESMF_RC_FILE_NOTDIR       64
 
 62-499 reserved for future Fortran symmetric return code definitions
 
 =====================================
 C/C++ Symmetric Return Codes 501-999
 =====================================
 
  ESMC_RC_OBJ_BAD          501 
  ESMC_RC_OBJ_INIT         502
  ESMC_RC_OBJ_CREATE       503
  ESMC_RC_OBJ_COR          504
  ESMC_RC_OBJ_WRONG        505
  ESMC_RC_ARG_BAD          506
  ESMC_RC_ARG_RANK         507
  ESMC_RC_ARG_SIZE         508
  ESMC_RC_ARG_VALUE        509
  ESMC_RC_ARG_DUP          510
  ESMC_RC_ARG_SAMETYPE     511
  ESMC_RC_ARG_SAMECOMM     512
  ESMC_RC_ARG_INCOMP       513
  ESMC_RC_ARG_CORRUPT      514
  ESMC_RC_ARG_WRONG        515
  ESMC_RC_ARG_OUTOFRANGE   516
  ESMC_RC_ARG_OPT          517
  ESMC_RC_NOT_IMPL         518
  ESMC_RC_FILE_OPEN        519
  ESMC_RC_FILE_CREATE      520
  ESMC_RC_FILE_READ        521
  ESMC_RC_FILE_WRITE       522
  ESMC_RC_FILE_UNEXPECTED  523
  ESMC_RC_FILE_CLOSE       524
  ESMC_RC_FILE_ACTIVE      525
  ESMC_RC_PTR_NULL         526
  ESMC_RC_PTR_BAD          527
  ESMC_RC_PTR_NOTALLOC     528
  ESMC_RC_PTR_ISALLOC      529
  ESMC_RC_MEM              530
  ESMC_RC_MEM_ALLOCATE     531
  ESMC_RC_MEM_DEALLOCATE   532
  ESMC_RC_MEMC             533
  ESMC_RC_DUP_NAME         534
  ESMC_RC_LONG_NAME        535
  ESMC_RC_LONG_STR         536
  ESMC_RC_COPY_FAIL        537
  ESMC_RC_DIV_ZERO         538
  ESMC_RC_CANNOT_GET       539
  ESMC_RC_CANNOT_SET       540
  ESMC_RC_NOT_FOUND        541
  ESMC_RC_NOT_VALID        542
  ESMC_RC_INTNRL_LIST      543
  ESMC_RC_INTNRL_INCONS    544
  ESMC_RC_INTNRL_BAD       545
  ESMC_RC_SYS              546
  ESMC_RC_BUSY             547
  ESMC_RC_LIB              548
  ESMC_RC_LIB_NOT_PRESENT  549
  ESMC_RC_ATTR_UNUSED      550
  ESMC_RC_OBJ_NOT_CREATED  551
  ESMC_RC_OBJ_DELETED      552
  ESMC_RC_NOT_SET          553
  ESMC_RC_VAL_WRONG        554
  ESMC_RC_VAL_ERRBOUND     555
  ESMC_RC_VAL_OUTOFRANGE   556
  ESMC_RC_ATTR_NOTSET      557
  ESMC_RC_ATTR_WRONGTYPE   558
  ESMC_RC_ATTR_ITEMSOFF    559
  ESMC_RC_ATTR_LINK        560
  ESMC_RC_BUFFER_SHORT     561
  ESMC_RC_TIMEOUT          562
  ESMC_RC_FILE_EXISTS      563
  ESMC_RC_FILE_NOTDIR      564
 
 562-999 reserved for future C/C++ symmetric return code definitions
 
 =====================================
 C/C++ Non-symmetric Return Codes 1000
 =====================================
 
  ESMC_RC_OPTARG_BAD      1000


next up previous contents
Next: About this document ... Up: ESMF_refdoc Previous: Bibliography   Contents
esmf_support@list.woc.noaa.gov