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

[McIDAS #HOJ-391973]: remap2.k

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: [McIDAS #HOJ-391973]: remap2.k
  • Date: Wed, 15 Aug 2018 12:52:06 -0600
Hi Greg,

re:
> I need the remap2.k command in mcidas but this command doesn't
> seem to be in my /home/mcidas/bin dir from the mcidas2018 version. In
> looking at my makelog file, I don't see any reference to that command.
> Any suggestions?

REMAP2 is part of the XRD package included with McIDAS-X.  The XRD package
is not built by default, but it is easy to build and install:

<as 'mcidas'>
cd ~mcidas/mcidas<version>/src      e.g., cd ~mcidas/mcidas2018/src
make xrd install.xrd

NB:

- XRD routines are not fully supported by SSEC or Unidata

- XRD routines are NOT documented in the McIDAS User's Guide

  For documentation, you will need to run 'HELP REMAP2' after
  the XRD package is built and installed

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: HOJ-391973
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.