Here we describe the various scripts we are using for the EGNoG project. Most of them will be based on the Miriad package, but we will also be using DS9, KARMA and NEMO, and maybe more (IDL, GIPSY)? To simplify/organize our scripts, we have assembled a CVS module called EGN, in which all scripts (and default parameter data to run the scripts) are maintained. First we describe EGN, after that the individual scripts.
This is our CVS based module to organize all our reduction scripts and store the parameters important for them as well. We separate these in a script independant way, so we allow anybody to use csh, sh, python, fortran, C, C++, Java, ...... There is also a manual available, although you can also generate a new one from your own EGN version.
If you want to grab a copy of EGN, for now use our CVS repository version (or use this tar file which you will need to cvs update):
cvs -d :pserver:$USER@cvs.astro.umd.edu:/home/cvsroot checkout egn
where $USER is your given username in CVS (or use anonymous if you only need to grab a copy for read-only use).
If you have never used CVS before, get your introduction from our CARMA pages here. If you need an account, you will need to email Peter your preferred username, and the hashed output of the password generator (details in that link) via the command
perl -e 'print crypt("my_password","b6"), "\n";'
and he better not get the response b60j72OwWnjlk from you!!!
Once you have obtained MIS, get it ready for installation:
cd egn ./configure source egn_start.csh
and you are in principle ready to use the MIS scripts. There are some additional powerful options to construct automated pipelines, but that is for another chapter.
Occasionally there will be updates. If you are not a developer, and just want to update EGN from what others have done, this should work in most cases:
is simply a shortcut to committing all your EGN changes back to CVS for others to pick up. Use that with caution, as it could commit more than you may have bargained for!
Not all scripts have been properly EGN-pipelined yet! Keywords followed by = means they can be input in this script, keywords preceded by = means they are set by this script
- getdata: project= rawdata= scp= =cvis
- report: =size
- reduc.csh: Amber's script, default works for project=c0834I.1D_97B1.1
- do_uvcat2: calibrate and map the calibrator to get an idea of the noise
Adding new data
When a new dataset needs to be added, read the $EGN/USING file on how this has to be done, but essentially these are the steps:
- place the dataset as compresses miriad tar file into your repository (the raw= directory is used for this)
- create a new directory $EGN/def/$project.$trial
- add scriptlog.txt and $project.obs to this directory
- append the $project name to the $EGN/cat/egn.lis file
- in your favorite datareduction directory you can now issue
pipepar -c project=$project.$trial getdata report do_uvcat1
Example Session using EGN
A simple non-pipelined session