1. The DA will tell you when your data is ready through a comment on the SCOPS data reduction ticket of the project
  2. Have look at the project in the OT (from the archive), to familiarize yourself with the science goal (SG), as well as the SG requested rms noise and resolution
  3. Determine if there are issues with the data, and particular issues that have not well been (or cannot be) taken care of by the pipeline calibration
    1. review the weblog in the qa directory following the instructions on NAWebLogReview .
    2. Have a quick sanity check at the calibrated visibilities in the calibrated directory using plotms.
  4. Report to the DRM on the data reduction SCOPS whether you saw something worrisome in your review. In particular If you think that a fraction of the calibrated data is obviously bad, and that an additional antenna or spw or scan needs to be flagged, a re-processing of the data may be performed.
  5. In the calibrated directory, download the template scripts from https://staff.nrao.edu/wiki/bin/view/NAASC/NAImagingScripts (until the 12/10/2015 update, the scripts are actually here: https://github.com/aakepley/ALMAImagingScript/tree/split_into_two). The imaging process is composed of two main steps: data preparation and imaging the emission, each of which has its own script. The scripts will be renamed in a later step.
  6. If necessary, include additional data flagging in scriptForImagingPrep.py
  7. Choose the apporpriate CASA version. Currently either CASA 4.2.2 or 4.3.1 are being used for pipeline calibration. Check in the weblog which version was used, and launch CASA by typing either casa - r 4.2.2 or casa -r 4.3.1-el6 on the command prompt
  8. Edit the imaging script as needed and run the tasks
  9. At the end of your imaging process, you should have produced .fits files that are relevant to the scientific goals, and that reach (when possible) the SG requested spatial and spectral resolution and sensitivity. Note that, for a 7m dataset, the requested rms and resolution do not directly apply to the 7-m-only dataset, since those requests are intended for the 12m + 7m dataset. This is also valid for _TC MOUS in multi-arrays SGs.
  10. Run the strip_instructions python script to remove the instructions for the data imager from the imaging and imaging prep scripts and copy the remaining lines to scripts for delivery to the PI. The instructions for the imager are designated by "#>>>".
  11. Move back up to one directory, copy the README file template (cp /users/thunter/AIV/science/qa2/README.header.cycle2.txt ./README.header.txt for Cycle 1 and 2, cp /users/thunter/AIV/science/qa2/README.header.cycle3.txt ./README.header.txt for Cycle 3), fill in the fields and add comments on the data reduction, Please state clearly that the pipeline was used for calibration
  12. Give the path to your images on the data reduction SCOPS ticket, and copy the README ticket there
  13. The DRM may ask you to change some formatting, add some images, edit the scripts...
  14. When the data are delivered, follow the "Final cleanup" procedures listed on the Cycle1and2ImagingReduction main page, move the entire directory package to /lustre/naasc/sciops/deliveries. If the data are QA2_FAIL move it to /lustre/naasc/sciops/qa2fails

-- ArielleMoullet - 2015-02-04

Topic revision: r14 - 2016-06-28, AndrewMcNichols
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback