[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
20000302: Unidata-Wisconsin products removed in July of 1999 (cont.)
- Subject: 20000302: Unidata-Wisconsin products removed in July of 1999 (cont.)
- Date: Thu, 02 Mar 2000 01:51:30 -0700
>From: "Karli Lopez (McIDAS)" <address@hidden>
>Organization: University of Puerto Rico
>Keywords: 200002010754.AAA03412 datastreams ROUTE PP BATCH LDM
Karli,
>Hi, Again I apologize for my delay in responding as I have been
>extremely busy these past couple of weeks. I did look into the
>configuration and noticed that the value of MCTABLE_WRITE was wrong,
>instead of being $MC_HOME/data/ADDESITE.TXT it was
>$MC_DATA/data/ADDESITE.TXT which is clearly wrong.
Right, assuming, of course, that $MC_HOME is ~mcidas.
>I have fixed that,
>however when attempting to change the dataset sources, for some odd
>reason, they still would not change:
>
>-----------------------------------
>Scheduler starting on file SKEDFILE
>DATALOC LIST
>
>Group Name Server IP Address
>-------------------- ----------------------------------------
>BLIZZARD 144.92.109.163
>MYDATA <LOCAL-DATA>
>PLANET <LOCAL-DATA>
>RTGRIDS <LOCAL-DATA>
>RTIMAGES ZERO.UNIDATA.UCAR.EDU
>RTNIDS <LOCAL-DATA>
>RTNOWRAD <LOCAL-DATA>
>RTPTSRC <LOCAL-DATA>
>RTWXTEXT <LOCAL-DATA>
>TOPO <LOCAL-DATA>
>
><LOCAL-DATA> indicates that data will be accessed from the local data director
> y.
>DATALOC -- done
>DATALOC ADD RTIMAGES LOCAL-DATA
>
>Group Name Server IP Address
>-------------------- ----------------------------------------
>RTIMAGES ZERO.UNIDATA.UCAR.EDU
>
><LOCAL-DATA> indicates that data will be accessed from the local data director
> y.
>DATALOC -- done
>DATALOC LIST
>
>Group Name Server IP Address
>-------------------- ----------------------------------------
>BLIZZARD 144.92.109.163
>MYDATA <LOCAL-DATA>
>PLANET <LOCAL-DATA>
>RTGRIDS <LOCAL-DATA>
>RTIMAGES ZERO.UNIDATA.UCAR.EDU
>RTNIDS <LOCAL-DATA>
>RTNOWRAD <LOCAL-DATA>
>RTPTSRC <LOCAL-DATA>
>RTWXTEXT <LOCAL-DATA>
>TOPO <LOCAL-DATA>
>
> <LOCAL-DATA> indicates that data will be accessed from the local data directo
> ry.
>DATALOC -- done
>DATALOC ADD RTIMAGES LOCAL-DATA
>
>Group Name Server IP Address
>-------------------- ----------------------------------------
>RTIMAGES ZERO.UNIDATA.UCAR.EDU
>
><LOCAL-DATA> indicates that data will be accessed from the local data director
> y.
>DATALOC -- done
>DSINFO IMAGE RTIMAGES
> No Datasets found of Type: IMAGE in Group: RTIMAGES
>DSINFO -- done
We have removed all "standard" data set definitions from zero.
>IMGLIST RTIMAGES/GE-VIS.ALL
>Image file directory listing for:RTIMAGES/GE-VIS
>IMGLIST: Image directory server unable to resolve this dataset: RTIMAGES/GE-VI
> S
>IMGLIST: done
This is showing that zero had those dataset definitions removed.
>DMAP ADDESITE.TXT
>PERM SIZE LAST CHANGED FILENAME DIRECTORY
>---- --------- ------------ ------------ ---------
>-rw- 273 Mar 02 03:45 ADDESITE.TXT /unidata/mcidas/data
>273 bytes in 1 files
I would suspect that the write permission on ~mcidas/data/ADDESITE.TXT did
not allow the write. Try the following:
cd ~mcidas/data
ls -l ADDESITE.TXT <- check the file permissions
chmod 664 ADDESITE.TXT
What is your umask? It should be 002.
By the way, since ADDESITE.TXT is a simple ASCII text file, it
can be edited directly. DSSERVE simply does that for you (and it
will add lines that define the IP address for machines whose names
are used instead of IPs).
>I beleive have followed every ADDE, except for setting up DSSERVE
>since I beleive that it's been set up previously. However I am not
>sure and I do not want to lose the redirections. My question is: what
>exactly refers to cylinders, and where do I find the correct cylinders
>for each dataset?
When referring to McIDAS standard data files, cylinders refers to the
4-digit number portion of the file name. For instance, the cylinder
number for the McIDAS image file AREA0001 is '0001'. The terminology
dates back to the mainframe McIDAS days when image data were stored
in disk cylinders. McIDAS file names use a "circular" naming convention.
For instance, the setup setup defined in ROUTE.SYS sent out with Unidata
McIDAS defines the set of GOES-East VIS images as the set of images
in AREA0140 - AREA0149; GOES-East IR images are in AREA0150 - AREA0159;
etc. Since AREA files are simply containers for image data, and since
their names really mean nothing about what is in the file per se,
we adopt conventions about what images we put in what "cylinders" or
files.
The definition of the datasets on your machine is based on a combination
of things:
o the setup you have in ROUTE.SYS
o how you define the datasets with DSSERVE commands
We send out a setup for ROUTE.SYS that has sites keep 10 of each kind
of image in the Unidata-Wisconsin datastream. Our default ROUTE.SYS
setup look like:
ROUTE LIST
S Pd Description Range Last Received Post Process C
- -- ------------------------- --------- ------------ ---------- ------------ -
s CI GOES-E/W IR Composite 80-89 none none none 3
s CV GOES-E/W VIS Composite 90-99 none none none 3
s CW GOES-E/W H2O Composite 70-79 none none none 3
LD NLDN Lightning Flashes 71-71 none none none 3
s MA Surface MD data default none none SFC.BAT 3
s N1 GOES-East IR/TOPO Composi 220-229 none none none 3
s N2 GOES-East VIS/TOPO Compos 230-239 none none none 3
s N3 GOES-West IR/TOPO Composi 240-249 none none none 3
s N4 GOES-West VIS/TOPO Compos 250-259 none none none 3
s N5 MDR/TOPO Composite 260-269 none none none 3
s N6 Mollweide IR/TOPO Composi 270-279 none none none 3
s N7 GOES-E/W IR/TOPO Composit 280-289 none none none 3
s N8 GOES-E/W VIS/TOPO Composi 290-299 none none none 3
NF Global Initialization Gri 101-102 none none GLOBAL.BAT 3
NG Early Domestic Products 1-2 none none ADDGRID.BAT 3
R1 Base Reflectivity Tilt 1 300-339 none none none 3
R2 Base Reflectivity Tilt 2 340-379 none none none 3
R3 Base Reflectivity Tilt 3 380-419 none none none 3
R4 Base Reflectivity Tilt 4 420-459 none none none 3
R5 Composite Reflectivity 460-499 none none none 3
R6 Layer Reflect SFC-24 K ft 500-539 none none none 3
R7 Layer Reflect 24-33 K ft 540-579 none none none 3
R8 Layer Reflect 33-60 K ft 580-619 none none none 3
R9 Echo Tops 620-659 none none none 3
RA Vertical Liquid H2O 660-699 none none none 3
RB 1-hour Surface Rain Total 700-739 none none none 3
RC 3-hour Surface Rain Total 740-779 none none none 3
RD Storm Total Rainfall 780-819 none none none 3
RE Radial Velocity Tilt 1 820-859 none none none 3
RF Radial Velocity Tilt 2 860-899 none none none 3
RG Radial Velocity Tilt 3 900-939 none none none 3
RH Radial Velocity Tilt 4 940-979 none none none 3
RI 248 nm Base Reflectivity 980-1019 none none none 3
RJ Storm-Rel Mean Vel Tilt 1 1020-1059 none none none 3
RK Storm-Rel Mean Vel Tilt 2 1060-1099 none none none 3
s RM Mandatory Upper Air MD da default none none MAN.BAT 3
s RS Significant Upper Air MD default none none SIG.BAT 3
U1 Antarctic IR Composite 190-199 none none none 3
U2 FSL2 hourly wind profiler default none none none 3
U3 Manually Digitized Radar 200-209 none none MDR.BAT 3
U5 GOES-West Western US IR 130-139 none none GW-IR.BAT 3
U6 FSL2 6-minute Wind profil default none none none 3
U9 GOES-West Western US VIS 120-129 none none GW-VIS.BAT 3
UA Educational Floater I 160-169 none none none 3
UB GOES-West Western US H2O 170-179 none none GW-WV.BAT 3
UC Educational Floater II 60-69 none none none 3
UI GOES-East North America I 150-159 none none GE-IR.BAT 3
UR Research Floater 180-189 none none none 3
US Undecoded SAO Data default none none none 1
UV GOES-East North America V 140-149 none none GE-VIS.BAT 3
UW GOES-East North America H 210-219 none none GE-WV.BAT 3
UX Mollweide Composite IR 100-109 none none MOLL.BAT 3
UY Mollweide Composite H2O 110-119 none none none 3
ROUTE: Done
The cylinder numbers for AREA files is seen in the "Range" column of this
list.
The ADDE dataset setup BATCH file we send out, DSSERVE.BAT, simply mimics
these defaults:
REM
REM Imagery received in the Unidata-Wisconsin datastream
REM
DSSERVE ADD RTIMAGES/EDFLOATER-II AREA 60 69 "Educational Floater II
DSSERVE ADD RTIMAGES/GEW-WV AREA 70 79 "GOES-East/West H2O Composite
DSSERVE ADD RTIMAGES/GEW-IR AREA 80 89 "GOES-East/West IR Composite
DSSERVE ADD RTIMAGES/GEW-VIS AREA 90 99 "GOES-East/West VIS Composite
DSSERVE ADD RTIMAGES/MOLL-IR AREA 100 109 "Mollweide Composite IR
DSSERVE ADD RTIMAGES/MOLL-WV AREA 110 119 "Mollweide Composite H2O
DSSERVE ADD RTIMAGES/GW-VIS AREA 120 129 "GOES-West Western US VIS
DSSERVE ADD RTIMAGES/GW-IR AREA 130 139 "GOES-West Western US IR
etc.
A quick look at this portion of DSSERVE.BAT (installed in ~mcidas/data)
shows that we will refer to GOES-East/West IR composite images as
RTIMAGES/GEW-IR. A quick comparison of the default ROUTE.SYS entries
and the default DSSERVE.BAT entries will show the correspondence.
Since a site can alter what they want to keep (by modifying entries in
ROUTE.SYS), we have the user make a copy of DSSERVE.BAT (into LSSERVE.BAT)
and then edit the file to make the dataset definitions correspond to
the AREA file numbers that were modified in ROUTE.SYS. For instance,
if one decided to keep 50 GOES-East IR images, and if it was decided
to store these images in cylinder numbers 1000 - 1049, your ROUTE.SYS
entry would look like:
UI GOES-East North America I 1000-1049 none none GE-IR.BAT 3
The corresponding entry in LSSERVE.BAT would look like:
DSSERVE ADD RTIMAGES/GE-IR AREA 1000 1049 "GOES-West Western US VIS
The thing that one has to worry about when modifiying how much is saved
is that the cylinder numbers for a product set must not overlap cylinder
numbers for other product sets.
Does this make sense to you? If not, let's work on this.
>Another concern I have is security. Some images are
>not supposed to be accessed outside of the network, or even the
>server. I wonder if by installing ADDE it will necessarily make those
>files available to the public.
There are a couple of things here. First, the only images that have
restricted distribution right now are NIDS imagery. The ADDE server
setup for my NIDS and NOWrad servers has an entry IPMASK that allows
one to define the set of IP addresses (through a regular expression)
that are allowed to look at the data. Images in RTIMAGES are not
prohibited from general distribution.
Second, ADDE has no discovery. You would have to know that a certain
machine was running an ADDE server, and you would have to know what
datasets are defined on that server, and you would have to be running
McIDAS in order to access the data. The combination of these three
things means that the number of people that might try to get stuff
off of your server is very small.
Third, one can setup TCP wrappers to limit access to the ports used
by ADDE (ports 500 and 503). This is not done as part of the standard
installation/configuration, but I may add the information in an upcoming
release.
>Thank You,
I am convinced that the reason you can't change your DATALOC for RTIMAGES
is that the file permission on ADDESITE.TXT does not allow writes.
Tom
