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.
>From: "Mekonnen Gebremichael" <address@hidden> >Organization: Pratt School of Engineering, Duke University >Keywords: 200504201601.j3KG1gv2005753 McIDAS access Hi Mekonnen, Sorry to take so long to get back to you, but I have been in committee meetings for the past three days. >The error message ("IMGDISP: stretch table specified in >SU= does not exist on server") still persists unpon executing the command >'imgdisp'. As you suggested, I did ' DATALOC ADD RTIMAGES atm.geo.nsf.gov', >but found the error message 'DATALOC couldnot resolve ATM.GEO.NSF.GOV. entry >not filed. Hmm... This indicates something strange with your session. I tried using 'nslookup atm.geo.nsf.gov' to see if the name could be resolved and I found that this didn't work. Closer inspection showed that your PATH did not have the /usr/sbin directory included, so I added it. While at it, I modified PATH to include the /home/space/mcidas/bin directory in it. The reason for this is that you were continually resetting PATH in ~/mek11.cshrc. This was causing a problem in your McIDAS session. After adding /usr/sbin to the end of your PATH and /home/space/mcidas/bin to the beginning of your PATH, I was able to run a McIDAS session to begin troubleshooting the error you report above. Unfortunately, DATALOC would still not work: % dataloc.k ADD RTIMAGES atm.geo.nsf.gov dataloc.k: Could not resolve ATM.GEO.NSF.GOV. Entry not filed. This indicates some sort of a problem with your McIDAS build as does the original error you report. >I would appreciate if you could logon and take a look. >The datafile is available under '/disk/space/mek11/GOESdatanew'. >Let me know if this works for you. I logged on with no problems, and confirmed the problems you are seeing. The only thing I can think of is that there is some problem with the McIDAS build, but will need the password for the 'mcidas' account in order to see what is possibly wrong. Can you give me this login? I think that if I can get on as 'mcidas', I will be able to get to the heart of the problem you are seeing quickly. >Thank you, No worries. Cheers, Tom -- 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.