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

[McIDAS #YAX-451139]: Creating TruColor RGB from GOES-16



Hi Carol,

re:
> I'm attaching a log message and the setup_mcenv.sh script I'm using. 

OK, gotem.

re:
> The
> log should have most of the needed info since I'm doing a lot of imglist
> and imgremaps. Also, I believe the setup_mcenv has all the details you
> described to set up MCDATA properly.

Yes, the setup_mcenv_test_rgb.sh script looks like it is setting 
up the environment variables needed for McIDAS correctly.  The
only thing that I am not sure about, because I have never done it, is
to 'exec' a script from within the environment created by 'mcenv'.
I will need to setup a test to see if doing things this way has
any unintended consequences (but I won't be 'exec'ing a Perl script
because I am no Perl programmer).

One would assume that the AREA files that would/will be part of the
RGB/TEMP dataset would be read/written in the $MCDATA directory
since $MCDATA is the first directory included in the $MCPATH that
should be in-scope during the script execution.  The exception to
this would be if there is a file REDIRECTion in place since file
REDIRECTions take precedence over MCPATH.  I have no idea if there
are any REDIRECTions defined, but if there are, they would be in
a file named LWPATH.NAM.

re:
> I'll send you a Google Meet invite for 1 pm.

I'm already in the Meet...

> Thanks,
> Carol
> 
> address@hidden> wrote:
> 
> > Hi Carol,
> >
> > re:
> > > I changed the permissions for RESOLV.SRV, so that shouldn't be the issue
> > > anymore.
> >
> > Very good.
> >
> > re:
> > > I have a setup_mcenv script that sets up the ldm environment that runs
> > for
> > > each new image. I attached the current 'setup_mcenv.sh' that I'm running.
> > >
> > > Now I'm getting an error for writing the data.
> > >
> > > IMGCOPY MYDATA/AREAS RGB/TEMP.3 STYPE=VISR SIZE=SAME BAND=1
> > > Beginning Image Data transfer, bytes= 1639328
> > > Transferring AREA data outbound, bytes= 1639408
> > > IMGCOPY: Error writing area directory
> > > IMGCOPY: done
> > > IMGCOPY failed, RC=1
> > >
> > > Within the setup_mcenv.sh MCDATA=/data/ldm/mcidas, and I can see that
> > files
> > > are written there from other scripts. I'm a little confused why
> > > ABITRUCOL.MCB can't write to /data/ldm/mcidas.
> >
> > McIDAS understands the MCPATH environment variable.  I added MCDATA
> > as a Unidata construct, and then set MCPATHs such that the first
> > directory included in MCPATH is MCDATA.  If your script is not
> > doing the same thing, the reason for ABITRUCOL.MCB not working
> > as expected/hoped would be explained.
> >
> > Here is how I set MCPATH in the scripts that I run as 'ldm' to
> > generate LOTS of content for the IDD UNIWISC feed:
> >
> > # LDM HOME directory
> > LDMHOME=`echo ~ldm`
> >
> > # Define McIDAS environment based on LDMHOME
> > MCHOME=`echo ~mcidas`
> > MCDATA=$LDMHOME/mcidas/data
> > MCPATH=${MCDATA}:$MCHOME/workdata:$MCHOME/data:$MCHOME/help
> >
> > PATH=$LDMHOME/mcidas/bin:$PATH:$MCHOME/bin:$LDMHOME/bin:$LDMHOME/util:$LDMHOME/decoders
> >
> > if [ -f "${MCDATA}/MCTABLE.TXT" ]; then
> >   MCTABLE_READ="${MCDATA}/MCTABLE.TXT;$MCHOME/data/ADDESITE.TXT"
> > else
> >   MCTABLE_READ="$MCHOME/data/ADDESITE.TXT"
> > fi
> > export MCHOME MCDATA MCPATH MCTABLE_READ PATH
> >
> > #log_message "INFO: MCDATA = $MCDATA"
> >
> > # Everything happens in the MCDATA directory
> > cd $MCDATA
> >
> > As you can see, I define and then CD to the $MCDATA directory AND make
> > sure that it is the first directory in the MCPATH definition.  SSEC's
> > ABITRUCOL.MCB script assumes it is run inside an environment in which
> > MCPATH is fully defined.  The various McIDAS commands run (IMGCOPY,
> > IMGREMAP, IMGOPER) will read and write to the first directory in
> > MCPATH that it can read from for reads and write to for writes.
> >
> > re:
> > > 46 typhoon:/data/ldm/mcidas-> ls -l
> > > total 51496
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:24 AREA0001
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:24 AREA0002
> > > -rw-rw-r-- 1 ldm ldm 1639328 Jul  2 11:04 AREA0003
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:23 AREA0004
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:23 AREA0005
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:23 AREA0006
> > > -rw-rw-r-- 1 ldm ldm 1639328 Jul  2 11:04 AREA0007
> > > -rw-r--r-- 1 ldm ldm 1639328 Jul  2 11:04 AREA0008
> > > -rw-rw-r-- 1 ldm ldm 1639328 Apr 19 09:58 AREA0010
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:24 AREA0011
> > > -rw-rw-r-- 1 ldm ldm 1639328 Apr 15 14:45 AREA0012
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:24 AREA0013
> > > -rw-rw-r-- 1 ldm ldm 1639328 Jul  2 11:04 AREA0014
> > > -rw-rw-r-- 1 ldm ldm 1200928 Aug  9 17:24 AREA0015
> > > -rw-r--r-- 1 ldm ldm 1200928 Aug  9 17:24 AREA0016
> > > -rw-rw-r-- 1 ldm ldm 1639328 May 11 16:02 AREA0020
> > > -rw-rw-r-- 1 ldm ldm 1639328 May 18  2020 AREA0021
> > > -rw-rw-r-- 1 ldm ldm 1540928 May 18  2020 AREA0022
> > > -rw-rw-r-- 1 ldm ldm 1540928 May 18  2020 AREA0023
> > > -rw-rw-r-- 1 ldm ldm 1540928 May 18  2020 AREA0024
> > > -rw-rw-r-- 1 ldm ldm 1540928 May 18  2020 AREA0025
> > > -rw-rw-r-- 1 ldm ldm 1920928 Sep  1  2020 AREA0030
> > > -rw-rw-r-- 1 ldm ldm 1920928 Sep  1  2020 AREA0031
> > > -rw-rw-r-- 1 ldm ldm 1920928 Sep  1  2020 AREA0032
> > > -rw-rw-r-- 1 ldm ldm 1920928 Sep  1  2020 AREA0033
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:23 AREA0044
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:23 AREA0045
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:25 AREA0050
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:25 AREA0051
> > > -rw-rw-r-- 1 ldm ldm 1639328 Aug  9 17:25 AREA0052
> > > -rw-rw-r-- 1 ldm ldm 1200928 Aug  9 17:24 AREA0061
> > > -rw-rw-r-- 1 ldm ldm 1200928 Aug  9 17:24 AREA0062
> > > -rw-rw-r-- 1 ldm ldm 1200928 Aug  9 17:24 AREA0063
> > > drwxrwxr-x 2 ldm ldm      10 Sep  1  2020 himawari
> > >
> > > Anyways maybe we can do a Google Meet tomorrow to chat about this
> > tomorrow.
> > > I'm available after 1 pm.
> >
> > OK, I'm around all day.  Please send me a Meet invitation when you have
> > time, and I will join you.
> >
> > 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: YAX-451139
> > Department: Support McIDAS
> > Priority: Normal
> > Status: Closed
> > ===================
> > 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.
> >
> >
> >
> 
> 

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: YAX-451139
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
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.



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.