==== UHDAS nb pings ================  



    (for example, no frills)

    To process raw data (assuming 300-second ensembles)
    (0) setup:
        (a) The raw/ and gbin/ files must exist.  see the web 
            documentation for details
        (b) A config directory must exist with files properly configured.
            This example is a short version of the demo in the web 
            documentation, and assumes an overall working directory with 
            config/ subdirectory and processing directories for each 
            instrument type.  Here is the  OS38nb example:

    (1) make processing directory:


    adcptree.py  os38nb  --datatype uhdas --configbase km0507 --configpath config


    (2) run quick_adcp.py (batchmode)

    quick_adcp.py --cntfile q_py.cnt


    #### begin q_py.cnt
    ## all lines after the first "#" sign are ignored
      --yearbase    2005
      --pingtype    nb                ## this is different for os38nb
      --cfgbase     kok0517
      --cruisename  kok0517
      --instclass   nb
      --instname    nb150
      --dbname      a_kk
      --datatype    uhdas
      --datadir     /home/jules/kok0517/data/raw/nb150
      --cfgpath     config
      --ens_len     300
      --use_refsm            ## optional command.  this is now the default.
      --ping_headcorr        ## (or post_headcorr) for heading correction

      --hcorr_inst  ashtech  ## ping_headcorr: this line overrides whatver 
                             ##     was in the config directory *_cfg.m
                             ## post_headcorr: must have this here; 
                             ##     whatver was in the config directory 
                             ##     *_cfg.m is irrelevant for post_headcorr

                             ## It is not a bad idea to put the command
                             ##     in here anyway, since it is a more
                             ##     obvious place to look, and makes 
                             ##     debugging and documentation easier
    ## end of q_py.cnt


      rotate, edit as usual.
      See web documentation for notes on heading correction