VMBICAL-AIR Operator Instructions: Processing a Siteday for the Instrument Team

NOTE: This assumes that the latest version of VMBICAL-AIR has been installed on a local machine for the operator to use. If VMBICAL-AIR has not been installed please see the installation instructions and do so.

  1. It is necessary to create a resource file that is sourced for paths to input and output files and directories. To create this file, copy the vmbicalrc file in /vmbical_air/templates/Startup to the operator's home directory.
      > cd vmbical_air/templates/Startup
      > cp vmbicalrc $HOME
      > cd $HOME
      > mv vmbicalrc .vmbicalrc

    Note: Once the file has been renamed to .vmbicalrc it will not be visible when a simple ls command is used. To see .files a ls -a is necessary.

  2. Parameters in the .vmbicalrc will need to be edited.
    • edit parm_path to the path of the vmbical_air/params directory
    • edit copy_path to the path of the field.tape.copies directory
    • edit cal_path to the path of the averaged calibration images needed for processing
    • edit ftr_path to the path of the VSN directories containing the raw data
    • edit disk_path to the directories to which the calibrated data will be copied after the output tape has been written
    • edit dsds_path to the path of the directory that holds or to be created to hold the toc and lbl files to be written to the calibrated data (output) tape
    • edit COPIPE_path to the directory to which the calibrated and compressed velocity images will be sent for COPIPE processing
    • edit tapehost to the machine name that tapes will be read from or written to
    • edit tpdrive_in to the tape drive that will be used to write the final tape
    • edit vmbical_soft to the path of the vmbical_air directory
    • edit iraf_home to the path of the vmbical_iraf directory
    • edit VGRASPBIN to the path to the local installation of GRASP executables
    • edit VIRAFBIN to the path to the local installation of IRAF executables

    NOTE: For Operator's not running in production mode it is not necessary to have the COPIPE_path, infact it can be commented out by placing a pound sign in front of it (#COPIPE_path).

  3. Create a control directory in a desired location for data to be processed on. Typically a control directory is named wa0.ssyymmdd where ss indicates the GONG site and yymmdd represents the first date of the data being processed.

  4. It is necessary to copy the run_vmbical_inst and parameter_inst.rc files to the created control directory from the /vmbical_air/templates/Startup directory. It is not necessary to edit the run_vmbical_inst file, but the parameter_inst.rc file will need to be edited. The parameter_inst.rc should be renamed to SSinstparyymmdd.rc where SS indicates the GONG site and yymmdd represents the first date of the data being processed.

  5. The following parameters will need to be edited in the parameter_inst.rc for processing:
    • edit SITE to the two-letter upper case site designation for the data being processed
    • edit wa1 to the directory path where the initial and intermediate (stz, raw, vmbi and geom) directories for each siteday will be created
    • edit wa2 to the directory path where the output (int, mag, mod, vel and vel.gz) directories for each siteday will be created
    • edit wa3 to the directory path where the DNSpipe results will be created
    • edit VSN_ins to the VSN numbers of the raw data tapes to be processed
    • edit VSN_ot to the VSN number that will be assigned to the calibrated data (output) tape written at the end of the processing
    • edit tpdrive_ot to the tape drive that will be used to write the final tape

    Check to make sure the run_vmbical_inst script is executable. If it is not executable, change the permissions on the file by typing

    chmod u+x run_vmbical_inst
    at the prompt.

  6. To begin processing, type run_vmbical_inst SSinstparyymmdd.rc at the prompt.

  7. Hit the Enter key at the Prepare the siteday directories prompt

      to begin setting up the directories for processing. If this step has been completed previously, enter s at the prompt to move on to the second stage of processing data. The second stage of processing data starts in step (15).

  8. Hit the Enter key at the get_site_days for VSN_in prompt
      to begin copying information for each VSN to be processed.

  9. Hit the Enter key at the Enter to process all days from VSN, or enter anything else for no prompt.

      in order to process all of the sitedays on the raw data tape. Or if the operator wishes to choose specific days to process, enter anything other than the Enter key at the prompt. The run_vmbical_inst script will then prompt the operator to hit the Enter key for each day to be processed or s to skip the processing of a specific day. This is most useful when it's obvious to the operator, judging from the instrumental profiles prepared by the FTR operator, that a given siteday is completely clouded out or that the instrument did not guide all day for any other reason.

  10. Hit the Enter key at the Edit tapedata prompt

      if the operator would like to edit the sitedays to be processed. At this point in the processing, after lists of images for each siteday are created, the operator has another opportunity to remove a day, or days, from processing. A vi editor environment is then opened and the tapedata file, which defines for the program which days to process, can be edited using vi commands. Otherwise, the operator enters s at the prompt to process the data as previously defined.

      NOTE: If a siteday has 00 listed for filenumbers that siteday should be deleted from further processing. If the operator does not remove this siteday from processing problems will arise later on in the processing.

  11. Hit the Enter key at the Use the edited file no. ranges in tapedata to copy subsets of hour_ang, phase, net_rad, guider, itime, rawlist prompt

      to create the hour_ang, phase, net_rad, guider, itime and rawlist files required by VMBICAL-AIR for the processing.

  12. Hit the Enter key at the Prepare disk directories (s to skip) prompt

      to create the necessary siteday directories for processing. The operator will then be prompted to hit the Enter key to create a set of directories for each siteday to be processed. Also at this point the operator is asked if the first day on the tape is a continuation from a previous tape, or if the last day is continued on a succeeding tape. The program makes the required files or file edits to accommodate the split day, but at this date the operator is responsible for deleting references to the split day in the VSN directory for the first tape and, at least for the time being, the operator also needs to go into an external window and cd to the hdr_parms directory of the split day's siteday directory and make a copy of the raw_list file in that directory, with the new file being named raw_list_cont.

  13. Hit the Enter key at the Transfer calibration correction images prompt

      to copy them into the control directories for all sitedays to be processed. This is the last step in prepping the data for processing.

  14. Steps 4 - 8 will be repeated for each raw data tape entered on the VSN_ins line of the parameter_inst.rc file.

  15. The second part of the VMBICAL-AIR processing is the staging and calibrating of the siteday data. Using the run_vmbical_inst script, all AIR modules will be skipped. Therefore processing with run_vmbical_inst is the equivalent of processing a siteday through the pre-AIR version of VMBICAL. To begin, hit the Enter key at the Stage all and then process all sitedays prompt.

  16. Hit the Enter key at the Copy All Files from ftr_path and run UNRICE from VSNs prompt

      to create symlinks to the location of the online data to the siteday stz directories and then to be efficient with processing time, in this version of VMBICAL-AIR all of the sitedays are first decompressed using UNRICE.

  17. Hit the 'Enter key at the Begin calibration on staged sitedays from VSNs prompt

      to start the calibration process. One press of the Enter key is all that's needed to process the data of all VSNs listed in the parameter_inst.rc file. At the completion of processing each siteday a geometry plot will be printed to the operator's default printer and will look like this. This plot should be included in the package of plots given to the instrument team.

  18. Hit the Enter key at the QA the sitedays and Open an iraf window to run getqa prompts

      and an xgterm window will open with IRAF already started to begin the QA portion of the processing. To load the VMBICAL scripts type

      at the prompt. Click here to see a screen shot of what the IRAF window should look like with the VMBICAL scripts loaded.

    Change directories to the control directory created for the data set in step (1).

    Type getqa at the prompt to begin the QA.

      The getqa script then prompts the operator to enter the path to the vmbical_air directory, the upper case site code, the VSN number and the printer to which to send send any plots.

    Then for each siteday getqa will prompt process the qa plot files.

      If the siteday is to be processed, type either y at the prompt or hit the Enter key.

    To print a copy of the good images plot, hit the Enter key at the prompt or type s to skip the plotting. To print a copy of the all images plot hit the Enter key at the prompt of type s to skip the plotting. In general, the operator will skip the plotting at this point until the QA plot has been examined, as discussed below.

    An IMAGE FLAGGING MENU will then be displayed in the IRAF window.

      At this point in the processing, the operator may begin flagging bad images. However, the instrument team is interested in as many images as possible so be weary of flagging too many images as bad.

    At the enter l, ln, r, pg, pgp, pa, pap, x, quit prompt, type in pg and hit the Enter key to check the QA plots onscreen. The velocity plot line can be more easily seen by also taking a look at the pgv plot option.

      Assuming all looks fine, just type x in the menu and the Enter key to print the edited good image plot to keep for the files.

    On the other hand, if the plots, especially the pgv plot, show a wayward point or two, type in l and hit the Enter key in the Flagging Menu. Enter the approximate wayward image time, to get the stats for the 15 images around the suspect minute(s). In this way the operator can pinpoint the images requiring flagging and enter the errant image with the f (flag) option in the Menu, or a range of images with the r option, before executing the x option. The operator can then re-check the pg or pgv plots onscreen before the final x Menu option which ends the flag process and produces the edited hardcopy plot before moving on to the next siteday for that VSN.

    The getqa script will need to be run individually for each VSN being processed in this job. After getqa has been run on all of the VSN's type

    at the prompt to close the IRAF window. A copy of the QA plots should also be provided in the package of plots to the instrument team.

  19. Hit the Enter key at the Split the images and Split the images from VSN_inprompts

      for the calibrated images to be split into the vzi, bzi, izi and mzi data products.

    The operator will need to hit the Enter key at each Split the images from VSN_in prompt or just type ahead by hitting another Enter for all tapes being processed in the job.

  20. Hit the Enter key at the Create lnu diagrams for processed sitedays prompt

      for DNSPIPE to be run on the processed siteday.

  21. VMBICAL and DNSPIPE are new finished processing the siteday. Change directories to the wa3 and print out lnu's to be provided to the instrument team.

  22. All plots (geomplot, QA plots and lnu's) should be given to the instrument team and an email should be sent indicating where the finished data may be found.

Documentation Main Page | FITS Header Parameter Descriptions | IRAF GRASP Help Pages

Revision: $Id$