Scripts

From CARMA
(Difference between revisions)
Jump to: navigation, search
(Example Session using MIS)
Line 63: Line 63:
 
In each project directory you will then have a xyt.tab file for the next stage.  For example to get a listing of how many pointings each track had, use
 
In each project directory you will then have a xyt.tab file for the next stage.  For example to get a listing of how many pointings each track had, use
 
   piperun n1333.lis pipepar -v project -v np
 
   piperun n1333.lis pipepar -v project -v np
 +
 +
and here's how to then create the inttime maps,in various formats (miriad, fits):
 +
 +
  mk_map_inttime.csh */xyt.tab

Revision as of 21:30, 9 March 2011

Here we describe the various scripts we are using for the NGC 1333 project. Most of them will be based on the Miriad package, but we will also be using DS9, KARMA and NEMO. To simplify/organize our scripts, we have assembled a CVS module called MIS, in which all scripts (and default parameter data to run the scripts) are maintained. First we describe MIS, after that the individual scripts.

MIS (Miriad Interferometry Singledish) toolkit

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 MIS version.

If you want to grab a copy of MIS, for now use our CVS repository version (or use this tar file):

 cvs -d :pserver:$USER@cvs.astro.umd.edu:/home/cvsroot checkout mis

where $USER is your given username in CVS (or use anonymous.

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 read for installation:

  cd mis
  ./configure
  source mis_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 MIS from what others have done, this should work in most cases:

  mis -u

whereas

  mis -i

is simply a shortcut to committing all your MIS changes back to CVS for others to pick up.

Scripts

Not all scripts have been properly MIS-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= ary= track= =cvis
  • report:
  • map_inttime: source= =np
  • reduceSD.csh: example of single dish data reduction (using sinbad/sinpoly/varmaps) - MPW

Example Session using MIS

A simple non-pipelined session could be as follows:

  mis -q
  mkdir data10
  cd data10
  pipepar -c rawdata=/home/teuben/carma/work/n1333/rawdata
  getdata project=cx323.1E_89NGC133.17
  getdata track=22 ary=E
  report
  map_inttime 

A more advanced session making the inttime map would be to first construct a pipeline consisting of getdata and map_inttime for all projects, and then use the piperun command to execute this.

  piperun -c n1333.lis 'pipeline 2 getdata map_inttime > Pipefile; pipepar -c project=%s; pipe all'

In each project directory you will then have a xyt.tab file for the next stage. For example to get a listing of how many pointings each track had, use

  piperun n1333.lis pipepar -v project -v np

and here's how to then create the inttime maps,in various formats (miriad, fits):

  mk_map_inttime.csh */xyt.tab
Personal tools