ConvertToHDF5 - Revision history

Paulochambel: /* CONVERT GENERIC NETCDF CF */

2015-10-26T18:29:51Z

‎CONVERT GENERIC NETCDF CF

2015-10-26T18:29:27Z

‎CONVERT GENERIC NETCDF CF

2015-10-26T18:28:51Z

‎CONVERT GENERIC NETCDF CF

2015-10-26T18:28:22Z

‎CONVERT GENERIC NETCDF CF

2013-10-23T15:03:15Z

2013-10-23T15:00:11Z

2013-10-09T14:38:45Z

‎Glue several MOHID(.hdf5) files with same instants (Merge)

2013-10-09T14:38:26Z

‎Samples

2013-10-09T14:13:12Z

‎GLUES HDF5 FILES

2013-10-09T14:09:42Z

‎Glue files

@@ Line 816: / Line 816: @@
   NETCDF_NAME_DEPTH   : ... ! (name of the netcdf property for the cells depth, generally "depth", usually is a  1D Field)
   STARTS_180W         : 0/1 ! (default 0 - only important for global solutions. Some times a solution that starts in 0º is not a good option. This allows a global solution to start at 180 W)
   <<end_grid>>

@@ Line 814: / Line 814: @@
   BATHYM_FROM_MAP     : 0/1  (based in the mask/mapping matrix and the field depth (NETCDF_NAME_DEPTH) the tool is able to generate a bathymetry)
   BATHYM_FILENAME     :  ... (File name of the bathymetry that can be generate by tool (BATHYM_FROM_MAP : 1)
   NETCDF_NAME_DEPTH   : ... ! (name of the netcdf property for the cells depth, generally "depth", usually is a  1D Field)
   STARTS_180W         : 0/1 ! (default 0 - only important for global solutions. Some times a solution that starts in 0º is not a good option. This allows a global solution to start at 180 W)

@@ Line 799: / Line 799: @@
   NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)
   OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)
   WINDOW_OUT          : imin imax jmin jmax (indexes of cells of the spatial window the user wants to extract, if this keyword in not used the entire domain is convert)

@@ Line 799: / Line 799: @@
   NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)
   OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)
   <<begin_time>>
@@ Line 810: / Line 812: @@
                             (It can also be used any field, i.e. temperature)
   MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus >0.5 water)
   <<end_grid>>

@@ Line 43: / Line 43: @@
 '''RUNING TIP:'''
-Could be necessary to use a single compilation because time values get corrupted with the double compilation
 ==Grid interpolation==
@@ Line 88: / Line 89: @@
 '''RUNING TIP:'''
 Could be necessary to use a double compilation because values like precipitation and relative humidity can get out of scale values due to Rounding errors. For example precipitation can be slightly smaller than zero (which is negative) and relative humidity could be slightly higher than 1.

@@ Line 41: / Line 41: @@
 '''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].
 ==Grid interpolation==
@@ Line 83: / Line 86: @@
 '''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].
 ===Patch files===

@@ Line 879: / Line 879: @@
   <<begin_list>>
   D:\Projectos\SurfaceHydrodynamic_21.hdf5
-  D:\Projectos\SurfaceWaterProperties_22.hdf5
+  D:\Projectos\SurfaceWaterProperties_21.hdf5
   <<end_list>>
   <end_file>

@@ Line 857: / Line 857: @@
 All sample files are named ''ConvertToHDF5Action.dat''.
-===Glue several MOHID(.hdf5) files===
+===Glue several MOHID(.hdf5) files sequentially (Concatenate)===
   <begin_file>
   ACTION                   : GLUES HDF5 FILES
@@ Line 866: / Line 866: @@
   D:\Projectos\SurfaceHydrodynamic_21.hdf5
   D:\Projectos\SurfaceHydrodynamic_22.hdf5
   <<end_list>>
   <end_file>

@@ Line 18: / Line 18: @@
 ===Glue files===
-This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued. The use of the OPEN POINTS information is optional.
+This action consists in two main apspects:
 '''Typical use:'''
 Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.
 '''Data input requirements:'''
-HDF5 files to be glued. "Grid" and "Results" data groups should be equal in all these files.
+HDF5 files to be glued. For the concatenation of consecutive files "Grid" and "Results" data groups should be equal in all these files. For the merging of groups bathymetry and time instants need to be the same in the HDF5 files.
 '''Output:'''