The frame to ILWD script tests the time it takes to convert the data in a frame file to ILWD format. It measures and records the time for each of the individual steps necessary for the conversion. By default, the script repeats the test on 100 frame files and reports the statistics. The statistics are written to a file in a directory identified by the current date. A separate script compares the current statistics with those reported from a previous test and reports the statistics of their differences. By default, the script performs the test on both frame files located on a network mounted file system and on frame files on a local file system.
Choose a directory to install the tests scripts. The required files are:
frame2ilwd.tcl
framestats.tcl
Frame files are required to perform the test. At the very least, one sample frame file can be provided, and the script will create the necessary number of copies. For the NFS tests, a directory that is NFS mounted is necessary. For the local tests, a local mounted directory is required. The script checks whether the frames directory is NFS or locally mounted and will complain if it is not. The algorithm used for this is not perfect, so it is possible to receive an error incorrectly.
Note: At all the sites, the required script files are installed at /ldas_usr/ldas/test/frame. A new sample frame file can be created by copying a frame file from any of the DataN subdirectories in /imports/frames. Results from previous test runs may exist in results-MMDD directories, and can be used for comparison purposes.
frame2ilwd.tcl [options]
| Option | Description |
|---|---|
-auto_path <path>
| add <path> to Tcl auto_path variable |
-nfsframes <dir>
| location of NFS mounted directory of frame files (default: /imports/frames/Data0) |
-locframes <dir>
| location of local mounted directory of frame files (default: ./frames/Data0) |
-sample <file>
| location of sample frame file (default: ./sample_frame) |
-numfiles <value>
| number of frame files to read (default: 100) |
-createnfs
| create frame files in NFS mounted directory from sample frame file |
-createloc
| create frame files in local mounted directory from sample frame file |
-noclean
| do not clean up any created frame files |
-nonfs
| do not perform tests on NFS mounted frame files |
-nolocal
| do not perform tests on local mounted frame files |
-h | --help
| brief help message |
Without any specified options, frame2ilwd will perform the NFS and local tests. It will expect to find 100 frame files in the default NFS and local mounted directories. Specify options from the above table to modify this default behavior.
frame2ilwd will create a new directory called results-MMDD, where MMDD is the month and day of the date the test was run. The results will be written to a file called frame2ilwd.log in this directory. The result file contains two sections, each containing the results for the NFS and local tests respectively. Each section is a table of timings for steps necessary to convert channels from a frame file to ilwd format. Each column represents a different step, and each row represents a different number of channels. The timings are the average taken over performing the same step on 100 frame files (this can be modified by specifying the -numfiles option).
framestats.tcl Current_results_file Previous_results_file
The framestats script allows you to compare the current results generated by frame2ilwd with results previously acquired. At the command prompt type framestats.tcl frame2ilwd.log ../results-MMDD/frame2ilwd.log, where MMDD is the month and day of the date the previous test was run. This will produce a statistics file called frame2ilwd.stats in the current directory. The timings of the current file is subtracted from the timings of the previous file to produce three levels of statistics. The top section is the overall