CLASSy Data Summary and Inspection

From CARMA
(Difference between revisions)
Jump to: navigation, search
(MIS Notes)
Line 6: Line 6:
 
Typical procedure to retrieve and modify flags for the example of c0924I.1D_88B1S.1:
 
Typical procedure to retrieve and modify flags for the example of c0924I.1D_88B1S.1:
  
   mis -u (or:  (cd def ; cvs up)  since the pipeline maintains a symlink to $MIS/def/$project)
+
 
   mkdir c0924I.1D_88B1S.1
+
  set p=c0924I.1D_88B1S.1
   cd c0924I.1D_88B1S.1
+
 
   pipepar -c project=c0924I.1D_88B1S.1
+
   mis -u         (or:  (cd def ; cvs up)  since the pipeline maintains a symlink to $MIS/def/$project)
 +
   mkdir $p      (the name of the directory can be anything)
 +
   cd $p
 +
   pipepar -c project=$p
 
   pipesetup
 
   pipesetup
 
   getdata
 
   getdata

Revision as of 18:51, 1 May 2012

Each observation will end by sending an email with the title Project c0924: CARMA track finished, and should contain two attachments: the c0924_XX_YYYY.obs (observing script) and scriptlog.txt (observing log). Peter will save these in MIS, download the data, and initialize MIS with a default mis.def and mis.uvflag file for anybody to start the initial data summary and inspection. For this to work, you will first have to update your MIS with the new files, so you can grab the the new data and work on that.

MIS Notes

  • flags file for do_uvflag are in mis.uvflag, qvack file for do_uvflag are in mis.qvack (both optional)

Typical procedure to retrieve and modify flags for the example of c0924I.1D_88B1S.1:


 set p=c0924I.1D_88B1S.1
 mis -u         (or:   (cd def ; cvs up)  since the pipeline maintains a symlink to $MIS/def/$project)
 mkdir $p       (the name of the directory can be anything)
 cd $p
 pipepar -c project=$p
 pipesetup
 getdata
 report
 <edit the mis.uvflag and/or mis.qvack>
 ...
 pipesave
 mis -i  (or:   (cd def ; cvs ci))  -- if you feel confident these files can be checked back into CVS

Clouds

Personal tools