| • |
|
|
|
|||
|
||||
Ask your system administrat or to create user individual accounts for running McIDAS-X.
Individual users or the system administrator must complete the following tasks for each account in which McIDAS-X will be run:
For convenience, files with the settings described below are downloadable here (remember to hold down the shift key while pressing mouse button 1 to transfer these files):
Defining all of these enviornment variables is easily accomplished by adding the following lines to your shell definition file:
| non-Conforming shells (e.g., .cshrc) | Conforming shells (e.g., .profile, .bash_profile, or .kshrc) |
setenv MCHOME /home/mcidas if ( -e $MCHOME/admin/user_env.csh ) then source $MCHOME/admin/user_env.csh endif |
MCHOME=/home/mcidas export MCHOME if [ -e $MCHOME/admin/user_env.sh ]; then . $MCHOME/admin/user_env.sh fi |
The environment variables that need to be defined for each account in which McIDAS-X will be run are:
| Environment Variable | Purpose |
|---|---|
| MCHOME | the HOME directory of mcidas |
| MCDATA | user's working directory for McIDAS-X sessions |
| MCPATH | MCPATH - a colon-separated list of directories that McIDAS routines will search when looking for data and ancillary data files |
| MCGUI | the directory in which the Unidata Tcl/Tk GUI executables and scripts and McIDAS-X executables reside. If you have your own McIDAS executables, add the directory location for those after the main McIDAS executable directory |
| MCTABLE_READ | a semi-colon separated list of fully qualified pathnames for ADDE client routing tables that the user can read |
| MCTABLE_WRITE | the single ADDE client routing table that the user can modify |
| PATH | add the MCGUI directory to the front of your PATH |
EXAMPLE:
The definitions for the needed environment variables for a Unix C-shell user look like:
# C-shell environment variable definitions for a general user
# NOTE: conditional definition is needed for C-shell users
if ( ! ${?MCPATH} ) then
setenv MCDATA $HOME/mcidas/data
setenv MCPATH ${MCDATA}:$MCHOME/data:$MCHOME/help
setenv MCGUI $MCHOME/bin
setenv MCTABLE_READ "$MCDATA/MCTABLE.TXT;$MCHOME/data/ADDESITE.TXT"
setenv MCTABLE_WRITE "$MCDATA/MCTABLE.TXT"
if ( ! ${?path} ) then
set path=$MCGUI
else
set path=(${MCGUI} $path)
endif
endif
# Limit ADDE transfers to compressed ones
setenv MCCOMPRESS GZIP
| NOTE: The conditional definition of MCDATA, MCPATH, MCGUI, MCTABLE_READ, and MCTABLE_WRITE is needed only by C Shell users. If the conditional clause is not included by these users, unpredictable results will occur. |
If you will not be writing and compiling McIDAS software, update your PATH with the modifications listed below.
| Operating System | Modification |
|---|---|
| AIX | none necessary |
| FreeBSD | none necessary |
| IRIX 6.x | none necessary |
| HP-UX 11 | add this directory to your path: /usr/bin/X11 |
| Linux | none necessary |
| Solaris | none necessary |
The actions required to enable certain keyboard function keys that can be used by McIDAS-X (for example, Alt A, Ctrl F11) vary depending on your workstation and its configuration. This section describes these actions for workstations running the following SSEC-recommended configurations:
These directions assume you are in the account's $HOME directory and logged on to the workstation console.
Enabling McIDAS-X Keys for AIX Motif --Follow the steps below if you use an AIX workstation console and the Motif window manager (mwm).
1. Make a copy of the mwm configuration file; enter the commands below.
2. Remove Alt<Key>Fn from the following lines in the Menu DefaultWindowMenu section in the account's .mwmrc.
"Restore" _R Alt<Key>F5 f.restore "Move" _M Alt<Key>F7 f.move "Size" _S Alt<Key>F8 f.resize "Minimize" _n Alt<Key>F9 f.minimize "Maximize" _x Alt<Key>F10 f.maximize "Lower" _L Alt<Key>F3 f.lower |
This allows McIDAS-X to use the Alt F3, Alt F5, Alt F7, Alt F8, Alt F9, and Alt F10 keys.
3. Remove Alt<Key>F4 from the line below in the Menu DefaultWindowMenu section in the account's .mwmrc.
"Close" _C Alt<Key>F4 f.kill |
This allows McIDAS-X to use the Alt F4 key.
4. Delete or comment out the line below from the Keys DefaultKeyBindings section in the account's .mwmrc.
Alt<Key>F6 window f.next_key transient |
Enabling McIDAS-X Keys for AIX Common Desktop Environment --Follow the steps below if you use an AIX workstation console and the Common Desktop Environment (dtwm).
1. Create or modify the account's $HOME/.Xdefaults and add the following line.
Dtwm*windowMenu: NoAcceleratorWindowMenu |
2. Select the Edit Dtwmrc icon from the Desktop_Tools section of the Application Manager. The Application Manager is started by clicking its icon on the Front Panel .
3. Delete or comment out the line below in the Keys DefaultKeyBindings and Keys DtKeyBindings sections in the account's dtwmrc file.
Alt<Key>F6 window f.next_key transient |
Enabling McIDAS-X Keys for HP-UX Visual Users Environment --Follow the steps below if you use an HP-UX workstation console and the Visual UsersEnvironment window manager (vuewm).
1. Set the environment variable EDITOR. If you use sh or ksh, enter the command below.
If you use csh, enter the command below.
2. Use the command below to display the vi editor and the vuewm resource file in a separate window.
3. Add the line below to the vuewm resource file using the vi editor, write the file, and quit vi.
Vuewm*windowMenu: NoAcceleratorWindowMenu |
This allows McIDAS-X to use the Alt F4 key.
4. Use the command below to display the vi editor and the vuewm initialization file in a separate window.
5. Delete or comment out the line below in the Keys VueKeyBindings section of the vuewm initialization file. Then, write the file and quit vi.
Meta<key>F6 window f.next_key transient |
Enabling McIDAS-X Keys for IRIX Extended Motif --Follow the steps below if you use an IRIX workstation console and the IRIS Extended Motif window manager (4Dwm).
1. Make a copy of the 4Dwm configuration file; enter the commands below.
2. Delete or comment out the line below in the Keys 4DwmKeyBindings section in the account's .4Dwmrc. The line may contain Meta instead of Alt.
Alt<Key>F6 window f.next_key transient |
This allows McIDAS-X to use the Alt F6 key.
3. Remove
This allows McIDAS-X to use the Alt F1, Alt F3, Alt F5, Alt F7, Alt F8, Alt F9, and Alt F10 keys.
Enabling McIDAS-X Keys for Linux and GNOME --Follow the steps below if you use an Linux workstation console and the GNOME desktop environment.
1. Bring up the Keyboard Shortcuts window by clicking the following in order: Main Menu (in lower-left corner), Preferences, Keyboard Shortcuts.
2. Highlight each shortcut associated with a key combination you want to use in McIDAS-X (e.g., <ALT>F2) and press the Backspace key to change it to Disabled. This allows McIDAS-X to use the key combination for strings and other applications.
Enabling McIDAS-X Keys for Mac OS X and X11 --Fol low the steps below if you use an Mac OS X workstation console and Apple's X11 desktop environment.
1. Start X11 by double-clicking the X11 icon in the Applications>Utilities folder. If X11 is already running, click the X11 icon in the dock to make the application active.
2. Click the X11 menu at the top of the display, then click Preferences to bring up the X11 Preferences window.
3. Click the Input tab, then uncheck the checkbox labeled Enable key equivalents under X11.
Steps 1-3 allow the open-apple keys (on each side of the spacebar) to function as the Alt keys in McIDAS-X.
4. Start a Terminal by double-clicking the Terminal icon in the Applications>Utilities folder. If a Terminal is already running, click the Terminal icon in the dock to make the application active. Then use the xmodmap utility to configure a key to function as the Insert key during McIDAS-X command entry. Choose the appropriate command below, depending on whether you have a fullsize (desktop) keyboard or a laptop.
On a fullsize keyboard, run the command below to configure the help key to function as Insert.
On a laptop, run the command below to configure the option (alt) key to function as Insert.Enabling McIDAS-X Keys for Solaris OPEN LOOK --Follow the steps below if you use a Solaris workstation console and the OPEN LOOK window manager (olwm).
1. Copy files .openwin-init and .Xdefaults to the account's home directory if they do not already reside there.
2. Add the following line to the account's .Xdefaults file.
OpenWindows.KeyboardCommands: SunView1 |
This allows McIDAS-X to use the Alt Q key.
3. Add the following line to the account's .openwin-init file.
xmodmap -e 'keycode 16 = F11' -e 'keycode 18 = F12' |
This allows McIDAS-X to use the F11 and F12 keys, and their Alt, Shift and Ctrl forms.
Enabling McIDAS-X Keys for Solaris Common Desktop Environment --Follow the steps below if you use a Solaris workstation console and the Common Desktop Environment (dtwm).
1. Create or modify the account's Xdefaults file $HOME/.Xdefaults and add the following line.
Dtwm*windowMenu: NoAcceleratorWindowMenu |
2. Select the Edit Dtwmrc icon from the Desktop_Tools section of the Application Manager. The Application Manager is started by clicking its icon on the Front Panel.
3. Delete or comment out the line below in the Keys DefaultKeyBindings and Keys DtKeyBindings sections in the account's dtwmrc file.
Alt<Key>F6 window f.next_keytransient |
This concludes the instructions for installing McIDAS-X and configuring user accounts. Continue with Configuring McIDAS-X Sessions with .mcidasrc, which provides information about tailoring McIDAS-X sessions to your preferences.
Depending on whether a user's account was setup to run a previous release of Unidata McIDAS-X, there are one or more files that need to be copied from the current distribution's package data directory (~mcidas/mcidas2009/data) to his/her McIDAS-X working directory ($HOME/mcidas/data). The files that potentially need to be copied are:
| File | Purpose |
|---|---|
| UNIMENU.DEF | File containing defaults for Unidata Fkey Menu and Tcl/Tk GUI |
| STRTABLE | McIDAS String Table (optional) |
| SKEDFILE | McIDAS Scheduler File (optional, we recommend using cron instead) |
If the user has been running a previous release of Unidata McIDAS-X, then the only file that needs to be copied (or merged with an existing copy) is UNIMENU.DEF.
After logging on to the workstation, the user must:
To simplify the process of copying files, a shell script, userdata, is provided in the mcidas' admin directory (~mcidas/admin).
To run userdata, each user should log on to his/her account and do the following:
If the account is new, make the McIDAS-X working directory:
After $HOME/mcidas/data has been created, the user needs to:
For instance, users other than mcidas need only do the following to setup access to datasets and ADDE servers defined by mcidas:
Start a McIDAS-X session:
If this is the first v200x session that the user has started, the file .mcidasrc will be created in his/her HOME directory.
If the mcidas user decided to not setup a remote ADDE server, each user must define the ADDE datasets that s/he wants to access from the realtime data ingested by the LDM. That user will need to complete the following steps.
In Preparing the mcidas Account, we saw that the user mcidas is responsible for creating a set of file redirections in /home/mcidas/data/LOCAL.NAM. These same redirections can be used by the non-mcidas user. To make those redirections active in their sessions, users need to do the following:
Within the now-active session, the user needs to restore the redirection definitions from LOCAL.NAM to his/her session:
LOCAL.NAM should be accessible to the McIDAS-X session by virtue of the user's MCPATH containing the /home/mcidas/data directory.
After the redirections are restored, the user should be able to access the data files accessible to his/her machine (either on local or NFS mounted disks). ADDE datasets accessible from the site's remote ADDE server will be available after the remote server is installed by root.
Next, the user will need to define the ADDE datasets that contain the locally accessible data files by using the LSSERVE.BAT file that mcidas also created. This is done as follows:
Here, fully_qualified_directory_name is the directory where McIDAS data files to be served are located.
In order to access McIDAS data files through local ADDE access, the user should now update her/his ADDE client and server routing tables by defining a dataset named MYDATA and declare it to be locally accessible. This is accomplished using the McIDAS BATCH file, MYADDE.BAT:
The same should be done for the TOPO dataset since the images that make up the dataset are included in the Unidata McIDAS-X release:
As this completes the configuration steps the user needs to make, he/she should now EXIT McIDAS:
This concludes the instructions for installing McIDAS-X and configuring user accounts. Continue with Configuring McIDAS-X Sessions with .mcidasrc , which provides information about tailoring McIDAS-X sessions to your preferences.
| Contact Us • Site Map • Search • Terms and Conditions • Privacy Policy • Participation Policy | |||||
|
|||||
