PACS

From CARMA
(Difference between revisions)
Jump to: navigation, search
 
Line 1: Line 1:
[http://www.mmarray.org/project/PairedAntennas/ PACS]
+
[http://www.mmarray.org/project/PairedAntennas/ PACS] notes for MIRIAD:
 +
 
 +
Peter will normally update the OVRO and CARMA machines, as well as the 32 bit version ('astroload miriad') and 64 bit version
 +
('astroload -v 64 miriad') on the UMD machines. For anybody else, check the procedure below if that is what you do:
 +
 
 +
== New/modified software ==
 +
 
 +
* gpbuddy: writes out (unwrapped) phaseatm from a gain solution (that came from selfcal)
 +
* uvcal: has new options=atmcal to apply the atmphase to a dataset. Make sure you have a good freqatm value in your dataset (for now)
 +
* uvwide: SZA data do not have narrow flags, this program was updated for this.
 +
      uvwide vis=$VIS narrow=t
 +
to fix this
 +
* panda: baseline based (not in miriad yet)
 +
* bldelay: baseline based  (not in miriad yet)
 +
 
 +
== Reminder on updating MIRIAD (old style) ==
 +
 
 +
* MAXDIM: two header files describing maximum sizes were updated: $MIRINC/maxdim.h and $MIRINC/maxdimc.h.  Edit this files and modify the MAXBUF parameter in both files to at least 10000000 (4 times the amount is the memory used by programs that use MAXBUF).
 +
  cd $MIRINC
 +
  edit maxdim.h  maxdimc.h
 +
and if to properly update the CVS status of these files (they changed on Dec 4, 2008) a one time is needed to old MIRIAD installs:
 +
  mkdir tmp
 +
  mv maxdim.h  maxdimc.h tmp
 +
  cvs update
 +
  mv tmp/max*h .
 +
 
 +
* CVS: always query your source tree and look for C (conflicts) and M (locally modified) files.  The U (to be updated) files will be new ones.
 +
  cvs -nq update
 +
and if happy with this, issue the real update
 +
  cvs update
 +
 
 +
* Old style updates: (you can give these commands from any directory and it assumed you have write permission in $MIR)
 +
  mirboss
 +
  mir.install subs prog
 +
for a blanket re-install of the library and programs. You need this if e.g. maxdim.h was changed, and/or your miriad does not use shared libraries. This is also the safest way to update.  On most computers this will only take 2-3 minutes. If however you know exactly what the impact of a new file is, you can pick any of the following examples, which will take 2-3 seconds:
 +
  mir.subs fitsio.for uvio
 +
and
 +
  mir.prog itemize gpbuddy
 +
Notice a file extension is optional, and multiple arguments can be given.  Watch the output carefully for fatal compile or link errors.
 +
 
 +
 
 +
 
 +
== Notes ==
 +
 
 +
* uvflag:
 +
    uvwide vis=$VIS narrow=t
 +
fixes the narrow band flags this
 +
 
 +
* puthd/uvcal: manually need to put freqatm in the dataset (phaseatm needs it in uvcal). Ideally selfcal would write the freq0 variable.
 +
 
 +
== Issues ==
 +
 
 +
* SZA data:
 +
  * antpos(3,nants) is not written correctly, this will impact gpbuddy's automatic nearest neighbor search

Revision as of 09:42, 5 December 2008

PACS notes for MIRIAD:

Peter will normally update the OVRO and CARMA machines, as well as the 32 bit version ('astroload miriad') and 64 bit version ('astroload -v 64 miriad') on the UMD machines. For anybody else, check the procedure below if that is what you do:

Contents

New/modified software

  • gpbuddy: writes out (unwrapped) phaseatm from a gain solution (that came from selfcal)
  • uvcal: has new options=atmcal to apply the atmphase to a dataset. Make sure you have a good freqatm value in your dataset (for now)
  • uvwide: SZA data do not have narrow flags, this program was updated for this.
     uvwide vis=$VIS narrow=t

to fix this

  • panda: baseline based (not in miriad yet)
  • bldelay: baseline based (not in miriad yet)

Reminder on updating MIRIAD (old style)

  • MAXDIM: two header files describing maximum sizes were updated: $MIRINC/maxdim.h and $MIRINC/maxdimc.h. Edit this files and modify the MAXBUF parameter in both files to at least 10000000 (4 times the amount is the memory used by programs that use MAXBUF).
 cd $MIRINC
 edit maxdim.h  maxdimc.h

and if to properly update the CVS status of these files (they changed on Dec 4, 2008) a one time is needed to old MIRIAD installs:

 mkdir tmp
 mv maxdim.h  maxdimc.h tmp
 cvs update
 mv tmp/max*h .
  • CVS: always query your source tree and look for C (conflicts) and M (locally modified) files. The U (to be updated) files will be new ones.
 cvs -nq update

and if happy with this, issue the real update

 cvs update
  • Old style updates: (you can give these commands from any directory and it assumed you have write permission in $MIR)
 mirboss
 mir.install subs prog

for a blanket re-install of the library and programs. You need this if e.g. maxdim.h was changed, and/or your miriad does not use shared libraries. This is also the safest way to update. On most computers this will only take 2-3 minutes. If however you know exactly what the impact of a new file is, you can pick any of the following examples, which will take 2-3 seconds:

 mir.subs fitsio.for uvio

and

 mir.prog itemize gpbuddy

Notice a file extension is optional, and multiple arguments can be given. Watch the output carefully for fatal compile or link errors.


Notes

  • uvflag:
   uvwide vis=$VIS narrow=t

fixes the narrow band flags this

  • puthd/uvcal: manually need to put freqatm in the dataset (phaseatm needs it in uvcal). Ideally selfcal would write the freq0 variable.

Issues

  • SZA data:
 * antpos(3,nants) is not written correctly, this will impact gpbuddy's automatic nearest neighbor search
Personal tools