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: "Alliss, Randall J." <address@hidden> >Organization: Northrop Grumman >Keywords: 200312222044.hBMKitp2002311 McIDAS WRTEXT Randy, >Yes...wrtext.for exists in the src directory. it is a UW program written in >1997. wrtext.for is a subroutine, not a program file. I was assuming that you would have a '.pgm' or '.c' file whose basename is wrtext that would get built into a '.k' executable from an action in the McIDAS makefile. I just looked through the Unidata McIDAS-X v2002x makefile and don't see any action that would create an executable named wrtext.k. The only thing I can offer in the way of advice at this point is to ask you to compare the timestamp on your wrtext.k executable with the timestamp on the rest of the v2002 executables. If it is much older than the rest, it is most likely a holdover from an older distribution or a site developed program. Sorry I couldn't be of more help. Tom