SDI Operator's Manual
Revised July 2000
[Search Manual]
[Table of Contents] [FAQ]
[Go
to Previous] [Go
to Next]
GOES
Channel Data
The GOES Channel
Data can be processed in either GINI format or in McIDAS area format, but not
both at the same time.
In all SDIs,
data and spool files are written to the data path defined in the file /etc/init.d/ingcntl.
When SSEC ships a GINI SDI system, the data path defaults to /data.
When NOAAPORT two-card systems are shipped, the GINI data path defaults to ~mcadde/mcidas/data and
the NCEP/NWSTG format files are written to /data.
The following
sections contain information specific to their data type:
GINI
Format
To save the
GOES channel data in GINI format, indicate the abbreviated WMO header (TTAAii)
of the product and the number of files to retain of each in the file /opt/nport/retain.nport.
Each WMO header and its number of files to be retained should appear on a separate
line. For example, to keep the last 10 copies of product TGIE01, add the following
line to /opt/nport/retain.nport.
The following
conventions also apply to GINI format data:
- All changes
to /opt/nport/retain.nport will take effect
when the next product comes in.
- The GINI format
file names include the image date and time. For example, TIGE04.2000.188.1901 would
be the name of the GINI file generated from WMO TIGE04, image time 1901UTC,
Julian Day 2000188.
- The default
number of files to keep for unlisted types is one. This means that one GINI
format file will be retained for each WMO type that is received that does
not have a corresponding entry in retain.nport.
This assists in identifying new WMO headers being sent.
- File retain.nport will
not be read if any area.<wmocode> files
(which manage area format files) exist in directory /opt/nport.
Area
Format
To process
GINI data into McIDAS area format, create files named area.<wmocode> in
the /opt/nport directory. Each file's content
must consist of the three numbers listed below.
starting_area_number ending_area_number current_area_number
|
For example,
if you create the file /opt/nport/area.TGIE01 with
the contents 2000 2099 2000, the area files for product TGIE01 would cycle
through area numbers 2000-2099. Note: When initially creating these area.<wmocode> files,
enter the same value for starting_area_number and current_area_number.
The current_area_number will automatically be incremented by the ingestor.
Also verify
that the line in the file /etc/inet.d/ingcntl that
defines the data path to write to reads cd ~mcadde/mcidas/data.
The following
conventions also apply:
- The name of
each of the ingested file contains the WMO header (e.g., TIGE04). If an area.<wmocode> file
exists for the WMO header, the ingestor calls program makgini.k,
which then takes the ingested file as input and creates an output area.
- The input files
are not deleted. They remain until overwritten the next time a product with
that WMO header is received.
- One GINI
format file is retained for each WMO type that is received, regardless of
whether a corresponding area.<wmocode> file
exists. This assists in identifying new WMO headers being sent.
Accessing
the Data via ADDE
Once the SDI begins to ingest data and is connected
to the network, the data can be accessed on workstations running McIDAS via
ADDE. The ADDE group name, by default, is GINI. Perform the Changing
Server Dataset Names procedurefollowing this section if you want to
change it.
Perform these
steps to access the SDI's data.
1. From a
McIDAS workstation:
Type: DATALOC
ADD GINI SDI_IP_address
For example,
if the SDI has an IP address of 144.92.108.32
Type: DATALOC
ADD GINI 144.92.108.32
2. Use the
ADDE command named DSINFO to list the descriptor names.
The output
should look similar to that below.:
Dataset Names of Type: IMAGE in Group: GINI
Name NumPos Content
------------ ------ ----------------------------------
TIGE01 99 Conus visible
TIGE02 99 Conus band 2
TIGE03 99 Conus band 3
TIGE04 99 Conus band 4
TIGE05 99 Conus band 5
TIGF01 99 NH visible
TIGF02 99 NH band 2
TIGF03 99 NH band 3
TIGF04 99 NH band 4
TIGF05 99 NH band 5
TIGN01 99 Super-national visible
TIGN02 99 Super-national band 2
TIGN03 99 Super-national band 3
TIGN04 99 Super-national band 4
TIGN05 99 Super-national band 5
TIGP01 99 Puerto Rico visible
TIGP02 99 Puerto Rico band 2
TIGP03 99 Puerto Rico band 3
TIGP04 99 Puerto Rico band 4
TIGP05 99 Puerto Rico band 5
TIGQ01 99 PR National band 1
TIGQ02 99 PR National band 2
TIGQ03 99 PR National band 3
TIGQ04 99 PR National band 4
TIGQ05 99 PR National band 5
DSINFO -- done
|
At this point
the suite of ADDE commands can be used with the data.
Changing
Server Dataset Names
Perform the following procedure to change or
update GINI server dataset names.
1. From the
console, login as user mcadde or telnet
into the ingestor as user mcadde.
2. To change
ADDE names associated with particular datasets, edit the file ~mcadde/mcidas/data/RESOLV.SRV.
The following is an example listing of this file. Notice that all fields
are comma delimited. You can not place a comma in the comment field.
N1=GINI,N2=TIGE05,TYPE=IMAGE,K=AREA,R1=501,R2=599,C=Conus
band 5,
N1=GINI,N2=TIGF01,TYPE=IMAGE,K=AREA,R1=601,R2=699,C=NH visible,
N1=GINI,N2=TIGF02,TYPE=IMAGE,K=AREA,R1=701,R2=799,C=NH band 2,
N1=GINI,N2=TIGF03,TYPE=IMAGE,K=AREA,R1=801,R2=899,C=NH band 3,
|
Where:
|
N1 |
is
the ADDE group name |
|
N2 |
is
the ADDE descriptor name (for clarity, we recommend that its value match
the wmocode in the corresponding /opt/nport/area.<wmocode> file) |
|
TYPE |
is
the data type |
|
K |
is
the data format or kind |
|
R1 |
is
the beginning dataset position number (must match the first number in
the sequence of numbers in in the corresponding /opt/nport/area.<wmocode> file) |
|
R2 |
is
the ending dataset position number (must match the second number in the
sequence of numbers in the corresponding /opt/nport/area.<wmocode> file) |
|
C |
is
the comment field displayed with DSINFO |
[Search Manual]
[Table of Contents] [FAQ]
[Go
to Previous] [Go
to Next]