1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
|
<html>
<head><title>
HDF5/Tools API Specification
</title>
<!-- #BeginLibraryItem "/ed_libs/styles_RM.lbi" -->
<!--
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Copyright by the Board of Trustees of the University of Illinois. *
* All rights reserved. *
* *
* This file is part of HDF5. The full HDF5 copyright notice, including *
* terms governing use, modification, and redistribution, is contained in *
* the files COPYING and Copyright.html. COPYING can be found at the root *
* of the source code distribution tree; Copyright.html can be found at the *
* root level of an installed copy of the electronic HDF5 document set and *
* is linked from the top-level documents page. It can also be found at *
* http://hdf.ncsa.uiuc.edu/HDF5/doc/Copyright.html. If you do not have *
* access to either file, you may request a copy from hdfhelp@ncsa.uiuc.edu. *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
-->
<link href="ed_styles/RMelect.css" rel="stylesheet" type="text/css">
<!-- #EndLibraryItem --></head>
<body bgcolor="#FFFFFF">
<!-- #BeginLibraryItem "/ed_libs/NavBar_RM.lbi" --><hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
<a href="index.html">HDF5 documents and links</a> <br>
<a href="H5.intro.html">Introduction to HDF5</a> <br>
<a href="H5.user.html">HDF5 User Guide</a> <br>
<!--
<a href="Glossary.html">Glossary</a><br>
-->
</td>
<td valign=top align=right>
And in this document, the
<a href="RM_H5Front.html">HDF5 Reference Manual</a>
<br>
<a href="RM_H5.html">H5</a>
<a href="RM_H5A.html">H5A</a>
<a href="RM_H5D.html">H5D</a>
<a href="RM_H5E.html">H5E</a>
<a href="RM_H5F.html">H5F</a>
<a href="RM_H5G.html">H5G</a>
<a href="RM_H5I.html">H5I</a>
<a href="RM_H5P.html">H5P</a>
<br>
<a href="RM_H5R.html">H5R</a>
<a href="RM_H5S.html">H5S</a>
<a href="RM_H5T.html">H5T</a>
<a href="RM_H5Z.html">H5Z</a>
<a href="Tools.html">Tools</a>
<a href="PredefDTypes.html">Datatypes</a>
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><center>
<h1>HDF5 Tools</h1>
</center>
<h2>HDF5 Tool Interfaces</h2>
<p>
These tools enable the user to examine HDF5 file contents,
to modify HDF5 file contents in a carefully prescribed manner, and
to convert files from HDF4 format to HDF5 format and vice versa.
<table border=0>
<tr><td valign=top>
<ul>
<li><a href="#Tools-Dump">h5dump</a> --
A tool for displaying HDF5 file contents
<li><a href="#Tools-Ls">h5ls</a> --
A tool for listing specified features of HDF5 file contents
<li><a href="#Tools-Diff">h5diff</a> --
A tool to identify and locate the differences between two HDF5 files
<em>(Beta version)</em>
<li><a href="#Tools-Repart">h5repart</a> --
A tool for repartitioning a file, creating a family of files
<li><a href="#Tools-Import">h5import</a> --
A tool for importing data into an existing or new HDF5 file
<li><a href="#Tools-GIF2H5">gif2h5</a> --
A tool for converting a GIF file to an HDF5 file
<li><a href="#Tools-H52GIF">h52gif</a> --
A tool for converting images in an HDF5 file to a GIF file
<li><a href="#Tools-H5toh4">h5toh4</a> --
A tool for converting an HDF5 file to an HDF4 file
<li><a href="#Tools-H4toh5">h4toh5</a> --
A tool for converting an HDF4 file to an HDF5 file
<li><a href="#Tools-Perf">h5perf</a> --
A tool for measuring HDF5 performance
<li><a href="#Tools-Redeploy">h5redeploy</a> --
A tool for updating HDF5 compiler tools after installing HDF5
<li><a href="#Tools-H5CC">h5cc</a> --
A tool for compiling HDF5 programs written in C
<li><a href="#Tools-H5FC">h5fc</a> --
A tool for compiling HDF5 programs written in Fortran90
<li><a href="#Tools-H5C++">h5c++</a> --
A tool for compiling HDF5 programs written in C++
<li><a href="http://hdf.ncsa.uiuc.edu/java-hdf5-html/">Java-based tools for HDF5</a> --
<em>(at <code>http://hdf.ncsa.uiuc.edu/java-hdf5-html/</code>)</em>
<br>
Java-based tools for viewing, manipulating, and generating HDF5
files (distributed separately)
<br>
Includes <code>H5view</code>, <code>H5gen</code>, Java HDF5
Interface (JHI5), and HDF5 VisAD Data Adapter
</ul>
</td></tr>
</table>
<p>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Dump">h5dump</a>
<dt><strong>Syntax:</strong>
<dd><code>h5dump
[</code><em>OPTIONS</em><code>]</code> <em>file</em>
<dt><strong>Purpose:</strong>
<dd>Displays HDF5 file contents.
<dt><strong>Description:</strong>
<dd><code>h5dump</code> enables the user to examine
the contents of an HDF5 file and dump those contents, in human
readable form, to an ASCII file.
<p>
<code>h5dump</code> dumps HDF5 file content to standard output.
It can display the contents of the entire HDF5 file or
selected objects, which can be groups, datasets, a subset of a
dataset, links, attributes, or datatypes.
</p>
<p>
The <code>--header</code> option displays object header
information only.
</p>
<p>
Names are the absolute names of the objects. <code>h5dump</code>
displays objects in the order same as the command order. If a
name does not start with a slash, <code>h5dump</code> begins
searching for the specified object starting at the root group.
</p>
<p>
If an object is hard linked with multiple names,
<code>h5dump</code> displays the content of the object in the
first occurrence. Only the link information is displayed in later
occurrences.
</p>
<p>
<code>h5dump</code> assigns a name for any unnamed datatype in
the form of
<code>#</code><em>oid1</em><code>:</code><em>oid2</em>, where
<em>oid1</em> and <em>oid2</em> are the object identifiers
assigned by the library. The unnamed types are displayed within
the root group.
</p>
<p>
Datatypes are displayed with standard type names. For example,
if a dataset is created with <code>H5T_NATIVE_INT</code> type
and the standard type name for integer on that machine is
<code>H5T_STD_I32BE</code>, <code>h5dump</code> displays
<code>H5T_STD_I32BE</code> as the type of the dataset.
</p>
<p>
<code>h5dump</code> can also dump a subset of a dataset.
This feature operates in much the same way as hyperslabs in HDF5;
the parameters specified on the commnd line are passed to the
function <a href="RM_H5S.html#Dataspace-SelectHyperslab">
<code>H5Sselect_hyperslab</code></a> and the resulting selection
is displayed.
</p>
<p>
The <code>h5dump</code> output is described in detail in the
<a href="ddl.html"><cite>DDL for HDF5</cite></a>, the
<cite>Data Description Language</cite> document.
</p>
<p>
<em>Note</em>: It is not permissable to specify multiple
attributes, datasets, datatypes, groups, or soft links with one
flag. For example, one may not issue the command
<br>
<font size=-1>WRONG:</font>
<code>h5dump -a /attr1 /attr2 foo.h5</code>
</br>
to display both <code>/attr1</code> and <code>/attr2</code>.
One must issue the following command:
<br>
<font size=-1>CORRECT:</font>
<code>h5dump -a /attr1 -a /attr2 foo.h5</code>
</br>
</p>
<p>
It's possible to select the file driver with which to open the
HDF5 file by using the --filedriver (-f) command-line option.
Acceptable values for the --filedriver option are: "sec2",
"family", "split", "multi", and "stream". If the file driver flag
isn't specified, then the file will be opened with each driver in
turn and in the order specified above until one driver succeeds
in opening the file.
</p>
<dt><strong>XML Output:</strong>
<dd>With the <code>--xml</code> option, <code>h5dump</code> generates
XML output. This output contains a complete description of the file,
marked up in XML. The XML conforms to the HDF5 Document Type
Definition (DTD) available at
<a href="http://hdf.ncsa.uiuc.edu/DTDs/HDF5-File.dtd">
<code>http://hdf.ncsa.uiuc.edu/DTDs/HDF5-File.dtd</code></a>.
<p>
The XML output is suitable for use with other tools, including the
<a href="http://hdf.ncsa.uiuc.edu/java-hdf5-html">HDF5 Java Tools</a>.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-h</code> or
<code>--help</code></dt>
<dd>Print a usage message and exit.</dd>
<dt><code>-B</code> or
<code>--bootblock</code></dt>
<dd>Print the content of the boot block.<br>
<em>(This option is not yet implemented.)</em></dd>
<dt><code>-H</code> or
<code>--header</code></dt>
<dd>Print the header only; no data is displayed.</dd>
<dt><code>-i</code> or
<code>--object-ids</code></dt>
<dd>Print the object ids.</dd>
<dt><code>-r</code> or
<code>--string</code></dt>
<dd>Print 1-bytes integer datasets as ASCII.</dd>
<dt><code>-V</code> or
<code>--version</code></dt>
<dd>Print version number and exit.</dd>
<dt><code>-a <em>P</em></code> or
<code>--attribute=<em>P</em></code></dt>
<dd>Print the specified attribute.</dd>
<dt><code>-d <em>P</em></code> or
<code>--dataset=<em>P</em></code></dt>
<dd>Print the specified dataset.</dd>
<dt><code>-f <em>D</em></code> or
<code>--filedriver=<em>D</em></code></dt>
<dd>Specify which driver to open the file with.</dd>
<dt><code>-g <em>P</em></code> or
<code>--group=<em>P</em></code></dt>
<dd>Print the specified group and all members.</dd>
<dt><code>-l <em>P</em></code> or
<code>--soft-link=<em>P</em></code></dt>
<dd>Print the value(s) of the specified soft link.</dd>
<dt><code>-o <em>F</em></code> or
<code>--output=<em>F</em></code></dt>
<dd>Output raw data into file F.</dd>
<dt><code>-t <em>T</em></code> or
<code>--datatype=<em>T</em></code></dt>
<dd>Print the specified named datatype.</dd>
<dt><code>-w <em>N</em></code> or
<code>--width=<em>N</em></code></dt>
<dd>Set the number of columns of output.</dd>
<dt><code>-x <em>U</em></code> or
<code>--xml</code></dt>
<dd>Output XML instead of DDL.</dd>
<dt><code>-D <em>U</em></code> or
<code>--xml-dtd=<em>U</em></code></dt>
<dd>In XML output, refer to the DTD at <em>U</em>
instead of the default DTD.</dd>
<dt><code>-s <em>L</em></code> or
<code>--start=<em>L</em></code></dt>
<dd>Offset of start of subsetting selection.
<br>
Default: the beginning of the dataset.</dd>
<dt><code>-S <em>L</em></code> or
<code>--stride=<em>L</em></code></dt>
<dd>Hyperslab stride.
<br>
Default: 1 in all dimensions.</dd>
<dt><code>-c <em>L</em></code> or
<code>--count=<em>L</em></code></dt>
<dd>Number of blocks to include in the selection.</dd>
<dt><code>-k <em>L</em></code> or
<code>--block=<em>L</em></code></dt>
<dd>Size of block in hyperslab.
<br>
Default: 1 in all dimensions.</dd>
<dt><code>--</code></dt>
<dd>Indicate that all following arguments are non-options.
E.g., to dump a file called `-f', use h5dump -- -f.</dd>
<dt><em>file</em></dt>
<dd>The file to be examined.</dd>
<br><br>
<dt>The option parameters listed above are defined as follows:
<dd><em>D</em> -- which file driver to use in opening the
file. Acceptable values are "sec2", "family", "split",
"multi", and "stream". Without the file driver flag the
file will be opened with each driver in turn and in the
order specified above until one driver succeeds in
opening the file.</dd>
<dd><em>P</em> -- The full path from the root group to
the object</dd>
<dd><em>T</em> -- The name of the datatype</dd>
<dd><em>F</em> -- A filename</dd>
<dd><em>N</em> -- An integer greater than 1</dd>
<dd><em>L</em> -- A list of integers, the number of which is
equal to the number of dimensions in the dataspace being
queried</dd>
<dd><em>U</em> -- A URI (as defined in
[<a href="http://www.ietf.org/rfc/rfc2396.txt">IETF RFC 2396</a>],
updated by
[<a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732</a>])
that refers to the DTD to be used to validate the XML</dd>
<br><br>
<dt>Subsetting paramaters can also be expressed in a convenient
compact form, as follows:
<br>
<code>--dataset="/foo/mydataset[START;STRIDE;COUNT;BLOCK]"</code>
<br>
All of the semicolons (<code>;</code>) are required, even when
a parameter value is not specified.
When not specified, default parameter values are used.
</dl>
<p>
<dt><strong>Examples:</strong>
<ol>
<li>Dumping the group <code>/GroupFoo/GroupBar</code> in the file
<code>quux.h5</code>:
<blockquote>
<code>h5dump -g /GroupFoo/GroupBar quux.h5</code>
</blockquote>
<li>Dumping the dataset <code>Fnord</code> in the group
<code>/GroupFoo/GroupBar</code> in the file <code>quux.h5</code>:
<blockquote>
<code>h5dump -d /GroupFoo/GroupBar/Fnord quux.h5</code>
</blockquote>
<li>Dumping the attribute <code>metadata</code> of the dataset
<code>Fnord</code> which is in group
<code>/GroupFoo/GroupBar</code> in the file <code>quux.h5</code>:
<blockquote>
<code>h5dump -a /GroupFoo/GroupBar/Fnord/metadata quux.h5</code>
</blockquote>
<li>Dumping the attribute <code>metadata</code> which is an
attribute of the root group in the file <code>quux.h5</code>:
<blockquote>
<code>h5dump -a /metadata quux.h5</code>
</blockquote>
<li>Producing an XML listing of the file <code>bobo.h5</code>:
<blockquote>
<code>h5dump --xml bobo.h5 > bobo.h5.xml</code>
</blockquote>
<li>Dumping a subset of the dataset <code>/GroupFoo/databar/</code>
in the file <code>quux.h5</code>
<blockquote>
<code>h5dump -d /GroupFoo/databar --start="1,1" --stride="2,3"
<br>
--count="3,19" --block="1,1" quux.h5</code>
</blockquote>
<li>The same example using the short form to specify the
subsetting parameters:
<blockquote>
<code>h5dump -d "/GroupFoo/databar[1,1;2,3;3,19;1,1]" quux.h5</code>
</blockquote>
</ol>
<dt><strong>Current Status:</strong>
<dd>The current version of <code>h5dump</code> displays the
following information:
<ul>
<li>Group
<ul>
<li>group attribute (see Attribute)
<li>group member
</ul>
<li>Dataset
<ul>
<li>dataset attribute (see Attribute)
<li>dataset type (see Datatype)
<li>dataset space (see Dataspace)
<li>dataset data
</ul>
<li>Attribute
<ul>
<li>attribute type (see Datatype)
<li>attribute space (see Dataspace)
<li>attribute data
</ul>
<li>Datatype
<ul>
<li>integer type
<br>
- H5T_STD_I8BE, H5T_STD_I8LE, H5T_STD_I16BE, ...
<li>floating point type
<br>
- H5T_IEEE_F32BE, H5T_IEEE_F32LE, H5T_IEEE_F64BE, ...
<li>string type
<li>compound type
<br>
- named, unnamed and transient compound type
<br>
- integer, floating or string type member
<li>opaque types
<li>reference type
<br>
- object references
<br>
- data regions
<li>enum type
<li>variable-length datatypes
<br>
- atomic types only
<br>
- scalar or single dimensional array of variable-length
types supported
</ul>
<li>Dataspace
<ul>
<li>scalar and simple space
</ul>
<li>Soft link
<li>Hard link
<li>Loop detection
</ul>
<dt><strong>See Also:</strong>
<ul>
<li>HDF5 Data Description Language syntax at
<a href="ddl.html"><cite>DDL for HDF5</cite></a>
<li>HDF5 XML DTD at
<a href="http://hdf.ncsa.uiuc.edu/DTDs/HDF5-File.dtd">http://hdf.ncsa.uiuc.edu/DTDs/HDF5-File.dtd</a>
<li>HDF5 XML information at
<a href="http://hdf.ncsa.uiuc.edu/HDF5/XML">http://hdf.ncsa.uiuc.edu/HDF5/XML/</a>
</ul>
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Ls">h5ls</a>
<dt><strong>Syntax:</strong>
<dd><code>h5ls
[</code><em>OPTIONS</em><code>]</code><em>
file</em><code>
[</code><em>OBJECTS...</em><code>]</code>
<dt><strong>Purpose:</strong>
<dd>Prints information about a file or dataset.
<dt><strong>Description:</strong>
<dd><code>h5ls</code> prints selected information about file objects
in the specified format.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-h</code> or
<code>-?</code> or
<code>--help</code>
<dd>Print a usage message and exit.
<dt><code>-a</code> or
<code>--address</code>
<dd>Print addresses for raw data.
<dt><code>-d</code> or <code>--data</code>
<dd>Print the values of datasets.
<dt><code>-e</code> or
<code>--errors</code>
<dd>Show all HDF5 error reporting.
<dt><code>-f</code> or
<code>--full</code>
<dd>Print full path names instead of base names.
<dt><code>-g</code> or
<code>--group</code>
<dd>Show information about a group, not its contents.
<dt><code>-l</code> or
<code>--label</code>
<dd>Label members of compound datasets.
<dt><code>-r</code> or
<code>--recursive</code>
<dd>List all groups recursively, avoiding cycles.
<dt><code>-s</code> or
<code>--string</code>
<dd>Print 1-bytes integer datasets as ASCII.
<dt><code>-S</code> or
<code>--simple</code>
<dd>Use a machine-readable output format.
<dt><code>-w</code><em>N</em> or
<code>--width=</code><em>N</em>
<dd>Set the number of columns of output.
<dt><code>-v</code> or
<code>--verbose</code>
<dd>Generate more verbose output.
<dt><code>-V</code> or
<code>--version</code>
<dd>Print version number and exit.
<dt><code>-x</code> or
<code>--hexdump</code>
<dd>Show raw data in hexadecimal format.
<dt><em>file</em>
<dd>The file name may include a printf(3C) integer format
such as <code>%%05d</code> to open a file family.
<dt><em>objects</em>
<dd>Each object consists of an HDF5 file name optionally
followed by a slash and an object name within the file
(if no object is specified within the file then the
contents of the root group are displayed). The file name
may include a <code>printf(3C)</code> integer format such
as "%05d" to open a file family.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Diff">h5diff</a> <em>(Beta version)</em>
<dt><strong>Syntax:</strong>
<dd><code>h5diff </code> <em>file1</em> <em>file2</em>
[<em>OPTIONS</em>]
[<em>object1</em> [<em>object2</em> ] ]
<dt><strong>Purpose:</strong>
<dd>Compares two HDF5 files and reports the differences.
<dt><strong>Description:</strong>
<dd><code>h5diff</code> is a command line tool that compares
two HDF5 files, <em>file1</em> and <em>file2</em>, and
reports the differences between them.
<p>
Optionally, <code>h5diff</code> will compare two objects
within these files.
If only one object, <em>object1</em>, is specified,
<code>h5diff</code> will compare
<em>object1</em> in <em>file1</em>
with <em>object1</em> in <em>file2</em>.
In two objects, <em>object1</em> and <em>object2</em>,
are specified, <code>h5diff</code> will compare
<em>object1</em> in <em>file1</em>
with <em>object2</em> in <em>file2</em>.
These objects must be HDF5 datasets.
<p>
<em>object1</em> and <em>object2</em> must be expressed
as absolute paths from the respective file's root group.
<p>
Additional information, with several sample cases,
can be found in the document
<a href="http://hdf.ncsa.uiuc.edu/HDF5/h5diff/h5diff_design.html">
<cite>H5diff Examples</cite></a>.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><em>file1</em>
<dt><em>file2</em>
<dd>The HDF5 files to be compared.
<dt><code>-h</code>
<dd>Print all differences.
<dt><code>-r</code>
<dd>Print only the names of objects that differ;
do not print the differences.
These objects may be HDF5 datasets, groups,
or named datatypes.
<dt><code>-n</code> <em>count</em>
<dd>Print difference up to <em>count</em> differences,
then stop.
<em>count</em> must be a positive integer.
<dt><code>-d</code> <em>delta</em>
<dd>Print only differences that are greater than the
limit <em>delta</em>.
<em>delta</em> must be a positive number.
The comparison criterion is whether the
absolute value of the difference of
two corresponding values is greater than
<em>delta</em>
<br>(e.g., <code> |a–b| > <em>delta</em></code>,
where <code>a</code> is a value in <em>file1</em> and
<code>b</code> is a value in <em>file2</em>).
<dt><code>-p</code> <em>relative</em>
<dd>Print only differences that are greater than a
relative error.
<em>relative</em> must be a positive number.
The comparison criterion is whether the
absolute value of the difference <code>1</code>
and the ratio of two corresponding values
is greater than <em>relative</em>
(e.g., <code>|1–(b/a)| > <em>relative</em></code>
where <code>a</code> is a value in <em>file1</em> and
<code>b</code> is a value in <em>file2</em>).
<dt><em>object1</em>
<dt><em>object2</em>
<dd>Specific object(s) within the files to be compared.
</dl>
<dt><strong>Examples:</strong>
<dd>The following <code>h5diff</code> call compares
the object <code>/a/b</code> in <code>file1</code>
with the object <code>/a/c</code> in <code>file2</code>:<br>
<code> h5diff file1 file2 /a/b /a/c</code>
<dd>This <code>h5diff</code> call compares
the object <code>/a/b</code> in <code>file1</code>
with the same object in <code>file2</code>:<br>
<code> h5diff file1 file2 /a/b</code>
<dd>And this <code>h5diff</code> call compares
all objects in both files:<br>
<code> h5diff file1 file2</code>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Repart">h5repart</a>
<dt><strong>Syntax:</strong>
<dd><code>h5repart
[-v]
[-V]
[-[b|m]</code><em>N</em><code>[g|m|k]]</code>
<em>source_file
dest_file</em>
<dt><strong>Purpose:</strong>
<dd>Repartitions a file or family of files.
<dt><strong>Description:</strong>
<dd><code>h5repart</code> splits a single file into a family of
files, joins a family of files into a single file, or copies
one family of files to another while changing the size of the
family members. <code>h5repart</code> can also be used to
copy a single file to a single file with holes.
<p>
Sizes associated with the <code>-b</code> and <code>-m</code>
options may be suffixed with <code>g</code> for gigabytes,
<code>m</code> for megabytes, or <code>k</code> for kilobytes.
<p>
File family names include an integer <code>printf</code>
format such as <code>%d</code>.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-v</code>
<dd>Produce verbose output.
<dt><code>-V</code>
<dd>Print a version number and exit.
<dt><code>-b</code><em>N</em>
<dd>The I/O block size, defaults to 1kB
<dt><code>-m</code><em>N</em>
<dd>The destination member size or 1GB
<dt><em>source_file</em>
<dd>The name of the source file
<dt><em>dest_file</em>
<dd>The name of the destination files
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Import">h5import</a>
<dt><strong>Syntax:</strong>
<dd><code>h5import
<em>infile</em> <em>in_options</em>
[<em>infile</em> <em>in_options</em> <b>...</b>]
-o <em>outfile</em>
</code>
<dd><code>h5import
<em>infile</em> <em>in_options</em>
[<em>infile</em> <em>in_options</em> <b>...</b>]
-outfile <em>outfile</em>
</code>
<dd><code>h5import -h</code>
<dd><code>h5import -help</code>
<dt><strong>Purpose:</strong>
<dd>Imports data into an existing or new HDF5 file.
<dt><strong>Description:</strong>
<dd><code>h5import</code> converts data
from one or more ASCII or binary files, <code><i>infile</i></code>,
into the same number of HDF5 datasets
in the existing or new HDF5 file, <code><i>outfile</i></code>.
Data conversion is performed in accordance with the
user-specified type and storage properties
specified in <code><em>in_options</em></code>.
<p>
The primary objective of <code>h5import</code> is to
import floating point or integer data.
The utility's design allows for future versions that
accept ASCII text files and store the contents as a
compact array of one-dimensional strings,
but that capability is not implemented in HDF5 Release 1.6.
<p>
<b>Input data and options:</b><br>
Input data can be provided in one of the follwing forms:
<ul><li>As an ASCII, or plain-text, file containing either
floating point or integer data
<li>As a binary file containing either 32-bit or
64-bit native floating point data
<li>As a binary file containing native integer data,
signed or unsigned and
8-bit, 16-bit, 32-bit, or 64-bit.
<li>As an ASCII, or plain-text, file containing text data.
(This feature is not implemented in HDF5 Release 1.6.)
</ul>
Each input file, <code><i>infile</i></code>,
contains a single <em>n</em>-dimensional
array of values of one of the above types expressed
in the order of fastest-changing dimensions first.
<p>
Floating point data in an ASCII input file must be
expressed in the fixed floating form (e.g., 323.56)
<code>h5import</code> is designed to accept scientific notation
(e.g., 3.23E+02) in an ASCII, but that is not implemented in HDF5 release 1.6.
<p>
Each input file can be associated with options specifying
the datatype and storage properties.
These options can be specified either as
<em>command line arguments</em>
or in a <em>configuration file</em>.
Note that exactly one of these approaches must be used with a
single input file.
<p>
Command line arguments, best used with simple input files,
can be used to specify
the class, size, dimensions of the input data and
a path identifying the output dataset.
<p>
The recommended means of specifying input data options
is in a configuration file; this is also the only means of
specifying advanced storage features.
See further discussion in "The configuration file" below.
<p>
The only required option for input data is dimension sizes;
defaults are available for all others.
<p>
<code>h5import</code> will accept up to 30 input files in a single call.
Other considerations, such as the maximum length of a command line,
may impose a more stringent limitation.
<p>
<b>Output data and options:</b><br>
The name of the output file is specified following
the <code>-o</code> or <code>-output</code> option
in <code><i>outfile</i></code>.
The data from each input file is stored as a separate dataset
in this output file.
<code><i>outfile</i></code> may be an existing file.
If it does not yet exist, <code>h5import</code> will create it.
<p>
Output dataset information and storage properties can be
specified only by means of a configuration file.
<table width=100% border=0>
<tr valign=top align=left><td width=30> </td><td>
Dataset path
</td><td>If the groups in the path leading to the dataset
do not exist, <code>h5import</code> will create them.<br>
If no group is specified, the dataset will be created
as a member of the root group.<br>
If no dataset name is specified, the default name is
<code>dataset1</code> for the first input dataset,
<code>dataset2</code> for the second input dataset,
<code>dataset3</code> for the third input dataset,
etc.<br>
<code>h5import</code> does not overwrite a pre-existing
dataset of the specified or default name.
When an existing dataset of a confilcting name is
encountered, <code>h5import</code> quits with an error;
the current input file and any subsequent input files
are not processed.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Output type
</td><td>Datatype parameters for output data
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Output data class
</td><td>Signed or unsigned integer or floating point
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Output data size
</td><td>8-, 16-, 32-, or 64-bit integer<br>
32- or 64-bit floating point
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Output architecture
</td><td><code>IEEE</code><br>
<code>STD</code><br>
<code>NATIVE</code> (Default)<br>
Other architectures are included in the <code>h5import</code> design
but are not implemented in this release.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Output byte order
</td><td>Little- or big-endian.<br>
Relevant only if output architecture
is <code>IEEE</code>, <code>UNIX</code>, or <code>STD</code>;
fixed for other architectures.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Dataset layout and storage <br>
properties
</td><td>Denote how raw data is to be organized on the disk.
If none of the following are specified,
the default configuration is contiguous layout and with no compression.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Layout
</td><td>Contiguous (Default)<br>
Chunked
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
External storage
</td><td>Allows raw data to be stored in a non-HDF5 file or in an
external HDF5 file.<br>
Requires contiguous layout.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Compressed
</td><td>Sets the type of compression and the
level to which the dataset must be compressed.<br>
Requires chunked layout.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Extendible
</td><td>Allows the dimensions of the dataset increase over time
and/or to be unlimited.<br>
Requires chunked layout.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
Compressed and<br>
extendible
</td><td>Requires chunked layout.
</td></tr>
<tr valign=top align=left><td width=30> </td><td>
</td><td>
</td></tr>
</table>
<p>
<p>
<b>Command-line arguments:</b><br>
The <code>h5import</code> syntax for the command-line arguments,
<code><em>in_options</em></code>, is as follows:
<table width=100% border=0>
<tr><td> </td><td>
<code>h5import <em>infile</em> -d <em>dim_list</em>
[-p <em>pathname</em>]
[-t <em>input_class</em>]
[-s <em>input_size</em>]
[<em>infile</em> ...]
-o <em>outfile</em></code><br>
or<br>
<code>h5import <em>infile</em> -dims <em>dim_list</em>
[-path <em>pathname</em>]
[-type <em>input_class</em>]
[-size <em>input_size</em>]
[<em>infile</em> ...]
-outfile <em>outfile</em></code><br>
or<br>
<code>h5import <em>infile</em> -c <em>config_file</em>
[<em>infile</em> ...]
-outfile <em>outfile</em></code>
</td></tr>
</table>
Note the following:
If the <code>-c <em>config_file</em></code> option is used with
an input file, no other argument can be used with that input file.
If the <code>-c <em>config_file</em></code> option is not used with
an input data file, the <code>-d <em>dim_list</em></code> argument
(or <code>-dims <em>dim_list</em></code>)
must be used and any combination of the remaining options may be used.
Any arguments used must appear in <em>exactly</em> the order used
in the syntax declarations immediately above.
<p>
<b>The configuration file:</b><br>
A configuration file is specified with the
<code>-c <em>config_file</em></code> option:
<table border=0>
<tr><td> </td><td>
<code>h5import <em>infile</em> -c <em>config_file</em>
[<em>infile</em> -c <em>config_file2</em> ...]
-outfile <em>outfile</em></code>
</td></tr>
</table>
<p>
The configuration file is an ASCII file and must be
organized as "Configuration_Keyword Value" pairs,
with one pair on each line.
For example, the line indicating that
the input data class (configuration keyword <code>INPUT-CLASS</code>)
is floating point in a text file (value <code>TEXTFP</code>)
would appear as follows:<br>
<code> INPUT-CLASS TEXTFP</code>
<p>
A configuration file may have the following keywords each
followed by one of the following defined values.
One entry for each of the first two keywords,
<code>RANK</code> and <code>DIMENSION-SIZES</code>,
is required; all other keywords are optional.
<p>
<table width=100% border=0>
<tr align=left><th valign=top align=left>
<hr>Keyword <br><code> </code>Value
</th><th valign=top align=left><hr>Description
</th></tr>
<tr valign=top align=left><td>
<hr><code>RANK </code>
</td><td><hr>The number of dimensions in the dataset. (Required)
</td></tr>
<tr valign=top align=left><td>
<code> <em>rank</em></code>
</td><td>An integer specifying the number of dimensions in the dataset.<br>
Example: <code> 4 </code> for a 4-dimensional dataset.
</td></tr>
<tr valign=top align=left><td>
<hr><code>DIMENSION-SIZES</code>
</td><td><hr>Sizes of the dataset dimensions. (Required)
</td></tr>
<tr valign=top align=left><td>
<code> <em>dim_sizes</em></code>
</td><td>A string of space-separated integers
specifying the sizes of the dimensions in the dataset.
The number of sizes in this entry must match the value in
the <code>RANK</code> entry.
The fastest-changing dimension must be listed first.<br>
Example: <code> 4 3 4 38 </code> for a 38x4x3x4 dataset.
</td></tr>
<tr valign=top align=left><td>
<hr><code>PATH</code>
</td><td><hr>Path of the output dataset.
</td></tr>
<tr valign=top align=left><td>
<code> <em>path</em></code>
</td><td>The full HDF5 pathname identifying the output dataset
relative to the root group within the output file.<br>
I.e., <code><em>path</em></code> is a string consisting of
optional group names, each followed by a slash,
and ending with a dataset name.
If the groups in the path do no exist, they will be
created.<br>
If <code>PATH</code> is not specified, the output dataset
is stored as a member of the root group and the
default dataset name is
<code>dataset1</code> for the first input dataset,
<code>dataset2</code> for the second input dataset,
<code>dataset3</code> for the third input dataset, etc.<br>
Note that <code>h5import</code> does not overwrite a
pre-existing dataset of the specified or default name.
When an existing dataset of a confilcting name is
encountered, <code>h5import</code> quits with an error;
the current input file and any subsequent input files
are not processed.<br>
Example: The configuration file entry
<table border=0>
<tr><td> </td><td>
<code>PATH grp1/grp2/dataset1</code>
</td></tr>
</table>
indicates that the output dataset <code>dataset1</code> will
be written in the group <code>grp2/</code> which is in
the group <code>grp1/</code>,
a member of the root group in the output file.
</td></tr>
<tr valign=top align=left><td>
<hr><code>INPUT-CLASS </code>
</td><td><hr>A string denoting the type of input data.
</td></tr>
<tr valign=top align=left><td>
<code> TEXTIN</code>
</td><td>Input is signed integer data in an ASCII file.
</td></tr>
<tr valign=top align=left><td>
<code> TEXTUIN</code>
</td><td>Input is unsigned integer data in an ASCII file.
</td></tr>
<tr valign=top align=left><td>
<code> TEXTFP</code>
</td><td>Input is floating point data in fixed notation (e.g., 325.34)
in an ASCII file.
</td></tr>
<tr valign=top align=left><td>
<code> TEXTFPE</code>
</td><td>Input is floating point data in scientific notation (e.g., 3.2534E+02)
in an ASCII file.<br>
(Not implemented in this release.)
</td></tr>
<tr valign=top align=left><td>
<code> IN</code>
</td><td>Input is signed integer data in a binary file.
</td></tr>
<tr valign=top align=left><td>
<code> UIN</code>
</td><td>Input is unsigned integer data in a binary file.
</td></tr>
<tr valign=top align=left><td>
<code> FP</code>
</td><td>Input is floating point data in a binary file. (Default)
</td></tr>
<tr valign=top align=left><td>
<code> STR</code>
</td><td>Input is character data in an ASCII file.
With this value, the configuration keywords
<code>RANK</code>, <code>DIMENSION-SIZES</code>,
<code>OUTPUT-CLASS</code>, <code>OUTPUT-SIZE</code>,
<code>OUTPUT-ARCHITECTURE</code>, and <code>OUTPUT-BYTE-ORDER</code>
will be ignored.<br>
(Not implemented in this release.)
</td></tr>
<tr valign=top align=left><td>
<hr><code>INPUT-SIZE</code>
</td><td><hr>An integer denoting the size of the input data, in bits.
</td></tr>
<tr valign=top align=left><td>
<code> 8</code><br>
<code> 16</code><br>
<code> 32</code><br>
<code> 64</code>
</td><td>For signed and unsigned integer data:
<code>TEXTIN</code>, <code>TEXTUIN</code>,
<code>IN</code>, or <code>UIN</code>.
(Default: <code> 32</code>)
</td></tr>
<tr valign=top align=left><td>
<code> 32</code><br>
<code> 64</code>
</td><td>For floating point data:
<code>TEXTFP</code>, <code>TEXTFPE</code>,
or <code>FP</code>.
(Default: <code> 32</code>)
</td></tr>
<tr valign=top align=left><td>
<hr><code>OUTPUT-CLASS </code>
</td><td><hr>A string denoting the type of output data.
</td></tr>
<tr valign=top align=left><td>
<code> IN</code>
</td><td>Output is signed integer data.<br>
(Default if <code>INPUT-CLASS</code> is
<code>IN</code> or <code>TEXTIN</code>)
</td></tr>
<tr valign=top align=left><td>
<code> UIN</code>
</td><td>Output is unsigned integer data.<br>
(Default if <code>INPUT-CLASS</code> is
<code>UIN</code> or <code>TEXTUIN</code>)
</td></tr>
<tr valign=top align=left><td>
<code> FP</code>
</td><td>Output is floating point data.<br>
(Default if <code>INPUT-CLASS</code> is not specified or is
<code>FP</code>, <code>TEXTFP</code>, or <code>TEXTFPE</code>)
</td></tr>
<tr valign=top align=left><td>
<code> STR</code>
</td><td>Output is character data,
to be written as a 1-dimensional array of strings.<br>
(Default if <code>INPUT-CLASS</code> is <code>STR</code>)<br>
(Not implemented in this release.)
</td></tr>
<tr valign=top align=left><td>
<hr><code>OUTPUT-SIZE</code>
</td><td><hr>An integer denoting the size of the output data, in bits.
</td></tr>
<tr valign=top align=left><td>
<code> 8</code><br>
<code> 16</code><br>
<code> 32</code><br>
<code> 64</code>
</td><td>For signed and unsigned integer data:
<code>IN</code> or <code>UIN</code>.
(Default: Same as <code>INPUT-SIZE</code>, else <code> 32</code>)
</td></tr>
<tr valign=top align=left><td>
<code> 32</code><br>
<code> 64</code>
</td><td>For floating point data:
<code>FP</code>.
(Default: Same as <code>INPUT-SIZE</code>, else <code> 32</code>)
</td></tr>
<tr valign=top align=left><td>
<hr><code>OUTPUT-ARCHITECTURE</code>
</td><td><hr>A string denoting the type of output architecture.
</td></tr>
<tr valign=top align=left><td>
<code> NATIVE</code><br>
<code> STD</code><br>
<code> IEEE</code><br>
<code> INTEL</code> *<br>
<code> CRAY</code> *<br>
<code> MIPS</code> *<br>
<code> ALPHA</code> *<br>
<code> UNIX</code> *
</td><td>See the "Predefined Atomic Types" section
in the "HDF5 Datatypes" chapter
of the <cite>HDF5 User's Guide</cite>
for a discussion of these architectures.<br>
Values marked with an asterisk (*) are not implemented in this release.<br>
(Default: <code>NATIVE</code>)
</td></tr>
<tr valign=top align=left><td>
<hr><code>OUTPUT-BYTE-ORDER</code>
</td><td><hr>A string denoting the output byte order.
This entry is ignored if the <code>OUTPUT-ARCHITECTURE</code>
is not specified or if it is not specified as <code>IEEE</code>,
<code>UNIX</code>, or <code>STD</code>.
</td></tr>
<tr valign=top align=left><td>
<code> BE</code>
</td><td>Big-endian. (Default)
</td></tr>
<tr valign=top align=left><td>
<code> LE</code>
</td><td>Little-endian.
</td></tr>
<tr valign=top align=left><td colspan="2">
<hr>The following options are disabled by default, making
the default storage properties no chunking, no compression,
no external storage, and no extensible dimensions.
</td></tr>
<tr valign=top align=left><td>
<hr><code>CHUNKED-DIMENSION-SIZES</code><br>
</td><td><hr>Dimension sizes of the chunk for chunked output data.
</td></tr>
<tr valign=top align=left><td>
<code> <em>chunk_dims</em></code>
</td><td>A string of space-separated integers specifying the
dimension sizes of the chunk for chunked output data.
The number of dimensions must correspond to the value
of <code>RANK</code>.<br>
The presence of this field indicates that the
output dataset is to be stored in chunked layout;
if this configuration field is absent,
the dataset will be stored in contiguous layout.
</td></tr>
<tr valign=top align=left><td>
<hr><code>COMPRESSION-TYPE</code>
</td><td><hr>Type of compression to be used with chunked storage.
Requires that <code>CHUNKED-DIMENSION-SIZES</code>
be specified.
</td></tr>
<tr valign=top align=left><td>
<code> GZIP</code>
</td><td>Gzip compression.<br>
Othe compression algorithms are not implemented
in this release of <code>h5import</code>.
</td></tr>
<tr valign=top align=left><td>
<hr><code>COMPRESSION-PARAM</code>
</td><td><hr>Compression level.
Required if <code>COMPRESSION-TYPE</code> is specified.
</td></tr>
<tr valign=top align=left><td>
<code> 1</code> through <code>9</code>
</td><td>Gzip compression levels:
<code>1</code> will result in the fastest compression
while <code>9</code> will result in the
best compression ratio.<br>
(Default: 6. The default gzip compression level is 6;
not all compression methods will have a default level.)
</td></tr>
<tr valign=top align=left><td>
<hr><code>EXTERNAL-STORAGE</code>
</td><td><hr>Name of an external file in which to create the output dataset.
Cannot be used with <code>CHUNKED-DIMENSIONS-SIZES</code>,
<code>COMPRESSION-TYPE</code>, OR <code>MAXIMUM-DIMENSIONS</code>.
</td></tr>
<tr valign=top align=left><td>
<code> <i>external_file</i> </code>
<!-- THE EXTRA NON-BREAKING SPACES AT THE END OF THE PRECEDING LINE -->
<!-- ARE PADDING SPACES TO ENSURE THE PROPER FORMATTING OF THIS TABLE. -->
<!-- DO NOT REMOVE THEM!!!!!!!!!!!!! -->
</td><td>A string specifying the name of an external file.
</td></tr>
<tr valign=top align=left><td>
<hr><code>MAXIMUM-DIMENSIONS</code>
</td><td><hr>Maximum sizes of all dimensions.
Requires that <code>CHUNKED-DIMENSION-SIZES</code> be specified.
</td></tr>
<tr valign=top align=left><td>
<code> <em>max_dims</em></code>
</td><td>A string of space-separated integers specifying the
maximum size of each dimension of the output dataset.
A value of <code>-1</code> for any dimension implies
unlimited size for that particular dimension.<br>
The number of dimensions must correspond to the value
of <code>RANK</code>.<br>
</td></tr>
<tr valign=top align=left><td><hr></td><td><hr></td></tr>
</table>
<p>
<b>The <code>help</code> option:</b><br>
The help option, expressed as one of
<table width=100% border=0>
<tr><td> </td><td>
<code>h5import -h</code><br>
or<br>
<code>h5import -help</code><br>
</td></tr>
<tr><td colspan="2">prints the <code>h5import</code> usage summary</td></tr>
<tr><td> </td><td>
<code>
h5import -h[elp], OR<br>
h5import <infile> <options>
[<infile> <options>...]
-o[utfile] <outfile></code>
</td></tr>
<tr><td colspan="2">then exits.</td></tr>
</table>
<p>
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>infile(s)</code>
<dd>Name of the Input file(s).
<dt><code>in_options</code>
<dd>Input options. Note that while only the <code>-dims</code> argument
is required, arguments must used in the order in which they are listed below.
<dl>
<dt><code>-d <em>dim_list</em></code>
<dt><code>-dims <em>dim_list</em></code>
<dd>Input data dimensions.
<code><em>dim_list</em></code> is a string of
comma-separated numbers with no spaces
describing the dimensions of the input data.
For example, a 50 x 100 2-dimensional array would be
specified as <code>-dims 50,100</code>.<br>
Required argument: if no configuration file is used,
this command-line argument is mandatory.
<dt><code>-p <em>pathname</em></code>
<dt><code>-pathname <em>pathname</em></code>
<dd><code><em>pathname</em></code> is a string consisting of
one or more strings separated by slashes (<code>/</code>)
specifying the path of the dataset in the output file.
If the groups in the path do no exist, they will be
created.<br>
Optional argument: if not specified,
the default path is
<code>dataset1</code> for the first input dataset,
<code>dataset2</code> for the second input dataset,
<code>dataset3</code> for the third input dataset,
etc.<br>
<code>h5import</code> does not overwrite a pre-existing
dataset of the specified or default name.
When an existing dataset of a confilcting name is
encountered, <code>h5import</code> quits with an error;
the current input file and any subsequent input files
are not processed.
<dt><code>-t <em>input_class</em></code>
<dt><code>-type <em>input_class</em></code>
<dd><code><em>input_class</em></code> specifies the class of the
input data and determines the class of the output data.<br>
Valid values are as defined in the Keyword/Values table
in the section "The configuration file" above.<br>
Optional argument: if not specified,
the default value is <code>FP</code>.
<dt><code>-s <em>input_size</em></code>
<dt><code>-size <em>input_size</em></code>
<dd><code><em>input_size</em></code> specifies the size in bits
of the input data and determines the size of the output data.<br>
Valid values for signed or unsigned integers are
<code>8</code>, <code>16</code>, <code>32</code>, and <code>64</code>.<br>
Valid values for floating point data are
<code>32</code> and <code>64</code>.<br>
Optional argument: if not specified,
the default value is <code>32</code>.
<dt><code>-c <em>config_file</em></code>
<dd><code><em>config_file</em></code> specifies a
configuration file.<br>
This argument replaces all other arguments except
<code><em>infile</em></code> and
<code>-o <em>outfile</em></code>
</dl>
<dt><code>outfile</code>
<dd>Name of the HDF5 output file.
</dl>
<dt><strong>Examples:</strong>
<dd><b>Using command-line arguments:</b>
<table width=100% border=0>
<tr><td colspan=2>
<code>h5import infile -dims 2,3,4 -type TEXTIN -size 32 -o out1</code>
</td></tr><tr><td> </td><td>
This command creates a file <code>out1</code> containing
a single 2x3x4 32-bit integer dataset.
Since no pathname is specified, the dataset is stored
in <code>out1</code> as <code>/dataset1</code>.
</td></tr><tr><td colspan=2>
<code>h5import infile -dims 20,50 -path bin1/dset1 -type FP -size 64 -o out2</code>
</td></tr><tr><td> </td><td>
This command creates a file <code>out2</code> containing
a single a 20x50 64-bit floating point dataset.
The dataset is stored in <code>out2</code> as <code>/bin1/dset1</code>.
</td></tr>
</table>
<dd><b>Sample configuration files:</b><br>
The following configuration file specifies the following:<br>
– The input data is a 5x2x4 floating point array in
an ASCII file.<br>
– The output dataset will be saved in chunked layout,
with chunk dimension sizes of 2x2x2.<br>
– The output datatype will be 64-bit floating point,
little-endian, IEEE.<br>
– The output dataset will be stored in
<code><em>outfile</em></code>
at <code>/work/h5/pkamat/First-set</code>.<br>
– The maximum dimension sizes of the output dataset
will be 8x8x(unlimited).
<pre>
PATH work/h5/pkamat/First-set
INPUT-CLASS TEXTFP
RANK 3
DIMENSION-SIZES 5 2 4
OUTPUT-CLASS FP
OUTPUT-SIZE 64
OUTPUT-ARCHITECTURE IEEE
OUTPUT-BYTE-ORDER LE
CHUNKED-DIMENSION-SIZES 2 2 2
MAXIMUM-DIMENSIONS 8 8 -1
</pre>
The next configuration file specifies the following:<br>
– The input data is a 6x3x5x2x4 integer array in
a binary file.<br>
– The output dataset will be saved in chunked layout,
with chunk dimension sizes of 2x2x2x2x2.<br>
– The output datatype will be 32-bit integer in
<code>NATIVE</code> format
(as the output architecure is not specified).<br>
– The output dataset will be compressed using Gzip compression
with a compression level of 7.<br>
– The output dataset will be stored in
<code><em>outfile</em></code> at <code>/Second-set</code>.
<pre>
PATH Second-set
INPUT-CLASS IN
RANK 5
DIMENSION-SIZES 6 3 5 2 4
OUTPUT-CLASS IN
OUTPUT-SIZE 32
CHUNKED-DIMENSION-SIZES 2 2 2 2 2
COMPRESSION-TYPE GZIP
COMPRESSION-PARAM 7
</pre>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-GIF2H5">gif2h5</a>
<dt><strong>Syntax:</strong>
<dd><code>gif2h5</code>
<em>gif_file</em> <em>h5_file</em>
<dt><strong>Purpose:</strong>
<dd>Converts a GIF file to an HDF5 file.
<dt><strong>Description:</strong>
<dd><code>gif2h5</code> accepts as input the GIF file <em>gif_file</em>
and produces the HDF5 file <em>h5_file</em> as output.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><em>gif_file</em>
<dd>The name of the input GIF file
<dt><em>h5_file</em>
<dd>The name of the output HDF5 file
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H52GIF">h52gif</a>
<dt><strong>Syntax:</strong>
<dd><code>h52gif</code>
<em>h5_file</em> <em>gif_file</em>
<code>-i</code> <em>h5_image</em>
<code>[-p</code> <em>h5_palette</em><code>]</code>
<dt><strong>Purpose:</strong>
<dd>Converts an HDF5 file to a GIF file.
<dt><strong>Description:</strong>
<dd><code>h52gif</code> accepts as input the HDF5 file <em>h5_file</em>
and the names of images and associated palettes within that file
as input and produces the GIF file <em>gif_file</em>,
containing those images, as output.
<p>
<code>h52gif</code> expects <em>at least</em>
one <em>h5_image</em>.
You may repeat
<br>
<code>-i</code> <em>h5_image</em>
<code>[-p</code> <em>h5_palette</em><code>]</code>
<br>
up to 50 times, for a maximum of 50 images.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><em>h5_file</em>
<dd>The name of the input HDF5 file
<dt><em>gif_file</em>
<dd>The name of the output GIF file
<dt><code>-i</code> <em>h5_image</em>
<dd>Image option, specifying the name of an HDF5 image or
dataset containing an image to be converted
<dt><code>-p</code> <em>h5_palette</em>
<dd>Palette option, specifying the name of an HDF5 dataset
containing a palette to be used in an image conversion
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H5toh4">h5toh4</a>
<dt><strong>Syntax:</strong>
<dd><code>h5toh4 -h</code><br>
<code>h5toh4 </code><em>
h5file
h4file</em><br>
<code>h5toh4 </code><em>
h5file</em><br>
<code>h5toh4 -m </code><em>
h5file1
h5file2
h5file3</em> ...
<dt><strong>Purpose:</strong>
<dd>Converts an HDF5 file into an HDF4 file.
<dt><strong>Description:</strong>
<dd><code>h5toh4</code> is an HDF5 utility which reads
an HDF5 file, <em>h5file</em>, and converts all
supported objects and pathways to produce an HDF4 file,
<em>h4file</em>. If <em>h4file</em> already exists,
it will be replaced.
<p>
If only one file name is given, the name must end in
<code>.h5</code> and is assumed to represent the
HDF5 input file. <code>h5toh4</code> replaces the
<code>.h5</code> suffix with <code>.hdf</code> to form
the name of the resulting HDF4 file and proceeds as above.
If a file with the name of the intended HDF4 file already
exists, <code>h5toh4</code> exits with an error without
changing the contents of any file.
<p>
The <code>-m</code> option allows multiple HDF5 file
arguments. Each file name is treated the same as the
single file name case above.
<p>
The <code>-h</code> option causes the following
syntax summary to be displayed:
<pre> h5toh4 file.h5 file.hdf
h5toh4 file.h5
h5toh4 -m file1.h5 file2.h5 ...</pre>
<p>
The following HDF5 objects occurring in an HDF5 file are
converted to HDF4 objects in the HDF4 file:
<ul>
<li>HDF5 group objects are converted into HDF4 Vgroup
objects. HDF5 hardlinks and softlinks pointing to
objects are converted to HDF4 Vgroup references.
<li>HDF5 dataset objects of integer datatype are
converted into HDF4 SDS objects. These datasets
may have up to 32 fixed dimensions.
The slowest varying dimension may be extendable.
8-bit, 16-bit, and 32-bit integer datatypes are
supported.
<li>HDF5 dataset objects of floating point datatype
are converted into HDF4 SDS objects.
These datasets may have up to 32 fixed dimensions.
The slowest varying dimension may be extendable.
32-bit and 64-bit floating point datatypes are
supported.
<li>HDF5 dataset objects of single dimension and
compound datatype are converted into HDF4 Vdata
objects. The length of that single dimension may
be fixed or extendable. The members of the
compound datatype are constrained to be no more
than rank 4.
<li>HDF5 dataset objects of single dimension and fixed length string
datatype are converted into HDF4 Vdata objects. The HDF4 Vdata
is a single field whose order is the length of the HDF5 string
type. The number of records of the Vdata is the length of the
single dimension which may be fixed or extendable.
</ul>
Other objects are not converted and are not recorded
in the resulting <em>h4file</em>.
<p>
Attributes associated with any of the supported HDF5
objects are carried over to the HDF4 objects.
Attributes may be of integer, floating point, or fixed length
string datatype and they may have up to 32 fixed dimensions.
<p>
All datatypes are converted to big-endian.
Floating point datatypes are converted to IEEE format.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-h</code>
<dd>Displays a syntax summary.
<dt><code>-m</code>
<dd>Converts multiple HDF5 files to multiple HDF4 files.
<dt><em>h5file</em>
<dd>The HDF5 file to be converted.
<dt><em>h4file</em>
<dd>The HDF4 file to be created.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H4toh5">h4toh5</a>
<dt><strong>Syntax:</strong>
<dd><code>h4toh5 -h</code><br>
<code>h4toh5 </code><em>
h4file
h5file</em><br>
<code>h4toh5 </code><em>
h4file</em><br>
<!-- currently no -m option
<code>h4toh5 -m </code><em>
h4file1
h4file2
h4file3</em> ...
-->
<dt><strong>Purpose:</strong>
<dd>Converts an HDF4 file to an HDF5 file.
<dt><strong>Description:</strong>
<dd><code>h4toh5</code> is a file conversion utility that reads
an HDF4 file, <em>h4file</em> (<code>input.hdf</code> for example),
and writes an HDF5 file, <em>h5file</em> (<code>output.h5</code>
for example), containing the same data.
<p>
If no output file <em>h5file</em> is specified,
<code>h4toh5</code> uses the input filename to designate
the output file, replacing the extension <code>.hdf</code>
with <code>.h5</code>.
For example, if the input file <code>scheme3.hdf</code> is
specified with no output filename, <code>h4toh5</code> will
name the output file <code>scheme3.h5</code>.
<p>
<!-- currently no -m option
The <code>-m</code> option allows multiple HDF5 file
arguments. Each file name is treated the same as the
single file name case above.
<p>
-->
The <code>-h</code> option causes a syntax summary
similar to the following to be displayed:
<pre> h4toh5 inputfile.hdf outputfile.h5
h5toh4 inputfile.hdf <!-- currently no -m option
h5toh4 -m inputfile1.hdf inputfile2.hdf ... --> </pre>
<p>
Each object in the HDF4 file is converted to an equivalent
HDF5 object, according to the mapping described in
<a href="ADGuide/H4toH5Mapping.pdf" target=ExternalWinA>
<cite>Mapping HDF4 Objects to HDF5 Objects</cite></a>.
(If this mapping changes between HDF5 Library releases, a more up-to-date
version may be available at
<a href="http://hdf.ncsa.uiuc.edu/HDF5/papers/h4toh5/H4-to-H5MappingGuidelines.pdf" target=ExternalWinB>
<cite>Mapping HDF4 Objects to HDF5 Objects</cite> on the HDF FTP server</a>.)
<p>
In this inital version, <code>h4toh5</code> converts the following
HDF4 objects:
<center>
<table width=75% border=0>
<tr><th width=40% valign=top align=left>
HDF4 Object
</td><th width=60% valign=top align=left>
Resulting HDF5 Object
</td></tr>
<tr><td width=40% valign=top align=left>
SDS
</td><td width=60% valign=top align=left>
Dataset
</td></tr>
<tr><td width=40% valign=top align=left>
GR, RI8, and RI24 image
</td><td width=60% valign=top align=left>
Dataset
</td></tr>
<tr><td width=40% valign=top align=left>
Vdata
</td><td width=60% valign=top align=left>
Dataset
</td></tr>
<tr><td width=40% valign=top align=left>
Vgroup
</td><td width=60% valign=top align=left>
Group
</td></tr>
<tr><td width=40% valign=top align=left>
Annotation
</td><td width=60% valign=top align=left>
Attribute
</td></tr>
<tr><td width=40% valign=top align=left>
Palette
</td><td width=60% valign=top align=left>
Dataset
</td></tr>
</table>
</center>
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-h</code>
<dd>Displays a syntax summary.
<!-- currently no -m option
<dt><code>-m</code>
<dd>Converts multiple HDF4 files to multiple HDF5 files.
-->
<dt><em>h4file</em>
<dd>The HDF4 file to be converted.
<dt><em>h5file</em>
<dd>The HDF5 file to be created.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Perf">h5perf</a>
<dt><strong>Syntax:</strong>
<dd><code>h5perf </code>[<code>-h </code>|<code> --help</code>]
<dd><code>h5perf </code>[<em>options</em>]
<!--
[<code>-a</code> <em>size</em> | <code>--align=</code><em>size</em>]
[<code>-A</code> <em>api_list</em> | <code>--api=</code><em>api_list</em>]
[<code>-B</code> <em>size</em> | <code>--block-size=</code><em>size</em>]
[<code>-c</code> | <code>--chunk</code>]
[<code>-C</code> | <code>--collective</code>]
[<code>-d</code> <em>N</em> | <code>--num-dsets</code><em>N</em>]
[<code>-D</code> <em>debug_flags</em> | <code>--debug=</code><em>debug_flags</em>]
[<code>-e</code> <em>size</em> | <code>--num-bytes=</code><em>size</em>]
[<code>-F</code> <em>N</em> | <code>--num-files=</code><em>N</em>]
[<code>-i</code> <em>N</em> | <code>--num-iterations=</code><em>N</em>]
[<code>-I</code> | <code>--interleaved</code>]
[<code>-m</code> | <code>--mpi-posix</code>]
[<code>-n</code> | <code>--no-fill</code>]
[<code>-o</code> <em>file</em> | <code> --output=</code><em>file</em>]
[<code>-p</code> <em>N</em> | <code>--min-num-processes=</code><em>N</em>]
[<code>-P</code> <em>N</em> | <code>--max-num-processes=</code><em>N</em>]
[<code>-T</code> <em>size</em> | <code>--threshold=</code><em>size</em>]
[<code>-w</code> | <code>--write-only</code>]
[<code>-x</code> <em>size</em> | <code>--min-xfer-size=</code><em>size</em>]
[<code>-X</code> <em>size</em> | <code>--max-xfer-size=</code>size<em></em>]
-->
<dt><strong>Purpose:</strong>
<dd>Tests Parallel HDF5 performance.
<dt><strong>Description:</strong>
<dd><code>h5perf</code> provides tools for testing the performance
of the Parallel HDF5 library.
<p>
The following environment variables have the following
effects on <code>H5perf</code> behavior:
<table border=0>
<tr align="left" valign="top"><td> </td><td>
<code>HDF5_NOCLEANUP</code></td><td>
If set, <code>h5perf</code> does not remove data files.
(Default: Remove)</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>HDF5_MPI_INFO</code></td><td>
Must be set to a string containing a list of semi-colon separated
key=value pairs for the MPI <code>INFO</code> object.<br>
Example:</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>HDF5_PARAPREFIX </code></td><td>
Sets the prefix for paralllel output data files.</td></tr>
</table>
<dt><strong>Options and Parameters:</strong>
<dl>
<dt>These terms are used as follows in this section:
<table border="0">
<tr align="left" valign="top"><td> </td><td>
<em>file </em></td><td>
A filename</td></tr>
<tr align="left" valign="top"><td> </td><td>
<em>size</em></td><td>
A size specifier, expressed as an integer greater than or equal
to 0 (zero) followed by a size indicator:<br>
<code>K </code> for kilobytes (1024 bytes)<br>
<code>M </code> for megabytes (1048576 bytes)<br>
<code>G </code> for gigabytes (1073741824 bytes)<br>
Example: <code>37M</code> specifies 37 megabytes or 38797312 bytes.</td></tr>
<tr align="left" valign="top"><td> </td><td>
<em>N</em></td><td>
An integer greater than or equal to 0 (zero)</td></tr>
</table>
<p>
<dt><code>-h</code>, <code>--help</code>
<dd>Prints a usage message and exits.
<dt><code>-a</code> <em>size</em>, <code>--align=</code><em>size</em>
<dd>Specifies the alignment of objects in the HDF5 file.
(Default: 1)
<dt><code>-A</code> <em>api_list</em>, <code>--api=</code><em>api_list</em>
<dd>Specifies which APIs to test.
<em>api_list</em> is a comma-separated list with the
following valid values:
<table border="0">
<tr align="left" valign="top"><td> </td><td>
<code>phdf5 </code></td><td>Parallel HDF5</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>mpiio</code></td><td>MPI-I/O</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>posix</code></td><td>POSIX</td></tr>
</table>
(Default: All APIs)<br><br>
Example, <code>--api=mpiio,phdf5</code> specifies that the
MPI I/O and parallel HDf5 APIs are to be monitored.<br><br>
<dt><code>-B</code> <em>size</em>, <code>--block-size=</code><em>size</em>
<dd>Specifies the block size within the transfer buffer.
(Default: 128K)<br><br>
Block size versus transfer buffer size:
The <em>transfer buffer size</em> is the size of a
buffer in memory. The data in that buffer is broken
into <em>block size</em> pieces and written to the
file.<br><br>
Transfer block size is set by the
<code>-x</code> (or <code>--min-xfer-size</code>) and
<code>-X</code> (or <code>--max-xfer-size</code>)
options.<br>
The pattern in which the blocks
are written to the file is described in the discussion
of the <code>-I</code> (or <code>--interleaved</code>)
option.<br><br>
<dt><code>-c</code>, <code>--chunk</code>
<dd>Creates HDF5 datasets in chunked layout.
(Default: Off)
<dt><code>-C</code>, <code>--collective</code>
<dd>Use collective I/O for the MPI I/O and Parallel HDF5 APIs.<br>
(Default: Off, i.e., independent I/O)<br><br>
If this option is set and the MPI-I/O and PHDF5 APIs
are in use, all the blocks in each transfer buffer
will be written at once with an MPI derived type.
<br><br>
<dt><code>-d</code> <em>N</em>, <code>--num-dsets</code><em>N</em>
<dd>Sets the number of datasets per file.
(Default: <code>1</code>)
<dt><code>-D</code> <em>debug_flags</em>, <code>--debug=</code><em>debug_flags</em>
<dd>Sets the debugging level.
<em>debug_flags</em> is a comma-separated list of
debugging flags with the following valid values:
<table border="0">
<tr align="left" valign="top"><td> </td><td>
<code>1 </code></td><td>Minimal debugging</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>2</code></td><td>Moderate debugging (“not quite everything”)</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>3</code></td><td>Extensive debugging (“everything”)</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>4</code></td><td>All possible debugging (“the kitchen sink”)</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>r</code></td><td>Raw data I/O throughput information</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>t</code></td><td>Times, in additions to throughputs</td></tr>
<tr align="left" valign="top"><td> </td><td>
<code>v</code></td><td>Verify data correctness</td></tr>
</table>
(Default: No debugging)<br><br>
Example: <code>--debug=2,r,t</code> specifies to
run a moderate level of debugging
while collecting raw data I/O throughput information
and verifying the correctness of the data.<br><br>
<dt><code>-e</code> <em>size</em>, <code>--num-bytes=</code><em>size</em>
<dd>Specifies the number of bytes per process per dataset.
(Default: <code>256K</code>)
<dt><code>-F</code> <em>N</em>, <code>--num-files=</code><em>N</em>
<dd>Specifies the number of files.
(Default: <code>1</code>)
<dt><code>-i</code> <em>N</em>, <code>--num-iterations=</code><em>N</em>
<dd>Sets the number of iterations to perform.
(Default: <code>1</code>)
<dt><code>-I</code>, <code>--interleaved</code>
<dd>Sets interleaved block I/O.<br>
(Default: Contiguous block I/O)<br><br>
Interleaved vs. Contiguous blocks
in a parallel environment:<br>
When contiguous blocks are written to a dataset,
the dataset is divided into <em>m</em> regions,
where <em>m</em> is the number of processes writing
separate portions of the dataset. Each process
then writes data to its own region.
When interleaved blocks are written to a dataset,
space for the first block of the first process is
allocated in the dataset, then space is allocated
for the first block of the second process, etc.,
until space has been allocated for the first block
of each process. Space is then allocated for
the second block of the first process,
the second block of the second process, etc.<br><br>
For example, in the case of a 4 process run
with 1M bytes-per-process, 256K transfer buffer size,
and 64KB block size, 16 <em>contiguous</em> blocks
per process would be written to the file in the
manner<br>
<code> 1111111111111111222222222222222233333333333333334444444444444444</code><br>
while 16 interleaved blocks per process would be
written to the file as
<code> 1234123412341234123412341234123412341234123412341234123412341234</code><br>
If collective I/O is turned on, all of the four
blocks per transfer buffer will be written in
one collective I/O call.<br><br>
<dt><code>-m</code>, <code>--mpi-posix</code>
<dd>Sets use of MPI-posix driver for HDF5 I/O.
(Default: MPI-I/O driver)
<dt><code>-n</code>, <code>--no-fill</code>
<dd>Specifies to not write fill values to HDF5 datasets.
This option is supported only in HDF5 Release v1.6 or later.<br>
(Default: Off, i.e., write fill values)
<dt><code>-o</code> <em>file</em>, <code> --output=</code><em>file</em>
<dd>Sets the output file for raw data to <em>file</em>.
(Default: None)
<dt><code>-p</code> <em>N</em>, <code>--min-num-processes=</code><em>N</em>
<dd>Sets the minimum number of processes to be used.
(Default: <code>1</code>)
<dt><code>-P</code> <em>N</em>, <code>--max-num-processes=</code><em>N</em>
<dd>Sets the maximum number of processes to be used.<br>
(Default: All <code>MPI_COMM_WORLD</code>processes)
<dt><code>-T</code> <em>size</em>, <code>--threshold=</code><em>size</em>
<dd>Sets the threshold for alignment of objects in the HDF5 file.
(Default: <code>1</code>)
<dt><code>-w</code>, <code>--write-only</code>
<dd>Performs only write tests, not read tests.
(Default: Read and write tests)
<dt><code>-x</code> <em>size</em>, <code>--min-xfer-size=</code><em>size</em>
<dd>Sets the minimum transfer buffer size.
(Default: <code>128K</code>)
<dt><code>-X</code> <em>size</em>, <code>--max-xfer-size=</code>size<em></em>
<dd>Sets the maximum transfer buffer size.
(Default: <code>1M</code>)
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-Redeploy">h5redeploy</a>
<dt><strong>Syntax:</strong>
<dd><code>h5redeploy </code>
[<code>help </code> | <code>-help</code>]
<dd><code>h5redeploy </code>
[<code>-echo</code>]
[<code>-force</code>]
[<code>-prefix=</code><em>dir</em>]
[<code>-tool=</code><em>tool</em>]
[<code>-show</code>]
<dt><strong>Purpose:</strong>
<dd>Updates HDF5 compiler tools after an HDF5 software installation
in a new location.
<dt><strong>Description:</strong>
<dd><code>h5redeploy</code> updates the HDF5 compiler tools after
the HDF5 software has been installed in a new location.
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>help</code>, <code>-help</code>
<dd>Prints a help message.
<dt><code>-echo</code>
<dd>Shows all the shell commands executed.
<dt><code>-force</code>
<dd>Performs the requested action without offerring any prompt
requesting confirmation.
<dt><code>-prefix=</code><em>dir</em>
<dd>Specifies a new directory in which to find the
HDF5 subdirectories <code>lib/</code> and
<code>include/</code>.<br>
(Default: current working directory)
<dt><code>-tool=</code><em>tool</em>
<dd>Specifies the tool to update.
<em>tool</em> must be in the current directory
and must be writable.<br>
(Default: <code>h5cc</code>)
<dt><code>-show</code>
<dd>Shows all of the shell commands to be executed
without actually executing them.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H5CC">h5cc</a>
<dt><strong>Syntax:</strong>
<dd><code>h5cc
[</code><em>OPTIONS</em><code>]</code> <em><compile line></em>
<dt><strong>Purpose:</strong>
<dd>Helper script to compile HDF5 applications.
<dt><strong>Description:</strong>
<dd><code>h5cc</code> can be used in much the same way MPIch is used
to compile an HDF5 program. It takes care of specifying where the
HDF5 header files and libraries are on the command line.
<p>
<code>h5cc</code> supercedes all other compiler scripts in that
if you've used them to compile the HDF5 library, then
<code>h5cc</code> also uses those scripts. For example, when
compiling an MPIch program, you use the <code>mpicc</code>
script. If you've built HDF5 using MPIch, then <code>h5cc</code>
uses the MPIch program for compilation.
<p>
Some programs use HDF5 in only a few modules. It isn't necessary
to use <code>h5cc</code> to compile those modules which don't use
HDF5. In fact, since <code>h5cc</code> is only a convenience
script, you are still able to compile HDF5 modules in the normal
way. In that case, you will have to specify the HDF5 libraries
and include paths yourself.
<p>
An example of how to use <code>h5cc</code> to compile the program
<code>hdf_prog</code>, which consists of modules
<code>prog1.c</code> and <code>prog2.c</code> and uses the HDF5
shared library, would be as follows:
<pre>
# h5cc -c prog1.c
# h5cc -c prog2.c
# h5cc -shlib -o hdf_prog prog1.o prog2.o
</pre>
<dt><strong>Options and Parameters:</strong>
<dd>
<dl>
<dt><code>-help</code>
<dd>Prints a help message.
<dt><code>-echo</code>
<dd>Show all the shell commands executed.
<dt><code>-prefix=DIR</code>
<dd>Use the directory <code><em>DIR</em></code> to find the HDF5
<code>lib/</code> and <code>include/</code> subdirectories.
<br>
Default: prefix specified when configuring HDF5.
<dt><code>-show</code>
<dd>Show the commands without executing them.
<dt><code>-shlib</code>
<dd>Compile using shared HDF5 libraries.
<dt><code>-noshlib</code>
<dd>Compile using static HDF5 libraries [default].
<dt><em><compile line></em>
<dd>The normal compile line options for your compiler.
<code>h5cc</code> uses the same compiler you used to compile HDF5.
Check your compiler's manual for more information on which
options are needed.
</dl>
<dt><strong>Environment Variables:</strong>
<dd>When set, these environment variables override some of the built-in
defaults of <code>h5cc</code>.
<dl>
<dt><code>HDF5_CC</code>
<dd>Use a different C compiler.
<dt><code>HDF5_CLINKER</code>
<dd>Use a different linker.
<dt><code>HDF5_USE_SHLIB=[yes|no]</code>
<dd>Use shared version of the HDF5 library [default: no].
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H5FC">h5fc</a>
<dt><strong>Syntax:</strong>
<dd><code>h5fc
[</code><em>OPTIONS</em><code>]</code> <em><compile line></em>
<dt><strong>Purpose:</strong>
<dd>Helper script to compile HDF5 Fortran90 applications.
<dt><strong>Description:</strong>
<dd><p>
<code>h5fc</code> can be used in much the same way MPIch is used
to compile an HDF5 program. It takes care of specifying where the
HDF5 header files and libraries are on the command line.
<p>
<code>h5fc</code> supercedes all other compiler scripts in that
if you've used them to compile the HDF5 Fortran library, then
<code>h5fc</code> also uses those scripts. For example, when
compiling an MPIch program, you use the <code>mpif90</code>
script. If you've built HDF5 using MPIch, then <code>h5fc</code>
uses the MPIch program for compilation.
<p>
Some programs use HDF5 in only a few modules. It isn't necessary
to use <code>h5fc</code> to compile those modules which don't use
HDF5. In fact, since <code>h5fc</code> is only a convenience
script, you are still able to compile HDF5 Fortran modules in the
normal way. In that case, you will have to specify the HDF5 libraries
and include paths yourself.
<p>
An example of how to use <code>h5fc</code> to compile the program
<code>hdf_prog</code>, which consists of modules
<code>prog1.f90</code> and <code>prog2.f90</code>
and uses the HDF5 Fortran library, would be as follows:
<pre>
# h5fc -c prog1.f90
# h5fc -c prog2.f90
# h5fc -o hdf_prog prog1.o prog2.o
</pre>
<dt><strong>Options and Parameters:</strong>
<dd>
<dl>
<dt><code>-help</code>
<dd>Prints a help message.
<dt><code>-echo</code>
<dd>Show all the shell commands executed.
<dt><code>-prefix=DIR</code>
<dd>Use the directory <code>DIR</code> to find HDF5
<code>lib/</code> and <code>include/</code> subdirectories
<br>
Default: prefix specified when configuring HDF5.
<dt><code>-show</code>
<dd>Show the commands without executing them.
<dt><em><compile line></em>
<dd>The normal compile line options for your compiler.
<code>h5fc</code> uses the same compiler you used
to compile HDF5. Check your compiler's manual for
more information on which options are needed.
</dl>
<dt><strong>Environment Variables:</strong>
<dd>When set, these environment variables override some of the built-in
defaults of <code>h5cc</code>.
<dl>
<dt><code>HDF5_FC</code>
<dd>Use a different Fortran90 compiler.
<dt><code>HDF5_FLINKER</code>
<dd>Use a different linker.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H5C++">h5c++</a>
<dt><strong>Syntax:</strong>
<dd><code>h5c++
[</code><em>OPTIONS</em><code>]</code> <em><compile line></em>
<dt><strong>Purpose:</strong>
<dd>Helper script to compile HDF5 C++ applications.
<dt><strong>Description:</strong>
<dd><p>
<code>h5c++</code> can be used in much the same way MPIch is used
to compile an HDF5 program. It takes care of specifying where the
HDF5 header files and libraries are on the command line.
<p>
<code>h5c++</code> supercedes all other compiler scripts in that
if you've used one set of compiler scripts to compile the
HDF5 C++ library, then <code>h5c++</code> uses those same scripts.
For example, when compiling an MPIch program,
you use the <code>mpiCC</code> script.
<p>
Some programs use HDF5 in only a few modules. It isn't necessary
to use <code>h5c++</code> to compile those modules which don't use
HDF5. In fact, since <code>h5c++</code> is only a convenience
script, you are still able to compile HDF5 C++ modules in the
normal way. In that case, you will have to specify the HDF5 libraries
and include paths yourself.
<p>
An example of how to use <code>h5c++</code> to compile the program
<code>hdf_prog</code>, which consists of modules
<code>prog1.cpp</code> and <code>prog2.cpp</code>
and uses the HDF5 C++ library, would be as follows:
<pre>
# h5c++ -c prog1.cpp
# h5c++ -c prog2.cpp
# h5c++ -o hdf_prog prog1.o prog2.o</pre>
<dt><strong>Options and Parameters:</strong>
<dd>
<dl>
<dt><code>-help</code>
<dd>Prints a help message.
<dt><code>-echo</code>
<dd>Show all the shell commands executed.
<dt><code>-prefix=DIR</code>
<dd>Use the directory <code>DIR</code> to find HDF5
<code>lib/</code> and <code>include/</code> subdirectories
<br>
Default: prefix specified when configuring HDF5.
<dt><code>-show</code>
<dd>Show the commands without executing them.
<dt><em><compile line></em>
<dd>The normal compile line options for your compiler.
<code>h5c++</code> uses the same compiler you used
to compile HDF5. Check your compiler's manual for
more information on which options are needed.
</dl>
<dt><strong>Environment Variables:</strong>
<dd>When set, these environment variables override some of the built-in
defaults of <code>h5c++</code>.
<dl>
<dt><code>HDF5_CXX</code>
<dd>Use a different C++ compiler.
<dt><code>HDF5_CXXLINKER</code>
<dd>Use a different linker.
</dl>
<!--
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
-->
</dl>
<!-- Template, next 40 lines -->
<!-- Template, next 40 lines -->
<!-- Template, next 40 lines
<hr>
<dl>
<dt><strong>Tool Name:</strong> <a name="Tools-H5toh4">h5toh4</a>
<dt><strong>Syntax:</strong>
<dd><code>h5toh4 -h</code><br>
<code>h5toh4 </code><em>
h5file
h4file</em><br>
<code>h5toh4 </code><em>
h5file</em><br>
<code>h5toh4 -m </code><em>
h5file1
h5file2
h5file3</em> ...
<dt><strong>Purpose:</strong>
<dd>Purpose...
<dt><strong>Description:</strong>
<dd><code>TOOL</code> is an HDF5 utility which ...
Paragraph
<pre> sample code
sample code
sample code </pre>
<p>
Paragraph
<p>
Paragraph
<dt><strong>Options and Parameters:</strong>
<dl>
<dt><code>-option</code>
<dd>Description
<dt><em>parameter</em>
<dd>Description
</dl>
<dt><strong>Current Status:</strong>
<dd>
<dt><strong>See Also:</strong>
<dd>
</dl>
-->
<!-- #BeginLibraryItem "/ed_libs/NavBar_RM.lbi" --><hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
<a href="index.html">HDF5 documents and links</a> <br>
<a href="H5.intro.html">Introduction to HDF5</a> <br>
<a href="H5.user.html">HDF5 User Guide</a> <br>
<!--
<a href="Glossary.html">Glossary</a><br>
-->
</td>
<td valign=top align=right>
And in this document, the
<a href="RM_H5Front.html">HDF5 Reference Manual</a>
<br>
<a href="RM_H5.html">H5</a>
<a href="RM_H5A.html">H5A</a>
<a href="RM_H5D.html">H5D</a>
<a href="RM_H5E.html">H5E</a>
<a href="RM_H5F.html">H5F</a>
<a href="RM_H5G.html">H5G</a>
<a href="RM_H5I.html">H5I</a>
<a href="RM_H5P.html">H5P</a>
<br>
<a href="RM_H5R.html">H5R</a>
<a href="RM_H5S.html">H5S</a>
<a href="RM_H5T.html">H5T</a>
<a href="RM_H5Z.html">H5Z</a>
<a href="Tools.html">Tools</a>
<a href="PredefDTypes.html">Datatypes</a>
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><!-- #BeginLibraryItem "/ed_libs/Footer.lbi" --><address>
<a href="mailto:hdfhelp@ncsa.uiuc.edu">HDF Help Desk</a>
<br>
Describes HDF5 Release 1.6.0, July 2003
</address><!-- #EndLibraryItem -->
Last modified: 11 June 2003
</body>
</html>
|
