[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #SET-184160]: GOES-W AREA Files

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDD #SET-184160]: GOES-W AREA Files
  • Date: Fri, 03 Apr 2020 12:52:14 -0600
Hi Jim,

re:
> Everything was unpacked and installed and running, but the logfile always
> gives errors as follows:
> 
> 20200403T180027.569435Z GvarFDRemap.sh[18684]: INFO: Starting up ...
> 20200403T180027.577456Z GvarFDRemap.sh[18684]: PROC: IMGCOPY G15GVAR/G15FDC04 
> MYDATA/IMAGES.3021 SIZE=SAME
> 20200403T180027.723702Z GvarFDRemap.sh[18684]: WARN: IMGCOPY G15GVAR/G15FDC04 
> MYDATA/IMAGES.3021 SIZE=SAME, return = 1
> 20200403T180027.727648Z GvarFDRemap.sh[18684]: ERROR: IMGCOPY 
> G15GVAR/G15FDC04 MYDATA/IMAGES.3021 SIZE=SAME failed, exiting

This error is most likely caused from the DIRFILE mask for the G15GVAR datasets
being incorrect.  I changed what I had for my own system to match what I thought
was your setup:

~ldm <-> /usr/local/ldm

Here are the entries:

N1=G13GVAR,N2=G13FDC01,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES13_FD_C01_VISR.area,C=GOES-13
 Full Disk Channel 1 VISR remap target,
N1=G13GVAR,N2=G13FDC02,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES13_FD_C02_VISR.area,C=GOES-13
 Full Disk Channel 2 VISR remap target,
N1=G13GVAR,N2=G13FDC03,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES13_FD_C03_VISR.area,C=GOES-13
 Full Disk Channel 3 VISR remap target,
N1=G13GVAR,N2=G13FDC04,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES13_FD_C04_VISR.area,C=GOES-13
 Full Disk Channel 4 VISR remap target,
N1=G13GVAR,N2=G13FDC06,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES13_FD_C06_VISR.area,C=GOES-13
 Full Disk Channel 6 VISR remap target,
N1=G15GVAR,N2=G15FDC01,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES15_FD_C01_VISR.area,C=GOES-15
 Full Disk Channel 1 VISR remap target,
N1=G15GVAR,N2=G15FDC02,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES15_FD_C02_VISR.area,C=GOES-15
 Full Disk Channel 2 VISR remap target,
N1=G15GVAR,N2=G15FDC03,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES15_FD_C03_VISR.area,C=GOES-15
 Full Disk Channel 3 VISR remap target,
N1=G15GVAR,N2=G15FDC04,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES15_FD_C04_VISR.area,C=GOES-15
 Full Disk Channel 4 VISR remap target,
N1=G15GVAR,N2=G15FDC06,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=999999,MASK=/usr/local/ldm/mcidas/data/GOES15_FD_C06_VISR.area,C=GOES-15
 Full Disk Channel 6 VISR remap target,

A quick way to check to see if there is something that doesn't match
with these dataset definitions is to clip out the value of MASK= and
us it in an 'ls' invocation.  For instance, vor G15GVAR/G15FDC04, the
test would be:

ls /usr/local/ldm/mcidas/data/GOES15_FD_C04_VISR.area

This assumes:

- that the tarball was unpacked from the HOME directory of the usr 'ldm'

- that the ~ldm/mcidas/data directory is, in fact:

  /usr/local/ldm/mcidas/data

- that the *.area files are readable

- that the /usr/local/ldm/mcidas/data directory is writable by
  the user 'ldm'

Is there any chance I could SSH to the machine and check things
out?


Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: SET-184160
Department: Support IDD
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.