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.
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.