First ISCCP Regional Experiment FIRE Cirrus-2 HIS Read Software README Document 1.0 Introduction This file contains information about the FIRE Cirrus-2 HIS sample read software and data files. Read software has been furnished, since granules are in binary format and cannot be readily interpreted. Software setup and operating instructions are described in the following sections. This readme file includes the following sections: Section 2.0 - describes C program utilities (source files) Section 3.0 - discusses how to create executables from the C program source. Section 4.0 - demonstrates how to invoke the run-time executable. Section 5.0 - provides general information on the data sets. Section 6.0 - detailed implementation notes. Section 7.0 - data reader utility output format examples. If users have questions while using the FIRE Cirrus-2 HIS sample read software, please contact the Langley DAAC User and Data Services (UDS) office. The UDS may be reached by: e-mail: userserv@eosdis.larc.nasa.gov, phone: (804) 864-8656 mailing address: Langley DAAC User and Data Services Office NASA Langley Research Center Mail Stop 157D Hampton, Virginia 23681-0001 < intro > 2.0 Read Software Files The sample read programs for FIRE Cirrus-2 HIS data sets are written in the C programming language. By design, it is expected that the C source shall be compiled and perform equally well on SunOS (OS 4.1.3), Solaris (OS 5.3), SGI (IRIX64), and HP (HP-UX) UNIX based workstations. All library functions in the C source code have been tested for ANSI conformance. The source file, fire_ci2_his_read.c, is compiled against system libraries to produce the reader program. A Unix script makefile 'Makefile.fci2' is included for the convenience of creating the executable files from C program source. Makefile.fci2 - a master set of commands and environment settings used to build FIRE CI2 software utilities. fire_ci2_his_read.c - the read program "C" source code which provides access to the FIRE Cirrus-2 HIS binary data sets. < intro > 3.0 Creating C Executable Files There are two methods that may be used to build the read program executable. One is entering the UNIX 'make' command which reads instructions from the 'Makefile.fci2' command file. This script file defines all resources and paths needed to compile the C source files listed in section 2.0. The other is using the C compiler 'cc' (or 'acc' for Sparc ANSI C compiler). Section 3.1 illustrates the first method, and section 3.2 the second. Obviously, calling make is much simpler than defining all arguments on the command line. < intro > 3.1 Create with "make" command Before invoking make, take a moment to review the Makefile.fci2 file, and make sure options are setup correctly for your system. You will need to know two things; the operating system name and the current revision level. If you're not sure of either, type in "uname -a" at the UNIX system prompt. Uname echos a complete set of system information to your screen. The first string is the trademarked operating system name, and the third string is the current revision. Now you're ready to begin changing Makefile.fci2 to run on your system. Begin editing Makefile.fci2 by locating sections marked by the line # -SYSTEM DEPENDENT CHANGES----------------------------- There are three of these sections you'll want to check: 1. CC - specifies the C compiler 2. STD_DEFINES - standard definitions, compiler flags STD_CPP_DEFINES - specifies the C pre-processor flags 3. INCLUDES LIB_FCI2_DIR INCLUDE_DIR LIB_DIR - the include and library directories. Simply uncomment the lines that correspond to your system and comment out the other settings by placing a "#" in column 1. The settings for CC, STD_DEFINES and STD_CPP_DEFINES for several systems is shown below: platform assignment ------------------ -------------------------- SunOS 4 (rev 4.1.3) CC = acc (or CC=/usr/lang/acc) others CC = cc SunOS 4 (rev 4.1.3) STD_DEFINES = -DSUNOS Solaris (rev 5.* ) STD_DEFINES = -Xa -w HP-UX (HP UNIX) STD_DEFINES = -Aa -DHPUX SGI (IRIX64) STD_DEFINES = -DIRIX -ansi -32 SunOS 4 (rev 4.1.3) STD_CPP_DEFINES = -DSUNOS others STD_CPP_DEFINES = The symbol '%' in this section represents the UNIX command line prompt. Before proceeding, we recommend changing the name of the Makefile.fci2 to Makefile to simplify the call. However, if Makefiles already exist on your area and you don't want to change anything, it's ok to use the Makefile.fci2 as is. HINT: entering "cp Makefile.fci2 Makefile" will leave the original and create a file named Makefile. To build the data reader executable file, type the following in at the command line prompt: % make -f Makefile.fci2 fire_ci2_his_read If you've changed Makefile.fci2 to Makefile, then this entry becomes: % make fire_ci2_his_read Make will produce the executable file "fire_ci2_his_read" that reads the Cirrus-2 HIS data granules. < intro > < back > 3.2 Create with C compiler "cc" No additional path definitions or library references should be necessary. HP: (HP-UX) cc -g -DNO_HAVE_PROTOTYPES -DNO_STDARG -Aa -DHPUX -o fire_ci2_his_read fire_ci2_his_read.c Sun Microsystems Sun4: (SunOS 4.1.3) cc -g -DNO_HAVE_PROTOTYPES -DNO_STDARG -DSUNOS -o fire_ci2_his_read fire_ci2_his_read.c Using Sun's ansi c compiler: acc -g -DNO_HAVE_PROTOTYPES -DNO_STDARG -DSUNOS -o fire_ci2_his_read fire_ci2_his_read.c Sun Microsystems Solaris: (SunOS 5.3) cc -g -DNO_HAVE_PROTOTYPES -DNO_STDARG -Xa -w -o fire_ci2_his_read fire_ci2_his_read.c Silicon Graphics (SGI): (IRIX64) cc -g -DNO_HAVE_PROTOTYPES -DNO_STDARG -DIRIX -ansi -32 -o fire_ci2_his_read fire_ci2_his_read.c < intro > < back > 4.0 Invoking Read Software This section discusses the invocation of the software executable. After compilation, the read utility may be activated by typing the following in at the shell prompt; fire_ci2_his_read Command line options: -f or -float Data representation in the output report is in floating point notation. The program default is scientific notation. example: fire_ci2_his_read -float Section 4.1 describes how to run the fire_ci2_his_read executable to sample FIRE Cirrus-2 HIS binary data. Refer to section 7.0 for further information on the -float option and output report formatting. 4.1 Running the FIRE Cirrus-2 HIS Read Program Before activating the read utility, take a moment to note the names and local directory path to your FIRE CI2 HIS granules. Unless you intend to simply browse and view information on the screen, select an appropriate file name for the output report before executing the reader. Generally speaking, the reader leads you through an orderly sequence of explanations followed by prompts requesting operator input. Screen dialog consists of menus, help screens, and prompts. When "-" (or nothing) is selected instead of an output report file name, all information generated during the survey is written to the screen. For convenience, "h" and "x" may be entered at any prompt. The "h" summons a brief help menu, and "x" terminates further processing and exits the program. Except for file name and paths, the reader is not case sensitive to alpha entries. In the following paragraphs, a "%" in the left margin indicates program output. Following activation, reader program flow is as follows: 1. Prompt for name of data granule, including path % "Enter FIRE CI2 HIS data file name:" Note: 1) If the path or name is incorrect, or an access problem exists, the following error message is output to the screen and the reader exits: "error opening file /directory_path/data_file_name" 2. Prompt for output file name (including path if other than current) % "Enter Output file name ( "-" defaults to screen, "x" to exit) :" Note: 1) Help is not available at this prompt. "h" will be accepted as a file name. 2) If NO entry is made, the screen (default) is selected. 3. Next, the "Customized Output Menu" is displayed with a list of valid operator entries. One or more selection numbers may be entered at a time. Zero (0) concludes the selection sequence and permits the reader to proceed to the next menu. % ******************************************************************* % * * % * Customized Output Menu * % * ====================== * % * * % * 1) Record Header - extract w/description * % * 2) Record Header - floating point data values * % * 3) Spectral Radiation floating point data values * % * 4) Both record header and spectral data values * % * 5) Record header data value range (MAX/MIN) * % * 6) Spectral data value range (MAX/MIN) * % * * % * h brief Help menu * % * m redisplay this Menu * % * x eXits program * % * * % * enter 0 (zero) to complete menu option selection process and * % * continue program. * % * * % ******************************************************************* % % Please enter number of desired selection (1-6) <0 = CONTINUE>: 4. After leaving the "Customized Output Menu", the range of records within the current granule may be specified. You can select all the records or restrict the range of records searched within the granule. As explained below, entering a -1 selects the entire granule and is equivalent to selecting records 1 through 360 in the example shown below. When -1 is entered, the "enter last record" prompt is not output to the screen. Note: 1) There is NO Help Menu available at this prompt. Entering an "h" here simply requeues the previous prompt. 2) Invalid entries are rejected, and will cause the prompt to be requeued. Alpha characters, out of range and out of sequence numeric entries are considered invalid. For example, the starting record number should be less than or equal to the ending record number. % ------------- SELECT RANGE OF RECORDS ------------- % % (there are 360 records in this granule) % Please indicate START and END record numbers to extract. If you enter -1 % for the starting record, ALL RECORDS WILL BE EXAMINED and extracted in % accordance with the previously specified criteria. % % Please enter starting record number (-1 or 360 >= number >= 1): % enter last record to examine ( 360 >= number >= 1): The reader commences processing after record selection has been made. 5.0 Data Sets Information FIRE Cirrus-2 HIS was conducted on November 26 and December 5, 1991, near Coffeyville, Kansas aboard the NASA ER-2 aircraft. A High-resolution Interferometer Sounder (HIS) measured upwelling calibrated radiance. The sounder was positioned to capture a nadir view along the ER-2 flight tracks. There are gaps in the data sets due to calibration views and aircraft turns. Vertical Domain: Stratosphere (54,600-65,000 feet) Data Geotype: Land & Ocean Survey date: November 26, 1991 granule size: 3096000 bytes granule name: ci2_his_911126_* number of records/granule: 360 maximum minimum ------- ------- latitude.......... 30.4920 38.6266 longitude......... -95.7078 -92.8740 altitude.......... 65,088 54,675 Survey date: December 5, 1991 granule name: ci2_his_911205_* granule size: 4936400 bytes number of records/granule: 574 maximum minimum ------- ------- latitude.......... 37.3599 27.5735 longitude......... -90.7345 -96.9840 altitude.......... 65,378 57,793 Spectral data range: maximum minimum ------- ------- ci2_his_911126_1 116.7179 10.9873 (reciprocal cm.) ci2_his_911126_2 68.7930 -0.1399 (reciprocal cm.) ci2_his_911126_3 3.8688 -0.1213 (reciprocal cm.) ci2_his_911205_1 122.2784 20.1941 (reciprocal cm.) ci2_his_911205_2 70.9606 -0.4145 (reciprocal cm.) ci2_his_911205_3 4.8912 -0.2122 (reciprocal cm.) < intro > < back > 5.1 File Naming Convention There are six FIRE Cirrus-2 HIS granules containing upwelling spectral radiance data. Each granule represents one of three instrumentation channels on the sounder. The file naming convention format is: ci2_his_YYMMDD_C Where: YY = year, MM = month, DD = day, C = channel number Example: ci2_his_911126_1 Where: ci2_his_ project identification; Cirrus-2 HIS 911126_ acquisition date; YYMMDD (Nov. 26, 1991) 1 instrumentation channel number (1-3). 5.2 Description Of File Format The spectra of upwelling radiance are stored in multi-record binary files in which each record contains a single spectrum. Each record consists of a 100-word header followed by 2050 words of data, each word being a 32-bit real (IEEE floating point format) value. Only the first 2049 of the 2050 data words are valid radiance values. The spectral range is given in the header of each record, and is the same for all records. The spectral limits and interval values assume a laser wavenumber of 15799.000 reciprocal centimeters. record size: 2150 words * 4 bytes/word = 8600 bytes per record granule size: 26 Nov 1991 = 360 records ==> 8600 * 360 = 3096000 bytes / file 05 Dec 1991 = 574 records ==> 8600 * 574 = 4936400 bytes / file Each day has three files (HIS Bands 1, 2, and 3) of the same length. Header File length in bytes: None (header embedded in each record) Trailer File length in bytes: None (no trailer) Granule data type (IEEE 32-bit floating point) The fill value number for this data set is zero (0). Number of different record types per file (including header): none Each logical record (2150 words) contains a 100 word header record followed by a 2050 word data record, 2049 of which are spectral data. Total number of variables in each record: 100 variables per header record 1 variable per data record Total number of records: 26 Nov 1991 = 360 records 05 Dec 1991 = 574 records < intro > < back > 5.3 Variables The 100 header words, MOST of which you will NOT need, are described as follows (a shorter list, of the most important ones, follows the long list): Word numbering is one-offset and corresponds to Fortran conventional array indexing. Word Word Index Description Index Description -- ----------------------------- -- ----------------------------- 1 Record number 51 Aircraft Latitude 2 Channel number 52 Aircraft Longitude 3 Mirror position 53 Aircraft Altitude 4 Scan direction(1,2) 54 Aircraft Heading 5 No. recs. with bad mir.align. 55 HBB temp.corr.coeff.#1 6 Buffer overflow flag 56 HBB temp.corr.coeff.#2 7 No. unknown records 57 HBB temp.corr.coeff.#3 8 No. points in ifgm. 58 CBB temp.corr.coeff.#1 9 Beginning record number 59 CBB temp.corr.coeff.#2 10 ZPD rec.no. (raw data) 60 CBB temp.corr.coeff.#3 11 Time (seconds) 61 Average beamsplitter temp. 12 Hot blackbody temp.(C) 62 Average laser temp. 13 Cold blackbody temp.(C) 63 Average ap. stop temp. 14 DC Level, Ch. 1 64 Average SCAM encl.temp. 15 DC Level, Ch. 2 65 Average recorder dr.temp. 16 DC Level, Ch. 3 66 Average power supply temp. 17 Year 67 Average Bomem p.s.temp. 18 Month 68 Average pod air temp. 19 Day 69 Average dewar window temp. 20 Flag for ifgm. with 0 ZPD 70 Average optics mir. temp. 21 Flag for Ifgm. "burst" noise 71 Average optics bench temp. 22 Std. dev. of phase 72 Average bb heatsink temp. 23 Beginning time (HHMMSS) 73 Average atmospheric pr. 24 Current time (HHMMSS) 74 Average det.#1 DC level 25 Flag for short ifgm (<0 = bad) 75 Average det.#2 DC level 26 Data conversion type 76 Average det.#3 DC level 27 ZPD word number (in ifgm) 77 Average dewar temp. #1 (K) 28 Time correction (seconds) 78 Average dewar temp. #2 (K) 29 Apodization (0=none) 79 No. bad HBB temps found 30 No. ifgm. points used if FFT 80 No. bad CBB temps found 31 No. points in spectrum 81 "File 1" seconds(AVDIRS) 32 Calibration record 1 82 "File 2" seconds(AVDIRS) 33 Interval in indep.var. 83 "File 1" hhmmss(AVDIRS) 34 Minimum value, indep.var. 84 "File 2" hhmmss(AVDIRS) 35 Maximum value, indep.var. 85 Mean sp.avg. (COADDHIS) 36 Number of 32-bit words/record 86 S.D. sp.avg. (COADDHIS) 37 Number of header words (100) 87 Lower wavenumber(COADDHIS) 38 Spectral resolution 88 Upper wavenumber(COADDHIS) 39 Flag for bad rec. count 89 A/C hdg., start(COADDHIS) 40 Number of records in file 90 A/C hdg., end(COADDHIS) 41 Average HBB temp., cal.pt. 1 91 Avg. HBB temp.#1,(HISAC3) 42 Average CBB temp., cal.pt. 1 92 S.D. HBB temp.#1,(HISAC3) 43 Average HBB temp., cal.pt. 2 93 Avg. CBB temp.#1,(HISAC3) 44 Average CBB temp., cal.pt. 2 94 S.D. CBB temp #1,(HISAC3) 45 Calib.rec.no., cal.pt. 1 95 Avg. HBB temp.#2,(HISAC3) 46 Calib.rec.no., cal.pt. 2 96 S.D. HBB temp.#2,(HISAC3) 47 Number of records in ifgm. 97 Avg. HBB temp.#2,(HISAC3) 48 QC Flag (0=ok, PLOVR) 98 S.D. CBB temp.#2,(HISAC3) 49 Missing-ch. flag(-1, CHKSET) 99 Std.Dev.(ph.-ref.,HISAC2) 50 Laser wavenumber 100 Maximum Delay (HISAC1) The most important header words are: 11. Time (UTC, seconds) 17. Year (tens & units digits) 18. Month 19. Day 24. Time (UTC, hhmmss) 31. Number of valid points in each spectrum 33. Wavenumber interval (reciprocal centimeters) 34. Minimum wavenumber (reciprocal centimeters) 35. Maximum wavenumber (reciprocal centimeters) 36. Number of 32-bit words per record 37. Number of 32-bit words in header 51. Aircraft latitude (+ = N) 52. Aircraft longitude (+ = E) 53. Aircraft altitude (feet) 54. Aircraft heading (degrees CW from north) < intro > < back > 5.4 Instrumentation NASA ER-2 based High-Resolution Infrared Spectrometer (HIS) observations were used to specify the upwelling radiances for deriving the cloud radiometric properties. The HIS is a Michelson Interferometer developed primarily as an aircraft prototype of a new generation satellite sounder (Smith et al. 1986, 1987, 1990). It operates in the infrared region between 600 and 2600 cm¯ (16.8-3.8 µ using three detectors to divide the entire spectrum into three bands: band 1..........  600-1080 cm¯ band 2..........1080-1850 cm¯ band 3..........2000-2600 cm¯ The HIS spectra have a spectral resolving power (l/dl) of approximately 2000 providing a spectral resolution (apodized) of approximately 0.5 cm¯ for band 1, and 1.0 cm¯ for bands 2 and 3.The ground resolution of the HIS nadir observation is approximately 2 km. from an ER-2 altitude of 19.8 km. 5.5 Contacts for Data Production Information Investigator: Dr. William Smith Phone: 608-263-4085 Address: Space Science and Engineering Center University of Wisconsin - Madison 1225 W. Dayton St. Madison, WI 53706 e-mail: bills@ssec.wisc.edu Technical Contact: Dr. Steve Ackerman Phone: 608-263-3647 Address: Space Science and Engineering Center University of Wisconsin - Madison 1225 W. Dayton St. Madison, WI 53706 e-mail: stevea@ssec.wisc.edu 6.0 Implementation Notes Pre-release functional testing revealed differences in IEEE floating point representations of binary values displayed in scientific notation format. Further investigation revealed these differences stem from variances in implementation among manufacturers of internal rounding and truncation algorithms used to represent floating point numbers. During inspection, rounding variances were most frequently observed on the Silicon Graphics (SGI) platform, but were noted on Hewlett Packard as well. According to the SGI C language Reference Manual (007-001-080 dated 3/95), section F.3.6, page 116 explains this manufacturer's implementation. "Per IEEE, the rounding is round-to-nearest (IEEE Standard 754, sections 4.1 and 5.5). If the two values are equally near, then the one with the least significant bit zero is chosen." example: granule ci2_his_911126_1, record 7, header array element 11 SGI [ 11] 5.5373E+04 2.5870E+01 -2.1553E+01 -3.1494E+00 -3.4577E+00 SUN [ 11] 5.5372E+04 2.5870E+01 -2.1553E+01 -3.1494E+00 -3.4577E+00 HP [ 11] 5.5372E+04 2.5870E+01 -2.1553E+01 -3.1494E+00 -3.4577E+00 Confidence was established in the base raw data granules by porting to each machine, and redirecting the output of the hex dump utility (od -X) to an ascii text file. These files were then compared and found to be in agreement. In the example show above, metrics for the highlighted floating point value were: NOTE: See section 7.0 below for output report data representation options. 7.0 Reader Utility Output The program focus can be changed after startup by selecting menu options from the "Customized Output Menu". By design, the operator may adjust the scope of data reporting by selecting one or more options at a time. Samples for each option are shown in the following sections. Data represented in the output report can be changed using the command line option -f or -float. Although the reader program is case sensitive to output report file name, options may be entered in either upper or lower case. The float option is set when the reader software is executed, and has been provided to allow the output data representation to be changed from scientific to floating point notation. The normal program default is to display floating point numbers in scientific notation. In general, each output report is organized according to runtime Output Menu options. Each group of data is preceded by a brief header consisting of a title line and the record number. There are additional subheaders denoting headers, spectral data and so on. Also, the input data file name is listed once at the beginning of the report. After activation, the fire_ci2_his_read utility displays a title screen shown below: % ========================================================================= % % First ISCCP Regional Experiment - Cirrus2 % (FIRE CI2 HIS) % % This utility was specifically designed to provide access to FIRE CI2 HIS % spectral data granules. A granule is composed of a set of records, each % of which contains a 100 word header followed by a 2050 word data block. % Words are represented in 32-bit IEEE floating point format. % % Data granules represent upwelling calibrated radiance from the High-resolution % Interferometer Sounder (HIS) aboard the NASA ER-2 aircraft during FIRE II % for the days 26 Nov 1991 and 5 Dec 1991. Header information in each record % contains dynamic physical information that identify mission parameters at time % of capture. % % Menu options during startup permit the operator to make functional selections % varying data content, presentation and scope. For convenience, help (h) and % exit (x) options may be invoked at any entry point in the program. % In addition, no data translation is performed by this utility. % % ========================================================================= % % Enter FIRE CI2 HIS data file name: < intro > < 7.1 Output report header: In this example, a soft link named "fire_link" was made to the actual data granule for convenience. It is recommended that the full path to the data granule be entered when output files will be used to generate hardcopy printouts for documentation. % ========================================================================= % % First ISCCP Regional Experiment - Cirrus2 % (FIRE CI2 HIS) % % Upwelling calibrated radiance from the High-resolution Interferometer Sounder % (HIS) aboard the NASA ER-2 aircraft during FIRE II for the days 26 Nov 1991 % and 5 Dec 1991. % % FILE NAME: fire_link % % ========================================================================= 7.2 Customized Output Menu option 1: "Record Header - extract w/description" % ================= Header Record 1 Extract ================= % ===== CI2 Selected Header Values ===== % % 2150 = NUMBER WORDS IN THIS RECORD % 2049 = NUMBER VALID POINTS IN EACH SPECTRUM % 100 = NUMBER OF WORDS IN THIS HEADER % 1 = RECORD NUMBER % 1 = CHANNEL NUMBER % 0.482147 = Interval (reciprocal cm.) % 1974.875000 = Minimum value (reciprocal cm.) % 2962.312500 = Maximum value (reciprocal cm.) % 2049 = Number of points in each spectrum % 152047.000000 = DATA START TIME(UT) % 152047.000000 = DATA END TIME(UT) % 11 = CIS2 SORTIE JULIAN_MONTH(UT) % 26 = CIS2 SORTIE JULIAN_DAY(UT) % 91 = CIS2 SORTIE JULIAN_YEAR(UT) % 30.492001 = AIRCRAFT LATITUDE % -94.664001 = AIRCRAFT LONGITUDE % 54674.898438 = AIRCRAFT ALTITUDE % 346.750000 = AIRCRAFT HEADING 7.3 Customized Output Menu option 2: "Record Header - floating point data values" % ========================================================================= % % ============ HEADER DATA - RECORD 1 =========== % ===== 100 CI2 Raw Header Data Values ===== % % [ 1] 1.0000E+00 1.0000E+00 0.0000E+00 3.0000E+00 0.0000E+00 % [ 6] 0.0000E+00 0.0000E+00 3.5700E+03 2.8010E+03 2.8060E+03 % [ 11] 5.5247E+04 2.5814E+01 -2.0651E+01 -3.1702E+00 -3.4931E+00 % [ 16] -2.0996E+00 9.1000E+01 1.1000E+01 2.6000E+01 0.0000E+00 % [ 21] 0.0000E+00 1.4422E-01 1.5205E+05 1.5205E+05 2.0000E+00 % [ 26] 1.0000E+00 1.4140E+03 0.0000E+00 0.0000E+00 2.0480E+03 7.4 Customized Output Menu option 3: "Spectral Radiation floating point data values" % ========================================================================= % % ============ SPECTRAL DATA - RECORD 1 =========== % % ===== 2049 CI2 Spectral Data Values ===== % % % index CHANNEL 1 % % [101] 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 % [106] 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 % [111] 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 % [116] 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 % [121] 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 7.5 Customized Output Menu option 5: "Record header data value range (MAX/MIN)" % ========================================================================= % % ============== MIN and MAX HEADER VALUES ============= % ========================================================================= % % [INDEX] MAXIMUM :: MINIMUM [INDEX] MAXIMUM :: MINIMUM % ---------------------::-------------- ---------------------::-------------- % [ 1] 360.0000 :: 1.0000 [ 2] 1.0000 :: *UNCHANGED* % [ 3] 0.0000 :: *UNCHANGED* [ 4] 3.0000 :: *UNCHANGED* % [ 5] 0.0000 :: *UNCHANGED* [ 6] 0.0000 :: *UNCHANGED* % [ 7] 16.0000 :: 0.0000 [ 8] 3570.0000 :: *UNCHANGED* % [ 9] 36573.0000 :: 2801.0000 [ 10] 36578.0000 :: 2806.0000 % [ 11] 63804.0000 :: 55247.0000 [ 12] 25.9900 :: -37.2000 7.6 Customized Output Menu option 6: "6) Spectral data value range (MAX/MIN) % ========================================================================= % % ============== MIN and MAX SPECTRAL DATA VALUES ============= % ========================================================================= % % [ 101] 0.0000 :: *UNCHANGED* [ 102] 0.0000 :: *UNCHANGED* % [ 103] 0.0000 :: *UNCHANGED* [ 104] 0.0000 :: *UNCHANGED* % [ 105] 0.0000 :: *UNCHANGED* [ 106] 0.0000 :: *UNCHANGED* % [ 107] 0.0000 :: *UNCHANGED* [ 108] 0.0000 :: *UNCHANGED* % [ 109] 0.0000 :: *UNCHANGED* [ 110] 0.0000 :: *UNCHANGED* < intro > < back >