CLASSy Data Summary and Inspection

From CARMA
(Difference between revisions)
Jump to: navigation, search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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.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.
+
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 ==
 
== 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 for the example of c0924I.1D_88B1S.1:
  
   mis -u (or:   (cd def ; cvs upsince the pipeline maintains a symlink to $MIS/def/$project)
+
  set p=c0924I.1D_88B1S.1
   pipepar -c
+
  #
   pipesetup
+
   mis -u         (update your MIS with new class.lis and project mis.def file(s))
   <edit the mis.uvflag>
+
   #
 +
  mkdir $p      (the name of the directory can actually be anything, but we need this name below)
 +
  cd $p
 +
  pipesetup project=$p (here the name $p needs to conform to one the projects/tracks in classy.lis)
 +
   getdata
 +
   report
 +
   <edit the mis.uvflag and/or mis.qvack>
 +
  ... inspect, map, etc.etc.
 
   pipesave
 
   pipesave
   mis -i  (or:  (cd def ; cvs ci))
+
  #
 +
   mis -i  (or:  (cd def ; cvs ci)) -- if you feel confident these files can be checked back into CVS
  
 
== Clouds ==
 
== Clouds ==
  
 
* [[B1s]]
 
* [[B1s]]
 +
* [[L1451]]  (aka B1e)
 
* [[Serpens Main]]
 
* [[Serpens Main]]
 +
* [[Serpens South]]
 +
 +
* [[CLASSyPrime]]

Latest revision as of 15:05, 7 October 2014

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.

[edit] 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         (update your MIS with new class.lis and project mis.def file(s))
 #
 mkdir $p       (the name of the directory can actually be anything, but we need this name below)
 cd $p
 pipesetup project=$p  (here the name $p needs to conform to one the projects/tracks in classy.lis)
 getdata
 report
 <edit the mis.uvflag and/or mis.qvack>
 ... inspect, map, etc.etc.
 pipesave
 #
 mis -i  (or:   (cd def ; cvs ci))  -- if you feel confident these files can be checked back into CVS

[edit] Clouds

Personal tools