McIDAS-V User's Guide

Version

Table of Contents

What is McIDAS-V?


What is McIDAS-V?

McIDAS-V is a free, open source, visualization and data analysis software package that is the next generation in SSEC's 50 year history of sophisticated McIDAS software packages. McIDAS-V displays weather satellite (including hyperspectral) and other geophysical data in 2- and 3-dimensions. McIDAS-V can also analyze and manipulate the data with its powerful mathematical functions. McIDAS-V is built on SSEC's VisAD and Unidata's IDV libraries, and an integrated version of SSEC's HYDRA software package.

Image 1: The McIDAS-V Main Display Window
Image 1: The McIDAS-V Main Display Window

For a brief description about getting started using McIDAS-V and making displays of common data available, refer to the Getting Started section.

This Guide was originally developed at the Unidata Program Center by the developers of the Integrated Data Viewer (IDV). The first version of the McIDAS-V User's Guide was created from the IDV User's Guide (September 2007) and has since been updated to reflect the changes that have been made to McIDAS-V, IDV, and VisAD (see the Release Notes for details on recent changes).

Development of McIDAS-V is ongoing at the Space Science and Engineering Center (SSEC) at the University of Wisconsin-Madison. The development is driven by the needs of the community of users. Suggestions, comments, and collaboration are welcomed and encouraged. See Documentation and Support for more information. The goal is to provide new and innovative ways of displaying and analyzing Earth science data, as well as provide common displays that many of its users have come to expect.

How can I get McIDAS-V?

See Downloading and Running McIDAS-V for information on how to download McIDAS-V, install McIDAS-V, and run McIDAS-V. For additional information, refer to the latest McIDAS-V training materials.


Overview

Release Notes

The items below list the changes in McIDAS-V for the most recent release version. For the release notes of previous versions, see All McIDAS-V Release Notes.

For a current list of known bugs and requested enhancements, please see the Open Inquiries Report from the McIDAS-V Inquiry System. To view the items currently under development, see the list of Critical Bugs and Critical Development Items.


McIDAS-V
Version 1.9

The items below reflect the changes since the 1.8 release.

Documentation Changes
Data Changes
Display Changes
Other Changes
Under Development

Documentation Changes

McIDAS-V User's Guide

Updated the McIDAS-V User's Guide to contain new features and more detailed content.
Data Changes

Orbit Tracks Chooser

Promoted the Under Development > Satellite Orbit Tracks chooser to a supported chooser (Satellite > Orbit Tracks). This chooser can load and display TLE (Two Line Elements) data loaded through a local file, ADDE, or a URL. For more information, see Choosing Orbit Tracks Data, Displaying Satellite Orbit Tracks, and Satellite Orbit Track Controls.

Local Servers

Updated local ADDE servers on Linux and OS X/macOS platforms. New servers include HimawariCast (WARC) as well as VIIRS for M, I, and Day/Night Band SDRs, and M and I band Imagery EDRs.

Remote Servers/Datasets

Added new imagery datasets for GOES-R series data. These servers/datasets are:

  • adde.ssec.wisc.edu/adde.ucar.edu/atm.ucar.edu/lead.unidata.ucar.edu:
    • DDSTALL - GOES East/West Debra Dust data rolling archive
    • EAST - GOES East L1b imagery
    • EASTALL - GOES East L1b imagery rolling archive
    • GEOCALL - GOES East/West GeoColor data rolling archive
    • GOESRALL - GOES-R imagery rolling archive
    • GOESSALL - GOES-S imagery rolling archive
    • GOESTALL - GOES-T imagery rolling archive
    • L2GEALL - Goes East L2 imagery rolling archive
    • L2GEAST - GOES East L2 imagery
    • L2GOESR - GOES-R L2 imagery
    • L2GOESS - GOES-S L2 imagery
    • L2GWALL - GOES West L2 imagery rolling archive
    • L2GWEST - GOES West L2 imagery
    • NPGOESR - GOES-R L1b and L2 imagery
    • NPGOESS - GOES-S L1b and L2 imagery
    • NPGRALL - GOES-R L1b and L2 imagery rolling archive
    • NPGSALL - GOES-S L1b and L2 imagery rolling archive
    • NPGWALL - GOES West L1b and L2 imagery rolling archive
    • RTDDST - GOES East/West Debra Dust data
    • RTGEOC - GOES East/West GeoColor data
    • RTGOESR - GOES-R L1b imagery
    • RTGOESS - GOES-S L1b imagery
    • RTGOEST - GOES-T L1b imagery
    • RTSNCL - GOES East/West Cloud Snow data
    • SNCALL - GOES East/West Cloud Snow data rolling archive
    • WEST - GOES West L1b imagery
    • WESTALL - GOES West L1b imagery rolling archive

Remote Archive Point Data

Added the ability to work with remote archive point data through the Point Observations>Plot/Contour chooser. Once the Point Type is selected, a window will appear prompting for a day to search for. This day can be changed in the Absolute Times tab of the chooser.

Absolute Times in Choosers

Added new functionality to the Absolute Times tab of the Radar>Level II> Remote, Radar>Level III, and Point Observations>Plot/Contour choosers to allow the user to specify a day, range of times, and number of times to list.

Gridded Aliases

Several gridded variables from GFS (Global Forecast System), HRRR (High Resolution Rapid Refresh), SREF (Short Range Ensemble Forecasting), NDFD (National Digital Forecast Database), RTMA (Real Time Mesoscale Analysis), FNMOC COAMPS (Fleet Numerical Meteorology and Oceanography Center Coupled Ocean/Atmosphere Mesoscale Prediction System), and NCEP National Blend of Models data were added to the list of known variables/aliases. All of these data sources are available through the default Gridded Data > Remote catalog, as well as the General >Files/Directories chooser with local gridded data. Adding these variables to the list of aliases allows for McIDAS-V to recognize them and therefore create derived fields and display the variables using the parameter defaults.

TROPOMI

Added support for L2 TROPOMI (TROPOspheric Monitoring Instrument) netCDF files downloaded from the Sentinel-5P Pre-Operations Data Hub or NASA Earthdata. These files can be loaded through the General -> Files/Directories chooser as a gridded data source (Grid files (netCDF/GRIB/OPeNDAP/GEMPAK). A variety of derived fields for the L2 products are also available, allowing easy access to different units available for many variables.

Gridded NUCAPS

Added support for NUCAPS (NOAA Unique Combined Atmospheric Processing System) gridded data files, which can be loaded through the General -> Files/Directories chooser or General -> Catalogs chooser as a gridded data source (Grid files (netCDF/GRIB/OPeNDAP/GEMPAK)).

NWS Warnings

Added a new menu item to the Main Display window (Display > Text Data > NWS Hazard Warning (from server)) that allows for plotting currently active severe weather warning (e.g. Severe Thunderstorm Warning, Tornado Warning) polygons in the Main Display window. This menu item adds a data source for the warnings to the Field Selector, and Create Display must be clicked in order for the polygons to be drawn in the Main Display.

Layer Cycling Speed

Added the ability to control the cycling speed when switching between displayed layers of 2D levels of a 3D variable. For example, a 2D contour display of a 3D temperature variable. There is now a Dwell setting in the Layer Controls to control the speed that the display cycles through the various 2D levels in the 3D variable. This is available for various gridded, point data, and radar displays.
Display Changes

MODIS and JPSS Dateline Improvements

Improvements were made in the Region tab of the Field Selector to allow for subsetting across the dateline for MODIS data loaded through the HYDRA chooser, as well as VIIRS SDRs and imagery EDRs loaded through the Under Development > JPSS chooser. Additionally, probing in the Main Display now works on both sides of the dateline.

MultiSpectral Display Probe Placement

Added a space between the probe (square) and numerical output value of a MultiSpectral Display in the Main Display window. Previously, an overlap between the probe and numerical values could make the value difficult to read. Additionally, probes now remain at the same latitude/longitude location after a projection change in the display. The probe and numerical output also work in sync when changing the vertical positioning of the probe.

New AWIPS Color Tables

Added several new color tables used to display gridded NUCAPS data from NASA SPoRT. These enhancements can be found under the "Satellite > NUCAPS" menu of the Color Table Editor. The color tables in this category are the defaults for any variable displayed from NASA SPoRT gridded NUCAPS files, though they can be applied to any displayed layer that uses an enhancement. A variety of additional AWIPS enhancements were added to the "AWIPS" menu of the enhancements. Many of these enhancements are under the "AWIPS > Grid" menu.

New NOAA STAR Color Tables

Added several new color tables used by NOAA STAR to display GOES-R series level 1b imagery data. These can be found under the "Satellite > GOES-R > STAR" menu of the Color Table Editor. Note that these enhancements are designed to display correctly on Brightness (0 - 255) calibration data.

Improved Relative Humidity Enhancement

Improved the System > Relative Humidity enhancement. Prior to McIDAS-V 1.9, the Relative Humidity enhancement had 20 color bins. The enhancement in version 1.9 now has 100 bins. The increase in the number of bins allows for a smoother transition of color between values and the ability to see more variation in displays.

Dark Mode

Added the ability to run McIDAS-V in dark mode. This functionality, currently available on macOS, can be enabled through the Advanced tab of the User Preferences.
Other Changes

Improved Layer Label Font Quality

Layer labels now use java font rendering. In previous releases, VisAD font rendering was used. Java font rendering allows for an improved quality of layer labels, especially with rounded characters.

Image and Movie Borders

Added the ability to add borders between panels when capturing a movie or animation of a multi-paneled display using All Views.

RGB and Channel Combination Formulas

Added a variety of formulas specific to:
  • ABI - Advanced Baseline Imager
  • AHI - Advanced Himawari Imager
  • AVHRR - Advanced Very High Resolution Radiometer
  • CLAVRx - NOAA Clouds from AVHRR Extended
  • MSG - Meteosat Second Generation (SEVIRI)
  • MODIS - Moderate Resolution Imaging Spectroradiometer
  • JPSS - Joint Polar Satellite System (VIIRS) - Under Development

These formulas will appear in the Field Selector tab of the Data Explorer when Formulas is selected. To evaluate the formulas, select the formula, the desired display type, and click Create Display. From here, an additional Field Selector window will appear where the user will manually select the bands/calibrations needed. Many of these formulas are also set up to be derived fields. This means that if a data source containing all of the required bands/calibrations is added, they will list in the Field Selector under an Imagery tree. Displaying the output of a formula through a derived field means that the manual band/calibration selection isn't necessary. For more information, see Description of Formulas - Imagery.

Note that not all of the RGBs and channel combination functions are considered to be operational, and therefore the functions may change in the future.

MPEG-4 Movie Capture

Added the ability to save movies in MPEG-4 (*.mp4) format, which is now available under the Files of Type dropdown menu when saving a movie.

Image and Movie Borders

Added the ability to add borders between panels when capturing a movie or animation of a multi-paneled display using All Views.

Alphabetical Field Listing

Organized the list of fields in the Field Selector alphabetically and/or monotonically. This makes the list of variables/fields more organized and easier to navigate through.

Location Labels

Added location labels for countries, world cities, and Canada provinces that can be found in the Display > Plot Location Labels > World menu in the Main Display. Added location labels for counties that can be found in the Display > Plot Location Labels > US menu in the Main Display. Updated the Volcanos location labels under Earth > Volcanos so the labels only contain ASCII characters, which makes many labels more readable.

Vertical Sum Formula

Added a vertical sum formula that can be found under "Formulas > Grids > Vertical Sum" that calculates the vertical sum of a 3D grid at the levels defined by the user. This formula uses the zsum() function that can be used in foreground and background scripts.

Vertical Min and Max Formulas

Added Max over grid levels and Min over grid levels formulas that can be found under "Formulas > Grids". These formulas calculate the vertical minimum and maximum value of a 3D grid at each x/y pixel across the vertical levels defined by the user.

Scripting

Added a variety of functionality related to scripting since the release of 1.8. Below is a list of significant changes:
  • New functionality with existing functions:
    • Added a new keyword to captureImage(), verbose, which allows the user to silence the a line printed to the Jython Shell letting the user know the image is being written.
    • Added the ability for listGridFieldsInFile() to work when the variables in the file don't include long_name attributes.
    • Added shorter server descriptions for ABI (ABIN), Sectorized CMI (SCMI), and Himawari (WARI) that can be specified in the format keyword of makeLocalADDEEntry().
    • Added the ability to specify coordinateSystem= and size='ALL' in loadADDEImage(). This is necessary to get the full domain and resolution of each image of a LEO or floating GEO sector loop where the sector moves between timesteps.

Java/Jython Update

Updated Java from 1.8.0_112 to 1.8.0_352, Java 3D from 1.6.0 to 1.6.2, and Jython from 2.7.1 to 2.7.2.
Under Development

JPSS Chooser

  • Added the ability to subset a region that crosses the dateline in the Region tab of the Field Selector. This allows users to display data that straddles the dateline at the native resolution of the data. Also, the user can now probe the data on either side of the dateline and see calibrated values output below the display.
  • Data objects returned from loadJPSSImage now include timestamp information, which allows for the %timestamp% macro to work in the layer label, as well as allowing the time to appear in the Time Animation Widget.
  • Imagery EDR (Environmental Data Record) files for all 5 I-bands and 16 M-bands are supported.
  • A variety of RGB and channel combination formulas have been added to the Formulas panel of the Field Selector, with separate categories for SDR (Sensor Data Record) and EDR formulas. Extra processing is done for the SDR formulas to remove the bowtie deletion lines. All of these formulas are available as derived products as well.
  • Added support for many JPSS VIIRS Products (Granule) available from NOAA CLASS.
  • Fixed a bug where certain imagery SDR bands/calibrations would not display correctly in multi-banded files or data sources.
  • The ability to access remote VIIRS (SDR and imagery EDR) datasets is available on all platforms.
  • Local servers have been added for VIIRS data on macOS and Linux platforms. When adding local VIIRS datasets, there are individual formats for:
    • VIIRS SDR I-Band
    • VIIRS SDR M-Band
    • VIIRS SDR Day/Night Band
    • VIIRS EDR I-Band
    • VIIRS EDR M-Band
  • With local datasets, the data and geolocation must be in separate files in the same directory, follow the standard NOAA CLASS naming convention, and use terrain-corrected geolocation.

GLM Chooser

Added a GLM (Geostationary Lightning Mapper) chooser to the list of Under Development choosers. This chooser is capable of loading GOES-R series GLM (Group, Event, Flash) data through remote ADDE. From the Increment option in the Data Sources tab, the user can specify the number of minutes of data to bin together into one timestep. This defaults to 5 minutes. To display the data, a gridded display or point data can be drawn.


System Requirements

McIDAS-V should run on any platform that fully supports Java and Java 3D. It has been tested on Linux, macOS, and Windows. AIX and IRIX support the requirements in certain configurations, but have not been tested.

To run McIDAS-V, a system will need to have a minimum of a 500 MHz processor and 512 MB of RAM free. However, if you are purchasing a new system, it is recommended that an Intel system running McIDAS-V have at least a 2 GHz processor, 4 GB memory (RAM), and at least 1 GB free hard drive space. Please note that Java on 32 bit operating systems can only utilize 1536 MB, while 64 bit operating systems can utilize all of the available memory. Performance will be better with faster processors and more memory. We have seen the best results with NVIDIA hardware and drivers.

Detailed requirements for the following are listed below:

Operating Systems

The chart below lists the software versions, by vendor, that McIDAS-V is known to run on, and that McIDAS User Services tests:

OS
Known to Work
Tested at SSEC (1)
Linux Any modern 64-bit distribution, 2014 or newer
e.g. RHEL, CentOS, Ubuntu, SUSE, Fedora
Red Hat Enterprise Linux WS 7
Red Hat Enterprise Linux WS 8
Red Hat Enterprise Linux WS 9
OS X/macOS Any 64-bit OS X using 10.9 or newer macOS 11.6.1
Windows Windows 7, 8, 10 Windows 10

Notes:
(1)The local ADDE servers are distributed as binaries compiled only on these Operating System versions. If you are running versions other than those listed, the local ADDE servers may not work and give you an error message that the "Local Server is not running".

Graphics Cards and Drivers

McIDAS-V works on systems with graphics cards that support OpenGL (all systems) and Direct-X (version 8.0+, Windows only). On Linux, the driver must support GLX, an X windows system extension to OpenGL programs. McIDAS-V also works on systems with stereo graphics cards. We have seen the best results with NVIDIA hardware and drivers, and with the display configuration set to a high screen resolution and the maximum number of colors.

McIDAS-V utilizes the latest developments in graphics cards, drivers and Java3D. If you encounter any problems with system instability (such as using all of the memory or CPU on your machine, or frequent software crashes) or unusual data displays with "torn" or "gray" images, you should make sure you have the latest driver for your system. Even if the system is brand new, the driver may not be the most recent version available.

Please Note: We have received reports of McIDAS-V failing to start (i.e., the windows never appear) on some systems using integrated graphics chipsets, including:

To determine the brand and driver information of your graphics card, follow the guides for each platform below:

Once you have determined your graphics card brand and driver information, check the manufacturers web page for information on their updated versions. Here are links to some of the most common graphic card Original Equipment Manufacturers (OEM):

Java Versions

McIDAS-V runs on any platform that supports:

McIDAS-V is packaged with the following versions included:

Versions Included with McIDAS-V
JRE (Java Runtime Environment)
Java3D
JOGL (Java OpenGL)
Linux(1)
1.8.0_352
1.6.2
2.5.0
OS X/macOS
1.8.0_352
1.6.2
2.5.0
Windows
1.8.0_352
1.6.2
2.5.0
other Unix
none
1.6.2
2.5.0

The necessary versions of the JRE, Java3D and JOGL are included with the Linux, OS X/macOS, and Windows installers. If other platforms fully support Java version 1.8+, Java 3D version 1.6.2+, and JOGL 2.5.0 they should also work, but have not been tested.

Notes:
(1)The version of the Mesa library that comes with Red Hat Linux may be incompatible with Java 3D packaged with McIDAS-V. If you experience X server crashes when exiting McIDAS-V, you will need to build and install Mesa from source available at http://www.mesa3d.org.

System Memory and Processor Speed

McIDAS-V can be demanding of hardware speed and memory depending on the size of the datasets you wish to work with. It is recommended that the system have a minimum of 512 MB of RAM free for McIDAS-V use. Performance is significantly better with 1 GB RAM or more. Please note that 32 bit Java Runtime Environments (JRE) can utilize a maximum of 1536 MB RAM, while 64 bit JREs can utilize all of the RAM available to the operating system (64 bit OS required).

The recommended processor speed will vary by platform. You can run on a system as slow as 500 MHz or even less, but response will be correspondingly reduced. In general, the faster the processor, and the more memory your system has, the better the performance will be.

For reasonable performance, it is recommended that an Intel system running McIDAS-V have at least a 2 GHz processor and 4 GB memory (RAM). Performance will be even better with faster processors and more memory.

Networking

McIDAS-V is designed to access data on remote servers on the Internet, as well as from local files. Downloading data from remote servers benefits from a fast connection to the Internet, since many data fields are large.

The following ports are used to access remote data, and must be open through any firewalls or proxies at your location:

When accessing local data via <LOCAL-DATA> ADDE datasets, incoming ports 8112 - 8122 must be allowed (Windows users may need to explicitly allow this connection). The Local ADDE Data Manager will attempt to connect to ports 8112 to 8122. If port 8112 cannot be connected to, port 8113 will be attempted, and then 8114 and so on.


Downloading and Running McIDAS-V

This page contains information on:

If there is any trouble downloading and installing McIDAS-V, first check the FAQ, then please report the problem as described to McIDAS-V Support.

For more information on downloading and using McIDAS-V, please see the Installation and Introduction tutorial on the McIDAS-V Documentation Page. Also, see this page for additional tutorials and instructional videos on more advanced subjects.

Downloading McIDAS-V
Check that your system meets the System Requirements for McIDAS-V and download the appropriate package for the following operating systems:

This file is just the installer and can be placed anywhere on your machine. When the installer is run in the next step, the user can then indicate where McIDAS-V should be installed.

Installing McIDAS-V

Start the installer by following the instructions appropriate for your operating system:


  • Linux
  •    open a terminal window and run sh ./<installer>.sh
  • Mac OS X/macOS
  •    mount the .dmg and double-click the installer
  • Windows
  •    double-click the downloaded .exe file
  • All other UNIX
  •    open a terminal window and run sh ./<installer>.sh

A GUI will walk through the installation steps and allow for creating a program group and/or desktop icon. When McIDAS-V is installed, a McIDAS-V-System directory will be created in the installation directory. This directory contains system files necessary to run McIDAS-V and users should not save files to the McIDAS-V-System directory. The first part of the installation GUI prompts the user to select if the install should update any existing installs, or if McIDAS-V should be installed into a new directory:

Image 1: Setup Window
Image 1: Setup Window

Note: Windows users should not install McIDAS-V in the /Program Files directory as this can lead to permissions problems.

Note: Users should install and run McIDAS-V as their own user, not as administrator. Installing or running as administrator may lead to problems starting or using McIDAS-V.

If an error occurs, please see the FAQ for information on solutions to common errors reported by users installing and running McIDAS-V. If the error is not listed, please send a support request to McIDAS-V Support.

Running McIDAS-V

On Mac OS X/macOS:

Double-click on the McIDAS-V shortcut icon that was created in /Applications. If the icon doesn't start McIDAS-V, see the FAQ. Alternatively, from a Terminal window from the McIDAS-V-System directory (where McIDAS-V was installed), run the command: ./runMcV

On Windows:

Double-click on the McIDAS-V shortcut icon that was created on the Desktop. Alternatively, from a Command Prompt window, from the McIDAS-V-System directory (where McIDAS-V was installed), run the command: runMcV.bat

On all other platforms:

At the UNIX prompt from the McIDAS-V-System directory (where McIDAS-V was installed), run the command: runMcV

If an error occurs, please see the FAQ for information on solutions to common errors reported by users installing and running McIDAS-V. If the error is not listed, please send a support request to McIDAS-V Support or use the Support Request Form in the Help menu of McIDAS-V.

Note: When McIDAS-V is first run, a /McIDAS-V directory will be created in the user path. This directory contains information about user-specified settings as well as XML files for color tables, projections, etc. that are used by McIDAS-V. Users can write files to this directory.

Setting Memory Usage

By default, McIDAS-V uses 80% of the available memory on your machine. The maximum amount of memory is determined by the operating system. To manually change the amount of memory used by McIDAS-V, edit the Maximum Heap Size in the Advanced tab of the Preferences by selecting Edit->Preferences... from the main menu. The new amount of memory will be saved and used in subsequent sessions. For 32 bit operating systems, it is recommended to set this to no more than 1250 MB. The maximum value for 32 bit operating systems is 1536 MB, while 64 bit operating systems can use all of the RAM available. To change the amount of memory used to a percentage, select the percentage option in the Advanced tab of the User Preferences by selecting Edit->Preferences... from the Main Display window.

Downloading McIDAS-V Source Code

The source code for McIDAS-V is available for download. For instructions on building McIDAS-V from source, see the Building McIDAS-V from Source document.


Data Formats and Sources

McIDAS-V can read a variety of data formats either from local files or remote data servers (e.g., HTTP, TDS, ADDE). This page contains information about some data sources that work with McIDAS-V.

To connect McIDAS-V to data sources, see Data Sources.

Supported Data Types and Formats
Data Type Description Supported Formats Access Method
Gridded Numerical weather prediction models, climate analysis, gridded oceanographic datasets, NCEP/NCAR Reanalysis - netCDF - local files, HTTP, TDS servers
- GRIB (versions 1&2) - local files, TDS servers
- Vis5D - local files, HTTP
- GEMPAK - local files, TDS servers
Satellite Imagery Geostationary and polar orbiter satellite imagery, derived satellite products - ADDE - ADDE servers
- McIDAS AREA - local files, local & remote ADDE servers
- AIRS - local files
- GINI - local files, TDS servers
- AMSR-E Level 1b - local ADDE
- AMSR-E Level 2a - local ADDE
- AMSR-E Rain Product - local ADDE
- EUMETCast LRIT - local ADDE
- Meteosat OpenMTP - local ADDE
- Meteosat Second Generation (MSG) Level 1b - local ADDE
- Metop AVHRR Level 1b - local ADDE
- MODIS L1b MOD02 (MODIS Level 1b) - local ADDE
- MODIS L2 MOD04 (Level 2 Aerosol) - local ADDE
- MODIS L2 MOD06 (Level 2 Cloud Top Properties) - local ADDE
- MODIS L2 MOD07 (Level 2 Atmospheric Profile) - local ADDE
- MODIS L2 MOD28 (Level 2 Sea Surface Temperature Products) - local ADDE
- MODIS L2 MOD35 (Level 2 Cloud Mask) - local ADDE
- MODIS L2 MODR (Level 2 Corrected Reflectance) - local ADDE
- MSG HRIT FD and HRV - local ADDE
- MTSAT HRIT - local ADDE
- NOAA AVHRR Level 1b - local ADDE
- SSMI (TeraScan netCDF) - local ADDE
- TRMM (TeraScan netCDF) - local ADDE
- Himawari-8 (*.DAT) * - local ADDE
- INSAT-3D Imager * - local ADDE
- INSAT-3D Sounder * - local ADDE
- GOES ABI * - local ADDE
- SCMI * - local ADDE
- GOES GLM - local files
- TROPOMI (netCDF) - local files
Orbit Tracks Orbit tracks of geostationary and LEO (Low Earth Orbit) satellites - TLE (Two-line element) - local files, ADDE, URL
Radar Radar images - Level II - local files or TDS
(bzip2 compressed or uncompressed)
- Level III - ADDE servers, local files or TDS
- Universal Format (UF) - local files
- DORADE - local files
Point Observational Surface observations (METAR and SYNOP), earthquake observations - ADDE - ADDE servers
- netCDF (Unidata, AWIPS/MADIS formats) - local files
- Text (ASCII, CSV), Excel spreadsheet - local files
Aircraft observations - netCDF (RAF convention) - local files
- Text (ASCII, CSV) - local files
Global balloon soundings - ADDE - ADDE servers
- netCDF (Unidata, AWIPS/MADIS formats) - local files
- CMA text format - local files
- GEMPAK - local files
GIS Data typically used in Geographic Information Systems (GIS) - ESRI Shapefile - local files, HTTP
- USGS DEM - local files
QuickTime QuickTime movies (without extensions) - QuickTime - local files, HTTP

* The Himawari-8 (AHI), INSAT-3D, SCMI, and ABI local servers are currently supported on Linux and OS X/macOS platforms

Remote Data Servers

Extensive meteorological and oceanographic data is available from remote data servers for use in research and education. Some of these data have restrictions on their use, see Using Data Acquired via Unidata for that information.

Abstract Data Distribution Environment (ADDE)

Most of the data choosers in McIDAS-V use ADDE as the access method (satellite imagery, Level III radar, surface, and RAOB). The ADDE choosers are pre-configured with a list of available servers. SSEC and the Unidata community each maintain a set of cooperating ADDE servers which serve up real-time and archived atmospheric datasets for use in McIDAS-V. You can use any of these to access the near-realtime data. For more information on accessing data on ADDE servers, see the Data Sources section.

SSEC image datasets include:

Additional datasets:

THREDDS Data Server (TDS)/OPeNDAP

McIDAS-V can access gridded data (netCDF/GRIB/GEMPAK) and NEXRAD radar data stored on a THREDDS Data Server (TDS) through the OPeNDAP (formerly called DODS) protocol. See Choosing Cataloged Data for more information. Below is a listing of the default catalogs included with the different choosers that use them:

HTTP

Many of the data sources listed in the table above can read files directly from web servers (e.g. Apache) through the HTTP protocol. In most cases, the server must support the HTTP 1.1 protocol and be configured to set the "Content-Length" and "Accept-Ranges: bytes" headers. See the Choosing a URL for more information. While other choosers accept HTTP URLs, only one chooser has a default URL:

netCDF files

The Network Common Data Form (netCDF) provides a common data access method for Unidata applications. This format can be used to store a variety of data types that encompass single-point observations, time series, regular grids, and satellite and radar images. The mere use of netCDF by itself is not sufficient to make data "self-describing" and meaningful to McIDAS-V.

Generally, McIDAS-V requires that datasets in netCDF format use metadata conventions to be able to fully understand and geolocate the dataset. These conventions provide documented "best practices". Using conventions with netCDF ensures your data is complete and self-describing, and can be used by others. We recommend you use CF, COARDS, or NUWG conventions for netCDF data files for McIDAS-V, and be sure to follow the best practices noted above.

McIDAS-V can read GOES-R Series GLM (Geostationary Lightning Mapper) data through the General->Files/Directories chooser using the GLM_EVENTS Data files, GLM_FLASHES Data files, or GLM_GROUPS Data files Data Type. Multiple files can be selected at once and they will be aggregated into one data source when Add Source is clicked. Note that each data point in the data source is its own timestep, and therefore Time Binning settings should be modified in order to create a usable loop in the Main Display window. The Point Data Plot display can be used to display the data, as well as the gridded fields.

ASCII Text Point Data

McIDAS-V can read point data and trajectories (aircraft tracks) from comma-separated value (CSV) text files. See the documentation on the Text (ASCII) Point Data Format.

Miscellaneous

There are a couple of data formats that can be of a variety of data types (e.g. Satellite, point) that can be loaded through the local files chooser.


Documentation and Support
Where to find Help and Support for McIDAS-V
If you are having problems installing or using McIDAS-V, or want to know how to perform a particular task, you have several resources to assist you.
McIDAS-V Documentation

The first source of support is this McIDAS-V User's Guide. It contains complete instructions for downloading, installing, running, and using the McIDAS-V reference application and all its features. It also has a Frequently Asked Questions (FAQ) section with answers to many of the most commonly asked questions. The User's Guide can be accessed from the McIDAS-V Help->User's Guide menu or online at https://www.ssec.wisc.edu/mcidas/doc/mcv_guide/current/.

Additional documentation is available on the McIDAS-V homepage (https://www.ssec.wisc.edu/mcidas/software/v/), including McIDAS-V training materials (tutorials and data used in training sessions) and McIDAS-V source code.

Other Sources of Help

If you have questions or encounter problems that the McIDAS-V documentation (described above) doesn't provide sufficient help, there are two additional sources of help. They are the McIDAS-V Support Forums and the McIDAS Help Desk.

The McIDAS-V Support Forums contain subject-based forums, each with topics and posts relating to the forum's subject. Only registered users can post on the forums. However, anyone can view the forums and their contents (i.e., visit as an unregistered "Guest").

The McIDAS Help Desk is staffed during business hours with user-support personnel. As noted in the MUG Policy Document, the help desk is supported by the fees paid by the McIDAS Users' Group (MUG) and thus provides advanced-level support for MUG members. For McIDAS-V all users (whether or not a MUG member) are welcome to contact the help desk to report software bugs or suggest improvements (enhancements).

When reporting a bug, first check for related error messages in the Message Console, and include the appropriate error messages in your email message. Also include as much information as you can about how you were running McIDAS-V and what happened, including:

Send this information to the McIDAS Help Desk using one of the three methods below.

  1. Fill out the support form available from the Help->Support Request Form menu. Please include as much information as possible about the problem. (This is the preferred method.)
  2. Fill out the contact form available on the McIDAS Website. Please include as much information as possible about the problem.
  3. You may contact McIDAS User Services or the McIDAS Help Desk by postal mail at the following address:

McIDAS User Services
Space Science and Engineering Center
University of Wisconsin-Madison
1225 West Dayton Street
Madison, WI 53706


License and Copyright
McIDAS-V
Version 1.9

Copyright© 2007-2023
Space Science and Engineering Center (SSEC)
University of Wisconsin - Madison
1225 W. Dayton Street, Madison, WI 53706, USA
https://www.ssec.wisc.edu/mcidas/

All Rights Reserved

McIDAS-V is built on Unidata's IDV and SSEC's VisAD libraries, and
some McIDAS-V source code is based on IDV and VisAD source code.

McIDAS-V is free software; you can redistribute it and/or modify
it under the terms of the GNU Lesser Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.

McIDAS-V is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Lesser Public License for more details.

You should have received a copy of the GNU Lesser Public License
along with this program. If not, see https://www.gnu.org/licenses/.
Other Licenses
McIDAS-V includes software developed by:
Please read the different LICENSE files present in the root directory of the McIDAS-V distribution for restrictions on those packages.

Getting Started

This section describes how to quickly get started using McIDAS-V and making displays of common data.

McIDAS-V Main Windows

There are two main windows in the McIDAS-V application, the Data Explorer window and the Main Display window. Other windows may appear when needed.

Data Explorer

The Data Explorer window is central to McIDAS-V. It is used to choose data sources and parameters to display, the types of displays to make, and times of data to display. More information can be found in the Data Explorer section of the McIDAS-V User's Guide.

Image 1: Data Explorer Window
Image 1: Data Explorer Window
Main Display window

The Main Display window includes the McIDAS-V display panels, Legend, Time Animation Controls, viewpoint controls for 3D displays, icons for zooming, panning, and rotating, menus of projections, the main McIDAS-V toolbar, and the main menu bar. More information can be found in Main Display window section of the McIDAS-V User's Guide.

Image 2: Main Display Window
Image 2: Main Display Window
Common Usage Scenario

To create displays with McIDAS-V, the common usage scenario is:

Getting Started Sections
Accessing Additional Tutorials

For more help with getting started with McIDAS-V, please see the Installation and Introduction tutorial on the McIDAS-V Documentation webpage.


Displaying Satellite Imagery

This section describes how to make displays using geostationary and polar orbiting satellite imagery.

Image 1: Satellite Image in the Main Display Window
Image 1: Satellite Image in the Main Display Window

The steps include:

Choosing Geostationary Satellite Imagery from a Remote Server

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Satellite->Imagery from the list of available choosers. For more information about the imagery chooser, see Choosing Satellite Imagery.

Image 2: Data Sources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer
  1. Choose the ADDE Server: adde.ucar.edu and the Dataset: RTGOESR.
    Image Server and Dataset menus
  2. McIDAS-V comes pre-configured with a list of ADDE servers and datasets, or you can enter your own. See Available data for a description of these pre-defined data sets.

  3. Press Connect to query the server for available image types.
    Connect button
  4. Select the Image Type to use (in the example below, CONUSC14 for GOES-East CONUS 11.2 um IR Imagery/SST/clouds/rainfall).
    Image Type Dropdown
  5. Choose the image time(s) you want. Either choose a set of relative times as shown in the example below (5 most recent), or a set of absolute times as shown in step 5.
    Relative Times
  6. A set of absolute times (e.g., 19:46:42 UTC, 20:06:42 UTC).

    Absolute Times
    When choosing absolute times for the first time McIDAS-V needs to query the ADDE server for the times. This may take some time. To select more than one time use Ctrl+click or Shift+click.

  7. Select the Navigation type (either Default or Lat/Lon). Choose Lat/Lon if you are using Level 1B or POES ADDE servers.
  8. If you do not want to create a preview image in the Field Selector tab of the Data Explorer, uncheck 'Create preview image' box.
  9. When done, load the selected image data with the Add Source button.
    Add Source button
Creating the Display

The image data source that you selected will be shown in the Field Selector tab. The available display types are listed in the Displays panel, the times are listed in the Times tab, the preview image or map is displayed in the Region tab, and the geographical selection parameters are listed in the Advanced tab.


Image 3: Field Selector Tab of the Data Explorer
  1. Select the calibration that you wish to display in the Fields panel. In this example, Temperature is selected.
  2. "Image Display" should be selected for you in the Displays panel. "Image Display" displays your data as an image and is the display type used for satellite and Level III radar images in almost all cases.
  3. Click the Region tab to view the Preview Image. Use the mouse to Shift+left click and drag to select the geographical boundaries of your image.
  4. Click Create Display button to display the image(s) in the Main Display window. To control time animation use the Time Animation Widget.

If you want to create another type of satellite display over your current display, click "Image Contours" in the Displays panel to contour your data. To change your contour colors, right click on the color bar in the Legend, and choose one of the color tables shown in the list.


Image 4: Satellite Image with Contours in the Main Display Window

Due to the variability in brightness values in satellite images, some changes may need to be made to the contours to produce a quality image. To reduce the number of contours in the image, the contour interval can be increased by clicking the Change button button next to Contour in the Layer Controls tab of the Data Explorer, and entering a higher value for the Contour Interval. To decrease the rigidness of the contours, select a new Smoothing method in the Layer Controls tab and enter a higher smoothing factor.

Displaying a Single Polar Orbiting Satellite Image from a Remote Server

Return to the Satellite Imagery chooser in the Data Sources tab of the Data Explorer. Selecting polar orbiting satellite data is similar to the method to select geostationary data.

  1. Choose the ADDE Server: adde.ucar.edu and the Dataset: RTIMAGES and press Connect to query the server for available image types.
  2. Select the Image Type to use (in the example below, ANTARCTIC - Antarctic Thermal IR POES Composite).
    Polar Image Type Button
  3. Choose the one most recent image, and click Add Source button.
  4. In the Fields panel, select the calibration to display.
  5. Create the image in the Main Display by clicking Create Display button.
  6. The polar orbiting satellite image will be displayed on top of the existing geostationary satellite image.
Creating a Loop of Polar Orbiting Satellite Images from a Remote Server

When creating loops of polar orbiting satellite images, it is recommended that the Auto-set Projection option be turned off, and a global projection be used in the map display to ensure all images can be viewed. For this example, turn the Auto-set Projection option off by going to the Main Display window and selecting Projections->Auto-set Projection. Under the same menu, change your projection to Projections->Predefined->World. These options can also be used for displaying single images of polar orbiting satellite data. If you have access to an ADDE server with Aqua or Terra granules, you can use the following steps to display the data:

  1. Return to the Data Sources tab of the Data Explorer.
  2. Select a different Image Type to use (in the example below, Aqua 500 meter resolution Calibrated Radiances).
    Image Type dropdown menu
  3. Choose a set of either the 10 most recent relative times, or a set of 10 absolute times.
  4. When done, load the selected images into the Field Selector with the Add Source button button.
  5. In the Fields panel, select the calibration that you wish to view.
  6. In the Advanced tab, change the Coordinate Type to Image Coordinates. There is currently no method of determining the latitude and longitude boundaries of multiple polar orbiting images. Using the Image Coordinates option ensures the images will be displayed.
    Advanced tab of subset menu in the Field Selector
  7. When done, load the selected images with the Create Display button button.
Accessing Additional Tutorials
For more help with displaying satellite data, please see the Satellite Imagery tutorial on the McIDAS-V Documentation webpage.


Displaying Hyperspectral Satellite Imagery Using HYDRA

This section describes how to create multispectral displays using HYDRA. The set of steps include:

Creating the Multispectral Display

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Satellite->HYDRA from the list of available choosers. For more information about the HYDRA chooser, see Choosing Hyperspectral Data.

Image 1: Data Sources Tab of the Data Explorer
Image 1: Data Sources Tab of the Data Explorer

The HYDRA chooser is fairly similar to the File Chooser. As a demonstration, download the IASI image from January 15, 2007 located at: https://bin.ssec.wisc.edu/pub/mug/mcidas-v/training/data/IASI_xxx_1C_M02_20070115_1140.nc. Navigate to the directory the file is in and press Add Source button.

In the Field Selector tab of the Data Explorer, select Imagery->Multispectral Display, and click the Create Display button button.

Image 2: Field Selector Tab of the Data Explorer
Image 2: Field Selector Tab of the Data Explorer

There are four aspects to the multispectral display. The first is the image in the Main Display window. The image will be over Northern Africa and the Mediterranean Sea. The second aspect is the Spectra. The Spectra is displayed in the Layer Controls tab under "MultiSpectral". The spectra displayed by default is the 919.50 cm-1 spectral region (10.8 µm). The final two aspects are the two spectrum probes. In the Main Display window, there are two colored square boxes that represent the main probe (magenta) and the reference probe (light blue). These two probes are listed under "Readout" under "No Display" in the Layer Controls tab of the Data Explorer. Left click and drag either probe to view the spectra measured in various pixels around the image, or use one as a reference spectrum.

Using the Multispectral Display

Change the wavenumber being displayed to 852.25 cm-1 by entering in the value into the Wavenumber: box in the Multispectral Display and hitting Enter. Move the magenta and light blue spectra probes to the approximate locations in the image below to locate an inversion at the location of the red box over Albania.

Image 3: HYDRA Data Displayed in the Main Display Window
Image 3: HYDRA Data Displayed in the Main Display Window

Once the two probes are in the approximate locations, the MultiSpectral window should look similar to the image below.

Image 4: HYDRA Data Displayed in the MultiSpectral Window
Image 4: HYDRA Data Displayed in the MultiSpectral Window

Zoom in over the 852.25 cm-1 region using the Ctrl+left click+drag combination to create a box of the region to zoom in on. If you miss the region, or want to return to the full spectra, use Shift+left click. The inversion should become clear as you zoom in, as shown in the image below.

Image 5: HYDRA Data Displayed in the MultiSpectral Window
Image 5: HYDRA Data Displayed in the MultiSpectral Window
Accessing Additional Tutorials

For more help with displaying hyperspectral satellite imagery using the HYDRA chooser, please see the Hyperspectral Data tutorial on the McIDAS-V Documentation webpage.


Displaying Satellite Orbit Tracks

This section describes how to create a display of satellite orbit tracks. The set of steps include:

Creating the Satellite Orbit Track Display

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Satellite->Orbit Tracks from the list of available choosers. For more information about the Orbit Tracks chooser, see Choosing Satellite Orbit Track Data.

Image 1: Data Sources Tab of the Data Explorer
Image 1: Data Sources Tab of the Data Explorer

The Orbit Tracks chooser has three different options for creating a data source:

As a demonstration, create a data source from the default URL (https://celestrak.com/NORAD/elements/weather.txt). In the Remote panel of the chooser, select URL and click Add Source button.

The Fields panel of the Field Selector tab of the Data Explorer lists all of the satellites included in the data source. Select SUOMI NPP and the Satellite Orbit Track display type. In the Time Range subset tab, the beginning and ending times of the track can be defined by the user. Select a Begin and End date and time (for example: Begin 17:50:00; End 18:50:00; Jun 4, 2019), and click the Create Display button button.

Field Selector Tab of the Data Explorer
Image 2: Field Selector Tab of the Data Explorer

When the display is created, satellite tracks will be drawn in the Main Display window for the satellite and time range selected.

Image 3: Orbit Track Data Displayed in the Main Display Window
Image 3: Orbit Track Data Displayed in the Main Display Window
Using the Satellite Orbit Track Display

In the Main Display window, zoom in a bit over the tracks. From the Layer Controls, change the Label Interval to 1, enable Swath Edges On/Off, change the color to red, and click Apply. The image below represents the Swath Controls panel of the Layer Controls after these changes have been made.

Image 4: Swath Controls Panel of the Layer Controls
Image 4: Swath Controls Panel of the Layer Controls

Once these changes are made, the display in the Main Display window may look like the following image. The solid line is the track of the satellite, and the dashed lines represent the swath that the satellite/instrument scans. This swath width value is defined in the Swath Width item in the Layer Controls.

Image 5: Orbit Track Data Displayed in the Main Display Window
Image 5: Orbit Track Data Displayed in the Main Display Window

From the Layer Controls, set the Ground Stations Available to SSEC and click Add Selected. Change the font size to 16 and click Apply. Note that the SSEC ground station is located over south central Wisconsin. Dependent on the geographical bounds of the display, a different station may need to be selected in order to see it in the display. The image below represents the Ground Station Controls panel of the Layer Controls after the SSEC ground station has been added.

Image 6: Ground Station Controls Panel of the Layer Controls
Image 6: Ground Station Controls Panel of the Layer Controls

Once these changes are made, the display in the Main Display window may look like the following image. The dashed line around the SSEC ground station represents the geographical range in which the ground station can see the Suomi NPP satellite . The size of this ring is dependent on the altitude of the satellite, as well as the elevation angle of the ground station, which is set by the Antenna Angle item in the Layer Controls.

Image 7: Orbit Track Data Displayed in the Main Display Window
Image 7: Orbit Track Data Displayed in the Main Display Window
Accessing Additional Tutorials

For more help with displaying satellite orbit track data using the Orbit Tracks chooser, please see the Orbit Tracks tutorial on the McIDAS-V Documentation webpage.


Displaying Level II Radar Imagery

This section describes how to make displays using NWS WSR-88D Level II data. The steps include:

Accessing WSR-88D Level II Radar Data

The Level II data is supplied as volume-scan files, each file having all data from WSR-88D radar for all sweeps for one "time". Archived Level II data is available from the National Centers for Environmental Information (NCEI) (data from NCEI must be un-tarred).

The files should be stored on your local file system with each station's files in a directory whose name is the 4-character ID (e.g., KTLX for Oklahoma City). In many cases, the data files do not have any location information in them and McIDAS-V uses the directory name as a first guess at the station location.

Choosing Level II Radar Data

In the Data Sources tab of the Data Explorer, select Radar->Level II->Remote to view the Level II radar chooser. The Radar->Level II->Local chooser allows you to choose Level II data from your file system. For more information about the Level II radar chooser, see Choosing NEXRAD Level II Radar Data.

Image 1: Data Sources Tab of the Data Explorer
Image 1: Data Sources Tab of the Data Explorer

Select a station and a relative or absolute set of times. When done, click the Add Source button button.

Making Level II Radar Displays

The data source is shown in the Field Selector tab of the Data Explorer. Level II data has three moments or data types: Reflectivity, RadialVelocity, and SpectrumWidth. McIDAS-V has several display types for Level II data, and any of the moments can be shown with any of the displays. Selecting "Reflectivity" in the Fields panel will show the list of available displays in the Displays panel.

Image 2: Field Selector Tab of the Data Explorer
Image 2: Field Selector Tab of the Data Explorer
Creating 2D Displays of Individual Sweeps
Image 3: Level-II 2D Radar Displayed in the Main Display Window
Image 3: Level II 2D Radar Displayed in the Main Display Window

Select the Radar Sweep View in 2D under Radar Displays in the Displays panel and click Create Display button. Radar Sweep View in 2D plots the data as a colored image on the base of the 3D display area.

The Radar Sweep Controls allow you to change which sweep elevation you want to use. You can add range rings with the Displays->Add Range Rings menu item.

Creating 3D Displays of Individual Sweeps
Image 4: Level-II 3D Radar Displayed in the Main Display Window
Image 4: Level II 3D Radar Displayed in the Main Display Window

Select the Radar Sweep View in 3D entry under Radar Displays in the Displays panel. The Radar Sweep View in 3D display plots the data as a colored image, with the data plotted in 3D space at the elevation where the sweep occurred. You can rotate the display to see its 3D nature.

Since the Earth is projected onto a flat surface in this display, the sweep has a shape very close to a rotated parabola. The Elevation Angles menu in the Layer Controls tab allows you to change which sweep elevation to display.

Displaying Pseudo-RHI Displays in 2D and 3D

Select RHI (Range-Height Indicator) under Radar Displays in the Displays panel and press Create Display. The RHI display plots the data as a colored vertical cross section at the true elevations of the beams in 3D space (Image 5). This pseudo-RHI is constructed from several horizontal sweeps of the radar. It may be necessary to rotate the display to see the RHI in 3D.

Image 5: Level II Pseudo-RHI Radar Displayed in the Main Display Window
Image 5: Level II Pseudo-RHI Radar Displayed in the Main Display Window
Image 6: Level II Pseudo-RHI Radar Displayed in the Layer Controls Tab
Image 6: Level II Pseudo-RHI Radar Displayed in the Layer Controls Tab

The beam width is indicated by the vertical extent of each colored vertical stripe, corresponding to a bin beam bin sample. The position of the RHI in azimuth can be adjusted by dragging the little box on the end of the selector line above the RHI.

A 2D plot of pseudo-RHI (Image 6), is shown in the Display tab of the Layer Controls tab. The RHI displays have an auto-rotate feature and a Time Animation Widget.

Displaying All Sweeps in 3D
Image 7: Level-II Radar Volume Scan in the Main Display Window
Image 7: Level II Radar Volume Scan in the Main Display Window

Select Volume Scan (all sweeps) in the Displays panel in the Field Selector. Volume Scan (all sweeps) plots the data as 3D field of points colored by value. Each point is a bin value; all sweeps and bins are shown.

Radar Isosurfaces in 3D

Select Radar Isosurface under Radar Displays in the Displays panel in the Field Selector tab. An isosurface is a 3D analog of a contour line which shows the location of all data with a single data value. Interpolation is used between sweep altitudes in the isosurface plot of Level II data, and all data in a volume scan is used.

Image 8: Level-II Radar Isosurface Displayed in the Main Display Window
Image 8: Level II Radar Isosurface Displayed in the Main Display Window
Choosing Local Level II Radar Data

To select Level II data from the Radar Imagery->Level II->Local file chooser:

Accessing Additional Tutorials

For more help with displaying Level II radar imagery, please see the Level II Radar Imagery tutorial on the McIDAS-V Documentation webpage.


Displaying Level III Radar Imagery

This section describes how to make displays using NWS WSR-88D Level III data.

Image 1: Level III Radar Display Overlaid with Range Rings
Image 1: Level III Radar Display Overlaid with Range Rings

The steps include:

Choosing Radar Image Data from a Remote Server

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Radar->Level III from the list of available choosers. For more information about the Level III radar chooser, see Choosing NEXRAD Level III Radar Data.

Image 2: Data asources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer
  1. Choose the ADDE Server: adde.ssec.wisc.edu and the Dataset: RTNEXRAD.
  2. Server and dataset selection for Level III Radar
  3. Press Connect to query the server for available radars types:
  4. Connect button
  5. Select a radar product, such as N0R - Base Reflectivity Tilt 1, from the pull-down menu.
  6. Level III Radar Product
  7. The map shows the available radar station locations and IDs. Select one by clicking on it.
  8. Radar map station selection panel

    The Declutter checkbox allows you to show all stations (not checked), or only a limited number of stations that do not overlap each other (checked). You will need to zoom in to see all the stations without overlaps.

  9. You can choose a relative set of times steps (e.g., Last 5 times) or absolute times (see step 6):
  10. Relative tab of the Times menu
  11. You can choose a set of absolute times:
  12. Absolute tab of the Times menu
    When choosing absolute times for the first time McIDAS-V needs to query the ADDE server for the times. This may take some time. To select more than one time use Control+click or Shift+click.

  13. When done, load the selected radar data with the Add Source button.
  14. Add Source button
Creating the Radar Display

The radar data source that you selected will be shown in the Field Selector tab of the Data Explorer.

Image 3: Field Selector Tab of the Data Explorer
Image 3: Field Selector Tab of the Data Explorer

Open up the Digital Accumulation Array tab under the Fields panel (Dropdown tab to reveal components of the individual field) to select a data type. Select "Image display" in the Displays panel under Imagery, and make the display by clicking the Create Display button button.

You can add Range Rings with the Display->Add Range Rings menu item. To control the looping of the images in the Main Display window, use the Time Animation Widget.


Displaying Surface and Upper Air Point Data

This section describes how to make layout model plots and contour displays using surface and upper air data. It also explains how to create and edit layout models.

Image 1: Layout Model Plot in the Main Display Window
Image 1: Layout Model Plot in the Main Display Window

The steps include:

Selecting Surface Observations from a Remote Server

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Point Observations->Plot/Contour from the list of available choosers. For more information about the Point Observations Plot/Contour chooser, see Choosing Point Data.

Image 2: Data Sources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer

In the Server: and Dataset: entry boxes, use the pulldown lists to select a local or remote server and a dataset with METAR data, such as adde.ssec.wisc.edu and RTPTSRC. You can also type a different server name into the entry box. Click Connect button to find data on the remote server. In the Point Type: selection box choose "Real-Time SFC Hourly", or the equivalent depending on your data source. You can choose either the latest N times using the Relative tab or select specific times using the Absolute tab. Click Add Source button when you have made your selection. Only data from the current date will be retrieved from the server.

Creating the Plot Display

The surface observation data will be shown in the Field Selector tab of the Data Explorer.

Image 3: Field Selector Tab of the Data Explorer
Image 3: Field Selector Tab of the Data Explorer

Select "Point Data" in the Fields panel and "Point Data Plot" under Point Data in the Displays panel. Make the display by clicking on the Create Display button at the bottom of the Field Selector tab.

To declutter the display, use the Point Data Plot Controls in the Layer Controls tab.

Upper air plots can be created the same way. In the Data Sources tab of the Data Explorer, select a Point Type: of "Real-Time Upper Air (Mandatory)," change the Interval to "12 hourly," and add the source. In the Field Selector, select a level of 500mb in the Level panel and click Create Display button to plot your data in the Main Display window.

Creating the Contour Display

The Gridded Fields tree allows you to use the Barnes analysis to create gridded fields of specific point observation parameters.

Image 4: Field Selector Tab of the Data Esplorer
Image 4: Field Selector Tab of the Data Explorer

Select the SYNOPTIC (SFCHOURLY) dataset from the Data Sources panel of the Field Selector. In the Fields panel, open the Gridded Fields tree by clicking on the tab icon (Dropdown tab icon) and select the temperature (T) parameter. In the Displays panel, select Contour Plan View, and create the display by clicking the Create Display button button at the bottom of the Field Selector tab. You can create or edit your own layout models by using the Layout Model Editor. To access the editor, click on the double down arrow (Double down arrow icon) and select Edit under the Layout Model: section in the Layer Controls tab or select Tools->Layout Model Editor from the Main Display window.

Upper air gridded fields can be created the same way. In the Field Selector, select the UPPERMAND dataset, open the Gridded Fields tab, select a parameter and level, and create the display.

Accessing Additional Tutorials

For more help with displaying surface and upper air point data, please see the Point Observations tutorial on the McIDAS-V Documentation webpage.


Displaying RAOB Sounding Data

This section describes how to make Skew-T plots from RAOB data.

Image 1: Skew-T Display in the Layer Controls Tab of the Data Explorer
Image 1: Skew-T Display in the Layer Controls Tab of the Data Explorer

The set of steps include:

Choosing RAOB Sounding Data from a Remote Server

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Point Observations->Soundings->Remote. For more information about the soundings chooser, see Choosing Upper Air Sounding Data.

Image 2: Data Sources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer

For the Server and Dataset, select adde.ssec.wisc.edu and RTPTSRC and click Connect. You must select UPPERMAND for real-time upper air mandatory data, and you have the option to also select UPPERSIG for real-time upper air significant data for the Soundings category. The stations that match your conditions will be displayed in the map. Select the station(s) you want to use. You can select one or more stations by clicking on them; hold down the Ctrl key to select more than one. When the Declutter checkbox is checked, only stations that do not overlap will be shown. When in declutter mode you can zoom in (by dragging the left mouse) to see more stations. The icons below the map allow you to navigate the map.

After you select your station(s), select the available time(s) you want to view in the Available box. The list of available soundings will be displayed in the Selected box. When you have made your selection click the Add Source button button.

Creating the Sounding Display

The RAOB data will be shown in the Field Selector tab.

Image 3: Field Selector Tab of the Data Explorer
Image 3: Field Selector Tab of the Data Explorer

Select "RAOB data" in the Fields panel and "Skew-T" or one of the other sounding types in the Displays panel. All times will be loaded by selecting the RAOB Data field. You can select individual times to display at once by selecting individual times under RAOB Data. Make the sounding display by clicking on the Create Display button button. The sounding will be displayed in the Layer Controls tab. For more information about the Skew-T and other aerological displays, see Sounding Display Controls.

Accessing Additional Tutorials

For more help with displaying RAOB sounding data, please see the Point Observations tutorial on the McIDAS-V Documentation webpage.


Displaying Gridded Data

This section describes how to make displays using gridded data sets. The steps include:

Connecting to a Data Source on a Remote Server

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Gridded Data->Remote from the list of available choosers. For more information about the catalog chooser, see Choosing Gridded Data.

Image 1: Data Sources Tab of the Data Explorer
Image 1: Data Sources Tab of the Data Explorer

Choose one of the remote Catalogs: such as https://www.ssec.wisc.edu/mcidas/software/v/threddsRTModels.xml for Unidata's catalog of near real-time model output.

A tree view of the catalog will be displayed. Open one, such as the NCEP Model Data->Global Forecast System (GFS)->GFS-CONUS 80km->Latest Reference Time Collection, by using the tab icons (Tab icon).

The list of this model's run times appears. Click on one time to select it, and then click the Add Source button button. You have selected this model run's output to be accessible by McIDAS-V.

Creating a Plot of 2D Data

The gridded data source that you selected will be shown in the Field Selector tab of the Data Explorer. The Field Selector tab contains folders of data categorized as 2D and 3D fields. Click on the 2D grid tab (Tab icon) to expand that category list. A list of all 2D grid parameters in the data source appears. When one of the fields is selected, the list of applicable display types will be added to the Displays panel.

Image 2: Field Selector Tab of the Data Explorer
Image 2: Field Selector Tab of the Data Explorer

Create a Contour Plan View display of a parameter by selecting a field to display in the Fields panel and selecting Contour Plan View in the Displays panel. Click the Create Display button. The display will be created and shown in the Main Display window. The display's Legend should also be shown on the right side of the Main Display window. You can open the Layer Controls for the item by right-clicking on the name in the legend and selecting Control Window.

Contour Display in the Main Display Window
Image 3: Contour Plan View Display in the Main Display Window
Creating a Plot of 3D Data

In the Field Selector tab of the Data Explorer, click on the 3D grid tab to expand that category. A list of all 3D grid parameters appears. To make a plot, first select a parameter name such as "Geopotential height @ Isobaric surface".

Display types suitable for this parameter are listed in then Displays panel. Select the Contour Plan View display, and click the Create Display button.

The initial plot is at the highest level in the data grid, such as 100 millibars. To shift the level to other levels:

The data in the Main Display window will now be displayed at the new level you have selected.

To zoom, pan, or rotate this 3D display, see Zooming, Panning, and Rotating. To toggle on the time animation loop, use the Run/Stop icon in the Time Animation Widget. To remove an existing display, use the File->Remove Display menu of the Layer Controls tab.

Subsetting Times

McIDAS-V automatically loads data for all times selected in the Layer Controls tab of the Data Explorer, and loads them as displays for an animation loop. Creating several displays may take time. If you only need to see one data time, it is better to only create displays for that time, as McIDAS-V will load in smaller loops of data faster than larger ones.

To make time selections that apply to all data in one data source, double click on the data source name in the Data Sources panel of the Field Selector tab to bring up the Data Source Properties editor. Click on the Times tab to subset the times.

Image 4: Times Tab of the Subset Menu
Image 4: Times Tab of the Subset Panel

Initially, all times are selected for display, indicated by the times in this window being grayed out and the Use Default checkbox being checked. To limit the selection to fewer times than all times, first check off the Use Default checkbox, and then select the times you want by clicking on the times (Note: You can select multiple times with the Shift and Ctrl keys). The selected times will be highlighted in blue, and these are the only times that will appear in your loop of data in the Main Display window.

To make time selections for one field, use the Times tab in the lower right panel of the Field Selector tab after you select the field and before you create the display. This will override the default times for the data source selected in the Field Selector tab of the Data Explorer.

Subsetting Spatially

You can also spatially subset the grid using the Spatial Subset tab of the Data Source Properties. This works similar to the times subsetting where you can set the property for all fields in the Data Source or override the default for a particular field.

Accessing Additional Tutorials

For more help with displaying gridded data, please see the Gridded Data tutorial on the McIDAS-V Documentation webpage.


Displaying Fronts

This section describes how to make plots of frontal analyses and forecasts from ADDE data.

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select Front Positions from the list of available choosers. For more information about the fronts chooser, see Choosing Front Positions.

Image 1: Data Sources Tab of the Data Explorer
Image 1: Data Sources Tab of the Data Explorer

In the Server: and Dataset: entry boxes, use the pull down lists to select a remote server and dataset containing front data, such as adde.ssec.wisc.edu and RTWXTEXT, and connect to the server.

Select either analysis or forecast fronts and click the Add Source button button. The fronts will automatically plot in the Main Display window.


Displaying Local Files

This section describes how to make a display using files or a directory located on your local machine.

Image 1: Satellite Image in the Main Display Window
Image 1: Satellite Image in the Main Display Window

The set of steps include:

Loading Local Files

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select General->Files from the list of available choosers. For more information about this chooser, see Choosing Data on Disk.

Image 2: Data Sources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer
  1. Navigate to the directory that contains the file(s) you are interested in. Use the Look In menu to select directories, or double-click on directory names to open the directories and load individual files.
  2. Select one or more files. Multiple files can be selected using Ctrl+click or Shift+click.
  3. Optionally, specify the type of data the file contains by using the Data Type menu.
  4. When done, load the selected file(s) by clicking the Add Source button button.
Loading Files from a Directory

Loading files from a directory is similar to loading files, however you are limited to one directory. Loading files from a directory also gives you the options of polling files, as well as limiting files to a specific file pattern.

Image 3: Data Sources Tab of the Data Explorer
Image 3: Data Sources Tab of the Data Explorer
  1. Open a directory containing data files, but do not select any individual files.
  2. Optionally, specify the type of data the directory contains by using the Data Type menu.
  3. Choose the number of files you want to to search for. You can select an absolute number of files that have been updated in a certain time period.
  4. When done, load the data in the selected directory by clicking the button.
Creating the Display

The local data files will be shown in the Field Selector tab of the Data Explorer.

Image 4: Field Selector Tab of the Data Explorer
Image 4: Field Selector Tab of the Data Explorer

The data source name listed in the Field Selector will be based upon whether you loaded files or a directory. If one file is loaded, the name of the file is shown. Multiple files will be listed as "N files" where N is the number of files loaded. A directory will be shown as the directory name plus the file pattern (if used), or ".*" if all files in the directory are loaded. Once you have selected a Field, Display, and Time(s), click the Create Display button button to display your data in the Main Display window.


Displaying Files from a URL

This section describes how to make a display using files located at a specific URL.

Image 1: URL Display in the Main Display Window
Image 1: URL Display in the Main Display Window

The set of steps include:

Loading Files from a URL

In the Data Explorer window, select the Data Sources tab. On the left side of this tab, select the General->URLs from the list of available choosers. For more information about this chooser, see Choosing a URL.

Image 2: Data Sources Tab of the Data Explorer
Image 2: Data Sources Tab of the Data Explorer
  1. Optionally, select the Data Type of your data using the pull down menu.
  2. Enter the URL into the field or choose a previously selected URL from the pull down menu.
  3. Change the URL option to Multiple to expand the box to allow for the entry of multiple URLs, one per line.
  4. When done, load the selected URL(s) by clicking the Add Source button button.
Creating the Display

The local image data source files will be shown in the Field Selector tab of the Data Explorer.

Image 3: Field Selector Tab of the Data Explorer
Image 3: Field Selector Tab of the Data Explorer

Once you have selected a Field, Display, and Time(s), click the Create Display button button to display your data in the Main Display window.


Using the Globe Display

This section describes how to make a globe display. The illustration below shows a McIDAS-V Globe Display of GFS numerical weather prediction model output of mean sea level pressure (as color-shaded image and contour lines) and 50 m/s wind speed isosurfaces showing the jet streams.

Image 1: Globe Display
Image 1: Globe Display

In the Globe Display display of McIDAS-V, the displays and maps are projected onto a spherical globe. The globe can be rotated by hand or automatically, along with the usual zooming and time animation of displays on the globe.

To create a Globe View window, use the File->New Display Tab->Globe Display->One Panel menu. This section describes how to make plots of global satellite imagery on the Globe display. The set of steps include:

Choosing Global Satellite Imagery

After creating a globe display in McIDAS-V, open the Data Sources tab of the Data Explorer and select the Satellite->Imagery chooser.

Displaying the Data

Once the data source has been selected, you can create the display by doing the following in the Field Selector tab of the Data Explorer:

Using the Display

You can move the display using the standard McIDAS-V zooming, panning and rotating functions. For this exercise try the following:

Any suitable data with navigation information (latitude, longitude, and altitude) that McIDAS-V can handle can be plotted on the globe display.


Data Explorer

The McIDAS-V Data Explorer window is composed of three tabs, Data Sources, Field Selector, and Layer Controls:

Image 1: McIDAS-V Data Explorer Window
Image 1: McIDAS-V Data Explorer Window

Data Sources

McIDAS-V can use data from local files, remote data servers such as OPeNDAP or ADDE and even web servers. Further about specific data formats and sources is available.

Select the sources of data to work with within McIDAS-V using the Data Sources tab of the Data Explorer. Once selected, the data source will be shown in the Field Selector tab where the user can select parameters, display times, the display type, and create the display.

McIDAS-V can work with any number of data sources at one time. Choosing a data source with McIDAS-V typically only reads the metadata (i.e., data about the data); no parameter data values are read until the user request a display to be made.

Use the Data Sources tab to select the data that is to be used in McIDAS-V. This can be brought up by selecting the Data Sources tab of the Data Explorer window, or by using the Display->Create Layer from Data Source... menu item in the Main Display window.

This section describes:


Choosing Satellite Imagery

The Satellite->Imagery chooser allows for accessing satellite imagery on local or remote ADDE servers. For more information on how to use this chooser, see Getting Started - Displaying Satellite Imagery.

Image 1: Satellite Imagery Chooser
Image 1: Satellite Imagery Chooser
Properties

Choosing Hyperspectral Data

The Satellite->HYDRA chooser allows for selecting data from the local file system or a mounted drive to be displayed using HYDRA. For more information on using this chooser, see Getting Started - Displaying Hyperspectral Satellite Imagery Using HYDRA.

Image 1: HYDRA Chooser
Image 1: HYDRA Chooser
Properties

Choosing Orbit Tracks Data

The Satellite->Orbit Tracks chooser provides three different methods of loading data:

For more information on using this chooser, see
Getting Started - Displaying Satellite Orbit Tracks.

Image 1: Orbit Tracks Chooser
Image 1: Orbit Tracks Chooser
Properties

Choosing NEXRAD Level II Radar Data

The Radar->Level II->Remote chooser allows for choosing Level II radar data from a remote THREDDS server. For more information on how to use this chooser, see Getting Started - Displaying Level II Radar Imagery.

Local Level II Radar Chooser

The Radar->Level II->Local chooser allows for choosing Level II radar data from the local file system or a mounted drive. The Level II data is supplied as volume-scan files, each file having all data from one WSR-88D radar for all sweeps for one "time". Archived Level II radar files can be displayed through the Radar->Level II->Local file chooser. The files should be stored on the file system with each station's files in a directory (folder) whose directory name is the station 4-character ID (e.g., KTLX for Oklahoma City). In some cases, the data files do not have any location information in them, and McIDAS-V uses the directory name as a first guess at the station location. Archived Level II data is available from the National Centers for Environmental Information (NCEI).

Image 1: Level II Local Radar Chooser
Image 1: Level II Local Radar Chooser
Properties
Remote Level II Radar Chooser
Image 2: Level II Radar Remote Chooser
Image 2: Level II Radar Remote Chooser
Properties

Choosing NEXRAD Level III Radar Data

The Radar->Level III chooser allows for choosing NEXRAD Level III radar data on remote ADDE servers. For more information on how to use this chooser, see Getting Started - Displaying Level III Radar Imagery.


Image 1: Level III Radar Chooser
Properties

Choosing Point Data

The Point Observations->Plot/Contour chooser allows for choosing surface, upper air, and other types of point data (e.g.: aircraft data) to plot or contour for the current date. For more information on how to use this chooser, see Getting Started - Displaying Surface and Upper Air Point Data.

Image 1: Point Data Chooser
Image 1: Point Data Chooser
Properties

Choosing Upper Air Sounding Data

Upper air RAOB data can be displayed as soundings. RAOB data as soundings can be accessed either from remote ADDE servers (using the Point Observations->Soundings->Remote chooser, pictured below) or from local files (using the Point Observations->Soundings->Local chooser). The only difference between these two choosers is specifying the source of data. The user can either select an ADDE server and press Connect, or select a file containing RAOB data. For more information on how to use these choosers, see Getting Started - Displaying RAOB Sounding Data.

Image 1: RAOB Chooser
Image 1: RAOB Chooser
Properties

Choosing Gridded Data

The Gridded Data->Remote chooser shows THREDDS catalogs of gridded data holdings on remote data servers (typically TDS or OPeNDAP). The pulldown menu has several catalog options. For more information on using this chooser to display grid data, see Getting Started - Displaying Gridded Data.

Image 1: Remote Grid Chooser
Image 1: Remote Grid Chooser
Properties

The following image displays the Gridded Data->Local chooser:

Image 2: Local Grid Chooser
Image 2: Local Grid Chooser
Properties

Choosing Front Positions

The Front Positions chooser allows for accessing analysis or forecast fronts on ADDE servers. For more information on using this chooser, see Getting Started - Displaying Fronts.

Image 1: Front Chooser
Image 1: Front Chooser
Properties

Choosing Data on Disk

The General->Files/Directories chooser allows for selecting data or a directory from the local file system or a mounted drive. For more information on using this chooser, see Getting Started - Displaying Local Files.

Image 1: File Chooser
Image 1: File Chooser
Properties

Choosing Cataloged Data

The General->Catalogs chooser shows THREDDS catalogs of data holdings on remote data servers (typically TDS or OPeNDAP) and provides access to remote Web Map Server (WMS) image servers. McIDAS-V provides a link to an initial default catalog, idvcatalog.xml, which should appear in the Catalog menu. If not, the user can directly enter the URL of the catalog: https://www.ssec.wisc.edu/mcidas/software/v/catalog.xml.

This URL links to a catalog of real time model data, a collection of county level shapefiles for roads and hydrography features, and a collection of useful Web Map Servers. For more information on using this chooser to display grid data, see Getting Started - Displaying Gridded Data.


Image 1: Catalog Chooser
Properties

The following image displays the WMS chooser:

Image 2: WMS Chooser
Image 2: WMS Chooser

The tree view on the left shows the different image layers available. The user can select one image or use Ctrl+click to select multiple images. The map on the right plots a red box around the bounding area of the particular item selected.

Data files that are imported through the WMS Servers must contain gridded data. Also, the NetCDF-Java Common Data Model must be able to identify the coordinate system used.

Properties

Choosing a URL

The General->URLs chooser allows for specifying the internet location (URL) of a data source. This URL may be a web page, a bundle or any data file that McIDAS-V can process from a URL. For more information on using this chooser, see Getting Started - Displaying Files from a URL.

Image 1: URL Chooser
Image 1: URL Chooser
Properties

Choosing Flat File Data

The General->Flat files chooser allows generic flat (2-dimensional) data to be loaded. The user must supply information about the format of the data by either specifying it directly or by loading a properly formatted header file. Flat files can be binary, ASCII values, or standard images (JPEG, GIF, etc.), and may contain multiple bands. Navigation may be loaded via separate navigation files or by specifying a bounding box for the data.

Image 1: Flat File Chooser
Image 1: Flat File Chooser
Properties

Field Selector

The Field Selector tab of the Data Explorer is used to list the loaded data sources, view their available fields, select a display type, subset (time and space) the field and create displays.

Image 1: Field Selector Tab
Image 1: Field Selector Tab

The Field Selector consists of four main panels:


Data Sources

The Data Sources panel lists the data sources currently loaded into McIDAS-V and provides access to both the user-made and native formulas. The data sources listed are chosen as described in the Data Sources page. The selected item is the data source that lists out its fields in this tab:

Image 1: Data Sources Panel
Image 1: Data Sources Panel

To set the defaults for a data source bring up the Properties dialog by right-clicking (or double-clicking) on the data source name in the Data Sources panel of the Field Selector tab and select Properties (note that the items in this menu will differ dependent on the data source type):

Image 2: Data Sources Panel Properties
Image 2: Data Sources Panel Properties
Properties

The Properties window is different for different types of data sources. Below is the Properties window for a gridded data source:

Image 3: Properties Tab of the Data Sources Properties Window
Image 3: Properties Tab of the Data Sources Properties Window
Properties
Time Binning

For point data you can define Time Binning settings (not shown) by selecting a Bin Size (e.g., 5 minutes, 1 hour) and a Round To value (e.g., On the hour, 15 minutes after the hour). This will map all the observation times into the nearest bin. The smallest time is rounded with the Round To value (e.g., if Round To was "10 after" and the smallest time was 10:23 then this time would be rounded to 10:20). This is the base time. Each actual observation time is mapped into a set of bins of Bin Size starting at the base time. Note that with certain point netCDF files where each data point has its own timestep, time binning may be necessary in order to create gridded displays.

Times

The Times tab allows you to select the times to use. Change the dropdown menu from Use Default to Use Selected to select individual times. If Use Selected was chosen, right click in the list to show a menu that allows for selecting different subsets (e.g., every 3rd time).

Image 4: Times Tab of the Data Sources Properties Window
Image 4: Times Tab of the Data Sources Properties Window
Spatial Subsetting

For grids and other data source types, the data can be subsetted and decimated with the Spatial Subset tab. The X Stride, Y Stride and Level Stride lists allows for decimating a grid, selecting every Nth point. The Bounding Box allows for defining a spatial area to load. The default spatial domain of the data is shown by the blue outline box. To select an area, left click and drag on the map. Alternatively, enter in Lat/Lon values in the fields to the left of the map and press Enter. Once a subset is selected it can be resized (grab on the little black selection points) moved (grab somewhere near the box) and delete (press the Delete key).

Subsetting can be useful when displaying an image that has a high resolution or covers a large spatial area as a Contour Plan View or Color-Filled Contour Plan View display. Instead of having McIDAS-V take the time to compute values between every point, a user can set a stride where only every Nth point will be taken into consideration. If a very detailed image is needed, it is recommended that stride is kept at the default (none). However, if a user is looking to get a general picture, the stride feature can be a time-saver.

Spatial Subset Tab of the Data Sources Properties Window
Image 5: Spatial Subset Tab of the Data Sources Properties Window

A version of this spatial subsetting window is used in the Field Selector tab of the Data Explorer. Here, a user explicitly enables these settings. The decimation and spatial subset are shown in different tabs:

Image 6: Subset Panels in the Field Selector
Image 6: Subset Panels in the Field Selector
Details

The Details tab shows further information about the data source, e.g.: any documentation associated with the data, what files or URLs are used, etc.

Metadata

For grid data sources the Metadata tab shows the NetCDF metadata information.

Objective Analysis

The Objective Analysis tab is available if working with Point Data.

Image 7: Objective Analysis tab of the data sources roperties window
Image 7: Objective Analysis Tab of the Data Sources Properties Window
Properties
Formulas

A user can create their own formulas using the McIDAS-V Formulas facility. The Formulas data source in the Field Selector is a special data source and lists all of the available end user formulas. Right-click on the data source to create new formulas and import and export formulas. The formulas are listed in the Fields tree. Right-clicking on one of the formulas listed in the Fields tree allows for editing, copying or evaluating the formula. This menu also provides access to the Jython Library and Jython Shell.

A user can select a formula just like any other Field and create a display from it. However, the formula, when evaluated to create the display, usually needs one or more other data fields to act on. In this case a special Field Selector window appears that allows the user to select the fields for the formula. (Note: The Fields selected here can also be Formula Fields resulting in further Field selection).


Fields

The Fields panel displays the list of data choices for the selected data source:

Image 1: Fields Panel in the Field Selector
Image 1: Fields Panel in the Field Selector

Selecting a data source in the Data Sources panel will list the available fields in the Fields panel. This list is usually hierarchical showing different categories of fields (e.g., 2D grids, 3D grids, image sequences, etc.). Note that these fields can be searched through these fields by clicking the Search Button button above the Fields panel. This allows for typing in the desired field without having to go through the entire list. To see the fields under a particular category, click on the toggle icon (Toggle icon).

If a NetCDF formatted data source is populating the Fields, a button will appear next to Fields for "show variables" Show Variables button. This is the default for the field listing, and will list the longname of each field included in the data source (also the %longname% macro used in the display). An example of a longname field would be "Pressure reduced to MSL @ Mean sea level". For many NetCDF data sources, this will provide a descriptive listing of each field in the file. When this "show variables" button is clicked, the button will change to say "show descriptions" Show Descriptions button, and the fields will change to list by their shortname included with the data source (also the %shortname% macro used in the display). An example shortname field would be "Pressure_reduced_to_MSL_msl". Both the longname and shortname of each field can be seen by mousing over a field name. Note that this button will not be available if the data source is not NetCDF.

Selecting a field will show the list of display types available in the Displays panel and subsetting information (e.g., times, spatial subset). The fields listed in the initial tree (in the above case, 3D and 2D) are all native to the data source. The fields listed under the Derived tree are produced from formulas that are applied to the native fields.

Derived Parameters

McIDAS-V provides derived parameters; parameters not provided by the original source data, but made from the source data with computations by McIDAS-V. This provides commonly used fields, such as dewpoint. While dewpoint is not included in the native fields of the data, it can be derived from humidity and temperature, where are native fields.

Since few data sets use the same names for parameters, McIDAS-V keeps of a list of "aliases" or particular parameter names that match with "canonical" names which are generally understood by all McIDAS-V users and which McIDAS-V uses for computations. Users can add their own special parameter names to the list of aliases. See the Parameter Alias Editor section for information on using that facility.

All needed source parameters for one derived parameter must come from one single data source (e.g. from one single netCDF file). McIDAS-V attempts to find derived parameters that can be made from data in each data source in the Data Sources panel, but not from all possible combination of data sources. If there are two data sources, one has the u-component and the other has the v-component of the wind, for example, the parameter names or aliases will not create derived wind vectors.


Displays

The Displays panel lists the display types applicable to the selected field. The display type selected will be used to display the data in the Main Display window or the Layer Controls tab of the Data Explorer. Note that the displays listed in this panel will be different depending on the type of data being displayed.

Image 1: Displays Panel in the Field Selector
Image 1: Displays Panel in the Field Selector
Creating Displays

The Displays panel shows a hierarchical list of the available displays for a particular field. Click on the type of display from the choices listed in the Displays panel to select it. There are a variety of different display types that are unique to particular types of data. For more information, see the Examples of Display Types pages.

Two or more displays (different display types) can be selected at one time. For an additional display, hold down the Control key and click on the second display type desired.


Data Subset

The Data Subset panel contains tabs for subsetting Times, Levels, Region, and Stride. These tabs may be different depending on the type of data.

The Times tab allows for selecting which times will be used in the display, as well as for matching or setting a time driver:

Image 1: Times Tab of the Subset Panel in the Field Selector
Image 1: Times Tab of the Subset Panel in the Field Selector

There are four different modes when selecting what times of data to display:

The Level tab allows for subsetting levels for 3D grids. This sets the level in the atmosphere that will be used to plot the data in the Main Display window:


Image 2: Level Tab of the Subset Panel in the Field Selector

For images, optionally subset the spatial area to be displayed. Use the Region tab to left-click and drag to select a geographical region to display. In the Main Display window, the display will be centered around the box and no data will be plotted outside of it. Note that the Use Default checkbox may have to be unchecked before subsetting a region:


Image 3: Region Tab of the Subset Panel in the Field Selector (Satellite)

Note that the Region tab is different for some data sources. For example, here is the Region tab when working with gridded data:

Image 4: Region Tab of the Subset Panel in the Field Selector (Grid)
Image 4: Region Tab of the Subset Panel in the Field Selector (Grid)

Use the dropdown menu to select what geographical region to display the data over:

Use the Advanced tab to further refine the data selection and refer back to the Region tab to view the domain that has been selected:

Image 5: Advanced Tab in the Subset Panel of the Field Selector
Image 5: Advanced Tab of the Subset Panel in the Field Selector
Properties

The image properties in the Advanced tab allow for overriding the default properties McIDAS-V uses to specify aspects of the image data. The widgets show the defaults McIDAS-V will use. Changing any of the widgets can override the default value.

Use the Data Sampling tab to change the number of points used to create the image. Fewer points along the X and Y-axes will display the data faster, but with less precision. It is recommended to leave the X and Y values as their default (all points) unless a general picture and nothing too specific is the overall goal.

Use the Settings tab to utilize any display settings that may have been set.

Subsetting

The Subsetting component of the Field Selector allows for subsetting the data in both time and space (if possible). If there are times in the data source they will be shown in this area. Likewise, if it is possible to do spatial subsetting or decimation. a Spatial Subset tab will be shown.

Time and spatial subsetting defaults can be applied to the data source itself through the Data Source Properties dialog or the defaults can be overwritten through the Field Selector tab.


Layer Controls

The Layer Controls tab of the Data Explorer is used to modify an existing display. The options to choose from in this tab will vary depending on the data source and field selected.

Image 1: Layer Controls Tab
Image 1: Layer Controls Tab

This section describes the specifics of the Layer Controls tab for different data sources and fields, including the following:

There are some general features of the Layer Controls tab that are consistent with every display, which are described below.

Options

Tab symbol - Provides a dropdown menu with options to move the Main Display window to the front displaying the selected tab, and allows for accessing the View and Projections menus of the Main Display window.

These options are found at the bottom left corner of the Layer Controls tab of the Data Explorer.

Image 2: Options in the Layer Controls Tab
Image 2: Options in the Layer Controls Tab
Properties
Menus

All parameters share a common set of File, Edit, View, and Help menu items, shown in the menu bar of the Layer Controls tab. Different controls may also have custom items in these menus as well.

The File menu has these common choices:

The Edit menu has these common choices:

The View menu has these common choices:

The Help menu has these common choices:
Gridded Data Displays

Plan View Controls
Overview

Plan views can be made in four types of displays: Contour Plan View, Color-Filled Contour Plan View, Color-Shaded Plan View, and Value Plots. Contour Plan View and Color-Filled Contour Plan View have the same properties. For more information on the Value Plots display, see Value Plot Controls.

Image 1: Contour Plan View Controls
Image 1: Contour Plan View Controls
Image 2: Color-Shaded Plan View Controls
Image 2: Color-Shaded Plan View Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Flow Display Controls
Overview

The Flow Plan View Controls are used to control plan (horizontal) displays (flow vectors, wind barbs, streamlines, trajectories, and curly vectors) of vector based data (e.g., wind components). They are similar to the Plan View controls. For more information on what wind speeds correspond to each of the wind barbs in McIDAS-V displays, please see the table in the FAQ.

The seven types of Flow Displays are Vector Plan View, Vector Colored by Speed, Vector Colored by Another Parameter, Wind Barb Plan View, Wind Barb Colored by Speed, Wind Barb Colored by Another Parameter, and Streamline Plan View. Under the 3D Surface displays, additional display types of Vectors Over Topography, Wind Barbs Over Topography, and Streamlines Over Topography can be selected. Under Flow Cross Section displays, Vector Cross Section and Wind Barb Cross Section can be selected. Note that with oceanographic wind data (where direction is opposite the normal convention in a way that 0 degrees is a wind from south to north) the vectors and barbs are handled in a way that they point in the correct direction. The Layer Controls listed below apply for all display types:

Image 1: Flow Displays Controls
Image 1: Flow Displays Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


3D Flow Display Controls
Overview

The 3D Flow Display controls are used to control 3D displays of flow vectors, trajectories, and streamlines derived from wind and vertical velocity data.

The ten types of 3D Flow Displays:

The controls for the 3D Vector Cross Section display are similar to those of the
Flow Display Controls. Note that in order to create these displays, at least four timesteps must be selected. The Layer Controls listed below apply for the 3D Volume Vector, Trajectory, and Streamline displays:

Image 1: 3D Volume Flow Display Controls
Image 1: 3D Volume Flow Display Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Value Plot Controls
Overview

The Value Plot controls are used to adjust the display of individual grid point values.

Value Plot Controls
Image 1: 2D Value Plot Controls
Image 2: 3D Value Plot Controls
Image 2: 3D Value Plot Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Vertical Cross Section Controls
Overview

The Vertical Cross Section Controls are used to adjust vertical cross section displays. Vertical cross sections can be made in three types of displays: Contour, Color-Filled Contour, and Color-Shaded. The control window has two tabs: Display and Settings. The endpoints of the cross section can be moved by clicking and dragging the endpoints in the Main Display window.

The Display tab includes a duplicate of the display in the Main Display window:

Image 1: Display Tab of the Layer Controls Tab
Image 1: Display Tab of the Layer Controls Tab
Properties

The Settings tab shows the settings for this display control:

Image 2: Settings Tab of the Layer Controls Tab
Image 2: Settings Tab of the Layer Controls Tab
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has this unique option:

The View menu has these unique options:


3D Surface Controls
Overview

Isosurfaces can be made in two types of displays, regular isosurfaces, and isosurfaces colored by another parameter. An isosurface is a 3D surface mapping the location of a single parameter value through a 3D field. Isosurfaces are a 3D analog of a single contour line in a 2D plot; the intersection of an isosurface and any plane is a contour line of the same value in that plane.

Coloring an isosurface by another parameter can serve many purposes. One example use of this is creating a display for possible icing conditions in the atmosphere that could be useful for pilots. To do this, the user would select Temperature as the field, the "Isosurface colored by another parameter" display type, and Relative Humidity in the Field Selector window that appears when Create Display is clicked. After the display is created, the isosurface value for Temperature can be set to be 0 degrees Celsius in the Layer Controls tab of the Data Explorer. Now, in the Main Display window, a surface of 0 degrees Celsius colored by Relative Humidity is displayed. Wherever high RH values are seen means that there is a lot of moisture in the atmosphere, and at the freezing temperatures, there could be icing conditions.


Image 1: Isosurface Controls Properties Dialog
Properties
Properties with *As Topography Displays
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The Edit menu has this unique option:

The View menu has these unique options:


Volume Rendering Controls
Overview

3D grids can be rendered as a volume display.

Image 1: Volume Rendering Controls Properties Dialog
Image 1: Volume Rendering Controls Properties Dialog

The transparency features of the color table can be adjusted to see through the display. This is done by right-clicking on the color bar, going down to Transparency, and selecting a percentage.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has these unique options:


Point Volume Controls
Overview

The Point Volume display shows the grid points in a volume of data as individual points in the display. The controls are used to change color tables, the number of points to skip, and the point size.

Image 1: Point Volume Controls Properties Dialog
Image 1: Point Volume Controls Properties Dialog

The transparency features of the color table can be adjusted to see through the display. This is done by right-clicking on the color bar, going down to Transparency, and selecting a percentage.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has these unique options:


Sounding Controls
Overview

For 3D derived gridded data, one of the Fields that can be selected is Sounding Data (Temperature & dewpoint only or with true winds). In the Displays panel of the Layer Controls tab, there is a category for soundings. The three sounding display options are Grid Skew-T, Grid Stuve Display, and Grid Emagram Display. This display uses the model data to produce soundings, and their controls are similar to those for Point Data sounding display controls. The location of the sounding in the Main Display window can be changed by dragging the selector point to a different position on the map.

The example below is loaded from the 'Sounding Data (with true winds)' field. If 'Sounding Data (Temperature & dewpoint only)' was selected, then wind data will not be included in the display. Therefore, there will be no barbs along the side of the sounding in the Sounding Chart tab, the Hodograph tab will not be available, and there will be no wind information listed in the Table tab. For more information on what wind speeds correspond to each of the wind barbs in McIDAS-V displays, please see the table in the FAQ.

The Sounding Chart tab includes an aerological diagram (e.g., skew-T, Stuve, Emagram):

Image 1: Sounding Display of Model Data
Image 1: Sounding Display of Model Data
Properties

A label above the sounding's chart shows the model, date, and time of the data. The user can modify the individual T and Td profiles on the skew T by clicking and dragging the profile lines. Changes in the parameter table to the left of the Skew-T will be made to reflect modifications made to the sounding.

The Hodograph tab shows a 3D hodograph display. Note that this tab is only included with the display if a Field that includes wind data was selected:

Image 2: Hodograph Display of Model Data
Image 2: Hodograph Display of Model Data
Properties

The hodograph is enabled if the plotted data includes wind fields. It can be rotated into 3D by right-clicking and dragging. The user can zoom in/out by holding down Shift and right-clicking and dragging up/down or by using the scroll wheel on the mouse. To reset the hodograph, use Ctrl+R.

The Table tab shows a table of all available values in the sounding. The user can invert the order of the table by double clicking on the name of a column (ex. AirPressure).:

Image 3: Table Display of Model Data
Image 3: Table Display of Model Data
Properties
Aerological Parameters

The table to the left of the sounding diagram contains aerological parameters determined from the atmospheric sounding displayed in the diagram. The following abbreviations are used:

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The File menu has this unique option:

The Edit menu has these unique options:

The View menu has these unique options:


Hovmoller Controls
Overview

The Hovmoller display plots grid, gridded point, and satellite imagery data in a diagram with the Latitude/Longitude component on the X-axis, and the time component on the Y-axis. This display option is found in the Displays menu of the Field Selector tab of the Data Explorer. The data can be displayed as Time with respect to either Latitude or Longitude, and either as a Color Shaded or Contour display type.

Image 1: Hovmoller Display
Image 1: Hovmoller Display
Properties

By default, if a Longitude display is selected, the entire spatial domain will be utilized, and the longitude range will go from the western extent to the eastern extent of the domain. The latitude will be averaged from the northern to southern boundaries of the domain. The user can restrict the latitude and longitude domain by selecting a region in the Region tab of the Field Selector tab of the Data Explorer. The Latitude displays work the same way, by averaging the longitude across the entire domain unless a region was subsetted.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple of options unique to this display.

The Edit menu has this unique option:

The View menu has this unique option:


Grid Trajectory Controls
Overview

The Grid Trajectory display types are capable of working with gridded data containing u and v-wind components, as well as a scalar quantity to color them by. Both 2D and 3D trajectories can be created dependent on the fields contained in the data. The relevant display types are:

The Grid 2D Trajectory or Grid 3D Trajectory formulas can be used to access these display types. The formulas will request for all of the fields to pass through it, including the u- and v-wind components, the vertical component, and a color-by component. An alternative to the formulas is utilizing the derived 2D and 3D fields of the data, Grid 2D Trajectory and Grid 3D Trajectory. When using these fields, all the user needs to specify is the scalar quantity when using the Trajectory Colored by Another Parameter display type, and McIDAS-V will pull out the relevant u- and v-wind components (as well as the vertical component when creating 3D Trajectories).

After clicking Create Display and choosing the field(s), the Layer Controls tab of the Data Explorer will appear, where various properties of the trajectories can be set:

Image 1: Grid Trajectories Layer Controls
Image 1: Grid Trajectories Layer Controls
Properties

Once Create Trajectory Button is clicked to display the trajectories, the options in the Layer Controls will expand to include more controls:


Image 2: Grid Trajectories Layout Tab
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple of options unique to this display.

The File menu has these unique options:


Theta Surface Controls
Overview

The Theta Surface display types are capable of working with gridded data containing a theta (potential temperature) component, as well as a scalar and/or vector components for different displays. The display types available are dependent on the derived field selected. The relevant derived fields and their respective display types are:

The Grid 2D Trajectory or Grid 3D Trajectory formulas can be used to access these display types. The formulas will request for all of the fields to pass through it, including the u- and v-wind components, the vertical component, and a color-by component. An alternative to the formulas is utilizing the derived 2D and 3D fields of the data, Grid 2D Trajectory and Grid 3D Trajectory. When using these fields, all the user needs to specify is the scalar quantity when using the Trajectory Colored by Another Parameter display type, and McIDAS-V will pull out the relevant u- and v-wind components (as well as the vertical component when creating 3D Trajectories).

Constant Theta Surface Height Plan View

After selecting the "Potential Temperature IsoSurface (from theta)" derived field, clicking Create Display, and specifying the potential temperature value, the Layer Controls tab of the Data Explorer will appear, where various properties of the display can be set. Note that different Constant Theta Surface Height Plan View display types may have different controls:

Image 1: Constant Theta Surface Height Plan View Controls
Image 1: Constant Theta Surface Height Plan View Controls
Properties
3D Theta Surface

After selecting the "Potential Temperature IsoSurface Scalar Analysis (from theta)" or "Potential Temperature IsoSurface Advection (from theta)" derived field, clicking Create Display, and specifying the potential temperature value and vector parameter to plot, the Layer Controls tab of the Data Explorer will appear, where various properties of the display can be set. Note that different 3D Theta Surface display types may have different controls:

Image 2: 3D Theta Surface Controls
Image 2: 3D Theta Surface Controls
Properties
Constant Theta Surface Flow Displays

After selecting the "Potential Temperature IsoSurface Vector Analysis (from theta)", clicking Create Display, and specifying the potential temperature value and vector parameter to plot, the Layer Controls tab of the Data Explorer will appear, where various properties of the display can be set. Note that different Constant Theta Surface Flow Displays display types may have different controls:

Image 3: Constant Theta Surface Flow Display Controls
Image 3: Constant Theta Surface Flow Display Controls
Properties
Menus

Many of the menu items seen utilizing these displays are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple of options unique to these displays.

The Edit menu can have these unique options:

The View menu has these unique options for all display types:


Satellite and Radar Displays

Image Controls
Overview

The Image Controls are used to adjust displays of satellite imagery. The control window generally consists of two tabs: Settings and Histogram.

The Settings tab allows you to customize many aspects of the appearance of your display. Note that the items in this control may be different depending on which display type you select:

Image 1: Settings Tab of the Image Controls Properties Dialog
Image 1: Settings Tab of the Image Controls Properties Dialog
Properties

The Histogram tab allows you to visualize a histogram of your Satellite data:

Image 2: Histogram Tab of the Image Controls Properties Dialog
Image 2: Histogram Tab of the Image Controls Properties Dialog

There are many ways that you can customize this histogram. If you right-click on the histogram and select Properties, you can get to a Plot Properties dialog which allows you to change many aesthetic properties of the histogram. You can also modify the display in the Main Display window through the Histogram tab. You can do this by left-clicking and dragging from left to right to zoom in over your desired range of data values. Once you are done zooming in, the display in the Main Display window will modify to use a color bar range that matches the boundaries of the zoom box you created in this tab. To return to the original data range, use the Reset Button button.

Image Display Over Topography

One of the display types in the Displays subset panel of the Field Selector is Image Display Over Topography. This display type differs from the other Imagery display types because it allows you to create a 3D display of your satellite image. In order to utilize this display type, you must have both the satellite data and a separate data source for topography. One example of a topographic data source is the 2D->Geopotential_height @ surface field of GFS CONUS model data.

To use this display type, select your satellite field, the Image Display Over Topography display type, and click Create Display. This will open a Field Selector window, prompting for your topography field. Once you select your topography field and click OK, a 3D display of your satellite image draped over topography will be displayed. You can rotate the image in the Main Display window using right-click and drag to visualize the 3D aspects of the display. You can also make the topographic features stand out more or less by using the Vertical Range item in the Viewpoint Toolbar in the Main Display window. Lowering the Max value field of the Vertical Range window will make tall features (ex. mountains) appear even taller.

The Layer Controls tab of the Data Explorer for this display type does not include a Histogram tab. The controls in this tab are Color Table, Pixel Sampling, and Texture Quality, which are described in the Properties section above.

Note: In order to get this display type to show 3D topographic features, the entire domain of your satellite data must lie within the domain of your topographic field. For example, if you are working with a full disk satellite image, but you only have topographic data over the United States, you must subset a satellite region over the United States in the Region tab of the Field Selector before creating the display. If you do not do this, the image will display entirely in the 2D and not show any topographic features.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


HYDRA Layer Controls

MultiSpectral Display Controls
Overview

HYDRA MultiSpectral Display controls are used to create a multispectral display within McIDAS-V. There are two sets of controls, the MultiSpectral Display and the MultiSpectral Probes. The Multispectral Display consists of three tabs: Display, Settings, and Histogram.

The Display tab shows the spectra. This may differ if the data source is Hyperspectral data or Multispectral data due to the number of bands included with the data. Hyperspectral data will have a spectra drawn as a line, while multispectral data will show a variety of points:

Image 1: Display Tab of the MultiSpectral Display Controls Window for Hyperspectral Data
Image 1: Display Tab of the MultiSpectral Display Controls Window for Hyperspectral Data
Image 2: Display Tab of the MultiSpectral Display Controls Window for Multispectral Data
Image 2: Display Tab of the MultiSpectral Display Controls Window for Multispectral Data
Properties

Use the Shift+left click+drag combination to create a box of a region to zoom in on. To return to the full spectra, use Ctrl+left click. Middle-clicking on a point in the spectra will change the wavelength/wavenumber of the image displayed. Right click+drag will translate the spectra left or right. Left click+drag on the green wavelength/wavenumber selector bar will allow for changing the wavelength displayed in the image. When dragging the selector bar, the wavelength/wavenumber will be displayed in the upper left corner of the spectra window for the current location of the the bar.

The Settings tab shows the settings for this display control and the readout probes:

Image 3: Settings Tab of the MultiSpectral Display Controls Window
Image 3: Settings Tab of the MultiSpectral Display Controls Window
Properties

The Histogram tab shows the histogram of the data for the image:

Image 4: Histogram Tab of Multispectral Display Controls Window
Image 4: Histogram Tab of the MultiSpectral Display Controls Window

Zoom in by left-clicking and dragging on the histogram, or enter in a set of minimum and maximum values.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Linear Combination Controls
Overview

The Linear Combinations controls are used to create and perform functions beyond the standard arithmetic functions in McIDAS-V. The Console tab consists of two parts - The Spectra and the Console:

Image 1: Linear Combination Controls Window
Image 1: Linear Combination Controls Window

The Console allows a user to define multiple spectra and perform more complex mathematical operations.

Command line functions
Linear Combination Properties

4 Channel Combination Controls
Overview

The 4 Channel Combination controls are used to create a basic linear combination of spectral bands. There are two sets of controls. The top of the controls shows the spectra, while the bottom half gives the linear combination option:

Image 1: Four Channel Combination Controls Window
Image 1: Four Channel Combination Controls Window
Multispectral Display Properties

Use the Shift+left click+drag combination to create a box of a region to zoom in on. To return to the full spectra, use Ctrl+left click. The Middle click+drag probing feature will list the wavelength/wavenumber as well as the reflectance or Brightness Temperature at a point along the spectra. Use the Left click+drag option to move the spectra selector bar(s) to a different value. The new value for where the spectra bar was moved to will be updated in the field at the bottom of the window.

The 4 Channel Combination tool allows for specifying arithmetic expressions for four spectral bands. Use the pull down menus between variables to select the appropriate arithmetic expressions for the equation. To apply a multiplier to any of the variables, change the value ahead of the wavelength/band.


ProfileAlongTrack Controls
Overview

The ProfileAlongTrack display controls are used to display CALIPSO (Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observation), CloudSat, and HSRL2 (High Spectral Resolution Lidar 2) lidar data, including backscatter and reflectivity. These lidar files should be loaded through the General->Files/Directories chooser with the HYDRA data source Data Type. There are a variety of formats of these data. Below is a sample list of file names from each satellite/instrument that are currently supported:

Once the data source has been added to the Field Selector and a field has been selected, a Track subsetting tab will appear that allows for setting several options for the display of the data:


Image 1: ProfileAlongTrack subsetting tab
Track Subset Tab Properties

Dependent on the field selected to be displayed, the Layer Controls tab of the Data Explorer may have only a Settings tab or tabs for both Settings and Display.


Satellite Orbit Track Controls
Overview

The controls for the Satellite Orbit Track display are used to adjust image displays of orbit track data:

Image 1: Satellite Orbit Track Controls Window
Image 1: Satellite Orbit Track Controls Window
Properties

WSR-88D Level III Controls
Overview

The controls for Level III Radar imagery are similar to the standard Image Controls and are used to adjust image displays of this Radar imagery. The control window consists of two tabs: Settings and Histogram.

The Settings tab allows for customizing many aspects of the appearance of the display:

Image 1: Settings Tab of the WSR-88D Level III Controls Window
Image 1: Settings Tab of the WSR-88D Level III Controls Window
Properties

The Histogram tab allows for visualizing a histogram of the Radar data:

Image 2: Histogram Tab of the WSR-88D Level III Controls Window
Image 2: Histogram Tab of the WSR-88D Level III Controls Window

There are many ways that the histogram can be customized. If right-clicking on the histogram and selecting Properties opens a Plot Properties dialog which allows for changing many aesthetic properties of the histogram. The Main Display window can also be modified through the Histogram tab. This can be done by left-clicking and dragging from left to right to zoom in over the desired range of data values. Once zooming in has been completed, the display in the Main Display window will modify to use a color bar range that matches the boundaries of the zoom box created in this tab. To return to the original data range, use the Reset button button.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Level 2 Radar Layer Controls

Radar Sweep View Controls
Overview

The Radar Sweep Controls are used to control displays of single level sweeps of radar data, and their display appears in the Main Display window. WSR-88D Level II radar data has three moments or display types: Reflectivity, RadialVelocity, and SpectrumWidth, indicated by the Display Type icon icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and DifferentialPhase.

The controls are identical for 2D and 3D displays:

Image 1: Level II Radar Sweep Controls Properties Dialog
Image 1: Level II Radar Sweep Controls Properties Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has this unique option:

The View menu has this unique option:


Radar RHI Display Controls
Overview

The RHI (Range-Height Indicator) display appears in the Main Display window and as a 2D plot in the Layer Controls tab. WSR-88D Level II Radar data has three moments or data types: Reflectivity, Radial Velocity, and Spectrum Width, indicated by the Level II Radar moment button icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and Differential Phase. In order for RHI to be listed as a valid Display Type in the Field Selector, one of the moments (ex. Reflectivity, RadialVelocity, etc.) must be chosen in the Fields panel, not one of their individual elevation angles. The control window contains two tabs, Display and Settings.

The Display tab shows the RHI in 2D:

Image 1: Display Tab of the Radar RHI Display Controls
Image 1: Display Tab of the Radar RHI Display Controls
Properties

The Settings tab shows settings to control the display:

Image 2: Settings tab of the Radar RHI Display Controls
Image 2: Settings Tab of the Radar RHI Display Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple of options that are unique to this display.

The View menu has this unique option:

The Edit menu has this unique option:


Radar Cross Section Controls
Overview

The radar vertical Cross Section Control is used to adjust vertical cross section displays of Level II Radar volume data. WSR-88D Level II Radar data has three moments or data types: Reflectivity, Radial Velocity, and Spectrum Width, indicated by the Radar Moments button icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and Differential Phase. In order for Radar Cross Section to be listed as a valid Display Type in the Field Selector, one of the moments (ex. Reflectivity, RadialVelocity, etc.) must be chosen in the Fields panel, not one of their individual elevation angles. The control window has two tabs, Display and Settings.

The Display tab includes a duplicate of the display in the Main Display window:

Image 1: Display Tab of the Radar Cross Section Controls
Image 1: Display Tab of the Radar Cross Section Controls
Properties

The Settings tab shows the settings for this Layer Control:

Image 2: Settings Tab of the Radar Cross Section Controls
Image 2: Settings Tab of the Radar Cross Section Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Radar CAPPI Display Controls
Overview

The CAPPI (Constant Altitude Plan Position Indicator) Radar display appears in the Main Display window. WSR-88D Level II Radar data has three moments or data types: Reflectivity, Radial Velocity, and Spectrum Width, indicated by the Level II Radar moments icon icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and Differential Phase. In order for CAPPI to be listed as a valid Display Type in the Field Selector, one of the moments (ex. Reflectivity, RadialVelocity, etc.) must be chosen in the Fields panel, not one of their individual elevation angles.

The CAPPI Radar displays data at a constant altitude around the Radar site:

Image 1: CAPPI Display in the Main Display Window
Image 1: CAPPI Display in the Main Display Window

The Layer Controls tab of the Data Explorer allows for several ways to customize the image or loop displayed:

Image 2: CAPPI Layer Controls Properties Dialog
Image 2: CAPPI Layer Controls Properties Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Radar Volume Scan Controls
Overview

The radar volume scan controls are used to show a radar volume as a series of nested cones. WSR-88D Level II Radar data has three moments or data types: Reflectivity, Radial Velocity, and Spectrum Width, indicated by the Level II Radar moment button icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and Differential Phase. In order for Radar Cross Section to be listed as a valid Display Type in the Field Selector, one of the moments (ex. Reflectivity, RadialVelocity, etc.) must be chosen in the Fields panel, not one of their individual elevation angles.

Image 1: Radar Volume Scan Controls Properties Dialog
Image 1: Radar Volume Scan Controls Properties Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Radar Isosurface Controls
Overview

Displays of Level II isosurfaces are controlled by the Isosurface controls. The Radar Isosurface display type allows for visualizing radar data in the 3D, including all elevation angles, at specific data values. An example of when this display type can be useful is for looking for only very high reflectivity values that may coincide with a hail spike. WSR-88D Level II Radar data has three moments or data types: Reflectivity, Radial Velocity, and Spectrum Width, indicated by the Level II Radar moment icon icon in the Field Selector. WSR-88D Dual Pole radar includes these three moments, as well as DifferentialReflectivity, CorrelationCoefficient, and Differential Phase. In order for Radar Isosurface to be listed as a valid Display Type in the Field Selector, one of the moments (ex. Reflectivity, RadialVelocity, etc.) must be chosen in the Fields panel, not one of their individual elevation angles.

Image 1: Radar Isosurface Controls Properties Dialog
Image 1: Radar Isosurface Controls Properties Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has this unique option:


Probes

Data Probe/Time Series
Overview

The Data Probe/Time Series display shows a time series chart of one or more fields at a single location. It also shows a tabular readout of the value at the current animation time step. In the image below we have a Probe Control showing three parameters: T, RH and windspeed. Their values at the current animation time step are shown in the table and their time series are shown. Note, the T and RH fields are shown in one chart and the windspeed is shown in another chart. There can be any number of fields and any number of charts. The user can configure the layout of the charts, the chart properties and the line properties for each parameter. See the Charts page for more information.

Image 1: Probe Control Window
Image 1: Probe Control Window

A small colored square selector point in the Main Display window shows the location of the data probe. The data probe over the map in the Main Display window can be moved by using left-clicking and dragging. When displaying a 3D field, the data probe can be moved vertically as well. As the selector point is moved, the data in the charts will change to represent the data at the location of the probe.

The table shows the parameters with their values, the level at which the value is sampled, and the type of sampling. At the bottom of the window, the location of the probe is shown in latitude, longitude, and altitude. When surface data is probed the height of the probe point does not matter. The probe can be moved by clicking and dragging it in the Main Display window, or by entering new values into the Lat, Lon, and Alt fields and pressing Enter.

New parameters can be added in a number of ways:

Parameter Properties

These parameter actions can be accessed by right-clicking on the parameter row in the table or through the View->Parameters menu.

Probing on Point Data

When probing on point data, the control will find the closest observation to the probe position and use that data to sample on.

Chart Options
Menu Options

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several menu options that are unique to the Data Probe/Time Series display. These menus are found at the top of the Layer Controls tab of the Data Explorer.

The File Menu has these unique options -

The Edit Menu has these unique options -

The View Menu has these unique options -


Time/Height Controls
Overview

A Time/Height Display is a display of samples of a 3D parameter along a vertical profile line from top to bottom of the available data, with time as the independent coordinate (X-axis). Dependent on the field used in the display, available display options include Contour, Color Shaded, Flow, and Wind Barb Time/Height Displays. Note that the options in the Layer Controls will differ dependent on the field used to create the display.

Image 1: Time-Height Display and Controls Window
Image 1: Time/Height Display and Controls Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Vertical Profile Controls
Overview

The Vertical Profile Display Control shows a plot of any number of field values versus altitude. See the Charts page for more information about customizing the chart. In order to use the Vertical Profile display, the parameter must be 3D data.

Image 1: Vertical Profile Controls Display Window
Image 1: Vertical Profile Controls Display Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Data Transect Controls
Overview

The Data Transect controls are used to adjust data transect displays. The control window includes a display of the profile of the data along the transect. The vertical axis is the parameter value and the horizontal axis is the distance along the transect line. In the Main Display window, a transect selector allows for positioning the location of the transect by dragging the selector points along the line. The control window consists of two tabs, Display and Settings.

The Display tab shows the the profile of the data along the transect:

Image 1: Display tab of the Data Transect Window
Image 1: Display Tab of the Data Transect Window
Properties

The Settings tab contains widgets for changing properties of that display:

Image 2: Settings Tab of the Data Transect Window
Image 2: Settings Tab of the Data Transect Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Mapping Controls

Map Controls
Overview

Maps in McIDAS-V are shown using the Map Display Controls. There are two ways these controls are used: for the default background maps and for a user created map display. The control window is composed of two tabs, Maps and Lat/Lon.

The Maps tab lists the set of available maps. The user has the ability to select which maps are displayed, as well as how they are displayed:

Image 1: Maps Tab of the Map Controls Window
Image 1: Maps Tab of the Map Controls Window
Properties

The Lat/Lon tab allows the user to set the visibility of and control the latitude/longitude lines and labels:

Image 2: Lat/Lon Tab of the Map Controls Window
Image 2: Lat/Lon Tab of the Map Controls Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The File menu has this unique option:

The Edit menu has these unique options:

The View menu has this unique option:


Topography Controls
Overview

The Topography controls allow for displaying topography datasets. These controls are available through the 3D Surface->Topography display type. An example of a field that can utilize this display type is the 2D 'Geopotential Height @ Surface' field in model data. The first image shows the control user interface which allows for customizing many options with this display.

Image 1: Topography Controls Properties Dialog
Image 1: Topography Controls Properties Dialog

This is an example of how the display may appear in the Main Display window:

Image 2: Topography Displayed in the Main Display Window
Image 2: Topography Displayed in the Main Display Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The View menu has these unique options:


Shapefile Controls
Overview

McIDAS-V supports the ability to load and display GIS shapefiles. The user can select and load a shape file (i.e., a file that ends with .shp) from the General->Files/Directories chooser in the Data Sources tab of the Data Explorer using the Shapefile Data Type. The zipped (.zip) version of shapefiles can also be loaded.

Image 1: Display Tab of Shapefile Controls Display Properties Dialog
Image 1: Display Tab of the Shapefile Display Properties Dialog
Properties

For shapefiles that also have a data base file (.dbf), users can control what shape segments are shown with the Filters tab.

Note: McIDAS-V supports a simple XML format for maps. The Shapefile Control can export the displayed shapes in this XML format the File->Save->Export Displayed Shapes... menu.

Image 2: Filters Tab of the Shapefile Display Properties Dialog
Image 2: Filters Tab of the Shapefile Display Properties Dialog
Properties

When the shapefile has an associated data base file (.dbf) a tabular listing of the attributes is shown in the Table tab. Use the Select Fields to Show button to select what fields to show. The table can be exported as a CSV file with the File->Save->Export Table... menu.

Image 3: Table Tab of the Shapefile Controls Properties Dialog
Image 3: Table Tab of the Shapefile Display Properties Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The Edit menu has this unique option:


Observation and Location Controls

Point Data Plot Controls
Overview

The Point Data Plot Control displays a set of observations using a layout model. This control is accessed by selecting the Point Data field and the Point Data Plot display. The control window consists of four tabs: Layout, Times, Plot, and Filters.

The Layout tab allows you to control basics of the display:

Image 1: Layout tab of the Point Data Plot Controls Dialog
Image 1: Layout Tab of the Point Data Plot Controls Dialog
Properties

The Times tab allows you to change the observation times that are shown in the display. By default, data for a single time corresponding to the current animation time will be shown. Using this widget allows you to show data from multiple times at once:

Times tab of Point Data Plot Controls window
Image 2: Times Tab of the Point Data Plot Controls Dialog

Clicking Edit icon opens a Time Settings window that allows you to select specific start and end times:

Image 3: Time Settings Dialog
Image 3: Time Settings Dialog

Properties

The Plot tab provides a time series chart and a data readout table of a selected station. To use this, left-click on a station in the main display. Double-click or right-click and select Add To Chart on a table row to add it to the time series chart. See the Charts page for more information about customizing the chart:

Image 4: Plot Tab of the Point Data Plot Controls Dialog
Image 4: Plot Tab of the Point Data Plot Controls Dialog
Properties

The Filters tab allows you to set individual or multiple filters to specify which data are shown in the Main Display window:

Image 5: Filters Tab of Point Data Plot Controls Dialog
Image 5: Filters Tab of the Point Data Plot Controls Dialog
Properties

As an example, the above image shows two filter expressions, one that states the Temperature Property needs to be greater that 35 F and the other states that the Wind Speed value needs to be greater than 15. The unit of [F] is entered for the Temperature Property. If you do not define a unit after the value, then McIDAS-V will utilize the native unit for the Property. Match all of the filters is selected, meaning only layout models where the Temperature is greater than 35 degrees F and the wind speed is greater than 15 will be plotted in the Main Display window.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The File menu has these unique options:

The Edit menu has this unique option:

The View menu has these unique options:


Point Data List Controls
Overview

The Point Data List Control shows a set of observation data in a textual list format. This control is accessed by selecting the Point Data field and the Point Data List display.

Image 1: Point Data List Window
Image 1: Point Data List Window
Properties

The Select Fields button button opens a Field Selector window that allows for determining which fields are included in the table:

Image 2: Field Selector Window to Add or Remove Fields from the Point Data List Window
Image 2: Field Selector Window to Add or Remove Fields from the Point Data List Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The File menu has this unique option:


Gridded Point Data
Overview

McIDAS-V can create gridded fields of numeric data using the Barnes Objective Analysis. You can control the parameters used to create the grid from the Data Source Properties or using the Grid Parameters tab in the Data Subset panel of the Field Selector. Note that since this gridded display will utilize point observation data, the display over areas with few observations (ex. open ocean) may not correctly represent the actual data over that region. Also note that with certain point netCDF files where each data point has a different time, time binning must be applied to the data source before the display is created to group multiple times of data into the same timestep for gridded displays to be created. To get more exact gridded displays of point data, it is best to utilize the Region tab to subset an area of interest with a relatively high density of point observations:

Image 1: Gridded Point Data in the Field Selector
Image 1: Gridded Point Data in the Field Selector

The resulting grid can be displayed using any of the Gridded Data Displays.

Properties

Sounding Display Controls
Overview

The meteorological sounding display is available for: RAOBs, numerical weather prediction model output, and from a local file that contains aircraft track data. The dewpoint temperature is computed by internal code from temperature and relative humidity grids.

To load sounding data see Choosing RAOB Sounding Data and Displaying Gridded Data. The sounding display consists of a table of aerological (thermodynamic) parameters and three tabs: Sounding Chart, Hodograph, and Table.

The Sounding Chart tab includes an aerological diagram (e.g., skew-T, Stuve, Emagram):

Image 1: Skew-T of Point Data
Image 1: Skew-T of Point Data
Properties

A label above the sounding's chart shows the station number, date, and time of the sounding. When displaying sounding plots made from gridded model output, the position of the sounding is shown in the Main Display window by a solid-color selector point and vertical line. The model-output-based sounding position over the map can be changed by dragging the selector point with the left mouse button.

When displaying a sounding diagram made from gridded numerical weather model output, there is a pull-down selector menu of the model output valid times in the upper right corner.

The animation control buttons are available in either case:

Time Animation widget

To increase precision using the sounding diagram, enlarge the window by dragging on the edges. Zoom in on the sounding diagram by holding down the Shift key and dragging the right button upwards; drag downwards to zoom out. Zooming can also be done by using the scroll wheel on the mouse. Pan the diagram by dragging the mouse pointer in any direction while holding down the right mouse button.

The temperature and dewpoint traces can be modified via the cursor. Press the left button on the first data-point to be modified and drag it horizontally along an isobar to the desired position, then move the pointer diagonally along an isotherm to keep the data-point at the desired position and to pick-up the next data-point. Repeat until done and then release the mouse button.

The Hodograph tab shows a 3D hodograph display:

Image 2: Hodograph of Point Data
Image 2: Hodograph of Point Data

The hodograph is enabled if the plotted data includes wind fields. It can be rotated into 3D by clicking and dragging the right mouse button. Zoom in/out by holding down Shift and right-clicking and dragging up/down or by using the scroll wheel on the mouse. To reset the hodograph, use Ctrl+R.

The Table tab shows a table of all values in the sounding:

Image 3: Table of Point Data
Image 3: Table of Point Data
Properties
Aerological Parameters

The table to the left of the sounding diagram contains aerological parameters determined from the atmospheric sounding displayed in the diagram. The following abbreviations are used:

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The File menu has this unique option:

The Edit menu has these unique options:

The View menu has these unique options:


Front Controls
Overview

The Front Controls shows a list of the different weather features (high and low pressures, fronts, etc.) shown in the Main Display window in a textual list format. This control becomes available once the Front Positions data source has been added:

Image 1: Front Display Controls Window
Image 1: Front Display Controls Window
Properties

Double-clicking on an item in this window open the Properties Editor for that item. This window consists of two tabs: Properties and Points:

The Properties tab allows for changing general characteristics of the display. Note that the options that appear in this tab may differ depending on what feature's properties are being viewed:

Image 2: Properties Tab of the Properties Window
Image 2: Properties Tab of the Properties Window
Properties

The Points tab provides information about the location of the selected feature:


Image 3: Points Tab of the Properties Window
Properties
Menus

All of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page.


Location Controls
Overview

McIDAS-V provides a collection of locations. These may be NEXRAD stations, states, counties, geographical features, countries, etc. The Location Controls are used to display these locations. The list of locations is accessed through the Display->Plot Location Labels... menu item in the Main Display window. Local files can also use these location controls. The user interface consists of four tabs: Display, Locations, Data Sets, and Filters.

The Display tab allows the user to control how the display will appear in the Main Display window:

Image 1: Display tab of the Location Controls Dialog
Image 1: Display Tab of the Location Controls Dialog
Properties

The Locations tab shows two sub-tabs, All Locations and Displayed Locations. Shown at the bottom are the details of a location:

Image 2: Locations Tab of the Location Controls Dialog
Image 2: Locations Tab of the Location Controls Dialog
Properties

The Data Sets tab lists all of the location files that are being displayed. A data set can be removed by clicking on the data set and pressing Delete:

Image 3: Data Sets tab of Location Controls Dialog
Image 3: Data Sets Tab of the Location Controls Dialog

The Filters tab allows for filtering what locations are being shown based on their internal attributes:

Image 4: Filters Tab of the Location Controls Dialog
Image 4: Filters Tab of the Location Controls Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Track Controls
Overview

The track controls display trajectory data sets, e.g., aircraft track, ship, buoys, etc. This data can be loaded in the General->Files/Directories chooser of the Data Sources tab of the Data Explorer, with the Data Type of Track files. The data can be displayed in the form of a chart, table, track, or as a Point Data Plot drawn in the Main Display window. The items in the Layer Controls for a Point Data plot are the same as the controls for displaying regular Point Data. If working with data for a lot of times, or have many parameters included with the data, the user may be prompted to subset the point data. This gives the option of only including the necessary fields to cut down on memory usage and time to display the data.

To draw a track in the Main Display window, select the field in the Fields panel, the Track Colored By Parameter display type, and hit Create Display. These same controls are utilized for the Trajectory Colored By Parameter display type. The track controls consist of two tabs, Layout and Times.

The Layout tab controls the appearance of the display:

Image 1: Layout Tab of the Track Controls Dialog
Image 1: Layout Tab of the Track Controls Dialog
Properties

The second tab controls the Times used for the display:

Image 2: Times Tab of the Track Controls Dialog
Image 2: Times Tab of the Track Controls Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one item that is unique to this display.

The Edit menu has this unique option:

The View menu has this unique option:


Miscellaneous Controls

Scatter Analysis Controls
Overview

The Scatter Analysis controls are used to create a scatter plot within McIDAS-V. The scatter controls show three different panels:

Image 1: HYDRA Scatter Analysis Display
Image 1: HYDRA Scatter Analysis Display

The plot on the first panel on the left represents the first field selected in the Field Selector, the panel in the middle represents the second field which is selected through the Field Selector window, and the panel on the right is the scatter analysis of the two fields. The first field selected is represented on the X-axis (abscissa) and the second field selected represents the Y-axis (ordinate). The X-axis is selected in the Field Selector - the channel selected in the lower right Channels tab will be used as the X-axis.

Regions can be subsetted in any of the three panels, and the equivalent points will also be selected in the other two panels. For example, if a box is drawn in panel 1, the same box will be drawn in panel 2, and the points in these boxes will be colored the same in panel 3, the scatter analysis. To draw a box, select a Box radio icon and a color and use Shift+left-click and drag to select a region. Any enclosed shape can be drawn by selecting the Curve radio button and a color and using left-click and drag in any panel to select a region. A user is allowed one box and one curve per color in the scatter analysis (panel 3), and one box and one curve for the images (panels 1 and 2). To remove a region that has been subsetted, double-click on the color of the region to remove next to the Box/Curve radio buttons.

Right-click on the color bar below the images to open the Color Table Editor, change the range, select other color tables, etc.

Under the scatter analysis, there is a Background Color option that allows for setting the background color of the scatter analysis. This defaults to black. When white is selected, the background will be come white and the scatter plot axes and labels will change to black.

To the right of the Box/Curve options, there is a Compute Statistics button button. Clicking this button will Scatter Statistics window that will list statistical information about the data as a whole, as well as the regions of the data that were subsetted with a box/curve. The values in the white columns are computed for the image as a whole, and the values in the colored columns are computed for the area of the respective box/curve.

Image 2: HYDRA Scatter Statistics Window
Image 2: HYDRA Scatter Statistics Window
Properties
Menus

All of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page.


Grid Table Controls
Overview

The Grid Table display in creates a table in the Layer Controls tab of the Data Explorer. This chart plots the numerical value of the selected field at every latitude and longitude point. The user can change the order of the items in this chart by Latitude, Longitude, or field values by clicking on the title of the respective column in the table. This will change the order of the table to go from lower to higher values, or higher to lower values.

Image 1: Grid Table Display
Image 1: Grid Table Display
Properties
Menus

All of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page.


Omni Controls
Overview

The Omni controls consist of a VisAD Spread Sheet, loaded with the parameter selected and its coordinates and units. The Spread Sheet is used to create a display where the user has complete control over which coordinates are the axes, how it is colored, and so on. Use of the VisAD Spread Sheet is not described here. See the VisAD Spread Sheet document at https://www.ssec.wisc.edu/~curtis/ss.html.

Image 1: Omni Controls Windows
Image 1: Omni Controls Windows
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The Edit menu has this unique option:


Jython Controls
Overview

The Jython Controls allow for the development of custom layer controls written in Jython. The controls operate in two modes.

First is the "developer" mode. Here the developer can create a Jython Control; specify the name of the display, any data categories, and the probe type; and write the Jython that creates a GUI and responds to data, animation time and probe position changes.

The default Jython code has examples of accessing data, etc.

The second mode is "user" mode. In developer mode the user can write out an specification of the Jython Control to a plugin through the File->Save->Write to Plugin menu. This plugin, when loaded, will only show the user interface that is created by the developer-written Jython.


Contour Properties Editor

The Contour Properties Editor is invoked from any contour display control with the Contour: Change button or through the Edit->Change Contours... menu item in the Layer Controls tab of the Data Explorer. Use the items in this window to set contouring properties.

Image 1: Contour Properties Editor
Image 1: Contour Properties Editor
Properties

Properties Dialog

The Properties dialog is accessed by right clicking on a layer in the Legend of the Main Display window, and selecting Edit->Properties menu item. This dialog can also be accessed in the Layer Controls tab of the Data Explorer, by clicking the Display Controls button button at the bottom of the tab. The Properties dialog consists of a Settings tab, and possibly others depending on item being displayed:

Image 1: Layer Control Properties Dialog
Image 1: Layer Control Properties Dialog
Properties

There may be other tabs shown, depending on the display. For example, the Color Scale tab allows for the configuration of where the color scale bar is shown. The Spatial Subset tab allows for defining further spatial subsetting of the data.


Color Scale

For those controls that include color tables, the color scale can be displayed in the Main Display window. Use the Edit->Properties->Color Scale menu in the Layer Controls tab of the Data Explorer to configure the visibility, positioning, and labeling of the color scale.

Image 1: Color Scale Properties Dialog
Image 1: Color Scale Properties Dialog
Properties

Charts
Overview

There are many different sources of data that can make use of the charting facility in McIDAS-V. It is possible to use the charting facility to display the data by selecting Data Probe/Time Series in the Displays menu in the Field Selector tab of the Data Explorer. The chart will be plotted in the Layer Controls tab, while a square representing the location of the probe will be shown in the Main Display window. The location of the probe can be changed by left-clicking on the probe and dragging it.

There are four levels of configuration available to the user, as well as several unique menu options for this display.

Chart Line Properties

At the lowest level, the user can set the properties of how each parameter or field is shown. This is done through the Chart Line Properties dialog, which is opened by right-clicking on the parameter below the chart and selecting Chart Properties.

Image 1: Chart Line Properties Dialog
Image 1: Chart Line Properties Dialog
Plot Properties

For each individual plot, there are a number of settings that can be changed through the Plot Properties dialog. This is also accessed through the View->Chart->Chart:->Properties... menu item.

Image 2: Data Probe Properties Dialog
Image 2: Data Probe Properties Dialog

When right-clicking on a chart, the user can also zoom in and out and save the chart as an image. There are also a number of key and mouse bindings on the chart:

Chart Properties

There are several chart properties that can be changed through the Chart Properties dialog box. This is accessed by right clicking on the chart and selecting "Properties." The Chart Properties dialog box consists of three tabs: Title, Plot, and Other. The Plot tab includes three tabs within itself: Domain Axis, Range Axis, and Appearance.

The Title tab sets the chart's title and its attributes.

Image 3: Title Tab of the Chart Properties Dialog
Image 3: Title Tab of the Chart Properties Dialog

The Domain Axis tab allows for customization of the domain axis.

Image 4: Domain Axis Tab in the Plot Tab of the Chart Properties Dialog
Image 4: Domain Axis Tab in the Plot Tab of the Chart Properties Dialog

The Range Axis tab allows for customization of the range axis.

Image 5: Range Axis Tab in the Plot Tab of the Chart Properties Dialog
Image 5: Range Axis Tab in the Plot Tab of the Chart Properties Dialog

The Appearance tab has several options to change the appearance of the plot.

Image 6: Appearance Tab in the Plot Tab of the Chart Properties Dialog
Image 6: Appearance Tab in the Plot Tab of the Chart Properties Dialog

The Other tab sets general chart properties.

Image 7: Other Tab of the Chart Properties Dialog
Image 7: Other Tab of the Chart Properties Dialog
Chart Layout

With multiple charts, different layouts can be set using the View->Chart->Layout menu item. There are a number of pre-defined layouts: Grid, Vertical, Horizontal, 2 Column, 3 Column, Tabs. The Grid Layout allows for much flexibility in how the charts are organized and laid out. The View->Chart->Layout->Change Grid Layout menu item brings up the Grid Layout Editor:

Image 8: Edit Chart Layout Window
Image 8: Edit Chart Layout Window

Rows and columns can be added/removed with the Plus and Minus button buttons. The user can then drag the graphical representations of the charts to place them in the grid. A chart can also span multiple rows or columns. This is done by grabbing the black square on one side of the chart image and dragging it to change the row or column.

Menu Options

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several menu options that are unique to the Data Probe/Time Series display.

The File menu has these unique options

The Edit menu has these unique options:

The View menu has these unique options:


Ensemble Grid Controls
Overview

The Ensemble Grid feature in McIDAS-V allows for creating a plot of possible forecast scenarios from model data. This plot is produced by adding a perturbation to the initial model solution, and by adding perturbations to every subsequent perturbation. Thus, each perturbation away from the unperturbed initial model output theoretically diverges further from the initial model solution. These perturbations can be the result of slightly different initial conditions or different physics utilized by the model. Ensemble Grid displays are a valuable tool for medium range weather forecasting.

The Ensemble Grid controls are accessed through the Data Explorer window by selecting an ensemble run in the Data Sources tab, and then defining the parameter to display and the output format in the Field Selector. McIDAS-V's ensemble formulas can also be used to display this data.

Image 1: Enxemble Grid Data in the Field Selector Tab of the Data Explorer
Image 1: Ensemble Grid Data in the Field Selector Tab of the Data Explorer

By default, McIDAS-V displays all ensemble members. This can be changed in the Field Selector by selecting the Ensemble tab. A range of ensemble members can be selected with the Shift key, or individual ensemble members with the Ctrl key. The times used to display the data can be changed in the Times tab. When displaying a 3D grid parameter, use the Level tab to select which level(s) to display. A specific region to plot the data can be selected with the Region tab, or select how many data points to plot with the Stride tab. Press Create Display button to plot the data in the Main Display window.

Image 2: Ensemble Grid Data Displayed in the Main Display Window
Image 2: Ensemble Grid Data Displayed in the Main Display Window

There are a variety of ways to customize the display once it has been plotted. These options can be found in the Layer Controls tab of the Data Explorer.

Image 3: Ensemble Grid Controls
Image 3: Ensemble Grid Controls
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple of options that are unique to this display.

The Edit menu has this unique option:

The View menu has this unique option:


Main Display Window
The Main Display window within McIDAS-V contains:

This section describes:

Image 1: McIDAS-V Main Display Window
Image 1: McIDAS-V Main Display Window

Menu Bar
The main menu bar shown at the top of the Main Display window has several different menus associated with it.
File Menu
Edit Menu
Display Menu
The display menu contains facilities in creating new displays.
Tools Menu
This menu allows for configuration and editing of different McIDAS-V resources.
History Menu

This menu lists the recently accessed data sources and layers and allows for them to be reloaded. This includes data sources from the current McIDAS-V session, and from previous sessions.

Bundles Menu
This menu allows for managing and loading favorite bundles.
Window Menu
This menu allows for bringing the Data Explorer for the front, as well as selecting which tab/panel is visible and active in the Main Display window.
Help Menu
This menu allows for viewing the User's Guide, showing error messages, etc.
Main Toolbar

Below the main menus is the Main Toolbar of the Main Display window.

Image 1: Main Toolbar (Default)
Image 1: Main Toolbar (Default)

Many of the more commonly used features of McIDAS-V can be accessed here. Hold the mouse over a toolbar button to get a popup tip on what that button does. The Main Toolbar is user configurable. Right-click on the toolbar to change the icon sizes and select "Customize..." to open the User Preferences' Toolbar Options tab where buttons can be added, removed, or moved in the toolbar.

The Current WX Button button contains a variety of system bundles to demonstrate various functionalities of McIDAS-V. This button appears on the Main Toolbar by default, and can be removed through either the General tab of the User Preferences or through the Local Favorite Bundles Manager. Clicking on this button opens a dropdown with several sample real-time bundles:

Along with the Current WX real-time bundles, there are also a variety of archive bundles that can be added to the Main Toolbar through the Plugin Manager. Under the Sample Bundles tree in the Plugin Manager, there are five separate plugins for bundles that demonstrate many of the same features as the real-time bundles. Once these plugins are added and McIDAS-V is restarted, a toolbar button called Archive WX will be added to the toolbar. This button behaves similarly to the Current WX button, where clicking Archive WX opens a dropdown containing any of the sample bundle plugins that were added. Once these Archive WX bundles are added, they can be removed only through the Plugin Manager.

The Main Toolbar can be undocked from the Main Display window by left-clicking and dragging the textured area on the left side of the toolbar. This will place the Main Toolbar in its own window. To dock the toolbar back into the Main Display window, click the 'x' in the toolbar's window.


Drag and Drop Tabs

McIDAS-V has drag and drop tabs which allows for organizing multiple tabs and windows.

Image 1: Drag and Drop Tabs in the Main Display Window
Image 1: Drag and Drop Tabs in the Main Display Window

Drag and drop tabs allows for separating tabs into individual windows, combining windows into tabs, as well as reorganizing the layout of tabs in a window. Drag tabs into separate windows by using the left-click and drag option to drag the tab outside of the Main Display window. When the last tab in a window is moved into another window, the window will disappear. When tabs are rearranged or added from a different window, green arrows will point to the location the new tab will be placed.

Rename the tab by double clicking on it. Close a tab by clicking on the on the right side of the tab. Closing a tab will remove all layers associated with the display, but will not remove the data sources.

Note: This functionality is not currently available on macOS platforms.


Display Menus

The View and Projections menus are associated with the 3D display and are located in the Main Display window.

View Menu

The View menu lists the displays shown in this window, allows you to change the point of view, capture images and movies, and make some other changes to the overall display.

Projections Menu
The Projections menu lets you change the map projection in the 3 dimensional display.
Properties Dialog

Accessed through the View->Properties menu item of a display panel, this Properties dialog allows for controlling many aesthetic aspects of the display. The Properties dialog window is composed of five tabs: Main, Aspect Ratio, Lighting, Vertical Scale, and Horizontal Scale. If working with a globe display, there is no Horizontal Scale tab, but there is an additional panel in the Main tab for Globe Display.

The Main tab of the Properties dialog allows for changing several general settings pertaining to the display. Many of the items in this tab can also be found in the Display Window tab of the User Preferences window.

Image 1: Main Tab of the Properties Dialog (Default)
Image 1: Main Tab of the Properties Dialog (Default)
Properties

The Main tab of the Properties window for a globe panel has an additional panel for Globe Display. This panel allows for setting the visibility, color, and the vertical positioning of the globe background.

Image 2: Globe Display panel of the Main Tab (Default)
Image 2: Globe Display panel of the Main Tab (Default)
Properties

The Aspect Ratio tab of the Properties dialog allows for changing the aspect ratio of the display with respect to the X, Y, and Z directions. X, Y, and Z values can be changed by using the slider. Any changes will be made to the display with Apply or OK. The Display Matrix Settings panel will actively update as the X, Y, and Z values are changed, and as rotation or zooming is applied to the Main Display window.

Image 3: Aspect Ratio Tab of the Properties Dialog (Default)
Image 3: Aspect Ratio Tab of the Properties Dialog (Default)
Properties

The Lighting tab of the Properties dialog allows for adding the effect of light shining on the display from different angles along the X, Y, and Z axes. The default values are listed in the image below.

Image 4: Lighting Tab of the Properties Window (Default)
Image 4: Lighting Tab of the Properties Dialog (Default)
Properties

The Vertical Scale tab of the Properties dialog allows for changing the vertical scale used for the Z-axis of the display panel.

Image 5: Vertical Scale Tab of the Properties Dialog (Default)
Image 5: Vertical Scale Tab of the Properties Dialog (Default)
Properties

The Horizontal Scale tab of the Properties dialog allows for setting the visibility and properties of the latitude/longitude labels along the outside of the wireframe box.

Image 6: Horizontal Scale Tab of the Properties Dialog (Default)
Image 6: Horizontal Scale Tab of the Properties Dialog (Default)
Properties

Visibility Animation

In the Legend of the Main Display window, the Layer Visibility checkbox to the left of each layer's label can be used to toggle the visibility of that layer. This checkbox can also be selected in the item's Layer Controls tab by selecting View->Visible. Visibility animation cycles through the visibility of each layer, showing them one at a time. This is not a time animation loop; it loops through the visibility of the layers present in the Main Display window.

The padlock icon Lock icon on the right side of each layer in the Legend is used to block the effects of the visibility animation described above. When locked (Lock image), the visibility of the layer is not affected by the animation.

Visibility Animation can be invoked via the Layer Visibility Animations button. You can add this button to your main toolbar in the Toolbar Options tab of the User Preferences window.

Image 1: Animate Visibility Window
Image 1: Animate Visibility Window
Properties

You can also access this tool in the Main Display window through the View->Displays->Visibility Animation menu item. In this menu, you can turn visibility animation on/off, and change the speed of the animation.

As an alternative to the Layer Visibility Animations tool, the function keys F1, F2, F3* can be used to cycle visibility as follows:


Time Animation
Time Animation Widget

Each McIDAS-V display area has a set of time animation controls above the Main Display window.

Time Animation Widget
Image 1: Time Animation Widget

The Time Animation Widget controls looping of displays through time. A series of small green boxes is displayed representing each frame of the animation. The box corresponding to the current time is colored blue. Click on a box to select a different time. Right-click on a box to disable that frame in the animation. Disabled boxes will be colored red. You can also Ctrl+left click on a box to turn on/off all of the frames to the left of the box you clicked on, and Shift+left click to turn on/off all of the frames to the right of the box you clicked on.

The time of the data is displayed in the labeled pull-down list and in the entries of the pull down list on the left. Holding the mouse over the time will show information about how many frames are in the loop, and what the starting and ending times are. The toolbar of button icons, on the right, control time animation. The Time Animation Widget buttons do the following:

Time Animation Properties Dialog

Click on the Properties button in the animation controls to see the Time Animation Properties Dialog box. This dialog has two tabs: Settings and Define Animation Times.

The Settings tab allows for defining how looping will work for the display:

Image 2: Settings Tab of the Time Animation Properties Dialog
Image 2: Settings Tab of the Time Animation Properties Dialog

By pressing Apply button or OK button, the properties will be set in the Animation Widget. If the Save As Default checkbox checked, then the properties will be saved and used every time a new Animation Widget is created. For example, you may find that you are always setting the dwell rate to a particular value. You can save that state as the default state for all Animation Widgets that are subsequently created, both in the current run of McIDAS-V and in future runs.

Properties
Define Animation Times Tab

The Define Animation Times tab allows for defining a custom animation time set:

Image 3: Define Animation Times Tab of the Time Animation Properties Dialog
Image 3: Define Animation Times Tab of the Time Animation Properties Dialog

By default, the times used in the animation time set are all of the times from the data that is being displayed. However, a specific time set can be defined by selecting the Define your own list of times button.

This allows for defining the start time, end time and a time interval. The time interval is used to create the set of time steps (inclusive) between the start and end times. The start time and end time modes are determined one of four ways:

Once the start and end time modes have been set, an offset can be added (or subtracted) to the base time. To change the offset select the Offset button button. When doing this, the Offset dialog will be shown:

Image 4: Set Round To Value Dialog
Image 4: Set Round To Value Dialog

This allows for defining a time offset by entering years, days, hours and minutes. Note that this Offset dialog will also include a +/- option when selected from Start Time or End Time.

The Predefined Button button gives another way to adjust the items in the Define Animation Times tab. The two options from this button are Uniform Across Data Range and Real Time.


Legend

The Legend in the Main Display window lists the set of Layer Controls within that view. The Legend can be floated from the Main Display window. This is done with the Flot Window button Float Window button (the Embed Window button Embed Window button will move the Legend back into the Main Display window).

Image 1: Side Legend in the Main Display Window
Image 1: Side Legend in the Main Display Window

The Legend shows each layer under the Layer Category of that display. For example, the Legend in the above image shows the categories "Maps", "Radar Displays", and "Plan Views". The Layer Category may be changed. This is useful for grouping and controlling the visibility of a group of layers.

The Legend Label shows the parameter or Field name, the display type, and sometimes other information such as the level of a plan view or value of an isosurface. The label may be changed using items under the Edit->Properties menu item. Clicking on the blue, highlighted part of the label will bring up the Layer Controls tab of the Data Explorer. Right-clicking will allow you to open the Layer Controls tab for that parameter, or access the menu options in the Layer Controls tab.

Each layer category within the Legend can be toggled to show or hide the layers under that category with the Toggle Category button. The visibility of the layers under a category (e.g., Radar Displays, Plan Views, etc.) can be changed with the Category Visibility checkbox. The visibility of an individual layer can be changed with the Layer Visibility checkbox.

The Trash can icon Remove button quickly removes a layer. The Lock icon Visibility Toggle Lock "locks" the current visibility of the layer and does not change it while cycling visibilities.

Detailed information about a layer may also be shown in the Legend. For example, for those layers that use a color table, the color bar will also be shown in the Legend. Moving the mouse over the color bar shows intermediate values. Right-click on the color bar to open the Color Table Editor, change the range, select other color tables, etc. You can also modify the color bar interactively for each display.

If using adaptive resolution, certain layers may list out data sampling text above the colorbar, as well as an extra Resolution Control button Resolution Control button to the right of the blue text of the Legend Label for the layer. This button allows for turning adaptive resolution on or off for the layer. This button is only available if adaptive resolution is enabled in the User Preferences. Note that adaptive resolution is still under development. For more information, see Adaptive Resolution.


Modify the Color Bar Interactively

Click the color bar in the Legend to interactively modify the color bar. Holding the cursor over the color bar shows the interactive color bar editor instructions.

Image 1: Interactive Color Bar Editor
Image 1: Interactive Color Bar Editor

These controls are activated once the color bar is clicked on in the Legend.


Status Bar

At the bottom of the Main Display window is a status bar. This bar is useful for seeing how much memory has been used, the current time, what McIDAS-V is doing, as well as the value of the parameter probed in the Main Display window. You can change the panel on the left back and forth between displaying time or memory by left-clicking on the time or memory that is currently being displayed.

Time
Image 1: Time Readout
Image 1: Time Readout

The time displayed in the left panel of the status bar is not the time associated with the data you have loaded into McIDAS-V, but rather the current time in GMT.

Memory
Image 2: Memory Readout
Image 2: Memory Readout

The memory displayed in the left panel of the status bar is in the format of (Currently used memory)/(Max used memory thus far in the session)/(Max memory available for McIDAS-V to use) in MB. You can change the amount of memory allocated by McIDAS-V at startup in the Advanced tab of the User Preferences window. When McIDAS-V has used up the majority of its available memory, the memory panel of the status bar will turn pink and then red. This will cause McIDAS-V to slow down, and may eventually prevent new data sources from being loaded. You can mitigate this problem by right-clicking on the memory and selecting: Clear Memory and Cache. This will clear out some memory so you can still work efficiently in your current session.

Messages
Image 3: Messages Readout
Image 3: Messages Readout

To the right of the Time/Memory readout panel is a Messages readout panel that tells you what McIDAS-V is doing. If no data is being loaded or no data sources are being loaded into McIDAS-V, this panel will be reserved for displaying the Latitude, Longitude, and Altitude information at the location of your cursor over the Main Display window. In the example above, a Grids data source is being loaded from an OPeNDAP server. If you are loading data into McIDAS-V as a loop, the middle message panel will list the data source name and also indicate how much data has loaded. To the right of this message is a loading panel. When data is loading into McIDAS-V, you will see this blue bar move from side to side. When McIDAS-V is completing various processes, different messages may be overlaid on top of this loading bar, including "Reading Data" and "Creating Layers".

Probe Readout
Image 4: Probe Value Readout
Image 4: Probe Value Readout

As a default in the Navigation Controls tab of the User Preferences window, holding down the middle mouse button over your display will probe the data and give a numerical readout of your displayed parameter(s). The probe value(s) will be listed at the bottom of the Probe Readout panel. This panel also lists the location of your mouse when you probe the data with respect to Latitude and Longitude. As a default, this panel will list your data source and the display type. You can change how your data source will be labeled in this panel by right-clicking on the item in the Legend, and going to Edit->Properties.... In the Settings tab of this Properties dialog, you can change the Legend Label to say anything, including adding macros to further customize the readout in this panel.


Zooming, Panning and Rotating

There are several methods to zoom, pan, and rotate in McIDAS-V. You can use the mouse, the arrow keys, a rubber band box, or the Zoom/Pan Toolbar. To reset to the initial base viewpoint use the key combination Ctrl+R.

Note: You need to click in the Main Display window when using key combinations.

Note: If you are using an Apple Mac with a single button mouse, see Apple Mac One Button Mouse Controls.

Zooming
Panning
Rotating
Mouse
Shift-Left Mouse Drag: Select a region by pressing the Shift key and dragging the left mouse button (MB1).
Shift-Right Mouse Drag: Hold Shift key and drag the right mouse button (MB3). Moving up zooms in, moving down zooms out.
Ctrl-Right Mouse Drag: Hold Control key and drag right mouse to pan. Right Mouse Drag: Drag right mouse to rotate. This works for a globe display.
Scroll Wheel
Scroll Wheel-Up: Zoom out.
Scroll Wheel-Down: Zoom in.
  Ctrl-Scroll Wheel-Up/Down: Rotate clockwise/counter clockwise.
Shift-Scroll Wheel-Up/Down: Rotate forward/backward clockwise.
Arrow keys
Shift-Up Arrow: Zoom in.
Shift-Down Arrow: Zoom out.
Ctrl-Up arrow: Pan down.
Ctrl-Down arrow: Pan up.
Ctrl-Right arrow: Pan left.
Ctrl-Left arrow: Pan right.
Left/Right Arrow: Rotate around vertical axis.
Up/Down Arrow: Rotate around horizontal axis.
Shift-Left/Right Arrow: Rotate clockwise/counter clockwise.

The default mouse and keyboard controls can be customized using the User Preferences window's Navigation Controls tab by selecting Edit->Preferences from the main menu.

Apple Mac One Button Mouse Controls

Mouse controls are a bit more challenging if you are running McIDAS-V on a Mac with a single mouse button. The typical left mouse button (MB1) functions are done with a click of the button. Right mouse options (MB3) are simulated using the Option key with a mouse click. Use the following:

There is no replacement for the mouse panning actions on the Mac. Use the keyboard arrow functions or the Viewpoint toolbar instead.

The Viewpoint Toolbar

The Viewpoint Toolbar allows you to quickly switch between different viewpoints, change the perspective of the display, and add rotation.

The Zoom/Pan Toolbar

The Zoom/Pan Toolbar assists in navigating the 3D space.

The Undo/Redo Toolbar

The Viewpoint Undo/Redo buttons allow you to undo/redo any zoom/pan/rotation/projection change made to the display. Note that you can hold down Shift and click these buttons to go forward/back 10 changes at once.


Transect Views

The Transect View is a 2-Dimensional display that shows data along a transect line. This type of view can be created through the File->New Display Tab(Window)->Transect Display menu item in the Main Display window.

Image 1: Transect View of Wind Speed
Image 1: Transect View of Wind Speed

The left vertical axis shows altitude in meters, the right axis shows pressure levels. The bottom horizontal axis shows distance along the transect. The top horizontal axis shows the latitude and longitude locations of the end points of the transect line drawn in the map display. You can zoom and pan in this display with the normal key and mouse combinations. The transect display will also be duplicated in the Layer Controls tab of the Data Explorer.

To work with a transect display, both a transect panel and a map panel must be open. A transect display can be opened in the Main Display window using the File->New Display Tab(Window)->Transect Display menu item to select one through four transect panels. With the transect panel selected, display any 3D data using one of the Vertical Cross Section display types available in the Displays panel of the Field Selector. This will create a display similar to the image above. The transect line used to create this display will be drawn in the map display panel.

To control the location of the transect, select Transects->Edit in the transect panel. This opens a Transect Drawing Control window that allows for modifying the transect lines in the map display. Using the Create a transect mode, click and drag in the map display to draw the transect. The transect drawn in the transect display will be representative of the most recent transect line you have drawn, assuming the Automatically update transects option is selected in the Controls tab of the Transect Drawing Control window. While multiple transect lines can be drawn in the map display, the transect used for the display in the transect panel will be green in color. When multiple transects are drawn in the map display, you can change which transect is being used for the transect display from the Transects menu of the transect display.

In the Transects tab of the Properties dialog for the Transect View (from View->Properties menu item in the transect display window/tab) you can define a maximum distance to show. Normally, data that lies with the bounding lines that are orthogonal to the transect line is shown in this display. The max distance gives a display radius. Data that lies past this max distance is not displayed.

An alternative to having the transect and map panels in different tabs or windows is to use one tab that contains both panels in one. To access this display, in the Main Display window, use File->New Display Tab(Window)->Misc->Transect and Map, 1 Map and 2 Transects, or 2 Maps and 1 Transect. Below is an example showing the 1 Map and 2 Transects panel configuration:

Image 2: Map and Transect Display
Image 2: Map and Transect Display

Display Controls

This section contains information about the different display controls that you can utilize in McIDAS-V. All of these display controls can be found in the menus of the Main Display window.


Range Ring Controls
Overview

The range rings control displays a set of concentric circles labeled by distance from the central point, with radial lines, useful for judging distance and angle from a geographic location. Range rings can be added to the Main Display window with the Display->Add Range Rings menu item. Range rings are often used with radar imagery, but they can be used with any data. The control window is composed of two tabs: Location and Settings.

The Location tab allows for specifying the location to center the range rings:

Image 1: Location Tab of the Range Rings Properties Dialog
Image 1: Location Tab of the Range Rings Properties Dialog
Properties

The Settings tab allows for controlling how the range rings are displayed:

Image 2: Settings Tab of the Range Rings Properties Dialog
Image 2: Settings Tab of the Range Rings Properties Dialog

The range rings are oriented with local north-south on the displayed map projection. In some cases, the eastward radial line may not be horizontal. The range rings will appear centered on the map projection. The range rings can be moved by resetting the latitude-longitude or the station. McIDAS-V can display multiple range rings at once and at any location.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there is one option that is unique to this display.

The Edit menu has this unique option:


Range and Bearing Controls
Overview

The Range and Bearing Controls show the distance, azimuth, and back azimuth of a great circle line connecting two positions on the Earth's surface. This feature can be found in the Main Display window in the Display->Add Range and Bearing menu item.

Image 1: Range and Bearing Properties Dialog
Image 1: Range and Bearing Properties Dialog

When the range and bearing controls are first created, a range and bearing line is added to the Main Display window. The distance, azimuth, and back azimuth values are shown on the Legend and at the top of the Range and Bearing control window. The latitude/longitude position values of the endpoints are shown in the control window. Computations are based on the WGS-84 reference ellipsoid, using computation code from the U.S. National Geodetic Survey. The endpoints can be repositioned by left-clicking and dragging them in the Main Display window, entering new values into the Latitude/Longitude boxes in the control window and pressing Enter or clicking Apply button, or selecting a location in the dropdown menu to the right of the Latitude and Longitude fields.

Note The line shown on the display is not the great circle path connecting the end points. The values are computed for a great circle path on the ellipsoidal Earth, using the numerical latitude and longitude values, not the line on the display. The line shown in the display is a straight line on the map projection; usually it will not coincide with the great circle line.

Note If the projection is changed, an existing range and bearing map line will stay at the same location in the display, hence the end points on the map are in new locations. The distance, azimuth, etc. values in the control window reflect the latitude-longitude positions in the control window and hence do not match the display picture until an end point is moved by hand.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are a couple options that are unique to this display.

The Edit menu has these unique options:


Transect Drawing Controls
Overview

The transect drawing controls are a version of the Drawing Controls that allows you to view, create, and modify the transect lines that are used in the Transect Views. This option can be found in the Main Display window under the Display->Draw Transect menu item or through the Transects menu in the Transect View.

This display control is a representation of the set of transects that are defined by the transect resource. Not only does it have its own state (that can be saved in a bundle, for example), but it also writes out any transects you may create or change into your local McIDAS-V state directory in a transects.xml file. This transects.xml file (if one is created) is carried over from session to session. Therefore, if you draw transects in one session and save the transects (via the File->Save or Automatically update transects items), the same transects will appear in subsequent sessions when you open the Transect Drawing Control widget.

In this control, there is only one shape that you can draw, a Transect Line. This control also shows a non-editable Transect Shape which displays the full transect line used by any Transect Views, called the "Active Transects". There are also a set of transect lines that are non-editable that are from the system transects property. For an active transect, if the Transect View that it represents has a max distance set then the transect will show this max distance as a rectangular box.

The Transect Drawing Control window consists of three tabs: Controls, Style, and Shapes.

The Controls tab allows for the user to draw features in the Main Display window:

Image 1: Controls Tab of the Transect Drawing Control Properties Dialog
Image 1: Controls Tab of the Transect Drawing Control Properties Dialog
Properties

The Style tab controls the appearance of the transect lines in the Main Display window:

Image 2: Style Tab of Transect Drawing Control Properties Window
Image 2: Style Tab of the Transect Drawing Control Properties Dialog
Properties

These menu options apply to the shapes listed in the Controls tab. Once modifications have been made in this tab, they will be applied to the next transect you draw in the Main Display window, without changing any transects already created. Note that Font and Justification are not valid options for this control, since there is no text component in the Controls tab.

The Shapes tab lists all of the graphical elements:

Shapes tab of the Transect Drawing Control window
Image 3: Shapes Tab of the Transect Drawing Control Properties Dialog
Properties

Double-clicking on an element in the Shapes tab will show its properties editor, which consists of two tabs: Properties and Points.

The Properties tab gives general information about each transect:

Image 4: Properties Tab of the Properties Dialog
Image 4: Properties Tab of the Properties Dialog
Properties

The Points tab gives general information about each shape:

Image 5: Points Tab of the Properties Dialog
Image 5: Points Tab of the Properties Dialog

You can modify a latitude/longitude value here by double-clicking in one of the cells for latitude or longitude, entering a new value, clicking in another cell, and clicking Apply or OK. The new latitude/longitude values will be applied to the endpoints of your transect line in the Main Display window.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options that are unique to this display.

The File menu has these unique options:

The Edit menu has these unique options:


Drawing Controls
Overview

The drawing controls consists of a drawing editor that supports polygons, lines, shapes and text. This tool allows for creating and moving graphics in the Main Display window. Drawing and selecting in 3D can be difficult and sometimes it is best to be in the main overhead view. This feature can be found in the Main Display window in the Display->Draw Freely menu item.

The Drawing Control window consists of three tabs: Controls, Style, and Shapes.

The Controls tab is used to draw features in the Main Display window:

Image 1: Controls Tab of the Drawing Controls Dialog
Image 1: Controls Tab of the Drawing Control Dialog
Properties

The Style tab controls the style that the drawings take in the Main Display window:

Image 2: Style Tab of the Drawing Control Dialog
Image 2: Style Tab of the Drawing Control Dialog
Properties

These menu options apply to the shapes listed in the Controls tab, excluding the High/Low pressures/fronts. Once modifications have been made in this tab, they will be applied to the next shape you make in the Main Display window, without changing any shapes already created.

The Shapes tab lists all of the graphical elements:

Image 3: Shapes Tab of the Drawing Control Dialog
Image 3: Shapes Tab of the Drawing Control Dialog
Properties

This tab lists out the different shapes drawn in the Main Display window from the Controls tab, as well as other information about them.

Double-clicking on an element in the Shapes tab will open its Properties Editor, which consists of two tabs: Properties and Points.

The Properties tab gives general information about each shape:

Image 4: Properties Tab of the Properties Dialog
Image 4: Properties Tab of the Properties Dialog

This tab allows you to control many aspects of the individual shapes. After making any modifications to this window, click Apply or OK, and the changes will be applied to the shape in the Main Display window. When editing the properties of a High or Low shape, there is the ability to change these shapes to 'A' (Spanish 'Alto' for High) or 'B' (Spanish 'Bajo' for Low). Note: The different types of shapes will have different menu options.

Properties

The Points tab gives general information about each shape:

Image 5: Points Tab of the Properties Dialog
Image 5: Points Tab of the Properties Dialog

This tab lists out location coordinates of your shape. The points listed can be seen in the Main Display window, and are represented by the pink squares along the boundaries of the shape. These values can be changed by double clicking on a coordinate, and typing in a new value. Once you click on a different coordinate, and then press Apply or OK, the change will be made in the Main Display window.

Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options that are unique to this display.

The File menu has these unique options:

The Edit menu has these unique options:


Location Indicator Controls
Overview

The location indicator controls display a configurable axis in the Main Display window and (optionally) a bearing point. This option can be found in the Main Display window under the Display->Add Location Indicator menu item. The Location Indicator window consists of three tabs: Location, Settings, and Orient.

The Location tab displays and allows for modifying the position of the origin and the bearing point:

Image 1: Location Tab of the Location Indicator Dialog
Image 1: Location Tab of the Location Indicator Dialog
Properties

The center point of the Location Indicator can be moved by left-clicking and dragging on the lines produced in the Main Display window. The user can also move the center point of the Location Indicator with a series of Ctrl+Alt key combinations.

The Settings tab allows for the configuration of display settings:

Image 2: Settings Tab of the Location Indicator Dialog
Image 2: Settings Tab of the Location Indicator Dialog
Properties

The Orient tab allows for the orienting the display based on the location. To change the origin, click and drag in the main display. To show and/or change the bearing point, do a Control+drag in the Main Display window. The x/y/z locations of the bearing point are shown on the origin axis as tick marks and, optionally, as longitude/latitude/altitude readouts:

Image 3: Orient Tab of the Location Indicator Dialog
Image 3: Orient Tab of the Location Indicator Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has this unique option:

The View menu has these unique options:


Web Map Server(WMS)/Background Image Controls
Overview

The WMS Controls display imagery from WMS servers. A set of predefined links to WMS servers for topographic, shaded relief and aerial imagery is also provided with the Background Image control.

To use the pre-defined background images, in the Main Display window, select the Display->Add Background Image menu item. To choose imagery from web map servers, bring up the Catalog Chooser in the Data Explorer and enter the URL that points to the Capabilities document of the desired WMS. We also provide links to a set of useful WMSs from the idvcatalog. If it is not in the Catalog pull down menu, enter the following URL:

https://www.unidata.ucar.edu/georesources/idvcatalog.xml

From this catalog open the Web Map Servers tab and select the WMS to access.

The WMS Controls makes a request to the Web Map Server for an image that covers the area currently being displayed in the Main Display window. Due to the time it takes to access remote servers, the WMS Control does not request new images while the user pans and zooms.

Image 1: WMS Control Dialog
Image 1: WMS Control Dialog
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options that are unique to this display.

The File menu has this unique option:

The View menu has these unique options:


QuickTime Movie Controls
Overview

McIDAS-V can display QuickTime movies. The user can pause, single step and play a movie. This option can be found in the Main Display window under the View->Capture->Movie menu.

Image 1: Movie Display Window
Image 1: Movie Display Window
Properties

The media properties is composed of three tabs, General, Video, and Plug-in Settings.

The General tab has general information about the QuickTime movie:

Image 2: General Tab of the Media Properties Window
Image 2: General Tab of the Media Properties Window
Properties

The Video tab lists the specific video information:

Video tab of the Media Properties window
Image 3: Video Tab of the Media Properties Window
Properties

The Plug-in Settings tab has access to the PlugIn Viewer details:

Image 4: Plug-in Settings Tab of the Media Properties Dialog
Image 4: Plug-in Settings Tab of the Media Properties Dialog
Properties
Menus

All of the menu items seen utilizing the movie display are standard options that can be found in the Menus section of the Layer Controls page.


Image and Movie Capture Controls

McIDAS-V can capture the Main Display window as an image, a QuickTime movie or an animated GIF.

Saving Images

The user can save a display as an image by selecting the View->Capture->Image... menu item in the Main Display window. A file dialog will open where you can enter a file name for the image file. McIDAS-V supports JPEG, PNG, GIF, PDF, PS, and SVG formats. From this File Dialog you can also select whether or not the background is transparent. The Borders Visible controls adds a border around panels when capturing an image with the All Views option. When enabled, borders the thickness specified in the dropdown and color specified in the swatch will be added around each panel.

Note: When capturing an image, the Main Display window cannot be obscured.

McIDAS-V can also write out an image and the corresponding Google Earth KML or KMZ file. For this to be correct, the projection must be a Lat/Lon geographic projection (i.e., rectilinear) and in an overhead view. Some of the default projections that are Lat/Lon include World, Africa, Asia, Australia, and the individual state projections (US->States->...). You can also create your own Lat/Lon projection using the Projection Manager. The simplest way to get a correct projection is to select the Projections->Use Displayed Area menu item in the Main Display window. If you specify a .kml file, McIDAS-V will generate an image with the same file prefix and the kml file that refers to the image. If you specify a .kmz file (which is a zip format) it will contain the image and the kml file.

Printing Current View

You can send any display to a printer. Select the View->Capture->Print... menu item in the Main Display window. A Print dialog will popup where you can configure and print an image.

Saving QuickTime Movies

You can save any sequence of displays as a movie. Select the View->Capture->Movie... menu item in the Main Display window to open the Movie Capture window:

Image 1: Movie Capture Window
Image 1: Movie Capture Window
Properties

Note: More information about these controls is found in the Creating a Movie section below.

Creating a Movie

To make a movie, there are three steps: capturing the frames, previewing the frames, and creating the movie. McIDAS-V supports QuickTime movies, animated GIF and AVI files, MPEG-4, Compressed ZIP, Google Earth KMZ and AniS or FlAniS HTML file formats.

Playing QuickTime Movies

McIDAS-V supports displaying certain types of QuickTime movies (including the ones McIDAS-V generates). These movies can be loaded in the General->Files/Directories Chooser in the Data Sources tab of the Data Explorer.


Timeline Controls

McIDAS-V makes use of a timeline widget in a variety of areas. The timeline allows for viewing the temporal distribution of a set of times and selecting them. There can also be a date selection mechanism (see below) that allows for selecting based on a range, interval, etc. The Match Time Driver checkbox automatically selects the dates and times that match closest to the time driver, assuming a time driver has been set. For more information, see Time Matching.

Image 1: Relative Times Chooser
Image 1: Relative Times Chooser
Image 2: Absolute Times Chooser
Image 2: Absolute Times Chooser
Date Selection

The date selection settings can be accessed by right-clicking in the timeline to show a popup menu. The menu allows for defining these settings through a Properties dialog or setting them directly with sub-menu choices. The date selection settings are listed below.

The View Managers use the timeline to show the animation time set and the times of the different displays. Here, the timeline is used for informational purposes and is not used to select times. This can be shown through the View->Animation Timeline menu from the Main Display window. The gray timeline represents non-visible displays. Double clicking in a timeline sets the animation step to that time.

Image 3: Animation Timeline Window
Image 3: Animation Timeline Window
Timeline Navigation

The timeline supports a variety of navigation mechanisms:

Event Action
Left Mouse Drag Change visible range or date selection range.
Left/Right Arrow Change visible range.
Use Ctrl+Key to change date selection.
Use Shift+Key to use larger increment.
Up/Down Arrow Zoom in/out visible range.
Use Ctrl+Key to change date selection.
Use Shift+Key to use larger increment.
Mouse Click; Control-Click; Shift-Click Select individual times, multiple times or a range of times
Shift-Drag When not showing the date selection mechanism you can choose a range of times with shift-drag
Right Mouse Click This brings up a popup menu that allows you to show the properties dialog, go to particular current date ranges, set the interval, range, skip factor and count of the date selection.

Tools

User Preferences

Preferences are used to save standard settings of McIDAS-V, such as the map projection to show when McIDAS-V starts. The Preferences Dialog is opened in the Main Display window through the Edit menu with Edit->Preferences.

Click on Cancel if you wish to exit preferences setting, Ok to accept the changed preferences and close this window, and Apply to accept the preferences and keep this window open.

Note: Some of these preferences only take effect the next time you run McIDAS-V or when you create a new view window. The preferences also may be overwritten when you use bundles.

The follow sections describe the different user preference options for McIDAS-V:


General Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The General tab allows the user to configure many of the general settings within McIDAS-V. The image below represents the default settings for the General tab.

Image 1: General Preferences (Default)
Image 1: General Preferences (Default)

General
When Opening a Bundle
Layer Controls
When Layer Control Window is Closed

Display Window Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Display Window tab allows the user to set preferences related to the Main Display window. The image below represents the default settings for the Display Window tab.

Image 1: Display Window Preferences (Default)
Image 1: Display Window Preferences (Default)

Navigation Toolbars

Legends
Panel Configuration
Color Scheme
Layer List Properties
Logo
Default Projection

Toolbar Options Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Toolbar Options tab allows the user to define what actions/icons are displayed in the toolbar. The list on the left shows all of the available actions. The list on the right shows the actions that make up the toolbar. The image below represents the default settings for the Toolbar Options tab.

Image 1: Toolbar Options Preferences (Default)
Image 1: Toolbar Options Preferences (Default)

Properties

Data Sources Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Data Sources tab allows the user to define what types of data choosers to use. This is a way to simplify the Data Explorer window by only showing the choosers that you want to use. Note that you must restart McIDAS-V for any changes made in this tab to take effect. The image below represents the default settings for the Toolbar Options tab, with all data sources turned on.

Image 1: Data Sources Preferences (Default)
Image 1: Data Sources Preferences (Default)

Properties

ADDE Servers Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The window is also accessible by clicking the Manage servers button (Manage servers button) next to the server name of the applicable choosers in the Data Sources tab of the Data Explorer. The ADDE Servers tab allows the user to add and manage a list of active ADDE servers separated by data type. The selected ADDE entries will be included in the list of servers in the Data Sources tab of the Data Explorer. Limiting the number of servers in the Data Sources tab will make it easier to find the desired sources of data.

The list of ADDE Servers is hierarchial, meaning that you can turn off all servers, specific groupings of servers (ex. Point), or individual servers within a group (ex. adde.ssec.wisc.edu/RTPTSRC can be turned off under POINT, but the rest can remain selected).

The image below represents the default settings for the for the ADDE Servers tab. All of the ADDE entries are checked on except for 'NAV' and 'UNKNOWN'.

Image 1: ADDE Servers Preferences (Default)
Image 1: ADDE Servers Preferences (Default)

Properties

Available Displays Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Available Displays tab allows the user to specify what types of displays to use. The chosen displays can possibly be included in the Displays list in the Field Selector if the field you are displaying includes the display type in its properties. Choosing what displays you want to appear in the Field Selector will limit the number of displays in the list, making it easier to create your desired image.

The list of display types is hierarchal, meaning that you can turn off all displays, specific groupings of displays (ex. Plan Views), or individual display types within a group (ex. Color-Shaded Plan View can be turned off under Plan Views, but the rest can remain selected).

The image below represents the default settings for the Available Displays tab. Every display is selected on by default.

Image 1: Available Display Preferences (Default)
Image 1: Available Displays Preferences (Default)

Properties

Navigation Controls Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Navigation Controls tab allows the user to change how McIDAS-V interprets mouse and keyboard events for navigating in 3D space. The user can choose to use the navigation defaults for the IDV, VisAD, Google Earth, or create their custom navigation settings. The below images represent the default Custom settings for the mouse and keyboard in the Navigation Controls tab.

Image 1: Mouse Navigation Controls (Default)
Image 1: Mouse Navigation Controls (Default)
Image 2: Keyboard Navigation Controls (Default)
Image 2: Keyboard Navigation Controls (Default)

Properties

Formats and Data Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Formats & Data tab allows the user to define data formats and defaults to be used when displaying data. The below image represents the default values for the Formats & Data tab.

Image 1: Formats and Data Preferences (Default)
Image 1: Formats and Data Preferences (Default)

Formats

Data

Advanced Preferences

The User Preferences window is accessed in the Main Display window through the Edit->Preferences menu. The Advanced tab allows for changing options that require a restart in order for them to take effect. To configure the settings before running McIDAS-V, execute runMcV-Config on Linux/macOS platforms or runMcV.bat on Windows from the directory where McIDAS-V was installed (normally McIDAS-V-System) or by selecting Configure McIDAS-V in the Windows Start menu. The below image represents the default settings for the Advanced tab.

Image 1: Advanced Preferences (Default)
Image 1: Advanced Preferences (Default)

Startup Options

Remote ADDE Data Manager

The Local and Remote ADDE Data Managers are accessible in the Main Display window through the Tools->Manage ADDE Datasets menu item. Click the Remote Data tab to manage access to data on other workstations, or the Local Data tab to manage access to data on your workstation. Continue below for more information about the Remote ADDE Data Manager, or go to the Local ADDE Data Manager page for more information.

Viewing the Existing Remote Datasets
Image 1: Remote ADDE Data Manager
Image 1: Remote ADDE Data Manager

The Remote ADDE Data Manager lets you add, delete or edit access to remote datasets that are available through the Satellite->Imagery chooser. You can also import a MCTABLE.TXT file that contains a preexisting set of entries for the Remote ADDE Data Manager.

The columns in the table are defined below.

The rows in this window are listed in the alphabetical order of the datasets by default, and this order can be reversed by clicking on the name of the column ('Dataset'). Each column can be sorted alphabetically by clicking on the name of the column. At the bottom of this window, there is a status message that lets you know if local servers are running and does not affect remote servers. For more information this, please see Local ADDE Data Manager.

The four buttons at the bottom of the window are described in the corresponding section below.

Adding a New Remote Dataset

The window below appears if you click the Add New Dataset button or select the File->New Remote Dataset menu in the ADDE Data Manager window.

Image 2: Add Remote Dataset Window
Image 2:Add Remote Dataset Window

The Add Remote Dataset window lets you add access to remote datasets so they are available through the Data Explorer.

The fields and buttons are defined below.

Editing an Existing Remote Dataset

If you highlight an editable entry in the ADDE Data Manager window and then click the Edit Dataset button, the window and fields are the same as above, except that the window title is Edit Remote Dataset and the bottom buttons say Verify and Save Changes, Verify Changes, and Save Changes (rather than Verify and Add Server, Verify Server, and Add Server).

Image 3: Edit Remote Dataset window
Image 3: Edit Remote Dataset Window

Note that you cannot edit any of the remote datasets that come with McIDAS-V.

Removing an Existing Remote Dataset

If you highlight an editable entry in the ADDE Data Manager window and then click the Remove Selection button, it immediately removes the entry from the table. There is no recovery option, so if you accidentally remove an entry you need, you will have to remake the entry using the Add New Dataset button. Note that you cannot remove any of the native remote datasets that come with McIDAS-V.

Importing MCTABLE...

The window below appears if you click the IMPORT MCTABLE... button in the Remote ADDE Data Manager window.

Image 4: Import MCTABLE Window
Image 4: Import MCTABLE Window

This window lets you import a MCTABLE.TXT file that contains a preexisting set of entries for the Remote ADDE Data Manager. For example, McIDAS-X users may have added access to many servers via the DATALOC command. Those entries are stored in the MCTABLE.TXT file, which can be imported to McIDAS-V.

The fields and buttons are defined below.

Menus

A couple of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several menu options that are unique to this tool.

The File menu has these unique options:

The Edit menu has these unique options:

The Local Servers menu has these unique options:


Local ADDE Data Manager

The Local and Remote ADDE Data Managers are accessible in the Main Display window through the Tools->Manage ADDE Datasets menu item. Select the Local Data tab to manage access to image data on your workstation, or the Remote Data tab to manage access to data on other workstations. Continue below for more information about the Local ADDE Data Manager, or go to the Remote ADDE Data Manager page for more information.

Viewing the Existing Local Datasets
Image 1: Local ADDE Data Manager
Image 1: Local ADDE Data Manager

The Local ADDE Data Manager lets you add, delete or edit local image datasets that are available through the Satellite->Imagery chooser when you select <LOCAL-DATA> in the Server field. Other types of data (e.g., grib or point) in local files can be accessed directly through other choosers (e.g., the General->Files/Directories chooser).

The columns in the table and buttons are defined below.

The rows in this window are listed in the alphabetical order of the datasets by default, and this order can be reversed by clicking on the name of the column ('Dataset'). Each column can be sorted alphabetically by clicking on the name of the column. At the bottom of this window, there is a status message that lets you know if local servers are running. The Server Manager will attempt to connect to ports 8112 to 8122. When port 8112 cannot be connected to, port 8113 will be attempted, and then 8114 and so on. After these ports have been stopped or cannot be connected to, the status message will say "Local servers have been stopped". When this status message is showing, you cannot connect to any local servers. To help avoid connection problems, your firewall software must allow connections to port 8112.

Adding a New Local Dataset

To add a new local dataset entry, select File->New Local Dataset from the ADDE Data Manager menu, or click Add New Dataset button.

Image 2: Add Local Dataset Window
Image 2: Add Local Dataset Window

The Add Local Dataset window lets you add access to local image datasets so they are available through the Satellite->Imagery chooser. The fields and buttons are defined below.

Editing an Existing Local Dataset

To edit an existing entry, double click on the entry, select Edit->Edit Entry..., or click Edit Dataset button to bring up the Edit Local Dataset window. Make the needed changes and click Save Changes button (or click Cancel button to discard any changes and close the window).

Image 3: Edit Local Dataset Window
Image 3:Edit Local Dataset Window
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several menu options that are unique to this tool.

The File menu has these unique options:

The Edit menu has these unique options:

The Local Servers menu has these unique options:


Weather Text Product Controls
Overview

The Weather Text Product Control is used to display weather text products (forecasts, warnings, watches, etc.) produced by the National Weather Service and other international meteorological agencies. The Weather Text Product Display is accessed through the Main Display window via Tools->Text Data->Weather Text Products(from server). The user interface consists of three tabs, Products, Display, and Locations.

The Products tab selects and displays the text products. When a product is selected, the available stations are plotted in the Main Display window. One or more stations can be selected by clicking on the station in the Main Display window (or Ctrl+click for multiple stations). When a station is selected, the text product for that station is displayed in the Weather Text Product Display:

Image 1: Weather Text Product Display in the Text View
Image 1: Weather Text Product Display in the Text View

By default, the text product is displayed as raw text. Click on the HTML tab at the bottom of the display window to view the product in HTML.

Image 2: Area Forecast Discussion in the HTML View
Image 2: Weather Text Product Display in the HTML View

By default, the most recent text product is displayed. Previous versions of the products can be displayed by selecting a time range from the Time Covered drop-down list. Use the Time Animation Widget to loop through multiple products. The time animation will be synced with any other data in the Main Display window.

The Display tab controls the display of the station locations in the Main Display window:

Image 3: Display Tab of the Weather Text Product Display Window
Image 3: Display Tab of the Weather Text Product Display Window

Properties

The Locations tab lists information about the selected location and shows lists of all the locations and the locations currently visible in the Main Display window:

Image 4: Displayed Locations Tab in the Locations Tab of the Weather Text Product Display Window
Image 4: Displayed Locations Tab in the Locations Tab of the Weather Text Product Display Window
Properties
Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The Edit menu has these unique options:

The View menu has these unique options:


Storm Track Controls
Overview

The Storm Track Control displays tropical storm observation and model output tracks. Currently the McIDAS-V supports both the Automated Tropical Cyclone Forecasting System (ATCF) data as well as data from the Shanghai Typhoon Institute.

To load in ATCF data select the Tools->Text Data->ATCF Tropical Storm Data menu item in the Main Display window. This creates a data source with a predefined path to the National Hurricane Center FTP site. Then, create the Storm Track display.

The display control shows the set of available storms on the left panel organized by year and basin, e.g., Atlantic (AL), Eastern Pacific (EP) and Central Pacific (CP).

Year Display

At the top of the list is an option (Yearly Tracks) which allows the user to display the observed tracks for all the storms in a given year. You can load and/or unload any number of years worth of observed tracks. The color swatch changes the color of the tracks for a given year. The Time Mode menu allows one to change the animation mode, e.g., use the year or use the storm start time.

Image 1: Storm Track Window
Image 1: Storm Track Window

Storm Display

To show the observation and all of the model results for a single storm select the storm in the list and press the Load Tracks button button. You can load any number of storms but they are shown in different panels. You can use the View->Storm Tracks menu to list out all of the loaded storms, remove them all, etc. Once a storm is loaded it can be removed with the Remove Storm icon icon shown in the upper right.

Once a storm is loaded the first thing you should do is to specify which "Techs" (or models) to use by bringing up the control's Properties dialog Edit->Properties menu. Use Ctrl+A to select all items in the tab, the left/right arrows to remove/add an item from/to the Use column, or Delete to remove an item from the Use Column.

Image 2: Techs to Use Tab of the Storm Track Properties Window
Image 2: Techs to Use Tab of the Storm Track Properties Window
Properties

The Storm display panel consists of three tabs: Tracks, Table and Storm Chart.

Tracks

The Tracks tab controls the display and animation of the tracks.

Image 3: Tracks Tab of the Storm Track Window
Image 3: Tracks Tab of the Storm Track Window

Properties
Table

The Table tab shows a tabular listing of all of the observational track data and individual forecast model runs. On the left is a tree view organized by the Tech and model run time. Selecting one of the model runs will display the data in the table. The main File->Save->Export to Spreadsheet menu allows you to export the track data to an Excel spreadsheet. In the File Dialog are options to select what is to be saved.

Imave 4: Table Tab of the Storm Track Window
Image 4: Table Tab of the Storm Track Window
Properties
Storm Chart

The Storm Chart tab shows time series charts of selected tracks. Under the main Edit menu you can any number of new forecast time or forecast hour charts. The forecast time chart is based around the model run time of the selected forecasts. The forecast hour charts selects data across the different model run times, e.g., you can show the 12 hour forecast from each model run.

To do the charting of the storm track, one or more Techs need to be selected. Once selected the Forecast Hour/Forecast Time list is populated. One or more times can be selected (Ctrl+click). Each Parameter that is selected will result in a new chart shown on the right.

Image 5: Storm Chart Tab of the Storm Track Window
Image 5: Storm Chart Tab of the Storm Track Window

Properties
Menus

Many of these menu items seen utilizing this tool are standard options that can be found in the Menus section of the Layer Controls page. However, there are some options that are unique to this display.

The File menu has these unique items:

The Edit menu has these unique items:

The View menu has these unique items:


Color Table Editor
Introduction

The Color Table Editor supports editing existing color tables and creating new ones. A color table is an ordered collection of colors that is used to color a display according to a range of data values.

Image 1: The Color Table Editor
Image 1: The Color Table Editor
Starting the Color Table Editor

The Color Table Editor can be used stand-alone by selecting the Tools->Color Tables menu item in the Main Display window. It can also be used or in conjunction with a particular layer by right-clicking on the layer's color bar in the Legend and selecting Edit Color Table, or through the layer's Edit menu (Edit->Color Table->Edit Color Table). You can also click on the button that represents the name of the color bar in the Layer Controls tab and select Edit Color Table.

The Color Table Editor starts with a color table loaded in it. If you are working with a data display and you open the Color Table Editor through the Layer Controls tab of the Data Explorer, the color table in the editor is the same as in the display. If you want to use or edit a different color table, use the Color Tables menu to select from the categorized list of color tables:

Image 2: The Color Tables Menu
Image 2: The Color Tables Menu

Color tables are grouped into categories. Click on a color table to bring it into the Color Table Editor. To change to the newly selected color table for a display on the Main Display window, click OK or Apply at the bottom of the Color Table Editor. Apply will save changes to the color table, while keeping the Color Table Editor open, and OK will save any changes to the color table and close the Color Table Editor. Also, when editing a color table that is currently being used to display a layer in the Main Display window, there is an Auto update checkbox on the bottom right of the Color Table Editor. When this box is checked, any changes made to the color table will be applied directly to the display in the Main Display window. If you are making several changes to the color bar at once, and you have a lot of data displayed in the Main Display, it is recommended that you do not have this option turned on, as it will use up more memory. Once done making changes to the color bar, click Apply or OK to apply your changes to the displayed data.

Using the Color Legend
Image 3: The Color Legend
Image 3: The Color Legend
Properties
Painting and Editing Colors

You can "paint" in the color table by left-clicking and dragging the mouse within it. When your mouse is over the color table the cursor will change to a paintbrush and a gray line is drawn to indicate the position of the cursor.

The type of painting is specified by the Paint Mode buttons.

Using Breakpoints

The editor uses "breakpoints" indicated along the top of the color legend with triangles and the numerical value. By default, the beginning and ending of the color bar will each be a breakpoint. You can add additional breakpoints to the color bar by right-clicking on the color bar and selecting Add Breakpoint, or by double-clicking on or above the color bar where you want a breakpoint.

Clicking on a breakpoint makes it active. The active breakpoint will have bold text for the label, and the colored triangle below it will have an outline of yellow. There is only one active breakpoint at a time. Breakpoints are used for a number of things: showing the data and transparency values at a point along the color table and changing the colors (fill, interpolation or transparency).

The values on the breakpoints are determined by the position of the breakpoint along the legend, proportional to the min and max of the Range. Changing the minimum and maximum of the Range changes the breakpoint values.

You can move the active breakpoint (assuming it isn't locked) in several ways:

If you have the Actively set color checkbox selected, when you change the color in the color chooser that color will be applied to the color slot under the selected breakpoint automatically.

You can also change colors and manipulate breakpoints by right-clicking on a breakpoint:

Image 4: Add a Breakpoint
Image 4: Add a Breakpoint

The choices are:

Saving, Importing, and Exporting

You can modify an existing color table, or edit an existing color table and save it with a new name to make a new color table. Any new or modified color table can be saved for future use. To save a new or modified color table simply select the the File->Save. To save a modified color table as a new color table, select File->Save As and enter the new name in the dialog box that appears. This new color table will now be permanently saved in your local collection of color tables. You can control where your color bar will be saved by selecting a Category in the upper right of the Color Table Editor.

To save a color table as a file which can be shared with others in McIDAS-V, select the File->Export menu item. A file dialog will appear that will allow you to save the color table as an XML-format file. We suggest you use a file extension of .xml.

To use a color table as a file which has been supplied to you by another McIDAS-V user, select the File->Import menu item. A file dialog will appear that will allow you to find the color table as an XML-format file. The following types of color tables can be imported:

Another way that you can save all of your color tables at once is to save them as a plugin. This can be done through the Plugin Manager, by including your colortables.xml file that is inside of your /User/McIDAS-V directory. You can then pass this on to any McIDAS-V user, and they can install this plugin and obtain all of your color bars without having to individually transfer them.

3-column RGB color table

The definitions of the 3-column RGB color table are divided over a range of values. Each line represents one of the equal sized blocks on the color bar, and the bar is saved in the *.ascii format. Ascii files are text files with three space-separated columns consisting of the RGB component counts. An example is shown below:

180 0 10

140 0 50

140 0 140

80 0 180

0 120 60

0 140 80

In the example above, there are six lines (definitions) that would be divided into the color table. The color table would be broken into six even segments, with the first line applying to the first segment, the second to the second segment, etc. Your file may be any number of lines long. The values in these columns must be between 0 and 255.

Using the Color Chooser
Image 4: The Color Chooser
Image 5: The Color Chooser

The Color Chooser, in the lower half of the Color Table Editor window, allows you to select any possible color. The chooser contains four tabs, HSV (Hue, Saturation, Value), HSL (Hue, Saturation, Lightness), RGB (Red, Green, Blue), and CMYK (Cyan, Magenta, Yellow, Black, Alpha). In most cases, the HSV tab provides better control and better depiction of color changes because of its hue, saturation, and value controls. Thus, it is recommended that you use the HSV tab (rather than the other tabs) unless you have specific values to set in the other tabs.

The HSV Tab

The HSB tab allows you to control color by hue, saturation, and brightness, thereby making any color. With the HSB tab open, click on one of the radio buttons marked H, S, or B for the corresponding control for hue, saturation, or brightness. All controls in the HSB tab also show the RGB values for any color selected, in case you need to know the RGB values for another use.

Hue is the term indicating a pure color selection from the spectrum. Saturation is an indication of how much white is added to the hue. 100% saturation is pure hue with no white. Brightness is an indication of how much black is added to the hue. 100% brightness has no black and maximum brilliancy, but can be any saturation from the hue to pure white. 0% brightness is solid black. Some colors are not found in the spectrum, and are a mixture of a hue and black and/or white. You only need to use one of the controls for H, S, or B to make any color.

With the Hue (H) radio button selected, the slider bar chooses the pure hue. Once Hue has been selected, clicking or dragging the mouse on the color display chooses degrees of saturation and value for that hue.

Image 6: The HSV Hue Tab, Set on Green With High S and High B
Image 6: The HSV Hue Tab, Set on Green With High S and High B

Saturation (S) has a slider bar with the full range of saturation. The bottom is always solid black. A saturation value of 100 is the pure hue, and more white is mixed in with the hue until it is solid white at a value of 0. The saturation value can be controlled by the slider to the right of the color square, or by entering a value into the field to the right of Saturation and pressing Enter. After selecting a saturation level, click and drag in the colored square to get your desired color.

Image 7: The HSV Saturation Tab, Set on the Same Green
Image 7: The HSV Saturation Tab, Set on the Same Green

Value (V) has a slider bar with the full range of brightness. The bottom is always solid white. A brightness value of 100 is the pure hue, and more black is mixed in with the hue until it is solid black at a value of 0. The brightness value can be controlled by the slider to the right of the color square, or by entering a value into the field to the right of Value and pressing Enter. After selecting a brightness level, click and drag in the colored square to get your desired color.

Image 8: The HSV Value Tab, Set on the Same Green
Image 8: The HSV Value Tab, Set on the Same Green

When a HSV color is selected, the numerical values in all of the other tabs are updated to reflect the color. There is also a Transparency slider at the bottom of this tab that sets the transparency associated with the HSV color. This transparency is applied to the color bar

The HSL, RGB, and CMYK Tabs

The other three tabs (HSL, RGB, and CMYK) all work in generally the same way as the HSV tab, with the color swatch, and different sliders to control aspects of the selected color. Below is a description of the components in each of these tabs.

As modifications are made in any of these four tabs, the current color will be displayed above the tabs next to the Actively set color checkbox. If the Actively set color checkbox is selected, any changes made in the tabs will be applied directly to the color bar as changes are made, with the exception of the Transparency and Alpha fields.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options unique to this display.

The File menu has these unique options:

The Color Tables menu has these unique options:


Layout Model Editor

The Layout Model Editor composes the model and style used to plot data on a map from observations at discrete points (e.g., weather observations). This tool is used to edit existing models or to create new models. The Layout Model Editor is opened with the Tools->Layout Model Template menu item in the Main Display window.

Image 1: Layout Model Editor
Image 1: Layout Model Editor
Creating a Layout Model

Layout models can be created from scratch by utilizing the File->New menu option, or an existing layout model can be edited from the Layout Models menu. The display includes a horizontal and vertical line, which acts as a reference point for the location of the layout model with respect to the physical location of the observation (at the origin). The different shapes and features that can be added to the layout model are in the left panel. The shapes and features can be added to the layout model by left-clicking the item and then left-clicking at the desired location in the panel. Once in the Layout Model, individual components can be moved by left-clicking and dragging them. When an item is placed into the layout model, the Properties dialog for the component will open. This Properties dialog can also be invoked by double-clicking on a shape.

Each component of the layout model can be resized by dragging the black squares along the outside of the item. Multiple items can be aligned at once by holding down Shift and left-clicking on the items to move. Clicking on an item makes it active, and active items have black squares around them. Each item in the layout model also includes a red "Alignment Point', which acts to locate the individual components of the model with respect to the center point of the observation. The location of the Alignment Point to the item can be changed via the Alignment Point option in the menu when an item is right-clicked on.

When the mouse is held over a component of the layout model, the name of the item will be listed in the bottom bar of the Layout Model Editor. This can be useful if multiple Value fields are included in the layout model (temperature, dew point, etc.).

To save a layout model, use the File->Save or File->Save As... menu items. When the layout model is saved, any point data displays or gridded value plot displays that are using it will be updated. To remove a model, use the File->Remove menu item. Layout models supplied with McIDAS-V cannot be removed, but user-created local models can be removed.

Editing a Layout Model

There are many options that can be controlled for each individual component of the layout model. This menu is seen by right-clicking on an item.

Image 2: Editing a Layout Model Menu
Image 2: Editing a Layout Model Menu

The Properties window consists of four tabs: Display, Color By, Scale Size, and Rotate.

Properties Dialog - Display Tab

The Display tab allows for assigning which observation variable is associated with that item. Numerical values should appear in a "Value" item, text in a "Text" item, etc. Note that the items in this tab may differ depending on the item.

Image 3: Display Tab of the Properties Dialog
Image 3: Display Tab of the Properties Dialog
Properties
Properties Dialog - Color By Tab

The Color By tab consists of two tabs within itself: Map Value Into Color Table, and Color From Parameter. This tab allows for specifying how to color the item in the layout model.

The Map Value Into Color Table tab allows for coloring the parameter based off of its numerical value in relation to the set data range and color table for the parameter.

Image 4: Map Value Into Color Table Tab of the Color By Tab
Image 4: Map Value Into Color Table Tab of the Color By Tab
Properties

For example, in the above image the Temperature parameter has been specified with data range -90 to 45 Celsius. For each display, McIDAS-V will find the Temperature value (e.g., 15 Celsius), convert it to the specified unit (if necessary), find where it lays within the range, and use the corresponding color from the color table to display the data in the Main Display window.

The Color From Parameter tab allows for specifying a parameter, a set of (regular expression) patterns, and a corresponding color. If the text value of the parameter matches one of the patterns then the given color is used to color the shape.

Image 5: Color From Parameter Tab of the Color By Tab
Image 5: Color From Parameter Tab of the Color By Tab
Properties
Properties Dialog - Scale Size Tab

The Scale Size tab allows for specifying a parameter to scale the shape by. For each point display, McIDAS-V will find the value of the parameter, determine where that value lies within the data range, and find the corresponding scaling from the scale factor range.

Image 6: Scale Size Tab of the Properties Dialog
Image 6: Scale Size Tab of the Properties Dialog
Properties
Properties Dialog - Rotate Tab

The Rotate About Axis tab works like the scale and color by facilities. Note that the rotation is about the Z axis in X/Y/Z space. It is not a rotation in Lat/Lon space. All three tabs in the Rotate tab have the same fields.

Image 7: Rotate About Tabs of the Rotate Tab
Image 7: Rotate About Tabs of the Rotate Tab
Properties
Alignment Toolbar

At the top of the Layout Model Editor window, there is an alignment toolbar that allows for specifying the location of one item in a layout model model with respect to another. To align one item with respect to another, both items must be selected in the Layout Model Editor must be active. To activate multiple items, use Shift+left click on each item.

Alignment toolbar
Image 8: Alignment Toolbar
Properties Dialog - Shapes

Two items that can be added to the layout model whose Properties windows are significantly different than described above are Shape and Mapped Shape. These allow for defining numerical values of a parameter as a variety of different shapes.

The Properties window of the Mapped Shape Symbol is shown below. The only tab that differs between the Properties of Mapped Shape Symbol, and Shape, and the Properties above is the Display tab. The Shape item does not include the Shape Mappings panel in the window below, so using Shape, all numerical values will be plotted with the same shape regardless of their value.

Image 9: Mapped Shape Properties
Image 9: Mapped Shape Properties
Properties

For example, in the above image the Value parameter has been specified. From the Shape Mappings panel, values of 1-5 will display as a Minus, 6 will display as a Pin, 8 will display as a Filled Star, and 10 will display as a Square. All other values will display as a Filled Diamond, as set in the Shape field.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options unique to this display.

The File menu has these unique options:

The Edit menu has these unique options:

The View menu has these unique options:

The Layout Models menu has these unique options:


Parameter Alias Editor

The Parameter Alias Editor is opened through the Tools menu in the Main Display window with Tools->Parameters->Aliases menu and allows for the association between "canonical" parameter names used by McIDAS-V for physical quantities, such as TEMP for temperature, and parameter names used in particular data sets for the same quantity, such as for example "jan_mean_temp."

Image 1: Alias Editor
Image 1: Alias Editor

Different data sets often have different names for the same physical quantity, such as the quantities for temperature or easterly wind speed component. McIDAS-V can recognize any particular variable name as representing a standard quantity with the use of a parameter alias. The Alias Editor associates any particular variable name that may appear in a data set (right column) with a canonical or McIDAS-V name or alias (left column). These columns are sorted in alphabetical order by default, and this order can be reversed by clicking on the name of the columns (e.g. 'User aliases').

The Alias Editor has a number of tabs that display the user editable aliases and the non-editable system aliases. To modify an alias in the Application aliases or the System aliases tabs, right-click on a row and select Edit Alias. This will copy the alias to the User aliases tab, where it can be modified by the user. While this alias will still exist in the Application aliases or System aliases tab, the alias in the User aliases tab will be used first by McIDAS-V. User aliases can be modified in the same way, by right-clicking on a row and selecting Edit Entry. User aliases can be deleted by right-clicking on a row and selecting Delete Entry.

When attempting to create a new alias or edit an existing one, a Data Alias dialog is shown:

Image 2: Data Analysis Properties Dialog
Image 2: Data Alias Properties Dialog
Menus

The File menu has these unique items:


Parameter Defaults Editor

The Parameter Defaults Editor is opened through the Tools menu in the Main Display window with Tools->Parameters->Defaults and allows for the specification of default color tables, ranges, units, and contouring values for different parameters:

Image 1: Parameter Defaults Editor
Image 1: Parameter Defaults Editor

Properties

This feature allows for presetting conventional color and contouring choices, and allows for overriding system defaults.

There are three sets of defaults: User defaults, Application defaults, and System defaults. These columns are sorted in alphabetical order by default, and this order can be reversed by clicking on the name of the columns (e.g. 'Parameter'). While the items in the Application defaults and System defaults tabs cannot be modified within the tab, a duplicate of the same parameter can be copied in the User defaults tab. This can be done by right-clicking on a row and selecting Copy Row to Users Defaults. If the same parameter is defined as a User default and an Application/System default, the User default will be used first. Once this is done, a user default can be edited by right-clicking on a row and selecting Edit Settings. This opens a Parameter Defaults window that allows for modifying and defining properties of the default:

Image 2: Parameter Defaults Properties
Image 2: Parameter Defaults Properties

In the example above, any time a parameter named "rh" is used to define a field, the data will display with the Relative Humidity color bar, a range of 0-100, and contour values as specified in the window. To define an individual item, such as Range, the Defined checkbox must be selected. If it is not checked, then any values stored in this window will not be saved as a default. From the User defaults tab, right-clicking on a row to adding a new row, editing the settings for the row, deleting the row, or exporting an individual row as a plugin.

The parameter names are given in regular expression syntax to help match with actual data names. Plain text is matched exactly. The string dot star, ".*", means "any text here." The ^ means "begin with the following text exactly".

Properties
Menus

The File menu has these unique items:


Parameter Groups Editor

The Parameter Groups Editor is opened through the Tools menu in the Main Display window with Tools->Parameters->Groups and allows for the specification of "parameter groups", named groups of parameter names.

Image 1: Parameter Groups Editor
Image 1: Parameter Groups Editor
Properties

There are two sets of defaults: user defaults in the tab User Groups, and system groups supplied with McIDAS-V in the System Groups tab. Look at the system defaults for examples. These columns are sorted in alphabetical order by default, and this order can be reversed by clicking on the name of the columns (e.g. 'Parameter Group').

The system settings cannot be edited by the user, but right clicking a row and selecting Copy Row to Users Defaults allows for copying a group to the "user defined" table where it can be modified. When this is done, the Parameter Group window allows for the sets of parameters that fall under this group. Parameters in each group should be separated by commas and only one group can be specified per line.

Image 2: Parameter Groups Properties
Image 2: Parameter Groups Properties
Properties
Menus

The File menu has these unique items:


Projection Manager

The Projection Manager allows you to choose, edit, and save map projections for use in McIDAS-V.

A projection is a way of mapping the surface of the Earth (a curved 2D surface) onto a flat 2D surface (a plane). A projection transforms a point on the earth (specified by latitude, longitude) to a point on the projection plane.

In the Projection Manager, both the projection and the area of the Earth can be specified. For example, you can make a Lambert Conformal map of North America, and a Lambert Conformal map of Sedgwick County, Kansas. Same projection, different areas.

McIDAS-V provides several basic types of projections: Lat/Lon, Lambert conformal conic, Transverse mercator, Stereographic, Mercator, Albers Equal Area, Lambert Azimuth Equal Area, Orthographic, VerticalPerspectiveView. Each of these can be parameterized (e.g., tangent point, origin longitude) to create a specific projection area of that type. When you define a projection and area, you specify the type of projection and its parameters.

Projection Manager Window

You can bring up the Projection Manager with the Projections-> New/Edit Projection buttonNew/Edit... menu item in the Main Display window, or through the Tools->Projections->Edit Map Projections menu option in the Main Display window. Projections supplied with McIDAS-V are shown in the list. There may be additional projections you have created and named. In the figure, the US->CONUS projection is highlighted, and displayed on the left.

Image 1: Projection Manager
Image 1: Projection Manager
Properties

McIDAS-V starts with a default projection. Use the Default pulldown menu to select the projection that will be shown each time your McIDAS-V starts. (The default projection may not be used if you are starting McIDAS-V with a Bundle of configuration information).

Define/Edit Projection Window

This allows you to define new projections and to modify existing ones. Remember that a projection not only consists of the mathematical projection, but also the area of the Earth that is seen.

Here is how to create a new or revised projection:

  1. Choose Edit button or New button from Projection Manager window. You can also double click on an existing projection in the Projection Manager to open the Define/Edit Projection window.
  2. Enter a new or revised name if necessary. See the Properties section below for more information about naming and creating hierarchies.
  3. Choose a Projection Type from the pull-down menu.
  4. Fill in the projection parameters.
  5. Set the map area shown with this projection by zooming and panning the view on the left. To zoom, click and drag the left mouse button. Use the other buttons in the window to zoom in/out and translate the display.
  6. Resize the map boundaries by clicking and dragging on the black boxes at the borders of the image. Pressing Delete or Ctrl+D will delete the box, and pressing Ctrl+R will resize the boundaries of the map to the current geographical boundaries of the map in the Define/Edit Projection window.
Image 2: Define/Edit Projection Dialog
Image 2: Define/Edit Projection Dialog

Note that some fields in this window may be different depending on the map type you select. There are no Projection Parameters when using a Lat/Lon map type. In the example shown, a Lambert conformal conic projection is being defined with the projection parameters as shown in the figure.

Properties

Data Analysis

Formulas

McIDAS-V provides techniques to make computations with data sources and to display the results. The simplest technique is using McIDAS-V formulas, which are one-line mathematical expressions. The steps for computing and displaying the output of a McIDAS-V formula are:

You can make formulas more powerful by writing methods (subroutines) in the Jython computer language, which is described in Jython Methods.

Once you define a McIDAS-V formula, it is saved and will appear in future sessions of McIDAS-V.

To create a formula, select the Tools->Formulas->Create Formula menu item in the Main Display window. This opens the Formula Editor dialog window used to define a formula:

Image 1: Formula Editor Dialog
Image 1: Formula Editor Dialog
Properties

The formula itself can use common mathematical operators much as +, -, * for multiply, / for divide, and ** for power. Other Jython operations such as sqrt(a), max(b), pow(a,b), and sin(c) are available. The Jython Methods section of the User's Guide explains how to write complete multi-line functions or Jython methods that you can call in one-line formulas.

The variable names in the formula definition, such as "NIR" in the figure above, are operands and do not need to exactly match any particular parameter name in any data source; the association is made later, in the parameter selection step.

Do not use spaces in formula variable names, such as "wind speed." The formula is an expression in the Jython language. Each variable name must start with a letter.

It is best to use variable names that suggest the parameter data they represent, so that later you can easily remember what the variables mean. Use names like Temp500m, RelHum_surf, absvort, sst_jan, density, or whatever makes sense to you. If you use a variable names like V1 and V2, then later when the formula requests which real parameter name goes with which variable name you may be puzzled which is which.

Variable names can have extra "syntactic sugar" attached to them that McIDAS-V uses for a variety of purposes. The "sugar" consists of a set of name/value pairs contained in brackets ("[...]") after the variable name.

For example, normally variables are used to select and define data choices. You can also have variables that are simple text input from a user. For example, evaluating the following expression:


   someProcedure(someValue[isuser=true])

will result in a dialog box being shown to allow for the user to enter a text value (e.g., a number) for the variable someValue.

You can provide default values with:


   someProcedure(someValue[isuser=true,default=some default])

An extension from the previous example, a formula can be created without using a pre-defined procedure from the Jython Library. For example, a formula can be created that will allow the user to divide the values of a field by a specific value. This can be done as follows, by specifying that the value is a float (the value could also be specified as an integer by specifying 'int' in place of 'float'):


   field/float(value[isuser=true,default=some default])

You can specify the types of data that can be selected for a variable with the categories name. e.g.:


   someProcedure(someDataValue[categories=param:ALTITUDE])

If you want multiple data categories, separate them with a ";":


   someProcedure(someDataValue[categories=param:ALTITUDE;param:elevation])

If you only want to select 3D grids do:


   someProcedure(someDataValue[categories=GRID-3D-*])

If you only want to select 3D or 2D grids do:


   someProcedure(someDataValue[categories=GRID-3D-*;GRID-2D-*"])

You can also specify a regular expression pattern that is used to pre-select the first data choice whose description matches the pattern.


   someProcedure(someValue[pattern=some_pattern])

A formula can be created that allows for multiple line text input by specifying rows= in the formula. For example:

   someProcedure(someValue(isuser=true,rows=4))

A formula can prompt the user with a menu of choices with type=choice in the formula. For example:

   someProcedure(someValue(isuser=true,type=choice,choices=lt;gt))

A formula can prompt the user with a Field Selector window that allows for selecting multiple fields at once with multiple=true in the formula. For example:

   someProcedure(someValue(multiple=true))

In the advanced section you can enter a description of the formula, its group or category, and you can define what types of displays are applicable for the given formula (the default is to be able to use all displays).

The group is used to display the formula in the Field Selector window and can be any alphanumeric text including spaces, numbers, and punctuation characters. Hyphens ("-") define sub-categories.

To save the formula, click on Add Formula button. A new entry appears in the selector panel. By right clicking on the formula entry in the Field Selector window you can edit the formula. If you edit a native formula and save it, the original formula will still be listed, but the modified formula will also be listed. To remove a formula, click on Remove Formula button in the pull down menu. You can also right click on a formula and select Remove Formula.

For information about the Derived tab, see Derived Data.

Different data sources and automatic navigation

McIDAS-V hides much of the computational complexity. You can write a simple formula such as (CT*1.8 + 32.0) - dewptF, and McIDAS-V will automatically apply the calculation to every element in large 3D grids referred to as CT and dewptF. No loops over grid points are needed; and you don't need to know anything about how the grid is defined, mapped on the Earth, or the data format. You can even use different sources for the individual parameters. For example, CT can come from a NAM model output grid and dewptF from your own local weather model. The two grids don't need to have the same grid point locations nor the same areal coverage. The results are computed in the area of overlap on the grid points locations of the first grid. Interpolation is automatically applied where needed.

Creating a Display with a Formula

Using a formula as the data when creating a display is just like using any other data. You select the formula entry in the Field Selector window, and the list of applicable displays will be shown and you create the display.

When you create a display, McIDAS-V needs to know what actual data should be bound to the operands within your formula. A Field Selector window will appear that allows you to select the actual data for each operand. You can select parameters from more than one data source for use in a single formula, for example, you can pick the same parameter from data sources of different times to compute a time difference in the parameter.

Image 2: Field Selector Window
Image 2: Field Selector Window

Open the data source to see the names of parameters available. Click on the parameter needed for each variable. Then click OK button. The result of the formula is computed for every data point in the source, and the result shown in the Main Display window.

Note that other windows may appear when evaluating a formula. For example, a Select Input window may be used if the formula prompts the user for a numerical value. This Select Input window may involve a combination of text fields or drop-down menus.

Image 3: Select Input Window
Image 3: Select Input Window

FAQ

Q. What is Jython?

A. Jython is a Java implementation of the Python language. It is used within McIDAS-V for data analysis. Complex routines can be written in the McIDAS-V Jython editor and called from the McIDAS-V Formulas.

Q. How do I learn to write Jython?

A. There are a number of books available on the language as well as a number of web sites:

Q. How does Jython work with my data in McIDAS-V?

A. McIDAS-V uses the VisAD package as as an underlying data model. There is a VisAD/Jython Tutorial available.

Q. Creating/Removing library files

A. To create a new file use the File->New Jython Library... menu. To remove the currently displayed library file use the File->Remove Library menu.

Q. Calling procedures from formulas

A. When creating a formula with the Formula Editor you can call any routines you have defined in the Jython Library. Simply enter the procedure name in the formula with appropriate arguments, if any. For example a formula might be "convertCToF(atemp)". When evaluating the formula for display, this will call the routine that you define in the Jython Library.

Q. Create a formula from my procedure

A. Right click on a procedure definition within the McIDAS-V editor window and choose Make formula for .... This is a convenience that brings up the Formula creation dialog with a call to that procedure.

As another convenience you can also right-click on the Formula: field of the Formula Editor to show the Insert Procedure Call menu. This lists all of the currently defined procedures in the other Jython libraries.

Q. Why do I see "TypeError: object is not callable" messages when scripting?

A. This error occurs when a user gives a variable the same name as a reserved keyword or function. For a list of reserved Jython functions, please see Built-in Functions. Variable names should be unique.

Jython Shell
The Jython Shell is an interactive command line interface to the McIDAS-V Jython interpreter that allows the user to type in arbitrary Jython to evaluate. This feature is brought up with the Tools->Formulas->Jython Shell menu item in the Main Display window. Alternatively, the Jython Shell can be brought up with Ctrl+J.
The User Interface
Image 1: Jython Shell Window
Image 1: Jython Shell Window

The Jython shell consists of an output window on the top and an input field on the bottom. The user enters Jython into the input field. When Enter or Evaluate button is pressed the Jython is evaluated and any output is shown in the output window. Note that Enter will only evaluate the field if the field has not been expanded. If your are using multi-line input for your commands, you can evaluate the commands with Shift+Enter.

The entry window can be expanded with the Jython Expand double down arrows to the right of the command line. When the entry field is expanded, you can enter more than one line of code to be processed at once. When the entry field isn't expanded, you are limited to evaluating one line of code at a time. As an alternative to the Jython Expand double down arrows button, you can use Ctrl+/ to change between single and multi-line command line structure.

Pressing the "Up" arrow and "Down" arrow in the entry field goes up and down through the history of commands when you are in single-line input. If you are using multi-line input, use Ctrl+P, Ctrl+N to cycle through previously-executed commands.

After a command has been evaluated, the command will be listed above the Evaluate field. To the right of the command, there are two buttons. The Down Arrow button button enters the formula back into the Evaluate field without evaluating it. The Reevaluate button button reevaluates the previously entered command without having to manually reenter it.

The Jython Shell window includes syntax highlighting, which colors different parts of the text in different colors. For example, strings will be pink and comments specified with a pound symbol (#) will be green. This syntax highlighting is only available in multi-line input mode. When in multi-line input mode, pressing enter will restore the indentation of the previously-entered line. For example, when setting up the addeParms dictionary in the image above, when Enter was pressed after line three, the indentation of four spaces was automatically applied for line four.

Print statements are not needed in the Jython Shell to output information when a single line of code is being evaluated. Below are a couple of examples:

Right-clicking in the entry field brings up a menu that allows for:

Menus

All of the menu items in this tool are unique to the Jython Shell.

The File menu has these unique items:

The Edit menu has these unique items:


Jython Library

Module: grid

This is the doc for the grid module. For more information, see Description of Formulas - Grids.

applyToRange(function, data):

Apply the function name to each timestep of the data

applyToRangeValues(function, data):

Apply the function name to each value in each timestep of the data

averageOverTime(field, makeTimes):

Average the values in each time step If makeTimes is true (1) then we return a field mapping all of the times to the average. Else we just return the average

combineFields():

Combine several fields together

differenceFromBaseTime(field):

Set the value of each time step N: D(N)=D(N)-D(0)

exportGridToNetcdf(grid, filename):

Writes out the gridded data to a CF-compliant netCDF file

extractLatitudeFromNWPGrid(fieldimpl):

Get the latitude coordinate from a grid. Return a grid of the latitudes at each point

extractLongitudeFromNWPGrid(fieldimpl):

Get the longitude coordinate from a grid. Return a grid of the longitudes at each point

extractPressureFromNWPGrid(fieldimpl):

Get the pressure coordinate from a time series grid and return a grid of the pressure at all points. Input grid must have pressure or height (which is converted to pressure in the standard atmosphere). User must be sure input is a suitable FlatField

flowVector(field):

Make a vector from flow direction

getAltitude(z):

Change units from geopotential meters to meters

getNthTimeGrid(fieldimpl, Nth):

Get the Nth grid in time series of grids; User must be sure input is a suitable data field. returns a single time. Nth is an integer, >=0, <= max index of grid time series

getSliceAtAltitude(fieldimpl, alt, unit):

Extract a 2D horizontal slice from a 3D grid at the given altitude; level is a real number; if unit is supplied, it must be compatible with meters (ft, fathoms, etc) param fieldimpl is a grid which may have one or more time steps

getSliceAtLevel(fieldimpl, level):

Extract a 2D horizontal slice from a 3D grid at "Level." level is a real number; must be appropriate for the grid. param fieldimpl is a grid which may have one or more time steps

GP2Z(gp):

Convert Geopotential (GP) to Height (Z)

horizontalAdvection(param, u, v):

Horizontal advection

horizontalDivergence(param, u, v):

Horizontal flux divergence

layerAverage(grid, top, bottom):

Wrapper for calculating layer average

layerDiff(grid, top, bottom):

Wrapper for calculating layer difference

lonFlip(grid):

Flip the longitudes in a grid from -180-180 to 0-360 (or vice-versa). Only works for cyclic rectilinear grids

make2D(slice):

Make a 2D slice from a 3D slice at a single level

make2DFlowTraj(u,v,s,s0):

Get the 2D u, v, and scalar variable s, s0 from a grid. Return grid trajectory.

makeFlowField(a, b, c):

Make a vector from 3 components

makeVector(a,b) = [a,b,c]

makeFlowTraj(u, v, w, s, s0):

Get the u, v, w, and scalar variables, s0 from a grid. Return grid trajectory.

makeTimeSequence(g):

Merge a set of single time grids/images into a time sequence

makeTopographyFromField(grid):

Make a topography field out of a grid

makeTrueVector(u, v):

True wind vectors

makeVector(a, b):

Make a vector from 2 components

makeVector(a,b) = [a,b]

maskGrid(grid, mask, value, resample):

Mask one grid by the values in the other. Value is the masking value

maxOverTime(field, makeTimes):

Take the max of the values in each time step if makeTimes is true (1) then return a field mapping of all times to the average. Else return the max

mergeTimeSequences(g):

Merge a set of time sequences of grids/images into a single time sequence. All grids/images must have the same parameter name

minOverTime(field, makeTimes):

Take the min of the values in each time step if makeTimes is true (1) then return a field mapping of all times to the average. Else return the min

newName(field, varname, copy):

Create a new field with a new parameter name

newUnit(field, varname, unitname):

Set the name and unit on a grid

noUnit(field):

Remove the units from a grid

resampleGrid(oldGrid, gridwithNewDomain):

Display gridded data on a new domain

runave(grid, nave, option):

Generate a running average. nave = number of steps to average over. option = option for unsmoothed end points (0: set to missing; 1: use symmetry; -1: assume cyclic)

setLevel(grid, level, unit):

substitute(data, low, high, newValue):

Change values in data between low/high to newValue

sumFromBaseTime(field):

Set the value of each time step N: D(N)=D(N)+D(0)

sumOverTime(field, makeTimes):

Take the sum of the values in each time step if makeTimes is true (1) then return a field mapping of all times to the average. Else return the sum

thetaSurface(grid, theta0):

thetaSurfaceA(grid, grid1, theta0):

thetaSurfaceV(gridt, gridu, gridv, theta0):

thetaSurfaceV(gridt, griduv, theta0):

thetaSurfaceADV(gridt, griduv, other, theta0):

timeStepDifference(field, offset):

Set the value of each time step N: D(N)=D(N)-D(N+offset) where offset should be negative

timeStepSum(field, offset):

Set the value of each time step N: D(N)=D(N)+D(N+offset) where offset should be negative

uvFromWindDir(dir):

Create the vector field using the wind direction

wgt_runave(grid, wgts, option):

Generate a weighted running average. wgts = comma separated list of weights option = option for unsmoothed end points (0: set to missing; 1: use symmetry; -1: assume cyclic)

windShear(u, v, z, top, bottom):

Calculate the wind shear between discrete layers

shear = sqrt((u(top)-u(bottom))^2 + (v(top)-v(bottom))^2)/zdiff

windShearVector(u, v, top, bottom):

Calculate the u and v layer difference and return as vector

writeGridToXls(grid, filename):

Write out the grid data to an excel spreadsheet

Module: griddiag

This is the doc for the Grid Diagnostics module. These functions are based on the grid diagnostics from the GEneral Meteorological PAcKage (GEMPAK). Note that the names are case sensitive and some are named slightly different from GEMPAK functions to avoid conflicts with Jython built-ins (e.g. str).

In the following operators, scalar operands are named Si and vector operands are named Vi. Lowercase u and v refer to the grid relative components of a vector.


GRAVITY():

Gravity constant

add(S1, S2):

Addition

ADD (S1, S2) = S1 + S2

adv(S, V):

Horizontal Advection, negative by convention

ADV ( S, V ) = - ( u * DDX (S) + v * DDY (S) )

age(obs, geo):

Ageostrophic wind

AGE ( S ) = [ u (OBS) - u (GEO(S)), v (OBS) - v (GEO(S)) ]

atn2(S1, S2):

Wrapper for atan2 built-in

ATN2 (S1, S2) = ATAN ( S1 / S2 )

avg(S1, S2):

Average of 2 scalars

AVG (S1, S2) = ( S1 + S2 ) / 2

avor(V):

Absolute Vorticity

AVOR ( V ) = VOR ( V ) + CORL(V)

circs(S, D):

Apply a circular aperature smoothing to the grid points. The weighting function is the circular aperature diffraction function. D is the radius of influence in grid increments, increasing D increases the smoothing (default D=2)

corl(S):

Coriolis Parameter for all points in a grid

CORL = TWO_OMEGA*sin(latr)

cress(S, D):

Apply a Cressman smoothing to the grid points. The smoothed value is given by a weighted average of surrounding grid points. D is the radius of influence in grid increments, increasing D increases the smoothing (default D=2)

cros(V1, V2):

Vector cross product magnitude

CROS ( V1, V2 ) = u1 * v2 - u2 * v1

ddx(S):

Take the derivative with respect to the domain's X coordinate

ddy(S):

Take the derivative with respect to the domain's Y coordinate

defr(V):

Total deformation

DEF ( V ) = ( STRD (V) ** 2 + SHR (V) ** 2 ) ** .5

dirn(V):

North relative direction of a vector

DIRN ( V ) = DIRR ( un(v), vn(v))

dirr(V):

Grid relative direction of a vector

div(V):

Horizontal Divergence

DIV ( V ) = DDX ( u ) + DDY ( v )

dot(V1, V2):

Vector dot product

DOT ( V1, V2 ) = u1 * u2 + v1 * v2

dvdx(V):

Partial x derivative of a vector

DVDX ( V ) = [ DDX (u), DDX (v) ]

dvdy(V):

Partial x derivative of a vector

DVDY ( V ) = [ DDY (u), DDY (v) ]

EllrodIndex(u, v, z, top, bottom, unit):

Calculate the wind shear between two discrete layers

EI = VWS X (DEF + DIV)

frnt(S, V):

Frontogenesis function from theta and the wind

FRNT ( THTA, V ) = 1/2 * MAG ( GRAD (THTA) ) * ( DEF * COS (2 * BETA) - DIV ) Where: BETA = ASIN ( (-DDX (THTA) * COS (PSI) - DDY (THTA) * SIN (PSI))/ MAG ( GRAD (THTA) ) ) PSI = 1/2 ATAN2 ( SHR / STR )

geo(z):

Geostrophic wind from height

GEO ( S ) = [ - DDY (S) * const / CORL, DDX (S) * const / CORL ]

grad(S):

Gradient of a scalar

GRAD ( S ) = [ DDX ( S ), DDY ( S ) ]

gwfs(S, N):

Horizontal smoothing using normally distributed weights with theoretical response of 1/e for N * delta-x wave. Increasing N increases the smoothing (default N=6)

gwfv(V, N):

Horizontal smoothing using normally distributed weights with theoretical response of 1/e for N * delta-x wave. Increasing N increases the smoothing (default N=6)

inad(V1, V2):

Inertial advective wind

INAD ( V1, V2 ) = [ DOT ( V1, GRAD (u2) ), DOT ( V1, GRAD (v2) ) ]

jcbn(S1, S2):

Jacobian Determinant

JCBN ( S1, S2 ) = DDX (S1) * DDY (S2) - DDY (S1) * DDX (S2)

lap(S):

Laplacian operator

LAP ( S ) = DIV ( GRAD (S) )

latr(S):

Latitude all points in a grid

lav(S, level1, level2):

Layer Average

LAV ( S ) = ( S (level1) + S (level2) ) / 2.

ldf(S, level1, level2):

Layer Average

LDF ( S ) = S (level1) - S (level2)

LPIndex(u, v, z, t, top, bottom, unit):

Calculate the wind shear difference between discrete layers

LP = 7.268DUDZ + 0.718DTDN + 0.318DUDN - 2.52

mag():

Magnitude of a vector

mixr(temp, rh):

Mixing Ratio from Temperature, RH (requires pressure domain)

mul(S1, S2):

Multiply

MUL (S1, S2) = S1 * S2

pvor(S, V):

Potential vorticity (usually from theta and wind)

quo(S1, S2):

Divide

QUO (S1, S2) = S1 / S2

qvcl(THTA, V):

Q-vector ( K / m / s )

QVCL ( THTA, V ) = ( 1/( D (THTA) / DP ) ) * [ ( DOT ( DVDX (V), GRAD (THTA) ) ), ( DOT ( DVDY (V), GRAD (THTA) ) ) ]

qvec(S, V):

Q-vector at a level ( K / m / s )

QVEC ( S, V ) = [ - ( DOT ( DVDX (V), GRAD (S) ) ), - ( DOT ( DVDY (V), GRAD (S) ) ) ] where S can be any thermal parameter, usually THTA.

rects(S, D):

Apply a rectangular aperature smoothing to the grid points. The weighting function is the product of the rectangular aperature diffraction function in the x and y directions. D is the radius of influence in grid increments, increasing D increases the smoothing (default D=2)

relh(temp, mixr):

Create relative humidity from temperature and mixing ratio (requires pressure domain)

savg(S):

Average over whole grid

SAVG (S) = average of all non-missing grid point values

savs(S):

Average over grid subset

SAVS (S) = average of all non-missing grid point values in the subset area

sdiv(S, V):

Horizontal Flux Divergence

SDIV ( S, V ) = S * DIV ( V ) + DOT ( V, GRAD ( S ) )

shr(V):

Shear Deformation

SHR ( V ) = DDX ( v ) + DDY ( u )

sm5s(S):

Smooth a scalar grid using a 5-point smoother

SM5S ( S ) = .5 * S (i,j) + .125 * ( S (i+1,j) + S (i,j+1) + S (i-1,j) + S (i,j-1) )

sm9s(S):

Smooth a scalar grid using a 9-point smoother

SM9S ( S ) = .25 * S (i,j) + .125 * ( S (i+1,j) + S (i,j+1) + S (i-1,j) + S (i,j-1) ) + .0625 * ( S (i+1,j+1) + S (i+1,j-1) + S (i-1,j+1) + S (i-1,j-1) )

sm5v(V):

Smooth a scalar grid using a 5-point smoother (see sm5s)

sm9v(V):

Smooth a scalar grid using a 9-point smoother (see sm9s)

strd(V):

Stretching Deformation

STRD ( V ) = DDX ( u ) - DDY ( v )

sub(S1, S2):

Subtract

SUB (S1, S2) = S1 - S2

thrm(S, level1, level2):

Thermal wind

THRM ( S ) = [ u (GEO(S)) (level1) - u (GEO(S)) (level2), v (GEO(S)) (level1) - v (GEO(S)) (level2) ]

thta(temp):

Potential Temperature from Temperature (requires pressure domain)

thte(temp, rh):

Equivalent Potential Temperature from Temperature and Relative humidity (requires pressure domain)

un(V):

North relative u component

ur(V):

Grid relative u component

vadd(V1, V2):

add the components of 2 vectors

VADD (V1, V2) = [ u1+u2, v1+v2 ]

vecn(S1, S2):

Make a true north vector from two components

VECR ( S1, S2 ) = [ S1, S2 ]

vecr(S1, S2):

Make a vector from two components

VECR ( S1, S2 ) = [ S1, S2 ]

vlav(V, level1, level2):

Calculate the vector layer average

VLDF(V) = [(u(level1) - u(level2))/2, (v(level1) - v(level2))/2]

vldf(V, level1, level2):

Calculate the vector layer difference

VLDF(V) = [u(level1) - u(level2), v(level1) - v(level2)]

vmul(V1, V2):

Multiply the components of 2 vectors

VMUL (V1, V2) = [ u1*u2, v1*v2 ]

vn(V):

North relative v component

vor(V):

Relative Vorticity

VOR ( V ) = DDX ( v ) - DDY ( u )

vquo(V1, V2):

Divide the components of 2 vectors

VQUO (V1, V2) = [ u1/u2, v1/v2 ]

vr(V):

Grid relative v component

vsub(V1, V2):

Subtract the components of 2 vectors

VSUB (V1, V2) = [ u1-u2, v1-v2 ]

wshr(V, Z, top, bottom):

Magnitude of the vertical wind shear in a layer

WSHR ( V ) = MAG [ VLDF (V) ] / LDF (Z)

xav(S):

Average along a grid row. KXD = number of points in row; KNT = number of non-missing points in row; XAV for a row is stored at every point in that row

XAV (S) = ( S (X1) + S (X2) + ... + S (KXD) ) / KNT

xsum(S):

Sum along a grid row. KXD = number of points in row; XSUM for a row is stored at every point in that row

XSUM (S) = ( S (X1) + S (X2) + ... + S (KXD) )

yav(S):

Average along a grid column. KYD = number of points in column; KNT = number of non-missing points in column

YAV (S) = ( S (Y1) + S (Y2) + ... + S (KYD) ) / KNT

ysum(S):

Sum along a grid column. KYD = number of points in row; YSUM for a column is stored at every point in that column

YSUM (S) = ( S (Y1) + S (Y2) + ... + S (KYD) )

zav(S):

Average across the levels of a grid at all points. KZD = number of levels; KNT = number of non-missing points in column

ZAV (S) = ( S (Z1) + S (Z2) + ... + S (KZD) ) / KNT

zsum(S):

Sum across the levels of a grid at all points. KZD = number of levels ZSUM for a vertical column is stored at every point

ZSUM (S) = ( S (Z1) + S (Z2) + ... + S (KZD) )

Module: ensemble

This is the doc for the grid ensemble module. For more information, see Description of Formulas - Grids.

ens_mode(grid):

Mode value

ens_prcntl(grid, percent):

Percentile value

ens_savg(grid):

Basic ensemble average

ens_smax(grid):

Max value of all members

ens_smin(grid):

Minimum value of all members

ens_srng(grid):

Max - min grid values

ens_ssprd(grid):

Standard deviation of all members

ens_uprob(grid, logicalOp1, pValue1, and_or, logicalOp2, pValue2, exptdLoBound, exptdUpBound):

Ensemble univariate probability calculation

Module: image


combineABIRGB(chP64, chP86, chP47):

Combines three GOES 16/17 bands (including a simulated green band) to create an RGB image

combineRGB(red, green, blue):

Combine 3 images as an RGB image

makeNavigatedImage(d, ulLat, ulLon, lrLat, lrLon):

This takes a image data object and a lat/lon bounding box and adds a lat/lon domain to the data. Use it in conjunction with a formula:

Module: maps

A set of utilities to apply to a map field. For more information, see Description of Formulas - Maps.

applyFunctionToValuesInField(function, field, min, max, inside):

applyFunctionToValuesInRange(function, range, timeStep, min, max, inside):

applyToIndices(function, range, timeStep, indices):

averageFromMap(field, mapSets):

mapSets defines a set of polygons. This procedure fills the areas in the field are enclosed by each polygon with the average value within that area

averageFromMapAndClip(field, mapSets):

averageRangeFromMap(range, timeStep, mapSets):

mapSets defines a set of polygons. This procedure fills the areas in the field are enclosed by each polygon with the average value within that area

filterMaps(mapSets, propName, operator, value):

Return a new set of maps whose property propName satisfies the given operator/value. The operators can be ==,!=, <,>,<=,>=, match, !match

getMapProperty(polygon, propName):

Get the named property from the given mapData

getMapsWithProperty(mapSets, propName, value):

Return a new set of maps that have the given property value

make3DMap(map, topo):

Make a 3d map. map - map line data - topo - topography dataset

makeFieldFromMapBounds(mapSets, length1, length2, fill, unit):

Make a field whose lat/lon area is the bounds of the given mapSet. It has length1 points in the x and length2 in the y. Fill it with the fill value and the given unit

mapsAbsoluteValue(originalValues, newValues, indexArray):

mapsApplyToField(function, field, mapSets, inside):

Fills the areas in the field are enclosed by each polygon with the average value within that area. mapSets defines a set of polygons

mapsApplyToRange(function, range, timeStep, mapSets, inside):

mapsAverage(originalValues, newValues, indexArray):

mapsMax(originalValues, newValues, indexArray, value):

mapsMin(originalValues, newValues, indexArray, value):

mapsSetValue(originalValues, newValues, indexArray, value):

subsetFromMap(field, mapSets, fillValue, inverse):

mapSets defines a set of polygons. This procedure fills the areas in the field that are not enclosed by the polygons with the fill value. If inverse is 1 then it fills the areas that are enclosed

subsetRangeFromMap(range, timeStep, mapSets, fillValue, inverse):

mapSets defines a set of polygons. This procedure fills the areas in the field that are not enclosed by the polygons with the fill value. If inverse is 1 then it fills the areas that are enclosed

subsetRangeWithProperty(range, mapSets):

test code

subsetWithProperty(field, mapSets):

test code

Module: shell

A set of utilities for selecting data and creating displays. For use from the Jython shell.

clear():

Clear the shell

createDisplay(displayType, data, dataName):

Create a display of type displayType. Right click in input field to select particular displayType. The data is can be a data object, a datachoice or a list of data or datachoices The dataName is used to name the data, i.e., its the parameter name

findDataSource(name):

Find the data source object with the given name. If no name is given then this will return the first (non-formula) data source

getData(dataSourceName, dataChoiceName):

Find the data source with the given name and the data choice on that data source with the given name. If no dataSourceName is given then use the first one in the list If no dataChoiceName is given then use the first one held by the data source Return the data for the data choice. If no data source or data choice is found then return null

getDataChoice(dataSourceName, dataChoiceName):

Find the data source with the given name and the data choice on that data source with the given name. If no dataSourceName is given then use the first one in the list If no dataChoiceName is given then use the first one held by the data source Return the data choice If no data source or data choice is found then return null

listVars():

List all of the variables defined in the shell's interpreter

makeDataSource(path, type):

Create a datasource from the given file name or url. The optional type parameter is used to specify the type of data

printType(data):

Print out the math type of the given data

selectData(name1, name2, name3, name4, name5):

Select up to 5 data fields. This returns a List of the actual Data objects

selectDataChoice(name1, name2, name3, name4, name5):

Select up to 5 data choices. This returns a List of the data choices, not the actual Data To get the data do:

dataList.get(0).getData(None)

setDataChoices(dataSource):

The given dataSource can be an actual data source or the name of a data source. This procedure will define a set of jython variables that correspond to the data choices held by the given data source

setDataSources():

This procedure will define a set of jython variables, 'dataSource0, dataSource1, ...' that correspond to loaded data sources

showLib():

Bring up the jython library dialog

Module: misc

A set of miscellaneous utilities.

cloneArray(array):

Make a 2 dimensional float array filled with the given value

idveval(formula):

Evaluate a formula

makeFloatArray(rows, cols, value):

A utility to make a 2 dimensional float array filled with the given value

printSounding(sounding):

Print out the values of the sounding data

printSoundings(data):

Print out the values of the set of sounding data

Module: sandwich


sandwich(imgIR, imgVIS, minIR, maxIR, colorTable, useNaN):

Creates a 3-color RGB sandwich product image from infrared and visible data


Display Settings

The Display Settings facility allows you to select a set of properties from a display control (e.g., color table, contouring info, isosurface value, label template, etc.) and apply them to other display controls and/or save them as preferences to be used when creating new display controls.

The Display Settings dialog can be opened with the Edit->Display Settings... menu in the Layer Controls tab of the Data Explorer.

Image 1: Display Settings Dialog
Image 1: Display Settings Dialog

The left panel in this window is titled Source and includes two tabs, Displays and Saved Settings. The Displays tab includes all of the display types currently loaded into McIDAS-V. This tab is useful to make display settings changes within a session. If you wish, you can save these settings to be used in future sessions by using the File->Save Selected Properties menu item. The Saved Settings tab includes a list of any saved display settings you have made in previous sessions. You can store several different saved settings at once by grouping them into different categories.

The center panel of the window is titled Properties. These are the properties of the currently selected display control, which is shown highlighted in blue in the Source panel. On the right is also a list of target display controls.

The purpose of this is that you can select properties in the Properties panel that you want to apply to the selected target display controls (via the checkboxes) on the right. Many of the properties can be changed by clicking on the Properties icon buttons.

The Select menu is useful for selecting different groups of target display controls. For example, you can select all displays, displays of certain types, displays that have the same data source, etc.

Display Settings Examples

If you have two different data sources loaded with several displays created from each, normally the legend will list all of the displays based on some display category (e.g., Plan Views). However, you can change their display category so that each group of displays that are from one data source have the same category (e.g., "Data source 1", "Data source 2"). You can do this by changing the "Display Category" property under "Labels" to "Data Source 1".

Image 2: Enter New Value for Legend Label Dialog
Image 2: Enter New Value for Legend Label Dialog

Then, you could manually select the displays you want to change, or use the Select menu and choose "Displays with data source: ...":

Image 3: Select Menu of the Display Settings Dialog
Image 3: Select Menu of the Display Settings Dialog

This selects the displays with the data source of the currently selected display.

Once selected, you then hit Apply button, and the "Display Category" will be set on the selected display controls.

To do the next set of displays, select a new Source display control in the list on the left. This will select this display and reset the properties list in the middle. Then, when you click Select->Displays with data source, the displays that share the data source from this new display will be selected.

Saving Display Settings

You can save the set of selected settings with the File->Save Selected Properties option. The Save Display Settings dialog will be shown:

Image 4: Save Display Settings Dialog
Image 4: Save Display Settings Dialog

You can enter a category and a name. The saved settings will be shown under the Saved Settings tab. When selected they will be applied to the list of properties on the left. If you select the checkbox for Applicable only to displays of type, only the display listed will be an option in the Displays panel of the Field Selector.

Using Display Settings in the Field Selector

The set of saved display settings are also shown in the Field Selector:

Image 5: Display Settings in the Field Selector
Image 5: Display Settings in the Field Selector

You can select any number of these, and when a new display control is created, these settings will be applied to the new display. The Show All checkbox allows you to list all of the settings, regardless if they were saved for a particular type of display.

Menus

Many of the menu items seen utilizing this display are standard options that can be found in the Menus section of the Layer Controls page. However, there are several options unique to this display.

The File menu has this unique option:

The Select menu has these unique options:


Plugin Creator

The Plugin Creator, accessed through the Tools->Plugins->Create... menu item in the Main Display window, allows you to create new plugins. The Plugin Creator is broken up into three tabs: Resources, Excludes, and Properties.

A plugin is a Java JAR file that contains a set of resource files. These resource files can include things like the color tables you have created, projections, layout models, formulas, etc. The plugin manager supports both adding in a whole file (e.g., all of the color tables you have created) as well as adding in individual resource objects (e.g., a specific color table you have created).

Adding Resources

To add in a file, use the File->Add File menu item. The file dialog will come up listing the contents of your local McIDAS-V directory. This is where all of the various resources that are created are stored. For example, if to include all of the color tables, add the colortables.xml file. Use the File->Add Preferences menu item to add your User Preferences to a resource, such as a bundle you are creating or editing. Individual resources can be added through the File->Add Resource menu item. Resources can also be added through the various resource editors (e.g., Jython Editor, Parameter Defaults, Parameter Aliases). Typically this facility is available through the editor's File menu.

Resources List

Each file, preference, and resource that is added into the Plugin Creator is listed under the Resources tab:

Image 1: Resources Tab of the Plugin Creator
Image 1: Resources Tab of the Plugin Creator

Resources can be deleted by clicking the Delete a plugin button button or by pressing the delete key when a resource is selected.

Excludes

The Excludes tab allows for the exclusion of system default resources. For example, in the below image, Color tables and Map projections are excluded. When the plugin that is defined here is loaded into McIDAS-V, the excludes will result in only the Color tables and Map projections that are defined in this plugin to be used.

Image 2: Excludes tab of the Plugin Creator
Image 2: Excludes Tab of the Plugin Creator
Properties

The Properties tab allows the user to overwrite different properties McIDAS-V uses. This listing is broken up into three categories: User Interface, Data, and Miscellaneous.

Image 3: Properties Tab of the Plugin Creator
Image 3: Properties Tab of the Plugin Creator

The User Interface category primarily affects the aesthetic appearance and basic usability in McIDAS-V. These options allow you to decide if you want to do the following:

The Data category affects what sources of data you will have available when selecting data in the Data Sources tab of the Data Explorer. These options allow you to decide the following:

The Miscellaneous category affects many features of McIDAS-V. While these options affect many things that go on 'under the hood' of McIDAS-V, there is a great deal that can be changed with these options. These options allow you to decide the following:

Writing the Plugin

To write the plugin, click the Write Plugin button button. If you have not specified a plugin file name, (i.e., a .jar file) you will be prompted. If you also want to install the plugin to your local McIDAS-V plugins area, select the Install checkbox. You can choose a specific location to save the plugin to by selecting the Browse button button, or by typing the file path into the field. Note: You will need to restart McIDAS-V for any installed plugins to take effect.

Menus

Many of the menu items seen utilizing the Plugin Creator tool are unique to this menu item.

The File menu has these unique options:


Plugin Manager

McIDAS-V plugins are a way to add to or modify the functionality of McIDAS-V. Plugins can range from adding new resources (e.g., color tables, layout models, maps) to changing the entire application. Plugins are typically Java JAR archive files that can contain a set of McIDAS-V resources and Java code. They are kept in a special directory on disk and are loaded at run time.

Plugin Command Line Arguments

You can load a plugin (one time only) with the:


-plugin <plugin file or URL>

command line argument.

You can install a plugin with the:


-installplugin <plugin file or URL>

command line argument.

You can start McIDAS-V without any plugins with the:


-noplugins

command line argument.

Plugin Manager

The Plugin Manager, accessed through the Tools->Plugins->Manage... menu item in the Main Display window, allows you to list, install, and manage plugins.

Image 1: Plugin Manager
Image 1: Plugin Manager

A list of the installed plugins is shown at the top of the Plugin Manager, and a list of available plugins is shown below that. Click on an icon to perform an action in the Plugin Manager:

Image 2: Plugin List Dialog
Image 2: Plugin List Dialog
Menus

There are a few menu items that are unique to this tool.

The File menu has these unique options:

The Help menu has this unique option:


Miscellaneous

Bundles

Bundles let you save a quick "snapshot" of McIDAS-V, including data sources, maps, and data displays. Bundles are small information files that specify the state of McIDAS-V. They are a kind of configuration file. They include information about what data sources are in use, and which parameters from the data sources are displayed, and how they are displayed.

The purpose of bundles is for you to save a particular McIDAS-V setup and display. A bundle can be used for your own reference at a later time, or others using McIDAS-V can use bundles you made to see data the same way you did.

Saving a Bundle

To make a new bundle file, select the File->Save Bundle menu item in the Main Display window. A pop-up window will let you set a new file location and name:

Image 1: Bundle File Dialog
Image 1: Save Bundle Dialog

The customary McIDAS-V bundle filename extension is .mcv; if you do not enter a file extension, .mcv will be appended. When saving a .mcv file, no data is saved with the bundle, only references to the remote or local Data Sources are saved.

McIDAS-V does support a zipped data bundle format: .mcvz. This is a zip file that contains a regular bundle (.mcv) and a set of data files. When the user does a "Save Bundle" or "Save Favorite" and specifies a .mcvz file extension, McIDAS-V prompts the user to select the data sources that should be written into the zip file. When opening a .mcvz file, McIDAS-V needs to unzip the data files, so it prompts the user as to where to place the files - a temporary directory or a user selected directory (this is a preference as well).

Note: In order for bundle files to work, the data must be available in exactly the same way you made connection to it when you made the bundle file. Others who use your bundles must have access to the same file system or to the same remote or local data servers you use, so that file paths or URLs to the data are exactly the same.

The file dialog has a set of buttons to define how parts of your bundle is saved.

Saving a Bundle as a Favorite

Favorite bundles are just normal bundles that are categorized and saved off in a particular location on disk and serve as a convenience to the user. This allows the user to organize their favorites by category and readily load them in. Favorite bundles are easily available through the Bundles menu and can also be displayed on the toolbar of the Main Display window.

A favorite bundle can be created through the File->Save Favorite... menu item in the Main Display window:

Image 2: Save As Favorite Dialog
Image 2: Save As Favorite Dialog

Define your favorite bundle by specifying a category in the Category field and a name in the Name field. Categories can be hierarchical; by using a ">" as a separator (e.g. Toolbar>sounding) the categories will appear as a tree structure in the Local Favorites Bundles Manager. The "Toolbar" category is a special category in the Favorite Bundles Manager. The bundles in the Toolbar category will also appear as links in the toolbar of your Main Display window.

The Local Favorite Bundles Manager, accessed through the Bundles->Manage... menu item in the Main Display window, allows you to reorganize the categories and favorites by drag-and-drop, or right click on a favorite or a category to delete it, export it, etc.:

Image 3: Local Favorite Bundles Manager
Image 3: Local Favorite Bundles Manager

Once a bundle has been saved as a favorite, it can be set as your default bundle that will load automatically when you start McIDAS-V. You can set a default bundle in the Advanced tab of the User Preferences window. Note that after saving a favorite bundle, you must restart McIDAS-V before the bundle will be visible in the User Preferences window.

The Show McIDAS-V system bundles checkbox at the bottom of the window sets the visibility of the Current WX bundles on the Main Toolbar. This option is turned on by default. The visibility of the system bundles can also be set in the General tab of the User Preferences window.

Opening a Bundle

Use the File->Open File menu item in the Main Display window to open a bundle. When loading in a new bundle you will be prompted whether the current displays and data should be removed. You can also start up McIDAS-V with a bundle file or URL in the command line.

There is also an option in the Open File window for Change data paths. If option is not selected, then the bundle will load exactly as it was saved, using the same data source. If this option is selected, then the user will be given the option of changing the data source to use when loading the bundle. This allows the bundle to load with a new data source, but display the data as it was saved in the bundle, essentially treating the bundle as a display template for the new data. An example of when this could be used would be if a bundle was created to display mean sea level pressure (MSLP) from GFS CONUS data. Once this bundle is loaded, if the Change data paths option was selected, the user could change the data source to NAM CONUS data, and the MSLP from NAM would display instead of GFS.

Copying Data Locally

For most remote data types, data can be copied from the server to the local disk using the "Make Remote Data Local" facility. The following ADDE types are supported: satellite, radar, point, sounding and forecast fronts. There is also preliminary support for grids on remote servers* (see below).

This is used in two ways. First, the user can right-click on a data source in the Field Selector and select "Make Data Local" for remote data sources. McIDAS-V prompts for a file directory and a file prefix (the default is to use the name of the data source) and the remote data is copied over. For multiple files the format used is: <directory><prefix><file count>.<suffix>. The data source object within McIDAS-V is then changed to point to the new file paths.

The second way this is used is when a .mcvz file is saved. The user is prompted for both the local data sources to be saved off as well as for the remote data sources. For the remote ones, McIDAS-V automatically copies the files over and zips them.

*Grids: There is preliminary support for grids. This support relies on some extra service information in the catalogs which, right at this moment, is not included in the regular IDV gridded data catalog but is included for model data under the "File_Access" dataset in the main thredds catalog: https://www.ssec.wisc.edu/mcidas/software/v/threddsRTModels.xml When saving gridded data the user is prompted for the fields to save and the geo-spatial subset is used to subset the grids. As of right now, there is not yet support for sub-setting on times and grid stride/decimation.

IDV Bundles

McIDAS-V has the ability to load IDV bundles (.xidv and .zidv), but all of the features between the two software packages may not be compatible, and therefore the bundles may not load properly in the other software package.


Time Matching

Time matching is a feature designed to create loops that accommodate data with differing temporal frequencies. An example where time matching would be useful is if a user wants to create a loop of satellite data overlaid with radar data but they have different frequencies (e.g., the satellite data comes in twice an hour while the radar data comes in eight times an hour). In the past, a user would have to use the Absolute Times tab of the radar data and individually select the times closest to those of the satellite data. With time matching, this is no longer necessary. See the example image below:

Image 1: Time Matching Example
Image 1: Time Matching Example

The example above shows the temporal frequency that satellite and radar images come in (each image is marked by an 'x'). In this example, the satellite data is set as the driver, and radar data is set to match the driver. When using time matching, McIDAS-V will look at the time of each satellite image and pick out the radar image with a time closest to that of the satellite image. This radar time may be earlier or later than the satellite time. In this example, only the satellite and radar times contained in the rectangles are used in the display. Therefore, every satellite image is displayed, but only every fourth radar image is displayed.

Time matching can be used with a variety of types of data, including satellite, radar, grid, and point data. In general, the item with the lowest temporal frequency will be set as the "time driver", while other items will be set to match the times of the driver.

The time driver can also be set in the Time Animation Widget. There is an option in the Define Animation Times tab called Set as Time Driver. This feature allows a user to set a block of times to be a driver before loading any data. For example, a time animation over the last 5 hours in 30 minute increments can be set as the driver, and layers chosen to match time driver times will match the Time Animation Widget times.

Multiple time drivers can be used in the same session, and each time driver is only the driver for the panel that the layer is displayed in. Therefore, with a multi-panel display, if a time driver is set in panel 1, only layers displayed in panel 1 will be able to match the time driver. If a layer is displayed in panel 2 using the Match Time Driver in the Times tab of the Field Selector, then there will be an error since no time driver is set in that panel. However, each panel is capable of having a time driver set for it.

Terminology
Methods of Setting the Time Driver
Methods of Matching the Time Driver

Adaptive Resolution

*** For this McIDAS-V 1.9 release adaptive resolution is still under development so there may be bugs and there could implementation changes in the future. Adaptive resolution is currently available in the Gridded Data, Point Observations, General Files/Directories, and the Under Development > Imagery - Satellite choosers. Because it's still under development, adaptive resolution is disabled by default. In order to use adaptive resolution, it must be enabled through the Display Window tab of the User Preferences.***

Adaptive resolution is a feature designed to load high resolution data efficiently by obtaining and loading only the minimum amount of data needed to display all of the observable features in the given display size and geographic domain. If the domain is subsequently changed by using either Shift+left-click+drag or the Projections menu, adaptive resolution automatically reloads the data at a higher resolution (if available) if the user zoomed in to a more detailed view, or reloads the data at a lower resolution (sampled) if the user zoomed out to a wider view.

If the data is sampled, it is indicated in the Legend of the Main Display, where a line similar to 'Data Sampling: every 3rd pixel' or 'Data Sampling: every 4th by 5th grid point' appears below the layer label. If the data is displayed at full resolution, then no data sampling text will be written. In the example below, the data is sampled is every 3rd grid point in the x direction by every 2nd grid point in the y direction. The sampling text is controlled by the resolution macro in the Extra Legend Labels field of the Properties Dialog for the layer.

Image 1: Legend of Main Display Window
Image 1: Legend of Main Display Window

The AR Off/On popup appears when the Resolution Control button Resolution Control Button is clicked. This button has two options:

There are four ways of setting adaptive resolution on or off:

Currently, these are the data sources that are capable of using adaptive resolution:


Scripting

McIDAS-V can be scripted to create and manipulate images and movies. The scripting is accomplished using Jython. Jython is an implementation of the Python language in Java and follows Python syntax.

McIDAS-V scripting can be done from the Jython shell, or a Jython script can be invoked as a command line argument.

In Unix, from the McIDAS-V-System directory:

   runMcV -script /home/user/example.py 
In Windows, from the McIDAS-V System directory:
   runMcV.bat -script C:/Users/user/example.py 

Users can pass arguments through scripts at runtime with the scriptargs flag, which uses uses standard Python optparse/argparse syntax within the script to specify the arguments. Anything after the scriptargs flag will be considered a scripting argument, so scriptargs should be specified last. For example, if a script is set up to allow a user to pass through a band number with "--bands", the script can be run in the following way to request band 8 (Unix and Windows examples):

   runMcV -script /home/user/example.py -scriptargs --band 8

   runMcV.bat -script C:/Users/user/example.py -scriptargs --band 8

When invoked as a command line argument, the user interface will not be shown. However, McIDAS-V still needs to be run with an active window system (e.g., X, MS Windows) for it to run. If running under a Linux/Unix machine with no X server running, McIDAS-V must be run under the X virtual frame buffer, xvfb.


McIDAS-V supports a number of functions and methods to load and display data, manipulate the display, and to save images. Download the example script to see how to use each one (example18.py). This page contains a list of functions that are supported in McIDAS-V. You can find more information about each function, including parameters, keywords, and example commands, by clicking on a function or a function category.

Create an Object:

Create an Object - Imagery:

Create an Object - Grids:

Modify the Display Object: Modify the Layer Object: Modify the Layer Object - Point: Data Analysis: Save the Display: Environment:

For users looking for more functionality from McIDAS-V scripting, additional functions can be found in the Java docs for visAD, netCDF, IDV, and McIDAS-V. Please send any questions or requests for functionality to the McIDAS-V Support Forum on scripting.


Create an Object

buildWindow - Creates a window and returns an array of panels (single panel currently supported)

Usage: panel=buildWindow(keywords)
Keywords - optional:
height= height of the window
width= width of the window
panelTypes= type of display to create
MAP (default)
GLOBE
MAP2D
widgets= include toolbar buttons in the window
True (default)
False
Example:
panel=buildWindow(height=600,width=800,panelTypes=GLOBE)
panel=buildWindow(height=600,width=800,panelTypes=MAP)
Remarks:
When widgets=False is passed through buildWindow(), there will be no toolbar buttons, including the top toolbar that allows for closing the window. There are two ways of closing this window within McIDAS-V. To do this, the findWindow() function (defined below) can be used, or a "with statement" can be used. When working in a foreground session, it is possible to build a window that will close itself once it has completed the process assigned to it using Python's "with statement" functionality. For example, a user can build a window, display a loop of satellite data, write a movie, then have the window close automatically when the movie capture is complete. Here is an example of how to use this functionality with buildWindow.
with buildWindow(height=1000,width=1200) as panel:
layer = panel[0].createLayer('Image Sequence Display',myLoop)
writeMovie('C:/Users/myUser/myMovie.gif')

createLayer - Creates a new data layer in a panel

Usage: myDataLayer = panel[0].createLayer(keywords)
Keywords - required:
display type= display type for layer; valid options shown in Field Selector (e.g. 'Image Display', 'Image Sequence Display')
myData= data object to display (from loadADDEImage)
Example:
layer=panel[0].createLayer('Image Display', data)

findWindow - Finds and creates a reference to the window containing a display

Usage: window = findWindow(display=panel[0])
Keywords - required:
display= display name defined from buildWindow
Remarks:
The buildWindow function returns a reference to a specific panel in a window, and therefore any functions run on this panel will only impact that one panel, not the window as a whole. This findWindow function returns a reference to the actual window containing the buildWindow panel. This allows for performing actions on the window itself, such as adding new tabs and closing the window.
Example:
panel = buildWindow()
window = findWindow(display=panel[0])
see(window) # return which functions/methods can be applied to 'window'
window.createTab()
window.close()

openBundle - Creates a new window and displays contents of a bundle

Usage: openBundle(keywords)
Keywords - required:
bundle file= file name of bundle
Keywords - optional:
height= height of display; default= height of the display window when the bundle was saved
width= width of display; default= width of the display window when the bundle was saved
dataDirectory= a dictionary where the keys are datasource names, and the values are either a string or list of strings representing the full path name/names of the data that will be used in place of the data in the bundle
mode= specifies the method that will be used to open the bundle
REPLACE - Removes any previously-loaded layers and data sources and replaces the current session with the bundle's data (default)
NEWWINDOW - Loads the bundle's data and displays into a new window, without removing any previously-loaded layers and data sources
MERGE - Loads the bundle's data and displays into the current tab of the active display window without removing any previously-loaded layers and data sources
NEWTAB - Loads the bundle's data and displays into a new tab of the active display window without removing any previously-loaded layers and data sources
Example:
openBundle('C:/Users/myUser/bundle.mcv',mode='NEWTAB')

Create an Object - Imagery

getLocalADDEEntry - Gets the descriptor for a local ADDE entry

Usage: localDescriptor=getLocalADDEEntry(keywords)
Keywords - required:
dataset= local ADDE entry dataset name
imageType= image type of local ADDE entry
Example:
desc = getLocalADDEEntry(dataset='AREA',imageType='Area files')

listADDEImages - Lists data from an ADDE Image server that matches the keywords in the request - returns metadata objects which can be passed into loadADDEImage

Usage: directoryList = listADDEImages(keywords)
Keywords - required (local):
localEntry= local dataset defined by makeLocalADDEEntry or the descriptor returned from getLocalADDEEntry
Keywords - required (remote):
server= ADDE server
dataset= ADDE dataset group name
descriptor= ADDE dataset descriptor
Keywords - optional:
day= single day ('date 1') or as a day range ('begin date','end date'); default=most recent day included in data
time= ('begin time','end time'); default=most recent time included in data
band= McIDAS band number; must be specified if requesting data from multi-banded image; default=band in image
unit= calibration unit to request; default = 'BRIT'
position= time relative (negative values) or absolute (positive values) position in the dataset. Use "ALL" to obtain all positions. Multiple positions are obtained when a negative value is used. For example, if position=-4 is used, then the five most recent images will be obtained (positions -4, -3, -2, -1, and 0 (most recent)); default=0 (most recent image).
accounting= ('user', 'project number') user and project number required by servers using McIDAS accounting; default = ('idv','0'). If no accounting is defined for a server/dataset requiring it, McIDAS-V will first check the ADDE Data Manager to see if any accounting is defined for the server/dataset before erroring
debug= send debug information to file; default=False
showUrls= True = Prints the ADDE URL returned from the server to the Jython Shell once the command has completed
False = Does not print the ADDE URL returned from the server to the Jython Shell once the command has completed
default=True
Examples:
directoryListLocal = listADDEImages(localEntry=desc, band=4, unit='TEMP')
directoryListRemote = listADDEImages(server='adde.ssec.wisc.edu',dataset='RTIMAGES',descriptor='GE-IR',unit='TEMP')
The data object returned from listADDEImages contains a variety of key:value pairings with information about the data. The list of keys may vary dependent on the server or type of data, but here is a general list of keys that may be included in the data object returned from listADDEImages as well as example values:
Key Example Value
accounting ('idv', '0')
band-count 1
bandList [10]
bandNumber 10
bands [10]
calibration-scale-factor 1
calibration-type RAW
calibration-unit-name None
calinfo ['RAW', 'RAW', 'TEMP', 'TEMPERATURE', 'BRIT', 'BRIGHTNESS'
center-latitude 38.494698
center-latitude-resolution 2.0
center-longitude -74.999992
center-longitude-resolution 2
centerLocation (38.494698, -74.999992)
dataset EASTA
datetime 2018-10-24 14:51:27Z
day 2018297
debug false
descriptor M1
directory-block list of the first 64 words of the AREA
elements 500
imageSize (500, 500)
lines 500
memo-field GOES Mesoscale1
nominal-time 2018-10-24 14:51:27Z
resolution (2.0, 2.0)
sensor-id 186
sensor-type GOES 16 imager
server easta.ssec.wisc.edu
source-type ABIN
start-time

2018-10-24 14:51:27Z

time 14:51:27
unitList ['TEMP']
unitType TEMP
url URL that prints to Jython Shell when data retrieved
These keys and values can be accessed the same way as defined in loadADDEImage.

listADDEImageTimes - Returns a list of available dates and times of data that match the keywords in the request

Usage: directoryList = listADDEImageTimes(keywords)
Keywords - required (local):
localEntry= local dataset defined by makeLocalADDEEntry or the descriptor returned from getLocalADDEEntry
Keywords - required (remote):
server= ADDE server
dataset= ADDE dataset group name
descriptor= ADDE dataset descriptor
Keywords - optional:
day= single day ('date 1') or as a day range ('begin date','end date'); default=most recent day included in data
time= ('begin time','end time'); default=most recent time included in data
band= McIDAS band number; must be specified if requesting data from multi-banded image; default=band in image
unit= calibration unit to request; default = 'BRIT'
position= time relative (negative values) or absolute (positive values) position in the dataset. Use "ALL" to obtain all positions. Multiple positions are obtained when a negative value is used. For example, if position=-4 is used, then the five most recent images will be obtained (positions -4, -3, -2, -1, and 0 (most recent)); default=0 (most recent image)
accounting= ('user', 'project number') user and project number required by servers using McIDAS accounting; default ('idv','0'). If no accounting is defined for a server/dataset requiring it, McIDAS-V will first check the ADDE Data Manager to see if any accounting is defined for the server/dataset before erroring
debug= send debug information to file; default=False
showUrls= True = Prints the ADDE URL returned from the server to the Jython Shell once the command has completed
False = Does not print the ADDE URL returned from the server to the Jython Shell once the command has completed
default=True
Examples:
print listADDEImageTimes(localEntry=desc, position=-5)
print listADDEImageTimes(server='adde.ssec.wisc.edu',dataset='RTIMAGES',descriptor='GE-IR',time=('02:00','04:00'),position='ALL')
The data object returned from listADDEImageTimes contains a variety of key:value pairings with information about the data. The list of keys may vary dependent on the server or type of data, but here is a general list of keys that may be included in the data object returned from listADDEImageTimes as well as example values:
Key Example Value
datetime '2018-10-24 14:46:27Z'
day '2018297'
time '14:46:27'
These keys and values can be accessed the same way as defined in loadADDEImage assuming that a data object returned from listADDEImageTimes was defined (e.g. timeList = listADDEImageTimes(...)).

loadADDEImage - Requests data from an ADDE Image server - returns one object containing both data and metadata

Usage: Local: dataLocal=loadADDEImage(keywords)
Keywords - required (local):
localEntry= local dataset defined by makeLocalADDEEntry or the descriptor returned from getLocalADDEEntry
Keywords - required (remote):
server= ADDE server
dataset= ADDE dataset group name
descriptor= ADDE dataset descriptor
Keywords - optional:
day= single day ('date 1') or as a day range ('begin date','end date'); default=most recent day included in data
time= ('begin time','end time'); default=most recent time included in data
coordinateSystem= coordinate system to use for retrieving data; default=server dependent
AREA = AREA file coordinates - zero based
LATLON = latitude and longitude coordinates
IMAGE = image coordinates - one based
location= (x,y); default=coordinateSystem dependent
x = AREA line, latitude, or IMAGE line
y = AREA element, longitude, or IMAGE element
place= CENTER places specified location (x,y) at center of panel (default)
ULEFT places specified location (x,y) at upper-left coordinate of panel
band= McIDAS band number; must be specified if requesting data from multi-banded image; default=band in image
unit= calibration unit to request; default = 'BRIT'
position= time relative (negative values) or absolute (positive values) position in the dataset; default=0 (most recent image)
size= number of lines and elements to request. Use "ALL" to obtain the full size of the image; default=(480,640).
mag= magnification of data (line,element), negative number used for sampling data; default=(1,1)
accounting= ('user', 'project number') user and project number required by servers using McIDAS accounting; default = ('idv','0'). If no accounting is defined for a server/dataset requiring it, McIDAS-V will first check the ADDE Data Manager to see if any accounting is defined for the server/dataset before erroring
debug= send debug information to file; default=False
track= True = with real-time data, will wait until the most recent image is complete before pulling it in
False = with real-time data, will not wait until the most recent image is complete before pulling it in. Dependent on when the loadADDEImage command is run, this may result in an incomplete image.
default=False
showUrls= True = Prints the ADDE URL returned from the server to the Jython Shell once the command has completed
False = Does not print the ADDE URL returned from the server to the Jython Shell once the command has completed
default=True
Examples:
dataLocal = loadADDEImage(localEntry=desc, size='ALL', mag=(1,1), unit='BRIT',debug=True)
dataRemote = loadADDEImage(server='adde.ssec.wisc.edu',dataset='RTIMAGES',descriptor='GE-IR',band=4,unit='TEMP')
The data object returned from loadADDEImage contains a variety of key:value pairings with information about the data. The list of keys may vary dependent on the server or type of data, but here is a general list of keys that may be included in the data object returned from loadADDEImage as well as example values:
Key Example Value
accounting ('idv', '0')
debug False
server adde.ssec.wisc.edu
calibration-scale-factor 1
bands [4]
nominal-time 2016-03-08 15:15:00Z
datetime 2016-03-08 15:15:18Z
directory-block list of the first 64 words of the AREA
source-type 'GVAR'
band-count 1
lines 480
day '2016068'
sensor-id 180
satband-band-label 10.7 um IR Surface/Cloud-top Temp
calibration-type 'BRIT'
start-time 2016-03-08 15:15:18Z
bandNumber 4
url URL that prints to Jython Shell when data retrieved
memo-field any memos included with data (e.g. the calibration-type)
elements 640
bandList [4]
sensor-type 'GOES 13 imager'
These keys and values can be printed as follows:
print dataRemote['satband-band-label']
A practical use for this satband-band-label key would be to apply it to a layer label. This example adds the key to the layer label along with the %timestamp% macro:
layer.setLayerLabel(dataRemote['satband-band-label']+' %timestamp%')

makeLocalADDEEntry - Creates a local ADDE entry in the server table

Usage: localDataset=makeLocalADDEEntry(keywords)
Keywords - required:
dataset= name of dataset - limit of 8 characters
mask= directory containing the files used by the dataset
format= data format of files used within the dataset. Either Full Name or Short Name can be used as valid options
Full Name Short Name
"AMSR-E L 1b" "AMSR"
"AMSR-E L 2a" "AMSE"
"AMSR-E Rain Product" "AMRR"
"LRIT GOES-9" "FSDX_G9"
"LRIT GOES-10" "FSDX_G10"
"LRIT GOES-11" "FSDX_G11"
"LRIT GOES-12" "FSDX_G12"
"LRIT MET-5" "FSDX_M5"
"LRIT MET-7" "FSDX_M7"
"LRIT MTSAT-1R" "FSDX_MT"
"McIDAS Area" "AREA"
"Meteosat OpenMTP" "OMTP"
"Metop AVHRR L 1b" "LV1B_METOP"
"MODIS MOD 02 - Level 1B Calibrated Geolocated Radiances" "MODS"
"MODIS MOD 04 - Aerosol Product" "MOD4"
"MODIS MOD 06 - Cloud Product" "MODX_06"
"MODIS MOD 07 - Atmospheric Profiles" "MODX_07"
"MODIS MOD 28 - Sea Surface Temperature" "MOD8"
"MODIS MOD 35 - Cloud Mask" "MODX_35"
"MODIS MOD R - Corrected Reflectance" "MODR"
"MSG HRIT FD" "MSGT_FD"
"MSG HRIT HRV" "MSGT_HRV"
"MTSAT HRIT" "MTST"
"NOAA AVHRR L 1b" "LV1B_NOAA"
"SSMI" "SMIN"
"TRMM" "TMIN"
"GINI" "GINI"
"MSG Native Format"* "MSGS"*
"Himawari-8"* "WARI"*
"HimawariCast"* "WARC"*
"INSAT-3D Imager"* "INSAT3D_IMAGER"*
"INSAT-3D Sounder"* "INSAT3D_SOUNDER"*
"GOES ABI"* "ABIN"*
"Sectorized CMI"* "SCMI"*
"VIIRS SDR Day/Night Band"* "VIIRSD"*
"VIIRS SDR I-Band"* "VIIRSI"*
"VIIRS SDR M-Band"* "VIIRSM"*
"VIIRS EDR I-Band"* "VIIREI"*
"VIIRS EDR M-Band"* "VIIREM"*

* The WARI, WARC, INSAT-3D*, ABI, SCMI, VIIRS, and MSGS local servers are currently supported on Linux and OS X/macOS platforms

Keywords - optional:
imageType= text description of the data used for the local server entry (default=format_dataset)
save= determines if the dataset will be retained from session to session (default = False)
True = retains the dataset between sessions
False = does not retain the dataset between sessions
Example:
dataPath = 'C:/Users/myUser/Data/AREA'
areaDataset=makeLocalADDEEntry(dataset='AREA', imageType='Area files', save=True, mask=dataPath, format='McIDAS Area')

Create an Object - Grids

listGridFieldsInFile - Lists the fields in a file brought in with loadGrid. The output is shortname ; longname

Usage: myData = listGridFieldsInFile(keywords)
Keywords - required:
filename= directory path to local gridded file
Example:
listGridFieldsInFile(filename='C:/Users/myUser/gfs.grb')

listGridLevelsInField - Lists the vertical levels included in a field of a loadGrid file

Usage: myData = listGridLevelsInField(keywords)
Keywords - required:
filename= directory path to local gridded file
field= the short name of the field to list levels of. A listing of field short names included in a file can be printed using listGridFieldsInFile
Example:
listGridLevelsInField(filename='C:/Users/myUser/gfs.grb',field='Temperature_Isobaric')

listGridTimesInField - Lists the times included in a field of a loadGrid file

Usage: myData = listGridTimesInField(keywords)
Keywords - required:
filename= directory path to local gridded file
field= the short name of the field to list times of. A listing of field short names included in a file can be printed using listGridFieldsInFile
Example:
listGridTimesInField(filename='C:/Users/myUser/gfs.grb',field='Temperature_Isobaric')

loadGrid - Loads local netCDF, hdf, and grib files.

Usage: myData = loadGrid(keywords)
Keywords - required:
filename= directory path to local gridded file
field= the short name of the field to load. A listing of field short names included in a file can be printed using listGridFieldsInFile.
Keywords - optional:
level= the vertical level and units to load. Default="All". A listing of vertical levels included with a field can be printed using listGridLevelsInField. Example: level="1000 hPa"
time= the time to load. This can be an integer representing the index of time to be loaded (Default=0 for earliest time). A listing of times included with a field can be printed using listGridTimesInField. This can also be set as a date/time text string. Example: time="2014-01-16 18:00:00 UTC"
xStride= integer value to reduce the resolution of display in the x-direction. Default=1 for full resolution. Higher values reduce the resolution.
yStride= integer value to reduce the resolution of display in the y-direction. Default=1 for full resolution. Higher values reduce the resolution.
stride= integer value to reduce the resolution of the display in the x and y-directions. Default=1 for full resolution. Higher values reduce the resolution.
xRange= integer for geographically subsetting by grid indices in the x-direction. By default, no geographical subsetting is done. Example: xRange=(0,80)
yRange= integer for geographically subsetting by grid indices in the y-direction. By default, no geographical subsetting is done. Example: yRange=(0,80)
latLonBounds= geographically subset by lat/lon bounds. By default, no subsetting is done. The expected format is (upper left lat, upper left, lon, lower right lat, lower right lon). Example: latLonBounds=(50,-130,20,-65)
Example:
t850 = loadGrid(filename='C:/Users/myUser/gfs.grb',field='Temperature_Isobaric',level='850 hPa')
The data object returned from loadGrid contains a variety of key:value pairings with information about the data. The list of keys may vary dependent on the type of data, but here is a general list of keys that may be included in the data object returned from loadGrid as well as example values:
Key Example Value
globalAttributes dictionary of all global attributes included with data
level 850.0
description 'Temperature @ Isobaric surface'
units 'K'
dataSourceName file path or URL of data source
times [2016-03-08T06:00:00Z]
filename name of file or URL of data source
field Temperature_isobaric
datatype float
metadataVariables dictionary of all metadata variables included with data
attributes lists all of the attributes of the field/variable loaded
projection projection information about the data
levels [850]
info 'Temperature_isobaric K false Temperature @ Isobaric surface'
variableAttributes lists all of the attributes of the field/variable loaded
These keys and values can be printed as follows:
t850['description']
The keys and values within one of the dictionary keys (globalAttributes or metadataVariables) can be printed as follows:
t850['globalAttributes']
An individual value of one of the keys in globalAttributes or metadataVariables can be printed as follows
t850['globalAttributes']['file_format']
A practical use for these key:value parings would be to apply it to a layer label. This example adds the description key to the layer label along with the %timestamp% macro:
layer.setLayerLabel(t850['description']+' %timestamp%')

Modify the Display Object

annotate - Writes text to a panel

Usage: panel[0].annotate(keywords)
Keywords - required:
text= annotation string. This string can contain HTML tags such as paragraph <p>, line break <br>, emphasize/italicize <em>, and bold <b>
lat=, lon= center text string at specified latitude and longitude (must be used together) -or-
line=, element= center text string at specified panel line and element (must be used together)
Keywords - optional:
font= name of font; default is system dependent, this uses the default defined in User Preferences
size= size of font; default = size of font defined in user preferences
style= style of font; default = style of font defined in user preferences
'BOLD'
'ITALIC'
'NONE'
color= sets the color of the text. There are two ways this can be set:
'color name'; default = 'red'
-or-
[R,G,B] fractional scaling factor for each red, green and blue value (0 to 255). For example, [255,0,0]
alignment= sets the location of the text with respect to the latitude/longitude or line/element combination entered. The format is alignment=(horizontal,vertical). For horizontal, values of "left", "right", and "center" can be used. For vertical, values of "top", "bottom" and "center" can be used. The default is alignment=("center","center") which means the text will be centered at the location of the latitude/longitude or line/element values.
bgColor= sets the background color of the text. default=None
There are two ways this can be set:
'color name'. For example, 'green' -or-
[R,G,B] fractional scaling factor for each red, green and blue value (0 to 255). For example, [0,255,0]
Example:
panel[0].annotate('EQUATOR',size=20, font='SansSerif.bold', lat=0, lon=-90, color='Green',alignment=("left","top"))

getMapLayer - Obtains a reference to the map layer in the display

Usage: panel[0].getMapLayer()
Example:
mapLayer = panel[0].getMapLayer()
mapLayer.setVerticalPosition(1)

setCenter - Centers the display on a specified latitude/longitude and sets a scaling factor

Usage: panel[0].setCenter(keywords)
Keywords - required:
lat= centers the display at the specified latitude (no default, required parameter)
lon= centers the display at the specified longitude (no default, required parameter)
Keywords - optional:
scale= scale factor for map; default = current scale factor
Remarks:
Scale factors between 0 and 1 zoom out centered on the specified latitude/longitude and scale factors greater than 1 zoom in.
Example:
panel[0].setCenter(45, -75, scale=20)

setMapLayerVisibility - Sets the visibility of the entire map layer in the display

Usage: panel[0].setMapLayerVisibility(keyword)
Keyword - required:
visibility= sets the visibility of the map layer in the display
True - displays the map
False - does not display the map
Example:
panel[0].setMapLayerVisibility(visibility=True)

setMapVisibilityByDescription - Sets the visibility of individual maps in the display

Usage: panel[0].setMapVisibilityByDescription(keywords)
Keywords - required:
description= the map to be added or removed from the display. The description matches the names of the maps in the Layer Controls.
visibility= sets the visibility of the map defined in the description keyword
True - displays the map
False - does not display the map
Examples:
panel[0].setMapVisibilityByDescription(description='World Coastlines', visibility=False)
panel[0].setMapVisibilityByDescription(description='U.S. County Outlines', visibility=True)

setProjection - Sets the projection of a panel

Usage: panel[0].setProjection(keywords)
Keywords - required:
projection= string specifying the projection; e.g., 'US>Southeastern U.S.' or the name of the layer returned from createLayer, which uses the default projection of that data. Alternatively, a layer object can be passed through this keyword. For example, if a layer was defined as myLayer when running createLayer, passing 'myLayer' through the projection keyword would set the projection to the native projection of the myLayer layer.
Example:
panel[0].setProjection(projection='US>States>N-Z>Pennsylvania')

setProjectionFromData - Enables or disables auto-set projection of a panel

Usage: panel[0].setProjectionFromData(False)
Example:
panel[0].setProjectionFromData(False)
Remarks:
By default, when a layer is displayed in a panel, the projection will be remapped to the native projection of the data. The user can disable this by passing "False" through setProjectionFromData. When this is done, the projection will not update when data is displayed. This is the same as disabling Projections -> Auto-set Projection in the Main Display window. The default for this command is "True".

setViewpoint - Sets the viewpoint of a panel

Usage: panel[0].setViewpoint(keywords)
Keywords - required:
viewpointName= string specifying the viewpoint; e.g., 'Viewpoint1'. This works in conjunction with the Projections->Viewpoints menu item in the Main Display window.
Example:
panel[0].setViewpoint(viewpointName='Viewpoint1')

setWireframe - Turns wire frame box on or off

Usage: panel[0].setWireframe(keywords)
Keywords - required:
visible= sets the visibility of the wireframe box
True - displays the wireframe box
False - does not display the wireframe box
Examples:
panel[0].setWireframe(False)
panel[0].setWireframe(True)

Modify the Layer Object

doRemove - Removes a displayed layer

Usage: layer.doRemove()
Example:
layer.doRemove()
Remarks:
This function removes a displayed layer. The user can specify the name of the layer used at createLayer() or by specifying a layer index from the array returned by getLayers().

getData - Returns a data object associated with the layer

Usage: myDataLayer.getData()
Example:
layerData = layer.getData()
Remarks:
The data object returned from the getData function (layerData from the above example) can now be passed through various formulas

getDisplayUnit - Returns the unit of a displayed layer

Usage: myDataLayer.getDisplayUnit()
Example:
layer.getDisplayUnit()

getLayer - Returns a reference to a displayed layer

Usage: layer = panel[0].getLayer(index)
Example:
satLayer = panel[0].getLayer[1]
Remarks:
This function returns a reference to a displayed error, which allows for passing this layer through other functions such as setLayerVisible(), setEnhancement(), and setLayerLabel(). The numerical value in the square brackets after getLayer in the example is the layer's index in the display. The index of displays in the displays begins with 0, which is the first layer displayed in the panel (normally the map layer). The second layer displayed would be index 1, the third layer display would be index 2, and so on.

getLayers - Returns a list of layer objects in the referenced display panel

Usage: layers = panel[0].getLayers()
Example:
layers = panel[0].getLayers()
satLayer = layers[1]
Remarks:
This function returns list of layers in the display panel. The first layer in the list, index 0 (zero) will be the first layer displayed, generally the map layer. Using this function in the above example, the satLayer object can then be passed through other functions such as setLayerVisible(), setEnhancement(), and setLayerLabel(). The numerical value in the square brackets after getLayer in the example is the layer's index in the display. The index of displays in the displays begins with 0, which is the first layer displayed in the panel (normally the map layer). The second layer displayed would be index 1, the third layer display would be index 2, and so on.

setColorScale - Displays color scale on a panel and specifies its attributes

Usage: myDataLayer.setColorScale(keywords)
Keywords - optional:
visible= True - displays color scale (default)
placement= location of color scale
'Top' (default)
'Bottom'
'Left'
'Right'
font= name of font; default = font defined in User Preferences
style= font style; default=font defined in user preferences
'BOLD' - bolded font
'ITALIC' - italicized font
'NONE'
size= size of font; default = size of font defined in User Preferences
color= 'color name'; default = color defined in User Preferences
-or-
[R,G,B] fractional scaling factor for each red, green and blue value (0.0 to 1.0)
showUnit= toggles the visibility of the display unit on the color scale (default = False)
Example:
layer.setColorScale(placement='Left',font='SansSerif',size=18.0,color='green',showUnit=True)

setDisplayUnit - Sets the unit of a displayed layer

Usage: myDataLayer.getDisplayUnit()
Keywords - required:
unitname= Sets the unit to be applied to the displayed layer.
Example:
layer.setDisplayUnit('hPa')

setEnhancement - Applies a color table and defines data range of data in a layer

Usage: myDataLayer.setEnhancement(keywords)
Keywords - required:
color table = color table name e.g., 'Longwave Infrared Deep Convection'
Keywords - optional:
range= (min,max) enhancement range; default = (min,max) of data
transparency= transparency to apply to entire enhancement. The valid range is 0 - 100, with 0 being opaque and 100 being 100% transparent; default=0
Example:
layer.setEnhancement('Longwave Infrared Deep Convection',range=(20,250),transparency=20)

setExtraLegendLabel - Sets the Extra Legend Label of the displayed layer. The Extra Legend Label is the text that lists below the blue Legend Label in the Legend of the Main Display window

Usage: myDataLayer.setExtraLegendLabel(keywords)
Keywords - required:
text= extra legend label string. This can include the macros included in the Remarks of setLayerLabel. Multiple lines can be created by using the HTML new line character: \n
Example:
layer.setExtraLegendLabel(text='%level%\n%shortname%')

setLayerLabel - Toggles a layer label on/off and defines its attributes

Usage: myDataLayer.setLayerLabel(keywords)
Keywords - required:
label = layer label string. This can include macros
Keywords - optional:
visible= True - displays layer label(default)
font= name of font; default = font defined in User Preferences.
style= font style; default = font defined in user preferences
'BOLD' - bolded font
'ITALIC' - italicized font
'NONE'
size= size of font; default = size of font defined in User Preferences
color= 'color name'; default = color defined in User Preferences
-or-
[R,G,B] fractional scaling factor for each red, green and blue value (0.0 to 1.0)
Example:
layer.setLayerLabel('%displayname% %timestamp%', size=15, color='blue', style='BOLD')
layer.setLayerLabel('%timestamp% - GOES East image', size=15, color='blue', style='BOLD')
Remarks:
There are a variety of macros that can be passed into the label keyword. Note that these macros must be contained within the label= string so they must be surrounded by quotes. These macros may differ between data sources and can include:
%displayname% The name of the display
%shortname% Shot name of parameter being displayed
%longname% Long name of parameter being displayed
%displayunit% Unit of parameter being displayed
%timestamp% Lists the timestep of parameter currently being displayed. This defaults to the time format in the User Preferences. The time format can be changed by using the macro in the form of:
%time:<time pattern>%
For example:
%time:HHz EEE dd MMM yyyy% would show something like 20UTC Wed 02 Dec 2015
%fhour% Forecast hour of grid being displayed followed by an 'H' for hour
%fhour2% Forecast hour of grid being displayed without being followed by an 'H' for hour
%level% Lists the vertical level of the parameter being displayed

setLayerVisible- Toggles layer visibility on/off, this includes any color scale or layer labels for the layer

Usage: myDataLayer.setLayerVisible(keywords)
Keywords - required:
visible= sets the visibility of the layer
True - displays the layer
False - does not display the layer
Example:
layer.setLayerVisible(visible=False)

setLegendLabel - Sets the Legend Label of the displayed layer. The Legend Label is the blue text of the layer seen in the Legend of the Main Display window

Usage: myDataLayer.setLegendLabel(keywords)
Keywords - required:
text= legend label string. This can include the macros included in the Remarks of setLayerLabel
Example:
layer.setLayerLabel(text='Layer 1')

setVerticalPosition - Sets the vertical positioning of the layer in the Main Display. The acceptable values range from -1 (bottom) to 1 (top)

Usage: myDataLayer.setLayerVisible(keywords)
Keywords - required:
verticalPosition= Sets the vertical positioning of the layer in the Main Display.
Example:
layer.setVerticalPosition(1)

Modify the Layer Object - Point

setDeclutter - Enables or disables decluttering of the layer in the display

Usage: myDataLayer.setDeclutter(keywords)
Keywords - required:
value = sets if decluttering is enabled or disabled for the layer
True - declutters the layer (default)
False - plots every point of data without decluttering
Example:
layer.setDeclutter(value=True)

setDeclutterFilter - Sets the level of decluttering used for the layer if setDeclutter is set to True

Usage: myDataLayer.setDeclutterFilter(keywords)
Keywords - required:
filterFactor = numerical value for level of decluttering to use in the display. This is a value between 0 and 1, where 0 is the maximum level of decluttering and 1 is the maximum level of decluttering. default=0
Example:
layer.setDeclutterFilter(filterFactor=0.5)

setLayoutModel - Sets the layout model used in the display

Usage: myDataLayer.setLayoutModel(keywords)
Keywords - required:
model= name of layout model to use in the display. The full directory structure to the layout model must be specified.
Example:
layer.setLayoutModel(model='Observations>Temperature')

setUseAltitudeForVerticalPosition- Toggles between displaying the data at the data's altitude (if available) or at a constant vertical position

Usage: myDataLayer.setUseAltitudeForVerticalPosition(keywords)
Keywords - required:
useAltitude= sets if the display plots at the altitude of the data or at a constant vertical position
True - displays the layer at the altitude of the data (if available) (default)
False - displays the layer at a constant vertical position, defined by setVerticalPosition()
Example:
layer.setUseAltitudeForVerticalPosition(useAltitude=False)

Data Analysis

describe - Returns a variety of statistical parameters about an imagery or gridded data objects

Usage: describe(myData1)
Example:
describe(imageryData1, imageryData2)
describe(imageryData1, imageryData2, 'Histogram', 'Mean')
Remarks:
By default, this function returns all of the following statistical parameters of data objects returned from loadADDEImage and loadGrid:

Multiple data objects can be passed through describe() at once, separated by commas (example: describe(imageryIR,imageryVIS)).

Users may select to output only certain statistical parameters for their data. When doing this, the first parameter(s) passed through describe() should be the data objects, and the last parameters should be the statistical parameters to output. These statistical parameters are included in the list above, and they should be entered as strings and quoted (see example 2 above).

findUnits - Returns the units of a data object

Usage: findUnits(myData)
Keywords - optional:
rangeOnly=

True - returns only the range unit (default)
False - returns all units associated with the data object

Example:
findUnits(imageryData)

sparkline - Returns a histogram of data values in a data object returned from loadADDEImage and loadGrid

Usage: sparkline(myData)
Example:
sparkline(imageryData)
Remarks:
Multiple data objects can be passed through sparkline() at once, separated by commas (example: sparkline(imageryIR,imageryVIS)).

Save the Display

captureImage - Writes panel display to a file

Usage: panel[0].captureImage(keywords)
Keywords - required:
file= name of file, file format determined by file extension; valid options: .jpg, .gif, .png, .ps, .pdf, .svg, .kml, and .kmz
Keywords - optional:
height= height of image (default - see Remarks)
width= width of image (default - see Remarks)
quality= quality of jpg file (0.0 to 1.0); default=1.0; not used with other formats
bgtransparent= captures image with transparent background; default=False
formatting= various formatting options to apply to the output image
createDirectories= creates the directory specified in the file keyword if it does not already exist when set to True; default=False
index= specifies the frame (index) in the display to capture when multiple frames are displayed in a loop. This is a 0-based list, where the first frame is index 0, the second frame is index 1, and so on; default=0
verbose= prints an informational line to the Jython Shell letting the user know that the image is in the process of being written; default=True
Remarks:
If captureImage is used to save a panel that was created with openBundle, the sizes default to size of the display window when the bundle was saved. If data was loaded using createLayer, the sizes default to those defined in buildWindow.
If running in a foreground session, the image capture is created from the display on the monitor. Therefore, the user is limited to a window size that fits within the bounds of the monitor. Any windows created with buildWindow must also include the Main Toolbar and Viewpoint Toolbar buttons in the window. Therefore, there is also a minimum size the display window can be. If a user wishes to capture larger or smaller images in a foreground session, they must use setFullScreenWidth(), setFullScreenHeight(), and toggleFullScreen(). The setFullScreen functions accept numerical pixel values. From the background, buildWindow can be used for any size display.
Example of capturing a large image in a foreground session:
panel=buildWindow()
panel[0].setFullScreenWidth(1500)
panel[0].setFullScreenHeight(1350)
panel[0].toggleFullScreen()
panel[0].captureImage('C:/Users/myUser/Image.gif')
Example without formatting:
panel[0].captureImage('C:/Users/myUser/Image.png')
Example with formatting:
myFormatting = [
Matte(
bottom="80",
top="80",
space="100",
),
Colorbar(
display=imLayer,
place="ML,50,0",
anchor="ML",
orientation="left",
interval="10",
width="25",
height="400",
),
ImageOverlay(
image='C:/Users/myUser/logo3.png',
place="UR,-20,10",
anchor="UR",
),
TextOverlay(
text="GOES East Image",
place="LM,0,-40",
anchor="LM",
fontSize="30",
color="black",
),
]
panel[0].captureImage('C:/Users/myUser/formattingExample.gif',formatting=myFormatting)

writeMovie - Writes an image sequence to a movie file (ISL function)

Usage: writeMovie(keywords)
Keywords - required:
file= name of file, file format determined by file extension; valid options: .gif, .mov, .mp4
Keywords - optional:
resize width= height= size of image (default = height of window)
globalPalette= sets if the animated GIF will use the color palette of each individual image or if the same colors will be used in each frame. Setting this to true helps to mitigate the flickering effect that can sometimes be seen in the color scale attached to the image. One circumstance where disabling this option may be ideal is if the movie starts with a low-light scene (not many colors) and there is no color scale in the display; default=True
createDirectories= creates the directory specified in the file keyword if it does not already exist when set to True; default=False
framesPerSecond= defines the number of frames to show each second in an animated GIF. The higher the number, the faster the GIF will play; default=2
endFramePause= defines the number of seconds to show the last frame in an animated GIF. The higher the number, the longer the last frame will be displayed before the animation returns to the beginning; default=2
Example:
writeMovie('C:/Users/myUser/movie.gif',params='resize width=600 height=800')

Environment

collectGarbage( ) - Performs a garbage collection to free up memory.

Usage: collectGarbage()

editFile( ) - Pastes the content of a text file into the text input field of the Jython Shell.

Usage: editFile(path)
path - Directory path to the file to be added to the Jython Shell.
Remarks:
Pastes the text of an existing file into the text input field of the Jython Shell. This makes it easy to evaluate and edit scripts.
Example:
editFile('C:/Users/myUser/myscript.py')

expandpath( ) - Expands the path entered.

Usage: expandpath(path)
Remarks:
Understands environmental variables such as "~" and "..".
Example:
print expandpath('$HOMEPATH')

getJythonShellMaxHistoryLength( ) - Returns the current number of commands that are saved.

Usage: print getJythonShellMaxHistoryLength()

getLogLevel( ) - Sets the logging level to be used by McIDAS-V.

Usage: print getLogLevel()
Remarks:
Returns the current logging level being used by McIDAS-V. This is composed of two items, level and effectiveLevel.
level- The logging level of the directory path used in the command. If a directory path is not specified, this is the logging level for the session as a whole.
effectiveLevel- The logging level for the specific module specified in the command
Example:
print getLogLevel( )
This returns the logging level for everything as long as a logging level for another directory hasn't already been set.

importEnhancement( ) - Imports a local enhancement file. This enhancement will then be available for use in a script as well as through the Color Table Editor in the current and future McIDAS-V sessions.

Usage: importEnhancement(filename,keywords)
Keywords - required:
filename= full path and file name of the local enhancement file
Keywords - optional:
name= name of the enhancement; default = the base filename without the extension (e.g. 'cape.xml' will become 'cape')
category= the category that the enhancement will be saved under. This name is used in the Color Table Editor under the Color Tables menu and allows for organization of enhancements; default= 'Basic'.
overwrite= sets if the command will overwrite any previously-existing enhancements with the same name. When set to False, an additional enhancement will be added to the list of color tables, and the name will be appended with '_#'. For example, if an enhancement named 'cape' already exists and an importEnhancement() command is run with the name specified as 'cape' and overwrite set to False, then the new enhancement will be saved with a name of 'cape_1'. If set to True, then the existing enhancement will be overwritten with the new one; default= False
Remarks:
The list of supported enhancement formats with importEnhancement() is the same as what can be imported through the Color Table Editor: If the enhancement specified in the filename keyword of importEnhancement() was originally exported from McIDAS-V, then the name and category keywords will be set from the values that already exist in the enhancement file.
Example:
importEnhancement(filename='C:/Users/myUser/cape.xml', name='CAPE', category='Severe')

removeAllData( ) - Removes all data sources added during the current session, without removing any displays.

Usage: removeAllData()

removeAllLayers( ) - Removes all layers that have been displayed.

Usage: removeAllLayers()

see( ) - Inspects an object passed through the function and prints out a list of different functions that can be used on the object.

Usage: setLogLevel(keywords)
Keywords:
obj= data or layer object passed through the function. The returned functions can be applied on the obj object.
pattern= filters the list of commands returned from the function. Wildcards (*) can be used.
Remarks:
If the obj keyword is omitted, the command will list all of the functions and packages that can be used in the current session.
Examples:
see(obj=data,pattern='.get*')
Returns a list of functions beginning with ".get" that can be applied on the data object.

setJythonShellMaxHistoryLength( ) - Sets the number of commands that will be saved.

Usage: setJythonShellMaxHistoryLength(number)
Remarks:
This is the number of commands that will be listed out with the File>List Saved History menu item in the Jython Shell, as well as the number that will be added to the Local Jython Library from the File>Save Commands to Jython Library menu item. The default number of commands saved to the history is 100.
Example:
setJythonShellMaxHistoryLength(25)

setLogLevel( ) - Sets the logging level to be used by McIDAS-V.

Usage: setLogLevel(level,keywords)
level- Logging level to be used. This can be set to TRACE, DEBUG, INFO, WARN, ERROR, or OFF. Information about each of these logging levels can be found in the Advanced Preferences page.
Keywords:
temporary= determines if the logging level will be saved from session to session (default = True)
Remarks:
This command can be used to set the logging level for the session as a whole, and it can also be used to set logging levels for specific directories to control what type of logging output goes to mcidasv.log.
Examples:
setLogLevel('TRACE')
Sets the logging level for everything to Trace as long as a logging level for another directory hasn't already been set.
print getLogLevel()
Returns the global logging level in McIDAS-V. Both level and effectiveLevel are set to TRACE.

Sharing
Sharing is a mechanism to share control operations between two or more displays. For example, you can have one
animation control control animation in two windows at once.

For sharing animation in two windows, such as in the main McIDAS-V view window and a vertical cross section control, open the animation properties dialog in each animation control by clicking on the icon. Toggle on the Shared box and click on Ok. Then using either animation control will effect animation in both windows.

You can share other kinds of layer controls, such as sharing one selector line in vertical cross sections. This is toggled on by clicking on the Share checkbox under the View menu in the control window.


Site Configuration
McIDAS-V can be customized for yourself and your site in a variety of ways. McIDAS-V is configured through a set of resource files. These are typically eXtensible Markup Language (XML) files that define things such as: Most of these resource files (with the exception of the chooser UI, help tips, data sources, displays and favorite bundle locations) are created through facilities provided by McIDAS-V (e.g., color table editor, formula editor, etc.).

By default McIDAS-V looks in four places for the resources it uses to configure itself. A user can enter the full path to the resource file, or use one of the four macros below which McIDAS-V will replace with the appropriate path:

When McIDAS-V first starts up it reads the system properties file: mcidasv.properties. This defines some basic information (e.g., title, splash icon, ADDE servers, etc.) as well as defining where to find other properties files. By default it looks for mcidasv.properties files under the app, site, and the user paths:

idv.properties = %APPPATH%/mcidasv.properties;%SITEPATH%/mcidasv.properties;%USERPATH%/mcidasv.properties;

You can also specify one or more properties files as command line arguments:

-properties your_properties_file

McIDAS-V processes these properties files in order, with properties defined in later files overriding those defined previously.

Once the properties have been processed McIDAS-V initializes its resources by reading in one or more resource definition files. These are called "RBI" files - (Resource Bundle for the IDV). These are XML files, the locations of which are defined by the idv.resourcefiles property:


idv.resourcefiles = %USERPATH%/mcidasv.rbi;%SITEPATH%/mcidasv.rbi;%APPPATH%/mcidasv.rbi;%IDVPATH%/mcidasv.rbi
When McIDAS-V is started for the first time, the application writes out an example RBI file to the ~user/McIDAS-V directory. This file defines the location of different collections of resources. When originally created, this mcidasv.rbi file doesn't define any paths to the different resources used by McIDAS-V, but it can be used as a template to do so. To show how this can be done, there is a commented out entry to define where McIDAS-V can find the XML files that define the color tables:

  <resources name="idv.resource.colortables" loadmore="true">

    <resource location="%USERPATH%/colortables.xml"/>

    <resource location="%SITEPATH%/colortables.xml"/>

    <resource location="http://www.somewebsite.edu/somepath/colortables.xml"/>

  </resources>

The example above tells McIDAS-V to look for color tables in the user path, sitepath, and an online URL. McIDAS-V uses the first entry in this list as the file path to write out color tables that are created using the color table editor.

The loadmore tag for the colortable resource is set to "true" by default. When this is set to true, then the colortables resource contained in all of the directories in the idv.resourcefiles property will be used, meaning the user will have access to system color tables (in the %APPPATH% directory) as well. If this loadmore tag were set to "false", then only the mcidasv.rbi contained in the %USERPATH% directory (the first path contained in the idv.resourcefiles property) would be used for the colortables resource, system resource.

This gives the flexibility to customize McIDAS-V to us only resources set by the user and not those used by McIDAS-V by default. This mcidasv.rbi file does not contain all of the resource files available for use by McIDAS-V, but instead contains a subset of commonly-used resources. Additional resources can be added to this file by the user.

An example use case of this mcidasv.rbi file is if your site needs to use a set of special color tables that you have created. Once the color tables have been created in McIDAS-V, they are saved to ~user/McIDAS-V/colortables.xml (as defined by the resource paths defined in the app path's mcidasv.rbi). This file can then be copied to a web site or on a shared file system that is pointed to by the McIDAS-V -sitepath flag. Now, your users simply need to define the -sitepath at startup and they will naturally pick up the color tables saved in colortables.xml.

Resource
Here is the list of the resource identifiers, description and file pattern (for use with plugins) of the different resources McIDAS-V uses.
Resource Identifier Description File Pattern
idv.resource.actions Actions actions.xml$
idv.resource.addeservers ADDE servers and datasets addeservers.xml$
idv.resource.aliases Data aliases aliases.xml$
idv.resource.autodisplays Automatic display creation autodisplays.xml$
idv.resource.backgroundwms Background WMS images backgroundwms.xml$
idv.resource.bundles Default bundles that are evaluated at start up no pattern
idv.resource.bundlexml Bundle xml no pattern
idv.resource.categories Display categories categories.xml$
idv.resource.choosers The definition of the user interface for data choosers choosers.xml$
idv.resource.colorpairs Color pairs no pattern
idv.resource.colortables Color tables used in the application colortables.xml$
idv.resource.controls Display controls controls.xml$
idv.resource.datasource Specification of the data sources datasource.xml$
idv.resource.derived Derived quantities derived.xml$
idv.resource.enduserformulas Native formulas enduserformulas.xml$
idv.resource.grib1lookuptables Grib 1 Lookup tables grib1lookuptable.lst$
idv.resource.grib2lookuptables Grib 2 Lookup tables grib2lookuptable.lst$
idv.resource.helptips Help tips shown in the help tips dialog helptips.xml$
idv.resource.imagesets Image Sets imagesets.xml$
idv.resource.jython Jython libraries .py$
idv.resource.locations Fixed station locations locations.xml$
idv.resource.maps Maps for the displays maps.xml$
idv.resource.menubar Commands in the menu bar (defaultmenu.xml$|menubar.xml$)
idv.resource.messages Message catalog messages.properties$
idv.resource.misccontrols Controls for different display types misccontrols.xml$
idv.resource.njConfig Configuration files njConfig.xml$
idv.resource.paramdefaults Display defaults for data paramdefaults.xml$
idv.resource.paramgroups Parameter groups paramgroups.xml$
idv.resource.plugins Plugins no pattern
idv.resource.preferences User preferences no pattern
idv.resource.projections Map projections projections.xml$
idv.resource.prototypes Prototypes no pattern
idv.resource.skin UI Skin skin.xml$
idv.resource.staeprojections Projections for USA states stateprojections.xml$
idv.resource.stationmodels Layout models stationmodels.xml$
idv.resource.stationsymbols Layout model symbols stationsymbols.xml$
idv.resource.toolbar Tool bar toolbar.xml$
idv.resource.transects Map transects transects.xml$
idv.resource.translations Hydrometeor classification value mapping translations.xml$
idv.resource.urlmaps Maps calls from old thredds server to another urlmaps.xml$
idv.resource.userchooser End user constructed data choosers no pattern
idv.resource.varrenamer Maps one field name to another varrenamer.xml$
idv.resource.viewpoints Viewpoints viewpoints.xml$

Plugin Jar Files
Note: This page is intended for someone who wants to create a McIDAS-V plugin. A description of installing and managing plugins is
here.

McIDAS-V supports a plugin architecture that allows for the easy extension and addition of functionality. A plugin is most commonly a Java Jar file that contains a set of resource files (e.g., color tables) and/or Java class files. The plugins are stored on a local directory or could be loaded form a web site. McIDAS-V processes the plugin Jar file at run time loading in the contained resources and code.

Basic Plugin
Lets suppose you have created a set of color tables and some Jython code that you want to make a plugin with. As described in the Site Configuration docs McIDAS-V stores these user created files in <user home>/.metappps/DefaultIdv as colortables.xml and default.py.

To make these into a plugin, e.g., myplugin.jar, simply jar the the files (you need to get a Java SDK for this):


jar -cvf myplugin.jar colortables.xml default.py

Now this plugin can be distributed to others and loaded into their McIDAS-V environment.

So, you might ask how does McIDAS-V recognize these files in the plugin and treat them appropriately? McIDAS-V loads in a set of resources (e.g., color tables, Python libraries). Each resource type is identified by a regular expression as shown in the resource list. In our example above the file name colortables.xml matches the pattern for color table xml resources.

Now, what happens if you have some file whose name does not match a pattern? Say, you have a color table xml file called myspecialtables.xml that you want to include in a bundle. In that case you can add a .rbi file, as described here, that defines this file as a resource:


<?xml version="1.0" encoding="ISO-8859-1"?>

<resourcebundle>

<resources name="TARGET_PluginJarFiles__idv.resource.colortables">
    <resource location="/myspecialtables.xml"/>

  </resources>

</resourcebundle>

This acts as a table of contents for the plugin. Make sure that the location is not relative. Note: Jar files can contain directory trees. e.g., /tables/myspecialtables.xml. In this case just have the location point to:

...

    <resource location="/tables/myspecialtables.xml"/>

...

Including Code
You can also include code that implements certain functionality by just including the Java .class files in the Jar. When you do this you need to include them like a normal class containing Jar file, i.e., the package structure of your code (e.g., edu.ucar.app.Test) needs to be reflected in the directory structure of the Plugin Jar file:

/edu/ucar/app/Test.class

For a single class file this is not necessarily required but if there are multiple class files that have interdependency among themselves then you will get into trouble if you don't follow this structure.

Now, what this code does can be anything and is best left up to the developer's guide.


Adding in New GRIB Tables

McIDAS-V can read Gridded Binary (GRIB) files in both GRIB-1 and GRIB-2 formats. Decoding GRIB files requires a set of lookup tables for parameters, issuing centers, etc. McIDAS-V comes pre-configured to support commonly used tables, but regional models and modeling centers may use tables that are not in the distribution.

You can add in specialized tables for both GRIB-1 and GRIB-2 using the steps below. Documentation on the format of the files can be found here.

GRIB-1 tables

To add in new GRIB 1 tables, you will need to create a file listing the special tables and the special table files themselves.

To add in a new parameter file, McIDAS-V would need to have access to a file called grib1lookuptable.lst which would list the parameter table (e.g.: gwctab_2.tab) and the parameter table itself.

The format of grib1lookuptable.lst is:


<center>:<subcenter>:<version>:  <table location>

so it would look like:


57:     1:      2:      gwctab_2.tab

gwctab_2.tab can be a relative or absolute path. The tables are in ncep format:


-1:57:-1:2

0:var0:undefined

1:PRES:Pressure [Pa]

2:PRMSL:Pressure reduced to MSL [Pa]

3:PTEND:Pressure tendency [Pa/s]

4:PVORT:Pot. vorticity [km^2/kg/s]

5:ICAHT:ICAO Standard Atmosphere Reference Height [m]

:GP:Geopotential [m^2/s^2]

...

(You can read more information about the format of this file and the parameter table here)

Once you've created this file, you would access it by putting the grib1lookuptable.lst in your <home>/McIDAS-V directory and put the corresponding table files where they are pointed to in the file. This can be a relative path or a web server. Alternatively, you could place the grib1lookuptable.lst and associated parameter tables on a local web server and use McIDAS-V's sitepath parameter (startup option or user preference) to point to the location where the files are.

GRIB-2 tables

To add in new GRIB 2 parameter, you would create a file named grib2lookuptable.lst which lists the parameters.

The format of grib2lookuptable.lst is:


<Discipline>  <Category>  <Parm #>  <Name>  <Units>  <Desc>

Parameters are listed by row, fields are separated by tabs, so it would look like:


#Dis    Cat     Parm #  Name            Units   Desc

0       0       0       Temperature     K       Temperature

(This is a sample table, the lines starting with # are not include in table.) (You can read more information about the format of this file and the parameter table here)

Once you've created this file, you would access it by putting the grib2lookuptable.lst in your <home>/McIDAS-V directory. Alternatively, you could place the grib2lookuptable.lst on a local web server and use McIDAS-V's sitepath parameter (startup option or user preference) to point to the location of the file.


McIDAS-V Special Data Formats

Text (ASCII) Point Data Format
If your point (in situ) data is not available in one of the file formats that McIDAS-V can handle, but it can output into a column-oriented ASCII text file, it may still be able to read into McIDAS-V. McIDAS-V supports reading in point observation data in a text comma separated value (CSV) file format.

The metadata of this point data must be specified. This can be done in two ways. First, the file can have two extra header lines that defines for McIDAS-V the fields that are within the file and the types of the fields. The only other requirement is that there must be a latitude, longitude and time field in the data. See below.

Secondly, if there are no metadata header lines defined, the Text Point Data Source will show the Metadata GUI described below.

More information about the format of Time and Lat/Lon symbols can be found in the User Preferences' Formats and Data Preferences page.

Examples:

Comma separated numeric values

In the simplest form, each line line is an observation at one time and one location:

(index) -> (Time,Latitude,Longitude,Altitude,PSL,GUS,SPD,DIR,TD,T)

Time[fmt="yyyy-MM-dd HH:mm:ss"],Latitude[unit="deg"],Longitude[unit="degrees west"],Altitude[unit="m"],PSL[unit="hPa"],GUS[unit="m.s-1"],SPD[unit="m/s"],DIR[unit="deg"],

TD[unit="celsius"],T[unit="celsius"]

2007-01-07 16:00:00Z,32.9,117.1,145.0,1026.1,NaN,0.0,0.0,-2.8,12.8

2007-01-07 16:00:00Z,48.3,92.5,341.0,1003.7,NaN,1.5,170.0,-2.0,-0.99

2007-01-07 16:00:00Z,36.8,98.7,449.0,1024.0,12.4,9.8,330.0,-3.0,3.0

2007-01-07 16:00:00Z,44.3,121.2,938.0,1030.1,NaN,2.1,110.0,-3.3,-1.7

Note also that the first line's structure is quite rigid -- there must be a variable (e.g., index, recNum) that is the domain parameter; this should map to the range values. The second line defines the formatting and units of the parameters. Unit names should be standard international unit specifications (udunits compatible). A list of valid names can be found here. (A complete description of this format is contained in the VisAD README.text file.)

Also note that "Time", as well as the locations as "Latitude", "Longitude" and "Altitude" must be specified (if needed).

Text fields

If there are text fields (i.e., non-numeric data) in the observation, just do this:

(index) -> (Time,Latitude,Longitude,Altitude,ST(Text),T)

Time[fmt="yyyy-MM-dd HH:mm:ss z"],Latitude[unit="deg"],Longitude[unit="degrees west"],Altitude[unit="m"],ST(Text),T[unit="celsius"]

2007-02-16 11:00:00 MST,32.9,117.1,145.0,CA  ,20.6

Here we have a ST field (State from metars). Its field name is defined as "ST(Text)" and its entry in the second line is the same.

Time in multiple columns

If there are time fields that span multiple columns, the colspan keyword should be used:

(index) -> (IDN, Latitude, Longitude, Time, WDIR, WSPD, GST)

IDN, Latitude[unit="deg"], Longitude[unit="deg"], Time[fmt="yyyy MM dd HH mm" colspan="5"], WDIR[unit="deg" miss="MM"], WSPD[unit="m/s" miss="MM"], GST[unit="m/s" miss="MM"]

41001 34.68 -72.66 2007 07 17 20 50 210 4.0 6.0

41004 32.5 -79.09 2007 07 17 20 50 210 6.0 MM

41008 31.4 -80.87 2007 07 17 21 50 170 7.0 8.0

If using the Point Data window to define a colspan value, the numerical value must be in quotes. For example: colspan="2". This colspan value goes into the Extra field in the Point Data window.

Skipping columns

The "skip" parameter should be used to ignore (not read) values in the text file that shouldn't be used:

(recNum)->(Latitude, Longitude, Altitude, type(Text), time, turb_intensity)

time[fmt=yyyyMMddHH], obtime, skip, type(Text), skip, skip, Latitude, Longitude[scale=-1], Altitude[unit=ft], Altitude2[unit=ft], turb_intensity, skip

2004050100 0005    34     C210 1 T  38.82   92.22   7000   7000  0 -9

2004050100 0004    35     PA32 0 T  35.40   98.62   4000   4000  0 -9

2004050100 0008    58      A36 0 T  29.18   81.05   5000   5000  2 -9

Fixed values for several observations

If there are values (like time or location) that are fixed for several observations then this construct may be used:

(index) -> (Longitude,Latitude,Time,ST(Text),SPD,DIR,TD,T)

Longitude[unit="degrees west"],Latitude[unit="deg"],Time[fmt="yyyy-MM-dd HH:mm:ss z"],ST(Text),SPD[unit="m/s"],DIR[unit="deg"],TD[unit="celsius"],T[unit="celsius"]



Longitude=-117.1

Latitude=32.9

ST=MSN

2007-02-20 11:00:00 ST  ,0.0,0.0,8.9,13.3

2007-02-20 12:00:00 ST  ,0.0,0.0,11.9,15.0



Longitude=-89.4

Latitude=43.1

ST=DEN

2007-02-20 11:00:00 ST  ,1.5,160.0,-7.0,-2.0

2007-02-20 12:00:00 ST  ,1.5,160.0,-7.0,-2.0



Longitude=-121.2

Latitude=44.3

ST=ORD

2007-02-20 11:00:00 ST  ,10.8,230.0,-1.1,6.7

Loading into McIDAS-V

Finally, after the file has been created, McIDAS-V displays can be tailored in two ways:
  1. Create a layout model for those variables using the McIDAS-V's "Tools->Layout Model Editor" menu item.
Then, here is the process to read in and display the data:
  1. Use Data Source Type as "Text Point Data files"
  2. Use the "Point Data Plot" for the Display
  3. Select the newly created layout model

Using the Text Point Metadata Gui

If the text data does not have the metadata header lines the Text Point Data Source will show the following dialog which allows for specifying the metadata.
Image 1: Point Data Dialog Window
Image 1: Point Data Dialog Window

Delimiter

This field specifies how the different data values are separated within the text file. The options are Comma, Semicolon, Tab, and Space. Selecting this option allows McIDAS-V to separate out different text fields to allow for defining them at the bottom of this Point Data window.

Skipping lines

At the top, a number of the initial lines from the text data are shown. The arrow keys allow for specifying the start line. For example, if there were header lines in the file, these lines can be skipped over.

Specifying metadata
For each column of text data there is a row shown in the bottom of the dialog. This shows the sampled value and allows for entering a name, unit, date format, missing value and extra information. There are some names that McIDAS-V treats special: "Latitude", "Longitude", "Altitude", and "Time". At least Latitude, Longitude and Time must be specified in the file.

The Unit/Date Format field allows for specifying the Unit for data fields and the date format. For text fields choose Misc->Text as the unit.

The Extra fields must be of the form:


name="value"

Don't forget the quotes!

Skipping columns
Certain columns can be skipped by entering the Name: "skip"

Saving this as a preference
To keep from having to enter in this data again the next time a new text point data of the same form is loaded, simply press the "Preferences" button and select Save Current. This allows for saving these metadata settings and reapply them later using the "Preferences" button.

Saving this as a data type through a plugin
To save the values in this Point Data window to a new data source so the Point Data window will no longer be needed, press the "Preferences" button and select Write Data Source Plugin . This brings up a Data Source Type Plugin window where the user defines "Type" (not seen by the user) as well as "Label", which is how the data type will appear in the Data Type dropdown in the General->Files/Directories chooser. Clicking OK in this window brings up the Plugin Manager where a plugin can be written and installed using the new data type. The next time McIDAS-V is started, through the General>Files/Directories choose the new data type named in the Data Source Type Plugin, select the data file, and click Add Source. At this point, the data source will be added to the Field Selector without needing to define the columns in the Point Data window.


Location XML Files

McIDAS-V supports a variety of location text file formats. All of these formats can be loaded through the File Chooser. Select the "Location" data type.

Locations XML

The main format McIDAS-V uses is a custom locations XML format. This format still has some nomenclature from when it was atmospheric science related (e.g. "stations"). A simple example:


<?xml version="1.0" encoding="ISO-8859-1"?>

<stationtable name="TARGET_LocationXml__Example">
<station name="TARGET_LocationXml__station 1"  lat="65:02:06" lon="-147:30:06" elev="790"/>
<station name="TARGET_LocationXml__station 2"  lat="40.3" lon="-107.5" elev="10"/>
    ...

</stationtable>

The lat and lon attributes can be of the form:


    +/-  ddd:mm, ddd:mm:, ddd:mm:ss, ddd::ss, ddd.fffff ===>   [+/-] ddd.fffff

    +/-  ddd, ddd:, ddd::                               ===>   [+/-] ddd

    +/-  :mm, :mm:, :mm:ss, ::ss, .fffff                ===>   [+/-] .fffff

    +/-  :, ::                                          ===>       0.0

    Any of the above with N,S,E,W appended

The elev attribute is optional. By default it is in meters. The default can be overridden with an elevunit in the stationtable tag. e.g.:


<?xml version="1.0" encoding="ISO-8859-1"?>

<stationtable name="TARGET_LocationXml__Example" elevunit="feet">
<station name="TARGET_LocationXml__station 1"  lat="65:02:06" lon="-147:30:06" elev="5340"/>
...

The station tags can have an id attribute as well:


<station  id="APD" name="TARGET_LocationXml__Fairbanks/Pedro Dome"
          lat="65:02:06" lon="-147:30:06" elev="790"/>

The station tags can also have any other attributes:


<station  id="APD" name="TARGET_LocationXml__Fairbanks/Pedro Dome"
          st="AK" co="US" 

          lat="65:02:06" lon="-147:30:06" elev="790"/>

<station id="FTG" name="TARGET_LocationXml__Denver/Boulder"
         st="CO" co="US" 

         lat="39:47:12" lon="-104:32:45" elev="1675"/>

These can be displayed by the layout model used in the Location Display Control.

To create a permanent list of stations that show up in the Display->Locations menu in the Main Display window, create a file called userstations.xml in the McIDAS-V directory under your user's home directory. The format would look like:


<?xml version="1.0" encoding="ISO-8859-1"?>

<stationtables>



<stationtable name="SubsetA" category="My Custom Stations">

(list of stations for SubsetA)

</stationtable>



<stationtable name="SubsetB" category="My Custom Stations">

(list of stations for SubsetB)

</stationtable>

</stationtables>

This will show up in the Display->Locations menu as a top menu called My Custom Stations and sub menus SubsetA and SubsetB. After adding this XML file in through the Files/Directories chooser, McIDAS-V must be restarted before the stations will be listed.

CSV Format

Location data can be defined in a CSV (Comma Separated Value) format. The first line is a comma separated list of column names. There must be columns that are latitude and longitude. These are denoted with (case insensitive):


latitude

lat

longitude

lon

long

Altitude is given by the column names:


alt 

altitude

The altitude value, if defined, is by default in meters. Optionally, specify a unit with the suffix: "[unit name]" (see example).

The first column that is found that is not one of the location columns is taken to be the name of the location.

Example:


Name,Latitude,Longitude,Altitude,State

Boulder,40,-107,5430[feet],CO

Miami,30,-95,0[feet],FL

...

GeoRSS Format

McIDAS-V can also read GeoRSS formats. This is a geocoded RSS feed.

KML/KMZ Format

McIDAS-V can also read KML/KMZ formats. This type of file can be read in through the General>Files/Directories Chooser of the Data Sources tab of the Data Explorer with the Google Earth Files KML/KMZ Data Type. An example file from the USGS can be found here:

https://waterwatch.usgs.gov/index.php?m=real&w=kml&r=us&regions=all


Image XML Files

The Image Xml file format (.ximg) allows one to define collections of geolocated images (and also shapefiles). The simplest file can define one geolocated image:


  <image url="sboulder.jpeg"

name="South Boulder-aerial photo"
       ullat="39.98890" ullon="-105.22782"

       lrlat="39.98755" lrlon="-105.22548"/>

The url attribute can be an absolute or relative url or file path. The ullat, ullon, lrlat and lrlon attributes are the upper left and lower right lat/lon of the image. It is assumed that the image is in a geographic (i.e., rectilinear, lat/lon) projection.

Collections

You can also define a collection of images:


<collection name="TARGET_ImageXml__Boulder Images">
  <image url="sboulder.jpeg"

name="South Boulder-aerial photo"
       ullat="39.98890" ullon="-105.22782"

       lrlat="39.98755" lrlon="-105.22548"/>



  <image url="bouldertopo.jpeg"

       ullat="40.06654" ullon="-105.34710"

       lrlat="39.98040" lrlon="-105.19676"

name="Boulder topo"/>


  <image url="bigtopo.jpeg"

       ullat="40.22807" ullon="-106.66437"

       lrlat="39.54718" lrlon="-105.45623"

name="Mountains topo"/>
</collection>

Collections can contain other collections:


<collection name="TARGET_ImageXml__My Images">
<collection name="TARGET_ImageXml__Madison Images">
        <image url="madison_aerial.jpeg"

              ullat="43.09444" ullon="-89.52626"

              lrlat="43.01143" lrlon="-89.36579"

name="Madison aerial"/>


        <image url="madison_topo.jpeg"

               ullat="43.09444" ullon="-89.52626"

               lrlat="43.01143" lrlon="-89.36579"

name="Madison topo"/>
    </collection>

<collection name="TARGET_ImageXml__Boulder Images">
       <image url="sboulder.jpeg"

name="South Boulder-aerial photo"
              ullat="39.98890" ullon="-105.22782"

              lrlat="39.98755" lrlon="-105.22548"/>

     </collection>

</collection>



There is also a shape tag for defining shape files:


<collection name="TARGET_ImageXml__Shapes">
<shape url="boulder_roads.zip" name="TARGET_ImageXml__Boulder roads"/>
<shape url="boulder_rivers.zip" name="TARGET_ImageXml__Boulder rivers"/>
</collection>

Grouping

The group tag allows you to group a set of images in time or space:


<group name="TARGET_ImageXml__group of images"
       format="yyyyMMddhhmm"

       ullat="39.991856"

       ullon="-105.226944"

       lrlat="39.989426"

       lrlon="-105.222656">

       <image

           date="200610011000"

           url="sketch.jpg"/>

       <image

           url="map.jpg"

           date="200610011100"/>

</group>

The format attribute defines the date/time format of the date attributes. The location attributes (ullat,ullon, etc.) can be defined both in the group tag as well as in each individual image tag.

If there are no date attributes then the group of images are aggregated together, each potentially covering a different area.

Images in 3D Space

One is not limited to just specifying the positions of the upper left and lower right corners of the image. There is support for defining the latitude and longitude for any of the four corners of the image:


  <image url="image.jpeg"

name="Image"
       ullat="40" ullon="-100"

       lllat="30" lllon="-100"

       urlat="50" urlon="-90"

       lrlat="30" lrlon="-90"

      />

One can also specify the altitude of any of the points. The unit specification is not required and will default to meters.


  <image url="image.jpeg"

name="Image"
       ullat="40" ullon="-100" ulalt="20000[feet]"

       lllat="30" lllon="-100" llalt="0[feet]"

       urlat="50" urlon="-90"  uralt="5000[feet]"

       lrlat="30" lrlon="-90"  lralt="0[feet]"

      />

McIDAS-V will try to fill in defaults. So, for example, if you wanted to have an image be a vertical cross section you could do:


  <image url="topo.jpg"

name="Image"
       ullat="40" ullon="-100" 

       urlat="50" urlon="-90"

       ulalt="20000[feet]"

       llalt="0[feet]"/>

Here, we define the lat/lon of the upper left and upper right of the image. We define the altitude of the upper left and lower left corners of the image. The altitude of the upper right corner defaults to that of the upper left and the altitude of the lower right defaults to the lower left altitude.


Image Movie Files

McIDAS-V can display a sequence of time-stamped images as an animation.

One can write their own xml file and display the images within McIDAS-V using this xml format.

There are really two xml formats used. The first defines a set of imagesets:


<imagesets base="http://www.unidata.ucar.edu/georesources/webcams/images" name="TARGET_ImageMovie__McIDAS-V Webcams">
<group name="TARGET_ImageMovie__Rockies">
<imageset name="TARGET_ImageMovie__Boulder, CO"
                  index="boulder_co/index.xml"

                  lat="40.0" lon="-105.27"/>

<imageset name="TARGET_ImageMovie__Denver, CO"
                  index="denver_co/index.xml"

                  lat="39.75" lon="-105"/>

    </group>

<group name="TARGET_ImageMovie__National Parks">
<imageset name="TARGET_ImageMovie__Theodore Roosevelt National Park, ND"
                  index="theodorerooseveltnationalpark_nd/index.xml"  

                  lat="46.94889" lon="-103.43306"/>

<imageset name="TARGET_ImageMovie__Big Bend National Park,TX"
                  index="bigbendnationalpark_tx/index.xml"

                  lat="29.25" lon="-103.25"/>

<imageset name="TARGET_ImageMovie__Olympic National Park"
                  index="olympicnationalpark/index.xml"

                  lat="48.26667" lon="-124.675"/>

    </group>

    ...

</imagesets>

This is a "table of contents". The base attribute, if defined, is used as a url base to prepend to the urls defined by the index attributes. The lat and lon attributes are optional and are used to locate the source of the movie on a map for the user to select.

Each of the index attributes refers to an images xml file of the form:


<images base="http://www.unidata.ucar.edu/georesources/webcams/images/boulder_co" 

name="Boulder, CO"
        group="Rockies" 

        format="yyyyMMddHHmmz" desc="From: http://9news.com">

    <image time="200607251446GMT" file="image_200607251446GMT.jpeg"/>

    <image time="200607251430GMT" file="image_200607251430GMT.jpeg"/>

    <image time="200607251414GMT" file="image_200607251414GMT.jpeg"/>

    <image time="200607251357GMT" file="image_200607251357GMT.jpeg"/>

    <image time="200607251344GMT" file="image_200607251344GMT.jpeg"/>

    ...

</images>

The images tag defines a base attribute (optional, used to prepend to any image urls), a name, a (optional) group and a date format and a description (desc). Each image tag has a time in the format specified in the images tag and a file attribute which refers to some image. This may be an absolute or relative url or file path.


XGRF Symbols
The drawing control can export and import its drawings in an xgrf format. In this format you can specify a symbol type. The symbol tag in the xgrf has a symbol attribute, the value of which can be any of the below symbols.

Actions
Below is a list of the actions that can be used in menubars, skins and in the html or qhtml pages.

To use these in an html or qhtml file simply specify a link with the href:


action:the_action_id

e.g.:

action:bundle.open


Command Line Arguments

There are a number of command line arguments for McIDAS-V. These command line arguments can be applied when starting McIDAS-V using a terminal or command prompt (e.g., from the McIDAS-V-System directory, type: runMcV -noplugins). To view them provide the argument: -help:

mcv -help

Specifying data source type

If you load in a data source from the command line using the -data argument, McIDAS-V tries to figure out what type of data it is by looking for patterns in the file or url you specify. If it cannot determine the type, McIDAS-V will prompt the user for the type.

You can add in a "type:" prefix to the argument that will specify the type with:


mcv -data type:somedatatype:the_file_or_url_to_the_data

For the different values for the "somedatatype", see Data Source Types.


Data Source Types
dods.gridGrids from an OPeNDAP server
opendap.gridGrids from an OPeNDAP server
dodsData from an OPeNDAP server
opendapData from an OPeNDAP server
adde.imageImages from an ADDE server
raob
adde.pointPoint data from an ADDE server
file.trackTrack files
opendap.trackTrack files
opendap.trajectoryTrack files
db.pointPoint data database
db.trajectoryTrajectory database
eol.trackdbEol Track Database
file.sondeUpsonde/Dropsonde files
file.bfr; file.bufr netCDF/GEMPAK Point Data files
netcdf.pointnetCDF Point Data files
netcdf.gridGrid files (netCDF/GRIB/OPeNDAP/GEMPAK)
httpserver.gridGrid files (netCDF/GRIB/OPeNDAP/GEMPAK)
file.gridGrid files (netCDF/GRIB/OPeNDAP/GEMPAK)
aggregated.netcdf.gridAggregate Grids by Time
file.netcdfnetCDF files
file.radarNEXRAD Radar files
opendap.radialOPeNDAP Radar files
file.doraderadarDORADE Radar files
wmsWMS image data
kmlGoogle Earth Files KML/KMZ
iserIDV Serialized Data
file.vis5dVis5D files
file.areafileMcIDAS AREA files
file.shapefileMap files
file.mapfileMap files
file.imageImage files (gif, jpg, png)
file.demDEM files
product.addeWeather Text Products (from server)
product.gempakWeather Text Products (from NWX files)
storm.atcfATCF Tropical Storm Data
file.textText or HTML files
file.pointtextText Point Data files
file.pointtracktextText Point and Trajectory Data files
file.locationLocations
file.imagemovieImage Movie Index
file.drawingDrawing files
file.imagexmlImage XML files
movieMovies
file.tiffTIFF files
cachedCached data source
file.audioAudio File
file.chatlogChat Log file
file.addetextAdde Text
text.frontFront Bulletins
netcdf.sweepnetCDF Radar Sweep files
netcdf.metarnetCDF METAR/Synoptic files
file.profilerEOL netCDF Profiler files
file.anyI'm Still Feeling Lucky

Performance Tuning

If you are running into issues with memory consumption or slow response of McIDAS-V, there are several things you can do.

The amount of memory used by McIDAS-V will depend on the size of the datasets you use and the types of displays. Datasets rendered as 2D depictions (plan views - contours or color shaded displays) use much less memory than 3D displays (isosurfaces, cross sections). Large datasets (images, dense grids) will use much more memory.

There are several features in McIDAS-V that allow you to more efficiently view large datasets:

Temporal/Spatial Subset of Data

Some data sources allow you to subset the data temporally and spatially. You can set these properties for all fields in a dataset through the Properties menu of the data source (double click on the Data Source in the Field Selector) or you can set these for individual field using the tabs in the lower right corner of the Field Selector. For more information, see Data Sources.

Memory Allocation
By default, McIDAS-V allocates 512 megabytes of maximum memory for Java. This is usually the optimum amount for a Windows system with 1 gigabyte of physical memory (RAM). Windows takes up half of that anyway and once Windows has to start swapping, performance severely degrades. On a Linux system, you can probably get away with 700m for 1 GB of memory as it does a much better job of swapping. All this also depends on what else you are running on the machine and how much memory those applications use.

If your system has more than 1 GB of memory, increasing the amount available to McIDAS-V can improve performance for displaying large datasets. You change the amount of memory used by McIDAS-V by editing the Maximum Heap Size in the Advanced tab of the User Preferences by selected Edit->Preferences from the Main Display window. The new amount of memory will be saved and used in subsequent sessions. Do not use the maximum amount of memory on your machine as some is needed for the operating system itself. If the system has to use swap memory, performance will degrade as well. For 32 bit operating systems, it is recommended to set this to no more than 1250 MB (i.e. -Xmx1250m). The maximum value for 32 bit operating systems is 1536 MB, while 64 bit operating systems can use all of the RAM available. For more information see Running McIDAS-V.

Data Caching

By default, McIDAS-V caches the data used for a display in memory. If a field is used more than once for several displays, caching the data prevents an additional reading from of the data from disk or a remote server. If you are only displaying/using a field (i.e. not using it for multiple displays or calculations), you can keep McIDAS-V from caching it in memory. You can turn off data caching by unchecking the Cache Data in Memory checkbox on the Formats & Data tab of the User Preferences window (accessible from the Edit->Preferences menu).

Maximum Grid/Image Size

You can also set the maximum size of a grid or image that will be displayed. This will allow you to download a large image or grid, but it will be re-sampled before displaying if it is larger than the maximum size you have asked for. You can set the maximum image/grid size under the Formats & Data tab of the User Preferences window (accessible from the Edit->Preferences menu).

Fast Rendering

By default, McIDAS-V will try to adjust the data layer (images, contours, etc.) renderings to account for projection seams. This is computationally intensive in some cases and slows down the display of data. If you change your User Preferences setting to Use fast rendering, McIDAS-V will not try to account for the projection seams. If you are displaying a layer of data in its native projection, this will result in faster rendering of the data depiction. However, if you have several layers of data, each from a different data source and on a different projection, you may see anomalies in one or more layers (spurious lines, portions of images). If that occurs, you can turn off fast rendering for the layer(s) by unchecking the Use Fast Rendering checkbox in its Properties dialog, or set your system preference back to not use fast rendering.

A separate fast rendering option for map layers is available in the Map Controls. Some maps display better when fast rendering is turned on, others display better when it's turned off. If a map displays poorly (e.g., has missing line segments), try switching its fast rendering settings to see if it fixes the problem.

Parallel Rendering and Data Reading
If you are running McIDAS-V on a multi-core machine you can configure it to render individual time steps in parallel. You can also do remote data reads in parallel. This typically results in a 50% reduction in overall data reading and rendering time.

The number of Rendering and Reading java threads can be set on the command line when starting McIDAS-V. To set these values, run the following when starting McIDAS-V (substitute in a numerical value in place of # in the commands to set the rendering and reading thread values):

For rendering McIDAS-V will render each time step in parallel. Note: Since the rendering processes can allocate temporary memory, it is possible to exhaust the available memory if too many threads are running concurrently. Linear speedup with the number of cores available for rendering (probably due to memory contention issues) is not seen, however a 40%-50% performance improvement is seen for complex rendering tasks (e.g., contouring).

The second preference is used when reading individual time steps of data from remote ADDE and OpenDAP servers. This parallelization takes advantage of the multiple cores available on the remote server and somewhat the available bandwidth on the network. A linear speed up in accessing remote data based on the number of cores on the remote server (ADDE or OpenDAP) has been seen. However, if you load the server too much your performance


Building McIDAS-V from Source
Developers can download the source files for McIDAS-V and build it from scratch.

Before building McIDAS-V you need to first install Java on your system. You need to use the Java SDK, because the Java RunTime Environment (JRE) does not contain the Java compiler (javac). You need to use a version of Java 1.6 or above. You can use either the Java 3D SDK or JRE, version 1.3.x.

You will also need to install the latest version of Ant http://ant.apache.org/) on your machine. Ant is similar to make - instead of a Makefile, Ant uses a build.xml file. Be sure to follow the instructions for installing Ant, especially those for setting up environment variables.

Build steps:

  1. Download the compressed source files from the McIDAS-V Download Page.
  2. Uncompress the .zip file. This will create a new directory containing the McIDAS-V source and Unidata IDV .jar files.

    The resulting directory structure will be:

    
    		mcidasv/
    
    		mcidasv/build.xml
    
    		mcidasv/...		<-- McIDAS-V source directories
    
    

    The Ant build script "mcidasv/build.xml" is be used to build and run McIDAS-V.

  3. Change to the mcidasv directory and run:


Message Console

Clicking on the main menu bar choice Help->Show Console in the Main Display window shows a Console window which has error messages and other text output from McIDAS-V. Error messages created before you open the console are shown, as well as later ones.

Image 1: Message Console Window
Image 1: Message Console Window

Properties

The console is useful if an error is encountered as the user can save the console message to a file and include it in email to McIDAS-V Support at SSEC or attach it in the Support Request Form.


Support Request Form

Clicking on the main menu bar choice Help->Show Support Request Form in the Main Display window opens a Request McIDAS-V Support window to post a support request to the McIDAS Help Desk. This form can also be brought up from the Support Form button of an Error dialog.

Image 1: Supported Request Form
Image 1: Support Request Form

Properties

Appendices

Examples of Display Types

Plan Views

A plan view is a flat, horizontal display of 2D data, or a horizontal cross section of 3D data. More simply, a plan view is a view from the top. These plan views are represented by contour lines used to display a parameter overlaying a base map. McIDAS-V offers the ability to shade or fill the spaces between the contour lines of the plan view display for further customization.

Contour Plan View
Image 1: Contour Plan View Display
Image 1: Contour Plan View Display
Color-Filled Contour Plan View
Image 3: Color-Filled Contour Plan View Display
Image 2: Color-Filled Contour Plan View Display
Color-Shaded Contour Plan View
Image 4: Color-Shaded Contour Plan View Display Overlaid with a Contour Plan View Display
Image 3: Color-Shaded Contour Plan View Display Overlaid with a Contour Plan View Display
Value Plots
Image 4: Value Plots Display
Image 4: Value Plots Display
Contour Plan View for Ensembles
Image 5: Contour Plan View Display for Ensembles
Image 5: Contour Plan View Display for Ensembles

Plan views can be displayed in several ways:

Colors help distinguish values and subtle features, and if used carefully can be an intuitive indication of value and trend, such as using "hot" colors for higher or important values.

All of these displays display in the Main Display window, with their controls in the Layer Controls tab of the Data Explorer. For more information about the controls for the Plan Views, see Plan View Controls. For more information about the Value Plot display, see Value Plot Controls. For more information about the Ensemble Contour Plan View display, see Ensemble Grid Controls.

A McIDAS-V 3D Plan View can be set to any of the data levels in the data source, or between data levels, in which case interpolation is used to estimate the data values in the plan view. A colored square selector point in the left corner of the 3D plan view can be moved up and down by dragging the mouse button to re-position the level. You can make several 3D plan views at the same time for one or more parameters in 3D data. To learn how to make a display, see Displaying Gridded Data.


3D Surface
Isosurface

An isosurface is a surface of a single value in a 3D parameter field. Isosurfaces are the 3D analog of a single-valued contour line in a 2D plot. The intersection of an isosurface and a plane is a contour line of the same value. Isosurfaces may form closed surfaces enclosing regions of higher or lower value, but not always.

Image 1: 3D Surface Isosurface Display
Image 1: 3D Surface Isosurface Display

McIDAS-V also supports isosurface displays that are colored from another parameter, not the parameter used to make the shape of the surface. The example here shows an isosurface of 89% relative humidity over North America colored by air temperature. A useful plot is to color isosurfaces by height (geopotential height) to show height of features by color.

Image 2: 3D Isosurface Display Colored by Another Parameter
Image 2: 3D Surface Isosurface Display Colored by Another Parameter.

All Isosurface displays display in the Main Display window, and their controls are in the Layer Controls tab of the Data Explorer. For more information about isosurface controls, see 3D Surface Controls.

Topography

For data sources that include topography or terrain data, such as the "terrain" parameter in NAM and RUC model output or DEM data, McIDAS-V can display a 3D relief map. Select "Topography" for the display type.

Image 3: 3D Topography Display of DEM Data
Image 3: 3D Topography Display of DEM Data
Image 4: 3D Topography Display of GFS Model Terrain Data
Image 4: 3D Topography Display of GFS Model Terrain Data
Image 5: 3D Surface Contours Over Topography Display
Image 5: 3D Surface Contours Over Topography Display
Image 6: 3D Surface Color-Filled Contours Over Topography Display
Image 6: 3D Surface Color-Filled Contours Over Topography Display
Image 7: 3D Surface Color-Shaded Contours Over Topography Display
Image 7: 3D Surface Color-Shaded Contours Over Topography Display
Image 8: 3D Surface Color-Shaded Parameter As Topography Display
Image 8: 3D Surface Color-Shaded Parameter As Topography Display
Image 9: 3D Surface Parameter as Topography Display
Image 9: 3D Surface Contoured Parameter as Topography Display
Image 10: 3D Surface Color-Filled Contoured Parameter as Topography Display
Image 10: 3D Surface Color-Filled Contoured Parameter as Topography Display

2D Data Draped Over Topography

Two dimensional grid data can be draped over a topography field to provide a terrain following representation of the data.

Image 11: Color-Filled Contours Over Topography Display Overlaid with the Contours Over Topography Display
Image 11: Color-Filled Contours Over Topography Display Overlaid with the Contours Over Topography Display

All topography displays display in the Main Display window, and their controls are in the Layer Controls tab of the Data Explorer. For more information about the the controls for these displays see 3D Surface Controls and Topography Controls.

For more information see Displaying Gridded Data.


Cross Sections

A cross section is a horizontal or vertical slice through a 3D space. This type of display can be useful to determine the vertical profile of a parameter over a specific region, or the profile of a parameter at a constant elevation level throughout the entire area. The Cross Sections display is available for 3D fields. The 3D derived parameter 'Relative Humidity (from Temperature & mixingratio)' was used to create the below examples.

Contour Cross Section
Image 1: Contour Cross Section Display
Image 1: Contour Cross Section Display
Color-Filled Contour Cross Section
Image 2: Color-Filled Contour Cross Section
Image 2: Color-Filled Contour Cross Section Display
Color-Shaded Contour Cross Section
Image 3: Color-Shaded Cross Section Display
Image 3: Color-Shaded Cross Section Display

You can adjust the end points of the cross section by left-clicking and dragging them in the Main Display window. A duplicate of the displays made in the Main Display window will be drawn in the Layer Controls tab of the Data Explorer, where you can also modify different characteristics of the display. For more information about cross section controls, see Vertical Cross Section Controls.


Probes
Vertical Profile Display

The Vertical Profile display is an available display type for 3D model data that plots the value of any number of fields versus altitude. For more information on this display type, see Vertical Profile Controls.

Image 1: Vertical Profile Display
Image 1: Vertical Profile Display
Data Probe/Time Series Display

The Data Probe/Time Series display plots in the Layer Controls tab of the Data Explorer, and plots a line that represents the numerical value of the parameter (Y-axis) at a given time (X-axis). You can change the location of the probe in the Main Display window by left-clicking and dragging it. See Data Probe/Time Series for more information on this display.

Image 2: Data Probe/Time Series Display
Image 2: Data Probe/Time Series Display
Time/Height Display

A Time/Height display plots a field's value in the vertical through the progression of time, with altitude on the Y-axis, and time along the X-axis. This can be a Contour or Color-Shaded display. For more information on this display type, see Time/Height Controls.

Image 3: Time/Height Display
Image 3: Time/Height Display

Hovmoller Display

The Hovmoller display plots grid, gridded point, and satellite imagery data in a diagram with the Latitude/Longitude component on the X-axis, and the time component on the Y-axis. You can display the data with respect to either Latitude or Longitude, and as a Color Shaded or Contour view.

Color Shaded Display
Image 1: Color Shaded display
Image 1: Color Shaded Display
Contour Display
Image 2: Contour Display
Image 2: Contour Display

For more information about the Hovmoller Display, see Hovmoller Controls.


Imagery
Satellite Imagery Display
Image 1: Image Display of a GOES Visible Satellite Image
Image 1: Image Display of a GOES Visible Satellite Image

Extensive satellite image data are available from both local files and remote ADDE servers. For more information see Displaying Satellite Imagery.

Level III Radar Display
Image 2: Image Display of a Level III Base Reflectivity Radar Image
Image 2: Image Display of a Level III Base Reflectivity Radar Image

For more information see Displaying Level III Radar Imagery.


Radar - Level II WSR-88D Data Displays

McIDAS-V can read and use WSR-88D Level II data, including reflectivity, radial velocity, and spectrum width, and display it in several ways.

Radar Sweep View

Image 1: Radar Sweep View in 2D Display

The Radar Sweep View in 2D display appears in the Main Display window. The display depicts radar data at a variety of different elevation angles. For more information, see Radar Sweep View Controls.

Image 2: Radar Sweep View in 3D Display
Image 2: Radar Sweep View in 3D Display

The Radar Sweep View in 3D display appears in the Main Display window. The display depicts 3D radar data at a variety of different elevation angles. For more information, see Radar Sweep View Controls.

RHI
Image 3: RHI Display in the Main Display Window
Image 3: RHI Display in the Main Display window

Image 4: RHI Display in the Layer Controls Tab

The RHI (Range-Height Indicator) display appears in the Main Display window and as a 2D plot in the Layer Controls tab. The display is a cross section of radar data, with one end point at the location of the radar and the other set by the user. In the chart, distance along transect is on the X-axis, and altitude is on the Y-axis. For more information, see Radar RHI Display Controls.

Radar Cross Section
Image 5: Radar Cross Section Display in the Main Display Window
Image 5: Radar Cross Section Display in the Main Display Window
Image 6: Radar Cross Section Display in the Layer Controls Tab
Image 6: Radar Cross Section Display in the Layer Controls Tab

The Radar Cross Section display appears in the Main Display window and as a 2D plot in the Layer Controls tab. The display is a cross section of radar data, with distance along transect on the X-axis, and altitude in the Y-axis. For this display, you have the ability to change the position both end points of the transect line. For more information, see Radar Cross Section Controls.

CAPPI
Image 7: CAPPI Display
Image 7: CAPPI Display

The CAPPI (Constant Altitude Plan Position Indicator) display appears in the Main Display window. The display depicts radar data at a constant altitude around the Radar site. For more information, see Radar CAPPI Display Controls.

Volume Scan
Image 8: Volume Scan Display
Image 8: Volume Scan Display

The Volume Scan Display appears in the Main Display window. This display depicts various elevation angles at once. For more information, see Radar Volume Scan Controls.

Radar Isosurface
Image 9: Radar Isosurface Display
Image 9: Radar Isosurface Display

The Radar Isosurface display displays radar data at the user-specified reflectivity value. For more information, please see Radar Isosurface Controls.

For more information see Displaying Level II Radar Imagery.


Soundings

The meteorological sounding display is available with a choice of thermodynamic diagrams (Skew-T, Stuve and Emagram), with a table of related aerological parameters.

Skew-T
Image 1: Skew-T Display
Image 1: Skew-T Display
Stuve
Image 2: Stuve Display
Image 2: Stuve Display
Emagram
Image 3: Emagram Display
Image 3: Emagram Display

A sounding diagram can be made for any point inside a data grid of numerical weather prediction model output with temperature and humidity (the dew-point temperature is computed by Unidata code from temperature and relative humidity grids), or from balloon soundings (RAOBs). The sounding display and its table and controls appear in a separate window. To learn more about the aerological displays see Sounding Display Controls.


Flow Displays

For parameters with a vector nature such as wind, vector and streamline displays of flow are available.

Vector Plan View
Image 1: Vector Plan View Display
Image 1: Vector Plan View Display
Streamline Plan View
Image 2: Streamline Plan View Display
Image 2: Streamline Plan View Display
Wind Barb Plan View
Image 3: Wind Barb Plan View Display
Image 3: Wind Barb Plan View Display
Vector Cross Section
Image 4: Vector Cross Section Display in the Main Display Window
Image 4: Vector Cross Section Display in the Main Display Window
Image 5: Vector Cross Section Display in the Layer Controls Tab
Image 5: Vector Cross Section Display in the Layer Controls Tab
Wind Barb Cross Section
Image 6: Wind Barb Cross Section Display in the Main Display Window
Image 6: Wind Barb Cross Section Display in the Main Display Window
Image 7: Wind Barb Cross Section Display in the Layer Controls Tab
Image 7: Wind Barb Cross Section Display in the Layer Controls Tab
3D Volume Vector
Image 8: 3D Volume Vector Display
Image 8: 3D Volume Vector Display
3D Volume Trajectory
Image 9: 3D Volume Trajectory Display
Image 9: 3D Volume Trajectory Display

For more information see Flow Display Controls and 3D Flow Display Controls.


Observations
Point Data Displays

You can make plots of point data such as meteorological surface (METAR) and synoptic surface weather station observations.

Image 1: Point Data Plot
Image 1: Point Data Plot

For more information see Displaying Surface and Upper Air Point Data . You can change the plot layout with the Layout Model Editor.

You can plot non-meteorological point data as well. The image below depicts the locations of earthquakes, sized by magnitude and colored by depth. Earthquake data can be obtained from the U.S. Geological Survey (USGS) in Google Earth (KMZ) format and can be loaded into McIDAS-V in the General->Files/Directories Chooser with the Data Type of "Google Earth Files KML/KMZ". Using the Layout Model Editor, you can specify how your data will be displayed in the Main Display window.

Image 2: Locations Display
Image 2: Locations Display
Track Displays

Aircraft and drifting buoy tracks can be plotted to show the path of the sensor. You can also plot the track data as observations along the track. The track path is brought into McIDAS-V through the General->Files/Directories Chooser with the Data Type of "Text Point and Trajectory Data files". The Flythrough feature is invoked in the Main Display Window through the View->Flythrough menu item. You can set the Flythrough to follow the track path by creating and importing an XML file with location (latitude, longitude, and altitude) data via File->Import in the Flythrough window.

Image 3: TTrack Colored by Parameter Display with a Flythrough
Image 3: Track Colored by Parameter Display with a Flythrough
Front Positions

Via ADDE, McIDAS-V has the ability to plot a frontal analysis or a forecast of frontal positions. You can create these displays by selecting Front Positions in the Data Sources tab of the Data Explorer. For more information about this feature, see Displaying Fronts and Front Controls.

Image 4: Front Positions
Image 4: Front Positions

Miscellaneous Display Types
Globe Display
Image 1: The Globe Display
Image 1: The Globe Display

The illustration shows a McIDAS-V globe display of the earth, with AVN numerical weather prediction model output of mean sea level pressure (as color-shaded image and contour lines) and 50 m/s wind speed isosurfaces showing the jet streams. The upper vertical scale is set to 32,000.

For more about this display and how to make it, see Using the Globe Display.

Multi-Panel Display

You can create multi-panel map and globe displays through the File->New Display Tab (Window)->Map (Globe) Display-># panel(s) menu. Below is an example of a four panel display of storms over Mississippi and the Gulf of Mexico. The first panel is radar reflectivity from central and southern Mississippi. Panel two is a Goes East visible satellite image. Panel three contains point data metars over the Gulf coast region. Panel four is a Goes East IR satellite image, with an enhancement for temperature.

Image 2: Four Panel Map Display
Image 2: Four Panel Map Display
ProfileAlongTrack Display

The ProfileAlongTrack display plots CALIPSO, CloudSat, and HSRL2 lidar data. See ProfileAlongTrack Controls for more information on this display. The image below shows CloudSat radar reflectivity (vertical curtain) displayed using the ProfileAlongTrack display type overlaid on a GOES-16 ABI image.

Image 3: ProfileAlongTrack Display
Image 3: ProfileAlongTrack Display
Data Transect Display

The Data Transect display plots in the Layer Controls tab of the Data Explorer, and plots a line of data at a constant height. The X-axis of the plot represents distance, and the Y-axis represents the numerical value of the parameter you are plotting. In the Main Display window, you can drag the end points of the transect line, to move the transect to your desired location. See Data Transect Controls for more information on this display.

Image 4: Data Transect Display
Image 4: Data Transect Display
Grid Table Display

The Grid Table display plots in the Layer Controls tab of the Data Explorer, and plots a chart of the numerical value of the field you are displaying at individual latitudes, longitudes, and altitudes (if available). See Grid Table Controls for more information on this display.

Image 5: Grid Table Display
Image 5: Grid Table Display
Omni Display

The Omni display is a VisAD Spread Sheet, loaded with the parameter selected and its coordinates and units. The Spread Sheet is used to create a display where you have complete control over which coordinates are the axes, how it is colored, and so on. See more in the Omni Control.

For use of the Spread Sheet, see the VisAD Spread Sheet document at https://www.ssec.wisc.edu/~curtis/ss.html.

Image 6: Omni Control Display
Image 6: Omni Control Display
Map and Transect Display

The Main Display window allows for various configurations of maps and transects. Through the Main Display window, use the File->New Display Tab (Window)->Transect Display-># panel(s) to create a tab that contains anywhere from one to four transects. Additionally, as shown below, there are a few panel configurations that allow for having maps and transects in the same display. These configurations can be found under File->New Display Tab (Window)->Misc, where there are options for one map and one transect, one map and two transects, as well as two maps and one transect.

For more on using the transect panel type, see Transect Views.

Image 7 - Map and Transect Display
Image 7: Map and Transect Display
Satellite Orbit Track Display

TLE data sources loaded through the Satellite->Orbit Tracks chooser are displayed with the Satellite Orbit Track display type. Customizable aspects of the display include setting the track/swath line width, color, and style. The user can also add ground stations to the display which are customizable as well. In the image below, Suomi NPP tracks are plotted and a ground station for SSEC (Space Science and Engineering Center, Madison, WI) is drawn.

For more on using the Satellite Orbit Track display, see Satellite Orbit Track Controls.

Image 8: Satellite Orbit Track Display
Image 8: Satellite Orbit Track Display

FAQ - Frequently Asked Questions

This section contains a list of questions commonly asked by users. The questions are organized by categories. You can find the answer to each question by clicking on the question, or the category that the question is in.

Reporting Problems

General FAQ

Q. What is McIDAS-V?

A. McIDAS-V is a free, open source, visualization and data analysis software package that is the next generation in the Space Science and Engineering Center's (SSEC) 50 year history of sophisticated McIDAS software packages. McIDAS-V displays weather satellite (including hyperspectral) and other geophysical data in 2- and 3-dimensions. McIDAS-V can also analyze and manipulate the data with its powerful mathematical functions. McIDAS-V is built on SSEC's VisAD and Unidata's IDV libraries, and an integrated version of SSEC's HYDRA software package.

Q. Is McIDAS-V still under development?

A. Development of McIDAS-V is ongoing at SSEC and as it progresses new features will be added and any problems/bugs will be fixed. The development will be driven by the needs of the community of users. Suggestions, comments and collaboration are welcomed and encouraged. The goal is to provide new and innovative ways of displaying and analyzing data, as well as provide the common displays that many users have come to expect.

Using McIDAS-V FAQ

Q. What do I do if McIDAS-V will not work on my computer?

A. Listed below is a basic checklist of steps to follow if your McIDAS-V is not working properly. Once you successfully complete each step in the process, restart McIDAS-V and try again. If the problem still exists, proceed to the next step, and so on.
  1. Make sure that your drivers are up to date. Please see the Graphics Cards and Drivers section of the System Requirements page for more information.
  2. Try the j3dtest script to verify that you can view the spinning cube. Please see the Java Versions section of the System Requirements page for more information. If this example does not work, then your system does not support Java3D. Instructions for running this test differ between operating systems:
    • Linux and macOS - cd to the directory where McIDAS-V was installed (likely the McIDAS-V-System directory) and run: ./j3dtest
    • Windows - From the Start menu, navigate through Programs to find the directory containing the McIDAS-V scripts. This directory is defined during the installation of McIDAS-V. Select the Java3D Test script. Alternatively, through a Command Prompt window, cd to the directory where McIDAS-V was installed (likely the McIDAS-V-System directory) and run: j3dtest.bat.
    Note: If your system does not support Java3D version 1.3.1+ McIDAS-V will not work for you.
  3. Set a small heap size by setting the Memory option to 512 megabytes in the User Preferences window's Advanced tab. If this resolves the issue, you can start increasing the memory until the problem appears again. Stay below the memory value that produces the problem.
  4. Disable Java Access to Image Data by Reference by unchecking Enable access to image data by reference option in the User Preferences window's Advanced tab.
  5. Rename your McIDAS-V document directory to start with a clean set of options. This will undo the changes made in steps 3-4 listed above, but it will eliminate any corrupt startup bundles or settings.
  6. Repeat steps 3-4 with a clean slate.

Q. Where are the McIDAS-V files stored on my computer?

A. McIDAS-V files are divided into two categories: "system files" (supplied files that should not be edited) in the McIDAS-V-System directory and "user files" (new user-created files and supplied ones that contain user settings and preferences) that are in the McIDAS-V directory. The files in McIDAS-V-System are specific to the version of McIDAS-V. The files in McIDAS-V are not dependent on McIDAS-V version (such as XML files containing color enhancements, formulas, projections, etc.), so these settings will be carried from version to version. The system file directory can be changed during installation and its location defaults to the OS application directory (e.g., C:\Program Files on Windows, /Applications on OS X/macOS). The user file directory is created in the user's document directory (e.g., C:\Documents and Settings\user\ or C:\Users\user\ on Windows, /Users/user/Documents on OS X/macOS, /home/user on Linux). Files in these directories should not be edited by the user, but rather contact the McIDAS Help Desk or post to the McIDAS-V Support Forums for assistance if it is necessary to edit them.

Q. How can I tell if McIDAS-V is busy doing something?

A. The lower right corner of the Main Display window shows a box with progress bars if McIDAS-V is busy making a display or doing anything. In the status bar at the bottom, messages will appear when McIDAS-V is reading data from a server or disk. Also, while the displays are being created, there is usually a "please wait" notice in the lower left corner of the main display. When McIDAS-V is in the middle of a process in the Data Explorer window, the cursor will change to a spinning, blue ring.

Q. How can I save a display?

A. McIDAS-V supports JPEG, PNG, and GIF image formats. McIDAS-V can also write out an image and the corresponding Google Earth KML or KMZ files. Animations can be captured as QuickTime movies or animated GIFs. See Image Captures for more information. You can save a particular McIDAS-V state with all displays, data sources, maps, etc. by saving the data as a bundle. You can also save a bundle as a favorite.

Q. How can I change the start-up settings?

A. You can customize many of the McIDAS-V properties through the User Preferences window, accessed through the Edit->Preferences menu item in the Main Display window. This allows you to configure the many features of McIDAS-V.

You can set a bundle to open by default when you start McIDAS-V. To do this, save a bundle as a favorite and set it as your default bundle in the Defaults panel of the Advanced tab of the User Preferences window.

You can also set the locations of the Main Display window and the Data Explorer window, as well as the number of tabs and panels. To do this, save a default layout via the File->Default Layout menu item in the Main Display window.

Q. How can I change the amount of memory available to McIDAS-V?

A. You can change the amount of memory used by McIDAS-V by editing the Memory in the Advanced tab of the User Preferences window by selecting Edit->Preferences... from the Main Display window. See Running McIDAS-V for more information.

Q. How can I reset the map projections?

A. This can be controlled with the Projections->Auto-set Projection menu check-box. You can switch an existing display to its native data set projection using the display control's View->Use Data Projection menu.

Q. How can I set the default projection?

A. The default projection is set with the Default Projection field in the Display Window tab of the User Preferences window. This window is accessed via the Edit->Preferences menu item in the Main Display. If you do not want to use any of the native projections of McIDAS-V, you can create your own projections with the Projection Manager which is accessed from the Projections->New/Edit menu item in the Main Display window. The default projection is overridden by the projection saved in the default bundle, or by displaying new data, if the Projections->Auto-Set Projection menu checkbox is checked on. As a result, you may never see the default map projection unless your default bundle has the default projection, and you have the checkbox checked off. Choosing a default map projection is not necessary to use of McIDAS-V, it is just a feature to allow for further user-customization of their sessions.

Q. How can I change the color table range of a displayed parameter?

A. You can change the range for a display parameter in the Color Table Editor. This can be accessed in the Layer Controls tab of the Data Explorer by clicking the button next to Color Table, or by right-clicking on the color bar in the Legend of the Main Display window and selecting Edit Color Table. The range of the color table can be changed next to the Range button in the Color Table Editor. Alternatively, you can change the range outside of the Color Table Editor by right clicking on the color bar in the Legend of the Main Display window and selecting Change Range..., which opens a Change Range window where you can enter new values. If you always want to use a specific data range for a parameter, you can create a user parameter default so the range you desire will always be used when displaying the parameter. This can be done through the Tools->Parameters->Defaults menu item in the Main Display window to get to the Parameter Defaults Editor.

Q. When I set a color table transparent, why doesn't it show up that way?

A. Using transparency in a color display may give unexpected results. In general, only the last thing added can be fully transparent. If you have a display that is transparent, then add in a new display, you may not see it. You can use the display control's View->Bring to Front menu to remove and re-add the display that you want to be transparent so it is last.

Q. When I load an image, why is it displayed with fewer colors than I expect?

A. First, check that your display configuration is set to the maximum number of colors (e.g., 32 bit) so that McIDAS-V is able to display imagery and color tables using a full range of colors. If that is set correctly, it's possible that the range of values defined for the color table is less than the range of values in the displayed image. You can view or modify the range of values defined for the color table by right-clicking on the color bar in the Legend of the Main Display window and selecting either Change Range... or Edit Color Table. Right-clicking also displays other options that let you apply a different color table or edit the current one. If you created a contour display, you may also need to lower the Contour Interval in the Contour Properties Editor.

Q. When I load an image, why does it appear pixelated (blocky)?

A. A displayed image can appear pixelated (blocky) due to one or more factors, including the resolution of the displayed image, the magnification and pixel sampling factors at which it was displayed, and the zoom factor.

For example, if you display an 8 km resolution image while zoomed in to a small geographic region such that each display pixel represents a higher resolution value (e.g., 1 km2 of the earth surface) the image pixels need to be duplicated to fill the display and thus the image will appear pixelated. The same effect will occur with any image if you zoom in (using the Zoom/Pan Toolbar buttons or other zooming actions) to where the display resolution is higher than the image resolution.

If you believe that the displayed image is more pixelated than it should be for its given resolution, check the settings of the Magnification sliders in the Field Selector's Advanced tab and the Pixel Sampling slider in the Layer Controls tab. In order to display the image at the highest possible resolution (its native resolution), the line and element magnifications must be set to 1 (sliders all the way to the right) and the pixel sampling set to 0 (slider all the way to the left).

Q. How do I change which maps are displayed by default?

A. By default, there are three maps that are displayed: 'North & Central America', 'World Political Boundaries', and 'World Coastlines'. Other system maps are included with the Map Controls, and their visibilities can be toggled on and off. Additional maps are contained in plugins that can be found under the Maps category in the Plugin Manager. Users can add their own shapefile maps through the Edit -> Add Your Own Map menu item in the Layer Controls of the Default Background Maps. To set a new group of maps as the default, use the File -> Default Maps -> Save as the Default Map Set menu item. This creates a maps.xml file in the McIDAS-V directory that includes which map layers are displayed, as well as different display settings including the line thickness, style, and color. Once the default map is saved, this will be used any time a new tab or window is created, and it will be persisted between sessions. To remove a default map setting that has been saved, use the File -> Default Maps -> Remove Local Map Defaults menu item. Removing the default map set requires a restart of McIDAS-V to take effect.

Q. What do I do if McIDAS-V will not start from an icon on macOS?

A. The likely cause of this problem is that /bin/sh has been disallowed to control Terminal.app. This is an issue because the McIDAS-V launcher relies on using the Terminal to launch runMcV. Here are steps that can be followed to resolve this issue:
  1. Open the macOS System Preferences.
  2. Click on Privacy & Security.
  3. In the Privacy section, select the Automation entry.
  4. Enable the Terminal sub-entry. There may be a prompt for an administrator password.
  5. Try the icon again to run McIDAS-V.

Data FAQ

Q. What is Fast Rendering and when should I use it?

A. By default, McIDAS-V will try to adjust the data layer (images, contours, etc.) renderings to account for projection seams. This is computationally intensive in some cases and slows down the display of data. If you change your User Preferences setting to Use fast rendering, McIDAS-V will not try to account for the projection seams. You can turn on/off Fast Rendering for individual displays in their Properties dialogs.

Q. What is the difference between the Standard Atmosphere and Vis5D pressure to height conversion?

A. McIDAS-V displays pressure surfaces by converting the pressure to a height in some reference system. There are two reference systems that come standard with McIDAS-V - the U.S. Standard Atmosphere and Vis5D. The U.S. Standard Atmosphere only computes has conversions for pressures up to about 80 km. The Vis5D coordinate system uses a logarithmic conversion:

      P = 1012.5 * e^( H / -7.2 )        (^ denotes exponentiation)

      H = -7.2 * Ln( P / 1012.5 )        (Ln denotes natural log)

so it can be used for heights above 80 km.

Q. Why do I get an error when I try to load radar data that I downloaded from NCEI?

A. There are few common problems that can cause this:
  1. The files are in a compressed tar file - Typically, when you download Level II data from NCEI, the files are in a compressed TAR file which holds the individual volume scans. You need to extract the volumes from the TAR file with utilities like tar, gunzip, WinZip into a directory.
  2. You are using the Files chooser - You should load the radar data using the Radar->Level II->Local file chooser in the Data Sources tab of the Data Explorer, not the General->Files chooser. In some cases, the files do not have any location information in them. The Level II data chooser allows you to associate a station location with the data file, using the directory name as a first guess.
  3. You are trying to load Level III raster products - McIDAS-V only handles the Level III data that is stored in radial format (Base Reflectivity, Storm Relative Velocity, Base Velocity, 1 and 3 hour precipitation, Echo Tops).

Q. When I try to read in my GRIB data, why do I get an ucar.grib.NotSupportedException?

A. For McIDAS-V to read in GRIB data, it needs access to lookup tables for decoding the information in the data. McIDAS-V comes pre-configured with most of the commonly used tables from NCEP, FNMOC, etc, but some GRIB data from regional centers may use tables other than the defaults. If McIDAS-V does not have the necessary table, you will get the NotSupportedException. You can add in new tables by following the instructions in the User's Guide section on Adding in new GRIB tables.

Q. How are grids resampled in McIDAS-V?

A. McIDAS-V uses two methods for resampling data - weighted average and nearest neighbor. These are the default sampling modes for VisAD, which McIDAS-V is based on. For any grid, the samples are organized in a topology, which may be triangles (Irregular2D), squares (Gridded2D), tetrahedra (Irregular3D) or cubes (Gridded3D). For target points the system finds which topology element contains the target. For nearest neighbor, it gets the values at the vertex of that containing topology element closest to the target point. For weighted average, it computes a weighted average of all vertices of that containing topology element, where the weights are bilinear in 2D and trilinear in 3D. (source: Bill Hibbard, SSEC)

Q. Why can't I create a time series from single time grid files?

A. If you receive an error message similar to the following:


      An error has occurred:

      Creating display: Color-Shaded Plan View

      org.python.core.PyException

      

      visad.UnitException: visad.UnitException: Set: units dimension 1 does

        not match Domain dimension 2

the files may not have a "time" dimension defined in them. It is recommended that you use the NetCDF Markup Language (NcML) to aggregate the files. See http://www.unidata.ucar.edu/software/thredds/current/netcdf-java/ncml/Aggregation.html for more information on aggregating files.

Q. How do I create a time series from individual grid files with different time steps?

A. If you have individual files of gridded data for multiple time steps that you want to display as a single layer to utilize the Time Animation Widget, there are two methods of doing this. First, in the Data Sources tab of the Data Explorer, navigate to the Gridded Data->Local or the General Files/Directories chooser. Select the Aggregate Grids by Time Data Type, navigate to the directory where your files are stored, and use Shift+click to select the files you wish to include in your layer. In the Field Selector, you will see that all of the times you selected for the data are grouped together. You can select your display type, create the display, and all of the data times will be loaded in as one layer and you can animate through them.

Alternatively, you can add all of the files individually through the Gridded Data->Local or General->Files/Directories chooser (without the Aggregate Grids by Time Data Type) and use the Make a time sequence from single time grids/images formula. This is a native formula of McIDAS-V that can be found under the Miscellaneous tree of formulas in the Field Selector. Using this formula, you can select all of the individual files, and McIDAS-V will add all of them to the Main Display window as a single layer you can animate through time.

Q. What are the wind speed thresholds for different wind barbs?

A. Below is a table that shows different wind speed thresholds when it comes to plotting wind barbs of gridded or point data. In this table, 'x' represents wind speed in knots.

Wind Barb Knots Wind Barb Knots
Calm x = 0 55kt 52.6 ≤ x ≤ 57.5
2kt 0 < x ≤ 2.5 60kt 57.6 ≤ x ≤ 62.5
5kt 2.6 ≤ x ≤ 7.5 65kt 62.6 ≤ x ≤ 67.5
10kt 7.6 ≤ x ≤ 12.5 70kt 67.6 ≤ x ≤ 72.5
15kt 12.6 ≤ x ≤ 17.5 75kt 72.6 ≤ x ≤ 77.5
20kt 17.6 ≤ x ≤ 22.5 80kt 77.6 ≤ x ≤ 82.5
25kt 22.6 ≤ x ≤ 27.5 85kt 82.6 ≤ x ≤ 87.5
30kt 27.6 ≤ x ≤ 32.5 90kt 87.6 ≤ x ≤ 92.5
35kt 32.6 ≤ x ≤ 37.5 95kt 92.6 ≤ x ≤ 97.5
40kt 37.6 ≤ x ≤ 42.5 100kt 97.6 ≤ x ≤ 102.5
45kt 42.6 ≤ x ≤ 47.5 105kt 102.6 ≤ x ≤ 107.5
50kt 47.6 ≤ x ≤ 52.5 110kt 107.6 ≤ x ≤ 112.5

Video Cards FAQ

Q. Do I need a special video card to run McIDAS-V?

A. Your graphics system must support 3D; make sure you have the latest video driver for your graphics card. This is included in the Windows operating system. On Linux the driver must support GLX, an X windows system extension to OpenGL programs. See Operating System Requirements for more information.

Q. Why does the display go gray or get corrupted when I resize my McIDAS-V display?

A. ATI cards do not always work correctly with the OpenGL version of Java 3D under Windows. If you experience problems with corrupted displays (sets of triangles, spurious lines, weird looking displays) and have an ATI card and are running Windows, try the following:

Q. If I'm having problems with the OpenGL version under Windows, can I run the Direct-X version Java 3D?

A. If you are using the version of Java 3D distributed with McIDAS-V (1.6.0), you can switch between the OpenGL and Direct-X versions of Java 3D with a command line switch. If you are using runMcV.bat to start McIDAS-V, edit that file and uncomment the appropriate line. If you have your own script for starting McIDAS-V, add in the -Dj3d.rend=d3d option to your start line (before -jar or class name).


Common Installation Errors FAQ

Q. How do I get around a security error when installing McIDAS-V on my 10.8 OSX machine?

A. After double-clicking on the *.dmg installer file, you may see the following error:

"McIDAS-V Installer" can't be opened because it is from an unidentified developer.
Your security preferences allow installation of only apps from the Mac App Store and identified developers.

To get around this, you could turn off the security checks or follow the next steps which will work around the security for the McIDAS-V installation. To do this, right-click on the installer icon to get a dropdown menu, and choose Open. After choosing Open, you should see the following message:

"McIDAS-V Installer" is from an unidentified developer. Are you sure you want to open it?
Opening "McIDAS-V Installer" will always allow it to run on this Mac.

Once you click Open in this window, you will be prompted to enter a login/password for the administrator account. After entering this information, click OK and the installation should proceed without error.

Q. What do I do if I am told to upgrade JDK when installing McIDAS-V?

A. A user reported --- The first time I ran the script, it told me I needed to upgrade my JDK. So I installed jdk1.6.0_03 and Java3D 1.3.1. Then McIDAS-V installed without any problem.

Q. How do I solve write permissions errors on OSX?

A. Browse for a writable directory (e.g. /Users/mcuser). Under "Select Additional Tasks", uncheck "Create Launcher and Configuration shortcuts in Applications folder"

Q. How do I solve shortcut permissions errors on OSX?

A. At Extracting files: McIDAS-V Configuration.app/Contents/Info.plist/Applications/McIDAS-V Configuration.app/Contents/Info.plist I can not create this file. To solve this, click "Cancel" and restart the installer. Follow instructions under Error #2 above.

Common Run-Time Errors FAQ

Q. Why do I see 'Local servers cannot write to userpath:' errors when starting McIDAS-V?

A. To use local servers in McIDAS-V, there is a background server listening process called mcservl. This process run for the duration of the session, and after McIDAS-V is exited, the process take extra time to terminate. If McIDAS-V is closed and started again before the mcservl process terminates, local servers will not be able to start and the 'Local servers cannot write to userpath:' error occurs. Once this error comes up, click OK. If you attempt connecting to a local dataset, a message will pop up directing you to the ADDE Data Manager, where navigating to the Local Servers -> Start Local Servers menu item will start up the local servers correctly so that local servers can be used in the session. To avoid this error, it is recommended that a user waits about 10 seconds after exiting McIDAS-V before starting again.

Additionally, if running 64bit Debian or Ubuntu operating systems, this message can appear at startup if the ia32-libs package is not installed on the workstation. The ia32-libs are the 32bit libraries that 32bit applications need to execute on a 64bit system.

Q. What do I do if I get a 'Could not create a graphics configuration' error?

A. Verify that the machine has the most updated video card driver.

Q. What do I do if I get 'JAVA 3D Error: GLX extension is not supported' and 'Could not create a graphics configuration' errors?

A. GLX is an extension that must be supported by the graphics card. This error is most likely occurring because the graphics drivers for RHEL are not properly configured.

Assuming that the latest graphics drivers are installed, they must be configured in the window system configuration file. Since RHEL uses Xorg, look in the file

/etc/X11/xorg.conf

and see if there are any references to "GLX" or "glx" (and possibly "dri"). If there are, try uncommenting them and rebooting.

Q. What do I do if I see 'Connection refused' and 'No public datasets found' errors when connecting to the listed data servers?

A. If you have a firewall and are trying to get data from the remote servers (image, radar, point, and upper air data), error messages such as "Error opening connection ... Operation timed out" or "No Data Available" are normal. For these servers to send data, your firewall software must allow connections on ports 112 (ADDE) and 8080 (THREDDS Data Server).

Q. Why am I having drawing problems on Monitor2 of a two-monitor system?

A. Some graphics card/driver combinations don't allow McIDAS-V window functions to work correctly in Monitor2 of two-monitor systems. For example, if your system has this problem and you move the McIDAS-V windows to Monitor2, the Image Chooser's Advanced tab in the Field Selector may not be visible, or adding a new tab in the Main Display may result in most of the window going blank ("graying out"). You may also receive the error (or see it in the mcidasv.log file), '...adding a container to a container on a different GraphicsDevice'.

For now, the only working solution for this problem is to move the McIDAS-V windows to Monitor1. After doing this, the windows should display correctly and you should be able to successfully add new tabs and run bundles.

If you are running Red Hat with a NVIDIA graphics card using TwinView and are having problems, go to the preferences, click on the primary display, and make sure the "Make this the primary display..." checkbox is checked.

Q. Why is there no map drawn in the McIDAS-V Main Display window?

A. Try changing your memory to use 1 GB or lower and restart McIDAS-V. You can change the amount of memory used by McIDAS-V by editing the Maximum Heap Size in the Advanced tab of the Preferences by selected Edit->Preferences... from the Main Display window. If this does not help, disabling geometry by reference in the Advanced Preferences and restarting McIDAS-V may return the map lines to the Main Display window.

Q. How do I fix the spurious map lines in my Main Display window?

A. If you run into this problem, you should first try changing your Enable access to geometry by reference VisAD setting in the Advanced tab of the User Preferences window. You can get to the User Preferences window through the Edit->Preferences menu item in the Main Display window. This option is turned on by default, but turning this option off can help to remove random/extraneous map lines that sometimes appear in the display. This is a problem that may occur more frequently on systems with ATI graphics cards. After changing this preference, click OK and restart McIDAS-V (any changes to the Advanced Preference require a restart to take affect).

If this did not solve the map line problem, look in the Layer Controls tab of the Data Explorer for the Default Background Maps. Determine which map is causing the spurious lines by toggling the visibility of the maps on and off. Once you determine which map is causing the lines, change the Fast Rendering option for this map.

Q. Why do my images display blank (black or white) when there should be valid data?

A. The first thing to do is to make sure that your graphics drivers are up to date. If this does not solve the problem, another option is to change the amount of memory allocated to McIDAS-V. From the Main Display window's menu bar, select Edit->Preferences. This opens a User Preferences window, where you want to select the Advanced tab. At the top of the window there are two options for selecting memory. Click the radio button that allows you to specify the numerical value of memory allocated to McIDAS-V. Enter in a value of 512 megabytes and click OK to save the change. Then exit and restart McIDAS-V (changes in the Advanced User Preferences require a restart of McIDAS-V to take effect). If this resolves the issue of white images, you can start increasing the memory until the problem appears again. Stay below the memory value that produces the problem.

We have also received reports of this problem (blank images in the Main Display window) occurring on computers with the Mobile Intel 4 Series Express Family of graphics cards. If you have a computer with that configuration and are seeing the problem, try setting the card's "Vertex Processing" configuration setting to "Enable Software Processing". That setting is recommended because it will likely work with a typical amount of memory allocated to McIDAS-V (e.g., 80% of available). If the "Vertex Processing" option is set to a different value (e.g., "Application Settings" and "Default settings"), you may have to select a memory value of 800 MB or less in order to avoid the problem.

Q. Why do I get an error that starts something like "Unexpected Signal : 11 occurred at PC=0x6F79CE1" when starting McIDAS-V under Linux?

A. If the error message also includes a line that is looking for a Library with "dri" in it's name (e.g.: Library=/usr/X11R6/lib/modules/dri/i915_dri.so), it means that you are trying to load the DRI library in your X server which is not compatible with Java 3D. You need to comment out the line:
Load "dri"

in your X server configuration file (xorg.conf or XF86Config).

Q. Why am I am seeing a "Canvas3D: Non-recoverable graphics configuration error" when starting McIDAS-V on my 64-bit Windows machine?

A. When starting McIDAS-V on a 64-bit Windows machine, you may see this error message as the last line of your mcidasv.log file: "Canvas3D: Non-recoverable graphics configuration error". If you run into this problem, you should first try updating your drivers and installing McIDAS-V again. If this does not solve the problem, it is possible that there are some graphics cards that do not have 64-bit drivers and thus will not be able to support the 64-bit installers. If this is the case for you, attempt to download McIDAS-V utilizing the 32-bit Windows installer instead of the 64-bit installer.

Users can also follow the steps outlined in the What do I do if McIDAS-V will not work on my computer? question of the Using McIDAS FAQ. McIDAS User Services received a report that a user was able to resolve this error by uninstalling NVIDIA PhysX package and then reinstalling McIDAS-V.


Reporting Problems FAQ

Q. What kind of support is provided for McIDAS-V?

A. For information about obtaining help and support for McIDAS-V, check out the Documentation and Support page in the McIDAS-V User's Guide.

Q. How do I report problems?

A. First, check this FAQ and the McIDAS-V Support Forums to make sure this is a problem that has not yet been reported.

If you experience unexpected problems that are not reported in those locations, please let us know. See the Documentation and Support section of the manual for the procedures on how to do this.

Q. How do I open the Error Logs Console?

A. Open a console to show error logs with the Help->Show Console menu.

Q. What do I do if McIDAS-V is locked up and not responding?

A. First, you need to retrieve a stack track of the program so we can find out why this is happening. McIDAS-V provides a web-based service that produces a stack trace. Just view the URL:

  http://127.0.0.1:8788/

and send the McIDAS-V Support Team on the Contact Us page. Note: This service is only available from browsers running on the machine McIDAS-V is running on.

You can also use this service to shutdown McIDAS-V.


McIDAS-X Commands in McIDAS-V

Listed Below are several common McIDAS-X commands, followed by a brief description of the corresponding method used in McIDAS-V.

ADDE Datasets

Frame Control

Gridded Data

Image Data

Image Enhancements

Surface Data

Upper Air Data

Other