CLASSy Data Summary and Inspection

From CARMA
(Difference between revisions)
Jump to: navigation, search
(MIS Notes)
Line 2: Line 2:
  
 
== MIS Notes ==
 
== MIS Notes ==
* flags file for do_uvflag are in '''mis.uvflag'''
+
* 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 in a project directory:
 
Typical procedure to retrieve and modify flags in a project directory:
Line 9: Line 9:
 
   pipepar -c
 
   pipepar -c
 
   pipesetup
 
   pipesetup
   <edit the mis.uvflag>
+
   <edit the mis.uvflag and/or mis.qvack>
 
   pipesave
 
   pipesave
 
   mis -i  (or:  (cd def ; cvs ci))
 
   mis -i  (or:  (cd def ; cvs ci))

Revision as of 18:41, 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 in a project directory:

 mis -u  (or:   (cd def ; cvs up)  since the pipeline maintains a symlink to $MIS/def/$project)
 pipepar -c
 pipesetup
 <edit the mis.uvflag and/or mis.qvack>
 pipesave
 mis -i  (or:   (cd def ; cvs ci))

Clouds

Personal tools