SUMMARY - USER INSTALL

To use NEMO make sure the following is present in your default startup file(s) .cshrc/.login:

• Setting the root directory of NEMO:

  
  	setenv NEMO /home/nemo

  Of course the rootname of NEMO on your system will probably differ from the one listed in this example.

• Executing the startup script for NEMO, which sets other environment variables etc:

  
  	source $NEMO/NEMORC

• Add NEMOs bin directory (NEMOBIN, which is set by NEMORC) to your search path. An example could be:

  
   	set path=( . $NEMOBIN $path )

A second method to load NEMO is by demand only, (so-called dynamic loading) by adding the following alias anywhere in your .cshrc file:

 	alias nemo 'source /home/nemo/nemo_start'

SUMMARY - USER INTERFACES

Most NEMO programs are invoked from the commandline, just like any other UNIX program, with a series of parameters of the form `keyword=value'. We call these program keywords, as the names of the keywords are unique to a program. The keyword= part is not needed in case the original order of the keywords is used. Once a keyword is specifically named, all remaining keywords need the keyword name too, e.g. `prognam val1 val2 key6=val6 key7=val7'. The value of a keyword can also be obtained from an 'include' file by using the keyword=@file construct.

There also exist a fixed set of system keywords, which are defined for every NEMO program. They are:

help Sets help level to program and can aid in command completion. Consist of a numeric and alpha part. The numeric part is a mask of individual help levels which are powers of 2:

1.
restore and save keywords in keyword file prognam.def.
2.
interactive prompting per keyword
4.
menu interface using environment variable EDITOR.
8.
curses based menu interface.
16.
reserved

For example, help=5 would no only use the menu interface, but also restore and save the keyword file.

The alpha part typically shows inline help:

?
list of options of help keyword (this list)
h
list keywords plus help string (requires new defv-format)
a
show the keyword=value strings.
p,k
show the keyword strings.
d,v
show the value strings.
n
add newline between keyword=value strings
t
output in exectool format
q
quit

The HELP environment variable will be used if keyword is not used.

debug Define debug output level between 0 and 9. Negative numbers are allowed, and should produce absolutely no warning messages. The higher the level, the more warnings and debug output. The routine dprintf(3NEMO) uses the debug value. The DEBUG environment variable will be used if keyword is not used.

error Bypass a number of fatal error(3NEMO) calls. It's really cheating, use at your own risk. The ERROR environment variable will be used if keyword is not used.

yapp Define graphics device, if applicable, for the program. The YAPP environment variable will be used if keyword is not used.

Reminder: environment variables can be set/reset using the shell commands setenv and unsetenv.

SUMMARY - ADVANCED USER INTERFACES

There are two more advanced (sometimes considered more user friendly) pieces of user interfaces to NEMO that are worth mentioning:

• miriad: Within NEMO the miriad shell can also be used to present a user interface that bears some similarity to AIPS. Usage:

  
  	% miriad -b $NEMOBIN -p $NEMODOC

• nemoman: The command nemoman is a front-end to a variety of manual browsers. Currently implemented are the xman (default, or -x flag) and tkman (using -tk flag). Your local system manager must have installed the programs themselves, nemoman merely calls them with the correct parameters. Examples:

  
  	% mirman
  	% mirman -tk
  	% manlaser snapplot

  The last command pertains to be smart about the NEMO manual pages, and searches for and prints the manual page for snapplot on your default laserprinter. Works fine on SUN workstations, but may need patchwork.

• About this document ...