[MOAB-dev] commit/MOAB: danwu: The purpose field of __<dim_name>_LOC_MIN_MAX is incomplete in metadata.h. Recovered the missing words using metadata_info.pdf
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Thu Aug 29 15:11:16 CDT 2013
1 new commit in MOAB:
https://bitbucket.org/fathomteam/moab/commits/2b7c32dca697/
Changeset: 2b7c32dca697
Branch: master
User: danwu
Date: 2013-08-29 22:10:47
Summary: The purpose field of __<dim_name>_LOC_MIN_MAX is incomplete in metadata.h. Recovered the missing words using metadata_info.pdf
Affected #: 1 file
diff --git a/doc/MetaData/metadata.h b/doc/MetaData/metadata.h
index 84aaf87..6d03665 100644
--- a/doc/MetaData/metadata.h
+++ b/doc/MetaData/metadata.h
@@ -677,13 +677,19 @@ netcdf file. The length of this tag is the number of
values stored for the dimension in the netcdf file.</td></tr><tr>
-<td>__<dim_name>_LOC_MIN MAX</td>
+<td>__<dim_name>_LOC_MIN_MAX</td><td>2*(I or D)</td><td>S</td><td>The indices (0-based) of the local min and max
values of dimension stored locally. For spatial
dimensions like lon or lat, this will store the
-minimum and maximum indices in the loca</td>
+minimum and maximum indices in the local partition
+of the grid. For dimensions like time, where each
+processor represents the entire dimension, this will
+likely store 0 and the number of values for that
+dimension. Only one of __<dim_name>_LOC_VALS and
+__<dim_name>_LOC_MIN_MAX can be used for a given
+dimension.</td></tr><tr><td >__<dim_name>_LOC_VAL </td>
@@ -693,8 +699,8 @@ minimum and maximum indices in the loca</td>
locally. This tag only makes sense for dimensions
that can be read in multiple pieces, such as time.
Only one of __<dim_name>_LOC_VALS and
-_LOC_MIN_MAX can be used for a given
-dimension.
+__<dim_name>_LOC_MIN_MAX can be used for a given
+dimension.</td></tr><tr><td>__<var_name>_DIMS
Repository URL: https://bitbucket.org/fathomteam/moab/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
More information about the moab-dev
mailing list