hdf5/INSTALL.ascired
Paul Harten 1bdb53fb6a [svn-r461] Purpose:
The purpose of the change is to correct the H5 filenames declared in
    testphdf5.c when used on the Intel TFLOP PFS system.

Problem:
    The ROMIO library complains of the H5 filenames having no "piofs:",
    "pfs:", "ufs:", or "nfs:" prefixes on the filenames.  The only type
    currently recognized are the "pfs:" prefixes, and the files must
    reside in the Intel TFLOP PFS system: /pfs.

Solution: (REQUIRED)
    The compile flag -DPOOMA_ARCH=TFLOP is added to the list of CFLAGS in
    Makefile.ascired located in the parallel test directory.  This compile
    flag will allow a special set of filenames to be used when compiling
    testphdf5.c on the Intel TFLOP.  In addition, instructions to editing
    the filenames in testphdf5.c to reside in the user's own /pfs directory
    are included in INSTALL.ascired.

Platform tested:
    Intel TFLOP
1998-07-07 16:09:07 -05:00

141 lines
3.0 KiB
Plaintext

FOR THE INTEL TFLOPS MACHINE:
Below are the step-by-step procedures for building, testing, and
installing both the sequential and parallel versions of the HDF5 library.
---------------
Sequential HDF5:
---------------
The setup process for building the sequential HDF5 library for the
ASCI Red machine is done by a coordination of events from sasn100 and
janus. Special effort must be made to move the compiled and linked
testers to disks local to the processors for execution. This special
effort is shown here at steps 9) and steps 10).
The total required steps are something similar to:
FROM SASN100,
1) uncompress hdf5-1.0.0a.tar.Z
2) tar xvf hdf5-1.0.0a.tar
3) cd ./hdf5
4) ./configure tflop
5) make H5detect
FROM JANUS,
6) cd ./hdf5
7) make H5Tinit.c
FROM SASN100,
8) make >&! comp.out &
When everything is finished compiling and linking,
FROM JANUS,
9) cp -r ../hdf5 /scratch
10) cd /scratch/hdf5/test
11) make test >&! test.out
Once satisfied with the test results, as long as you
have the correct permission,
FROM SASN100,
12) make install
---------------
Parallel HDF5:
---------------
The setup process for building the parallel version of the HDF5 library for the
ASCI Red machine is very similar to the sequential version. It is done by a
coordination of events from sasn100 and janus. Special effort must be made to
move the compiled and linked single processor testers to disks local to the
processor for execution. This special effort is shown here at steps 9) and
steps 10). Following these test, there are the edit, compile, link, and
execution of parallel tests described in steps 12) through 16).
The total required steps are something similar to:
FROM SASN100,
1) uncompress hdf5-1.0.0a.tar.Z
2) tar xvf hdf5-1.0.0a.tar
3) cd ./hdf5
4) sh INSTALL_parallel.ascired /* this is different from the sequential version */
5) make H5detect
FROM JANUS,
6) cd ./hdf5
7) make H5Tinit.c
FROM SASN100,
8) make >&! comp.out &
When everything is finished compiling and linking,
FROM JANUS,
9) cp -rp ../hdf5 /scratch
10) cd /scratch/hdf5/test
11) make test >&! test.out
Once satisfied with the single processor test results,
FROM SASN100,
12) cd testpar
13) /* edit testphdf5.c, change the following lines */
char *filenames[]={ "pfs:/pfs/multi/tmp_1/your_own/ParaEg1.h5f",
"pfs:/pfs/multi/tmp_1/your_own/ParaEg2.h5f",
"pfs:/pfs/multi/tmp_1/your_own/ParaEg3.h5f" };
/* change "your_own" to your own directory name */
char *filenames[]={ "pfs:/pfs/multi/tmp_1/my_dir/ParaEg1.h5f",
"pfs:/pfs/multi/tmp_1/my_dir/ParaEg2.h5f",
"pfs:/pfs/multi/tmp_1/my_dir/ParaEg3.h5f" };
14) make -f Makefile.ascired
When everything is finished compiling and linking,
FROM JANUS,
15) cd ./hdf5/testpar
16) make test -f Makefile.ascired >&! test.out
Once satisfied with the parallel test results, as long as you
have the correct permission,
FROM SASN100,
17) make install