QA2 Report Project information Name Pattern Speed in the Double-Barred Galaxy: NGC 3504 Code 2016.1.00650.S PI Yu-Ting Wu Organization Institute of Astronomy and Astrophysics, Academia Sinica Co-Is P. Hsieh, I. Jiang, K. Sakamoto, R. Taam, A. Trejo ObsUnitSet information Name Member OUS (NGC3504) QA2 Status Pass Member OUS Status ID uid://A001/X87a/X70a SchedBlock name NGC3504_a_06_7M SchedBlock UID uid://A001/X87a/X702 Array 7M Mode Standard Band ALMA_RB_06 Repr.Freq. (sky) 229.37 [GHz] Spectral setup ACA Sources NGC3504 Other SBs in this Group OUS (Member OUS Status ID in brackets): NGC3504_a_06_TM1 (uid://A001/X87a/X706), NGC3504_a_06_TM2 (uid://A001/X87a/X708) Execution count 2.00 of 2 expected Final QA2 comment Comments from Reducer CASA version: 5.4.0-70, Pipeline:42254M (Pipeline-CASA54-P1-B) Reduction mode: PL calibration and imaging Calibration issues: None. Imaging issues: This SB has been reprocessed with CASA 5.4.0 due to the issues in previous versions of CASA described at the following links: See the "Imaging" section at: https://casa.nrao.edu/casadocs/casa-5.4.0 <https://casa.nrao.edu/casadocs/casa-5.4.0> General info: The continuum in each spectral window was identified and subtracted by the pipeline before cube imaging. It is recommended that the PI carefully assess the results on the hif_findcont weblog page, and in the "line-free moment 0" images on the cube imaging weblog page. Self-calibration was not performed. This is a line project, thus QA2 was performed on the Aggregate Continuum and the PI specified representative spectral window. Both the beam size and the RMS meet the PI requested performance parameters. Therefore, this scheduling block has been deemed a QA2 PASS. Aggregate Continuum 16,18,20,22 Image name: uid___A001_X87a_X70a.NGC3504_sci.spw16_18_20_22.cont.I.pbcor.fits Robust = 0.5 Beam size = 5.92"x5.53",61.2deg RMS = 0.170 mJy/beam over 6.2184 GHz Representative Window 16 Image name: uid___A001_X87a_X70a.NGC3504_sci.spw16.cube.I.pbcor.fits Robust = 0.5 Beam size = 6.34"x5.79",66.4deg RMS = 4.651 mJy/beam over 3.906 MHz For additional information on the calibration and imaging pipeline products please see the Knowledgebase article: https://help.almascience.org/index.php?/Knowledgebase/Article/View/375/ RMS and beam size at representative frequency Sensitivity goal 9.286 [mJy] over bandwidth 3.904 [MHz] Angular resolution goal N/A Achieved RMS for desired bandwidth 4.651 [mJy] for continuum N/A Synthesized beam Mean (arcsec) 6.059 Major axis (arcsec) 6.340 Minor axis (arcsec) 5.790 Position angle (deg) 66.400 Execution blocks summary EB N Ant. Start Time End Time ToS (sec) Avg. Elev. (deg) Trans. Elev. Mean PWV (mm) Phase RMS (deg)* Min BL (m) Max BL (m) AR (") MRS (") EF uid://A002/Xba839d/X4bca 12 2016-11-12 10:23: 2016-11-12 11:57: 5629 37.4 39.0 0.0 10.754 8.9 48.9 4.9 28.8 1.00 uid://A002/Xbabd27/X4714 11 2016-11-17 11:21: 2016-11-17 13:06: 6296 38.0 39.0 0.0 7.504 8.9 45.0 5.0 28.8 1.00 *WVR-corrected value averaged over all basebands and scans. Pipeline executions CASA version Pipeline version Report date Processing time 5.4.0-70 42254M (Pipeline-CASA54-P1-B) 2019-03-11 17:10:13 3:20:13 Calibrator source fluxes Source name Flux (Jy) Flux error (Jy) Frequency (GHz) Intents J1058+0133 3.849 0.385 229.389 CALIBRATE_ATMOSPHERE, CALIBRATE_BANDPASS, CALIBRATE_FLUX, CALIBRATE_POINTING, CALIBRATE_WVR J1058+0133 3.886 0.389 230.755 CALIBRATE_ATMOSPHERE, CALIBRATE_BANDPASS, CALIBRATE_FLUX, CALIBRATE_POINTING, CALIBRATE_WVR J1058+0133 3.736 0.374 243.713 CALIBRATE_ATMOSPHERE, CALIBRATE_BANDPASS, CALIBRATE_FLUX, CALIBRATE_POINTING, CALIBRATE_WVR J1058+0133 3.721 0.372 245.588 CALIBRATE_ATMOSPHERE, CALIBRATE_BANDPASS, CALIBRATE_FLUX, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 1.052 0.105 229.389 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 1.061 0.106 230.755 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 1.024 0.102 243.713 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 1.019 0.102 245.588 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 0.981 0.098 229.388 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 0.977 0.098 230.755 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 0.952 0.095 243.713 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR J1159+2914 0.942 0.094 245.588 CALIBRATE_ATMOSPHERE, CALIBRATE_PHASE, CALIBRATE_POINTING, CALIBRATE_WVR Spectral Windows Transition Central Frequency (sky, GHz) Bandwidth (GHz) N of channels CO_v_0_2_1 (SW-1) 229.367 2.000 512 H__30___ (SW-1) 230.733 2.000 512 CS_v_0_5_4 (SW-1) 243.691 2.000 512 Continuum (SW-1) 245.566 2.000 128 Instructions INTERFEROMETRY INSTRUCTIONS OVERVIEW Introduction Data Delivery Contents Interferometric Calibration and Imaging Regeneration How to Restore the Calibrated Measurement Set for Your Data Primary Beam Correction ##### INTRODUCTION ------------ ALMA currently provides data products for each member observation unit set (MOUS), corresponding to one or more executions of a single scheduling block (SB).  In all cases except for polarization projects, each execution is independently calibrated, and then all executions are imaged together. The following text describes the contents of this data package. Further details and updates can be found in the ALMA Knowledge Base (KB) articles indicated throughout this document. ##### DATA DELIVERY CONTENTS ---------------------- Each data package tarball expands to contain a single member.<ous_id> directory with the following sub-directories: calibration, script, qa, log, product. (Note: The ALMA archive will have prepended many product and script names with the MOUS UID, compared to the names displayed in the pipeline's weblog.) - 'qa/' contains a number of files that summarize the quality of the observations and products.  There is a "QA0 report" for each execution giving an overview of the conditions (Tsys, phase RMS) and quality of each observation. The "QA2 report" (this file) provides an overall assessment of the complete observation and final products. For pipeline-processed data there is a member.<ous_id>.*.weblog.tgz file for each time the pipeline was run (calibration, imaging, or calibration+imaging) that unpacks into "weblog" (open the pipeline-<DATE>/html/index.html file in a web browser), which is a series of webpages that present the details of the pipeline run, many diagnostic plots, and quality metrics.  For manually calibrated products, several text files and png images are provided instead, which can be used in conjunction with the *scriptForCalibration.py described below to understand how the data were calibrated. - 'product/' contains fits files of the imaging products. In some cases, only a subset of all science targets/spectral windows are imaged,  to demonstrate the quality of the calibration and images. If the products were created by the imaging pipeline, a detailed comprehensive explanation of what images were created, how continuum was subtracted, and the quality of the processing is contained in the pipeline weblog (see above). If images were created manually, please refer to the *scriptForImaging.py described below for details of the process. - 'script/' contains the scripts to:   - calibrate raw visibilities (*casa_pipescript.py in the case of pipeline calibration, and *scriptForCalibration.py in the case of manual calibration).   - restore calibrated visibilities without fully rerunning the pipeline (*casa_piperestorescript.py)   - restore calibrated visibilities ("*scriptForPI.py";  works for either pipeline or manually calibrated data - see the section "How to restore the calibrated Measurement Set (MS) for your data" further below).  - create images (*casa_pipescript.py in the case of pipeline imaging, and *scriptForImagingPrep.py and *scriptForImaging.py in the case of manual imaging).   - In case the calibration was done by the automated pipeline, you will also see the Pipeline Processing Request file (PPR). (Note: the ALMA archive may prepend the script names with the MOUS UID.) - 'calibration/' contains the files needed for calibration, including calibration and flagging tables and manually introduced flagging commands, which allow the user to start from the initial ASDM files and obtain the fully calibrated data. - 'log' contains the CASA log files. For more information see the ALMA QA2 Data Products document (https://almascience.org/processing/qa2-data-products), the ALMA Technical Handbook (in particular chapter 11 on the QA2 pass criteria), and the relevant Call for Proposals for this Cycle, which are available for download from the ALMA Science Portal at https://almascience.org/documents-and-tools. ##### INTERFEROMETRIC CALIBRATION AND IMAGING REGENERATION ---------------------------------------------------- This section concerns ALMA interferometric (12m Array and ACA) data. The ALMA KB article "How to Restore the Calibrated Measurement Set (MS) for your Data" at https://help.almascience.org/index.php?/Knowledgebase/Article/View/399 will contain an up-to-date version of the procedures described below. How to Restore the Calibrated Measurement Set (MS) for your Data --------------------------------------------------------------- Calibration is the first step of processing interferometric data. Many users will want to recreate the calibrated measurement set and then perform the second step (imaging) using their own scripts, or by modifying the imaging script provided with the data. In order to obtain your calibrated data, download the raw data in ASDM format from the science archive. If you downloaded and untarred all available files for this delivery as described in the notification email, then you will already see these files (with names like "uid*.asdm.sdm") in an additional sub- directory called "raw". Otherwise, you will need to download and untar the tar balls of the raw data in the same directory that you untarred the tarball of the products, creating the "raw" sub-directory and associated ASDM files. For the next step, you will need the right version of CASA to be installed. Please find the line starting with "CASA version used for reduction:" in your QA2 report or README. The version indicated there is what you need to use for running the scriptForPI. Once the raw data is in place, cd to the "script" sub-directory, start CASA: casa --pipeline (Note: For some versions, CASA is released without pipeline and the "--pipeline" switch is not available. You will need a version with the pipeline if there is a file named "PPR*.xml" or "*pprequest.xml" in your script/ sub-directory. If there is no such file, you will not be able to run the the pipeline or restore pipeline-calibrated data. For more information on the execution of the pipeline, please refer to the ALMA Science Pipeline User's Guide available at https://almascience.org/documents-and-tools/pipeline-documentation-archive). Then look for the script ending in "scriptForPI.py" and execute it, e.g.: execfile("member.uid___A001_X123a_X45.scriptForPI.py") Running the scriptForPI will result in one or more calibrated measurement sets (MSs) ready for imaging. You can use the uid_*.ms directly, keeping in mind that the calibrated data is stored in the CORRECTED data column, and all sources (including calibrators) are in the MS. If you want to run the imaging pipeline, you should run it from this point, without changing the uid_*.ms. Imaging ------- If the data were imaged with the pipeline, many details of what images were created, how and why, are contained in the pipeline weblog.  Each "task" of the pipeline weblog corresponds to a pipeline "hif_" or "hifa_" task which the user can run manually to reproduce what the pipeline did, optionally changing parameters.  The full sequence of such tasks run by the pipeline are contained in "script/*casa_pipescript.py", which could be run to completely reproduce all pipeline processing. Alternatively, the calibrated measurement set produced above can be used as the basis for running only the imaging tasks in the pipeline. See https://casaguides.nrao.edu/index.php/ALMA_Imaging_Pipeline_Reprocessing for details. Each imaging section of the weblog also links to the CASA commands that were used by the pipeline ��� these form a good initial template which users can modify to manually image the data with different parameters. If the data were manually imaged, refer to "script/*scriptForImaging.py", which contains the CASA commands that were used to create the image products from the calibrated MS. The "*scriptForImaging.py" may partially be interactive (for masking) and should be executed by copy and paste. Options ------- 1) If you want to force scriptForPI.py to split out the science spectral windows, you need to set the variable DOSPLIT=True before starting the scriptForPI in CASA. 2) The scriptForPI will usually run *casa_piperestorescript.py, which applies the calibration and flagging tables from the calibration/ sub-directory to the raw MS, restoring a calibrated MS. If *casa_piperestorescript.py is not available (as is the case for manually-calibrated datasets), the scriptForPI will instead run the entire calibration script, re-creating the calibration and flagging tables. You can force the execution of *casa_pipescript.py to rerun the entire calibration pipeline (instead of only restoring the existing calibration) by moving *casa_piperestorescript.py out of the script directory. Rerunning the calibration can be useful if you want to tweak its parameters. Otherwise the restore is faster. 3) The scriptForPI offers some global variables for your convenience. You can find an explanation in this Knowledgebase Article: https://help.almascience.org/index.php?/Knowledgebase/Article/View/380/ ##### PRIMARY BEAM CORRECTION ----------------------- The images included in delivery are corrected for the primary beam (PB) response, i.e. the dependence of the instrument's sensitivity on direction within the field of view. For each image, two files are being delivered:   a) the PB-corrected image (file name ending in ".pbcor.fits")   b) the image of the PB which was used in the correction (ending in ".pb.fits" or ".flux.fits", typically gzipped in which case you need        to unzip the file before using it) The image noise was measured in the uncorrected image. The corrected image (a) was then obtained by dividing the uncorrected image by the PB image (b).  The uncorrected image can be recovered using the CASA task impbcor in mode "m": impbcor(imagename='image.pbcor.fits', pbimage='image.pb.fits', mode='m', outfile='image.recovered') See also the ALMA KB article "Where is the Primary Beam Correction Information in my Delivered Data" at https://help.almascience.org/index.php?/Knowledgebase/Article/View/398 for any updates to this procedure. ##### Page 1 of  1