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

20020221: McIDAS measuring temperature

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: 20020221: McIDAS measuring temperature
  • Date: Sat, 23 Feb 2002 16:10:27 -0700
>From: Student mail Account <address@hidden>
>Organization: CCNY
>Keywords: 200202212035.g1LKZGx03095 McIDAS IMGPROBE

Kamal,

Sorry I couldn't get to your inquiry before today.

>The MAPH command now works in McIDAS but the Alt D command gives
>brightness value instead of the temperature value. Can you please tell me
>a way to convert the raw value into actual temperature or a way to
>calibrate.

If you load an IR image into a frame and then run IMGPROBE on it (the D
command simply runs the IMGPROBE command for a single point for you)
the RAW, BRIT, and TEMP values for the point(s) requested should be
listed.  If this is not happening, it means that there is a problem on
your system, and the most likely culprit is the existence of one or
more frame related files existing in a directory other than your
~/.mctmp/... directory(ies).

Here is what you need to do to troubleshoot this problem:

1) start a McIDAS-X session

2) run the command:

   DMAP Frame

   If FrameN.M files (e.g., Frame1.0, etc.) are found in any directory
   other than a subdirectory of your ~/.mctmp directory, then these
   files must be removed before you proceed.  It is possible that one
   or more of these files may be owned by a user other than yourself,
   so you may not be able to delete them.  In this case, you will need
   to get your system administrator to delete them for you.

   For instance, if the listing from the DMAP command above shows the
   file Frame1.0 in the /home/mcidas/help directory, you must get your
   system administrator to run:

   <as either 'mcidas' or 'root'>
   rm -f /home/mcidas/help/Frame*

3) in a manner exactly analogous to 2), you must make sure that files
   named FRAMED, FRAMENH.001, and TERMCHAR.001 are not found by a DMAP
   command in any directory other than your ~/.mctmp/... directories.
   The commands to run to check this are:

   DMAP FRAMED
   DMAP FRAMENH.001
   DMAP TERMCHAR.001

   If any of these files are found in a directory other than ~/.mctmp/...
   then they must be deleted.  Again, they may have to be deleted by
   someone other than yourself, like 'mcidas' or 'root'.

When deleting files like FrameN.M, FRAMED, FRAMENH.001, or TERMCHAR.001,
you must NOT be running your McIDAS-X session, so EXIT your session
before deleting/getting the files deleted.

Once the environment in which McIDAS runs is cleaned up, you should be
able to load IR satellite images and interrogate them with D and/or
IMGPROBE.

Please let me know if you still have problems after performing the
steps above.  If you do have continuing problems, please include in
your email the exact McIDAS commands you used to load and interrogate
the image and the output that is shown in the McIDAS Text and Command
window when you loaded those images.  Thanks!

Tom Yoksas