Setting up your account to use MIRIAD
varies from system to system.
If in doubt, ask a local! We will assume you are using the csh
shell.
If you are using the `standard' login scripts on the Marsfield machines, you will be prompted whether you wish to include MIRIAD when you first log in.
On other systems, you will need to include two lines in your
.login script.
At Parkes (or at Marsfield if you are not using the standard login scripts)
include;
source /applic/miriad/bin/MIRRC
set path = ($path $MIRBIN)
Similarly at Narrabri, include
source /miriad/bin/MIRRC
set path = ($path $MIRBIN)
(At Narrabri, partial initialisation of MIRIAD
\
happens for all accounts. This will be adequate for many peoples needs.
All the same, we suggest fully initialising MIRIAD
, using the above two
lines, to avoid possible confusion). Other sites should have similar
arrangements -- only the directory should change.
The operations performed by these two lines are simple enough.
The MIRRC script, in the first line, sets up environment
variables (including MIRBIN) to point to the appropriate directories.
The second line includes the MIRIAD
executables
in your executable search path (you may choose to place it somewhere other
than the end of the search path).
You may also wish to set the environment variable MIRDEF to point
to a directory where the keyword files
generated by the miriad front-end should be stored. For example:
% setenv MIRDEF /mydirectory/mirdefBy default these keyword files are stored in the directory
~/mirdef,
if it exists when MIRRC is invoked, or in your current working directory.