Files that can be downloaded

july, 2002


cordmp - dump a summary of an AO correlator datafile
phil's idl routines to analyz AO   data.

Intro: (top)

The following files can be downloaded via your browser. They are normally tar files with a zipped and unzipped files:
    cordmp.tar    Uncompressed version (larger)
    cordmp.tar.gz compressed version (smaller).

To get an uncompressed tar file:
  • click on the link and specify the filename to store it in. If it tries to display the file, use the right button on the link and specify the saveas option.
  • tar -xf filename    .. this will unpack the tar file into the individual files/directories
  • To get a compressed tar file:
  • click on the link, specify the file to store it in..
  • gunzip -c filename | tar -xf -
  • Executables will have listed the version of sunOS they were compiled under.  Any dynamic linking need should be from standard libraries (libc, etc..)

    cordmp - dump a summary of an AO correlator datafile   (top)

        Cordmp contains a macro (cordmp) and an executable (cordmpprg) that will scan an AO correlator file and output a summary of what is contained in the file.(see cordmp documenation)


        cordmp [-c {-f char} -d ] [corfile]


  •     -c    output a 1 line summary for each calibrate pattern (heiles cross scan) found in the file
  •     -f char    prepend each line with character char.
  •     -d    output debugging info while the file is read
  • corfile    name of file to scan. If no file is supplied then the default file hard coded in the cordmp macro is used.
  • Version:

    compiled with gcc version 2.95.3 20010315 (release). Sunos version 5.8.


     cordmp.tar  14Kb, 30jul02
     cordmp.tar.gz  5Kb, 30jul02

    idl routines to analyz AO  data  (top)

        These idl routines are used to analyze various arecibo datasets (ri, atm,cor,was,wapp,mock...)  The individual documentation for these routines is included as an html file (cordoc.html,...). It can also be found at ~phil/#idl routines.  T The routine ReadmeExport explains how to install the routines at your site. The steps you should follow are shown below.
  • click on the uncompressed or compressed version to download. Store the file aoIdl.tar in the directory you want to keep the idl routines. I'll assume you put them in /share/idl/ao.
  • If it was the uncompressed version: tar -xf aoIdl.tar

  • If is was the compressed version:  gunzip -c aoIdl.tar.gz | tar -xf -
  • In the user's  startup file for idl add:

  •    !path = expand_path('+/share/idl/ao/gen')+':'+ !path
  • You need a directory to hold the html documentation and a url. Assume you want to keep the html documentation in /home/aoidl/public_html  and the url to this will be:
  • Edit the file  /share/idl/ao/gen/
  •       change:     return,'/pkg/rsi/local/libao/phil/'
              to:     return,'/share/idl/aoidl/' 
          change:     return,'/home/phil/pubilc_html/'
              to:     return,'/home/aoidl/pubilc_html/'
          change:     return,''
              to:     return,''
    You should make sure the documentation directory exists and you have write access to it.
     --> Warning.. the filenames need the trailing /
             '/share/idl/aoidl/'  .. correct
             '/share/idl/aoidl'  .. incorrect
  • When starting idl, you need to specify where the aoidl routines are located. The easiest way is to use an idl startup file and the shell environment variable IDL_STARTUP. The file could contain:
  •    ;lines starting with ; are comments
       ;  edit_input tells idl how many lines to remember when using the
       ;  up arrow to recall/edit previous commands
       ;  the next line tells idl where to find the aodefdir routine
       ;  that is then used to define all of the paths...
       !path = expand_path('+/share/idl/ao/gen')+':'+ !path
       ;  This is just some extra junk i use for plotting
    IDL will look in the environment variable IDL_STARTUP to see if you have defined a startup file.
    A csh example is:
      In .cshrc put
      setenv IDL_STARTUP  ~yourHomedir/startup.idl
    Then idl   will startup idl and execute the above commands.
  • The first time you start idl, you need to create the documentation.  Enter @allmkdoc   This will create the  .html files in the doc directory you specified. Be sure that you have write permissions to these directories or the command will fail.

  • ./swmodhistory.html has the modification history for the routines. Every time I find a bug or add something,i'll put an entry in this table. Move this to an html directory and add a link to it.
  • aoIdl.tar       9 Mbytes (uncompressed) last updated  11feb15
    aoIdl.tar.gz   3 Mbytes (compressed) last updated 11feb15

    For those who have already downloaded the software, checkout the  software modification history to see if there is anything new or fixed that you may want (note:27sep12.. i haven't been very religious in maintaining this web page since i moved the idl routines to svn).  You need to also check that the last updated date for the tar files includes anything new you may want (i try to remember to update the tar files but sometimes i'm a few days behind).