1 Support of the Taiwanese astronomical community is shared by the EA and NA ARCs.

 

4 Proposal types

Footnotes:

2 Note that the 5% of time allocated to VLBI Proposals is included in the 20% of the time allocated to non-standard modes (Section 5.2).

1 During southern summer, the high-pressure system over the Pacific Ocean weakens and moves southwards, allowing warm humid air from the Amazons to flow over the Andes into northern Chile, causing rain and occasionally snow to fall on the usually dry Altiplano: this phenomenon is known as Altiplanic winter.

5.3.3 Angular resolution

In Cycle 5, PIs will be allowed to enter a range of angular resolutions for a given SG in the OT. The range should be justified in the proposal and be scientifically meaningful (Section 6.2). In practice, if the PIs enter their sensitivity request in flux density units (e.g. Jy), the OT will assign to a given SG any number of configurations that fulfil the angular resolution range requested by the PI taking into account the observing efficiency. If the execution of a SG is time wise significantly more efficient in a subset of the allowed configurations, only that subset will be considered. This choice is reflected in the OT, which will only display the configurations that the Observatory will consider for scheduling the SG.

PIs aiming to obtain high quality images of complicated structures may enter their sensitivity request in temperature units. The time estimate in these cases will correspond to the time needed to achieve the surface brightness requested in the finest angular resolution specified. This should not prevent PIs from entering a range of angular resolutions, as it is expected that a relatively small range of angular resolutions will be scientifically meaningful for these programmes.

Users are referred to the OT documentation for an extensive description of this new feature.

 

5.3.4 Configuration schedule for the 12-m Array

During Cycle 5, it is anticipated that the 12-m Array will be reconfigured about fourteen times. At the end of each of these reconfigurations, the Array is expected to have imaging properties similar to one of the ten “representative” configurations that are used to characterize the advertised Cycle 5 imaging capabilities and estimate the observing times (denoted as C43-x, with x=1 for the most compact configuration and x=10 for the most extended; see Section A.2 and Chapter 7 of the Technical Handbook for details). The planned 12-m Array configuration schedule for Cycle 5 is given in Table 2 below. On average, there will be a new configuration every 3 weeks. As mentioned in Section 5.3.2, observations will not be scheduled in February due to the bad weather conditions during the Altiplanic winter.

The first column of Table 2 gives the planned dates for the midpoint of each configuration. Modifications to these dates may be impacted by weather conditions, particularly during wintertime. The overall schedule may also be modified depending on the results of the proposal review process and the proposal pressure in the different configurations. The second column gives the 12-m Array configuration, and the third column lists the longest baseline for the configuration (see Table A-1). The fourth column lists the LST ranges when the observing conditions are most stable, which is approximately two hours after sunset to 4 hours after sunrise. The effective observing time available per configuration for executing PI projects (excluding time spent on observatory calibration, maintenance, reconfigurations, and other activities – see Section 5.3) is shown in Figure 4.

 

Table 2: Planned 12-m Array Configuration Schedule for Cycle 5

Start date	Configuration	Longest baseline1	LST for best observing conditions
2017 October 1	C43-7	3.6 km	~ 21h – 10h
2017 October 5	C43-8	8.5 km	~ 22h – 11h
2017 October 25	C43-9	13.9 km	~ 23h – 12h
2017 November 10	C43-10	16.2 km	~ 1h – 13h
2017 December 1-18	No observations due to large antenna reconfiguration
2017 December 19	C43-6	2.5 km	~ 4h – 15h
2018 January 10	C43-5	1.4 km	~5h – 17h
2018 February 1-28	No observations due to February shutdown
2018 March 1	C43-4	0.78 km	~ 8h – 21h
2018 March 30	C43-3	0.50 km	~ 10h – 0h
2018 May 15	C43-2	0.31 km	~ 12h – 3h
2018 June 15	C43-1	0.16 km	~ 14h – 5h
2018 July 15	C43-2	0.31 km	~ 17h – 7h
2018 August 15	C43-3	0.50 km	~ 18h – 8h
2018 August 30	C43-4	0.78 km	~ 19h – 9h
2018 September 15	C43-5	1.4 km	~ 20h – 10h

 

Notes for Table 2:

1. Configuration properties are given in Section A.2.

Given the anticipated configuration schedule and taking into account the weather constraints, the following considerations apply:

1. Band 9 and 10 observations will not be scheduled outside the LST ranges given in the fourth column of Table 2. The amount of time with stable atmospheric conditions suitable for Bands 7 and 8 observations outside of those LST ranges will be limited (see Figures 2 and 3), but such proposals are permitted.

2. High frequency projects (Bands 7, 8, 9, and 10) and Band 5 observations near the atmospheric absorption feature at 183 GHz are not recommended around the Altiplanic winter (especially December-February) at any LST.

3. Projects that have imaging requirements (constraining the necessary configuration) and time constraints that do not coincide cannot be scheduled.

The compact configurations for Cycle 5 will occur during the 2018 austral winter (June – August), when longer periods suitable for high frequency observing are expected. In Cycle 6 the array configuration schedule will likely complement this plan, such that extended configurations will be scheduled for the 2019 austral winter.

Figure 4. Effective observing time available per configuration for executing PI projects. As an example, up to 10 hours may be allocated to Large Programmes in configuration C43-1 at LST = 0 h. The total number of hours excludes time spent on observatory calibration, maintenance, reconfigurations, and other activities. The fraction of that time available for Large Programmes and high frequency observations is also indicated. The configuration schedule and, consequently, the total number of hours available per configuration may change as a result of proposal pressure (see text). The data files containing these histograms are available here.

 

5.3.5 Observing pressure as a function of Right Ascension

Figure 5 shows the Right Ascension (RA) distribution of Cycle 4 requested proposals, colour-coded by requested array. The highest demand for observations is in the 2-6 h and 12-19 h RA ranges, with low demand in the 7-9 h and 22-1 h RA ranges. Earlier cycles had similar distributions. Proposals in less subscribed RA ranges will have a higher probability of execution.

From Cycle 5 on, the range of angular resolutions provided by PIs (Section 5.3.3) will have a direct impact in the observing pressure per configuration. Proposals that specify a broad range of acceptable angular resolutions (i.e., several acceptable configurations) will increase the likelihood that the proposal can be
scheduled and executed. However, PIs should only request the range of angular resolutions that is acceptable for their science goals, as this will be evaluated during the proposal review process.

In addition, the observing pressure per configuration, estimated via simulations of the full cycle taking into account the APRC ranks and historical weather patterns, may change during the building of the observing queue (Section 6.5.3) by adjusting the configuration schedule (Section 5.3.4).

 Figure 5: Distribution of requested 12-m Array time for the Cycle 4 proposals as a function of Right Ascension and colour-coded by array.

5.4 Duplicate observations and resubmissions

5.4.1 Checking for duplications

To ensure the most efficient use of ALMA, duplicate observations of the same location on the sky with similar observing parameters (frequency, angular resolution, coverage, and sensitivity) are not permitted unless scientifically justified. Archival data should be used whenever possible to accomplish the science goals of a proposed investigation. Observations are considered duplicates if the conditions indicated in Appendix A of the Users’ Policies are met.

Proposers are responsible for checking their proposed observations against the Archive and the list of Cycle 4 accepted programmes provided by the ALMA to avoid duplicate observations. Proposers will not be penalized for proposing duplications of previous cycle observations if they had no way to know about them by the release of the Call for Proposals. See the Duplications link on the Science Portal for information on checking for duplications.

The proposal cover sheet contains a section where PIs can justify proposed duplicate observations. PIs are also advised to justify their proposed observations in cases where they are similar to previously executed or accepted programmes but are not formal duplicates. The ALMA Review Panels (ARPs) will determine if the requested duplicate observation is scientifically justified.

5.4.2 Resubmission of an unfinished proposal

Proposal teams that submit a Cycle 5 proposal to observe some or all SGs of a currently active but unfinished project will have the relevant SGs identified as a “resubmission” by ALMA. A SG is deemed a “resubmission” if it constitutes a duplication of an active SG following the rules specified in Appendix A of the Users’ Policies and the PI of the relevant Cycle 4 project is listed as a PI, co-PI or co-I of the corresponding Cycle 5 proposal or the Cycle 5 PI is listed as an investigator on the Cycle 4 proposal.

For such resubmissions, the relevant portion of the Cycle 5 proposal will be cancelled if the observations are successfully completed in Cycle 4. Observations started in a previous cycle and accepted as a resubmission in Cycle 5 will continue to be observed with the setup of the previous cycle even if the setup has “slightly changed”⁴ in the current cycle.

A scientific justification must be provided if the proposers request one or more additional epochs of observations in Cycle 5 even if the Cycle 4 observations are completed. The ALMA Proposal Review Committee (APRC) will decide if such resubmissions are accepted.

5.5 Estimated observing time

Proposal requests are cast in terms of SGs, each specifying a desired sensitivity, range of angular resolutions, and LAS to be obtained for a set of sources and a given spectral setup. These are used to estimate a total observing time to reach the SGs (except for Solar or VLBI observations or when overridden by the PI - see Appendix B). This observing time is the sum of the required time-on-source for all science targets, time for all calibrations including overheads, and the time for any additional array configurations needed to meet the specified LAS. The estimated observing time for the proposal is the sum of the times for all SGs. The actual observing time to reach a given sensitivity, resolution and LAS will depend on the prevailing conditions when the project is observed, the number of antennas available, and the actual array configuration.

The estimated time-on-source is calculated from the ALMA Sensitivity Calculator (ASC), available within the OT or as a stand-alone application on the Science Portal. The parameters that affect these time estimates include requested sensitivity, source declination, observing frequency, spectral bandwidth, number of antennas, angular resolution (if the sensitivity is specified in temperature units⁵) and default weather conditions. A description of the ALMA Sensitivity Calculator is given in Chapter 9 of the Technical Handbook. The time-on-source is subject to a minimum of 10 seconds per pointing, and a minimum of 5 minutes for all sources in a SG (see Section 5.3.5.3 of the OT Users Manual). If the total time-on-source(s) is more than 50 minutes, the OT determines that additional executions of the same observing commands, or SB, need to be executed. The number of required executions is based on the total time on all sources calculated by the ASC. Starting in Cycle 5, consecutive executions of a given SB (if needed) will be favoured during scheduling to maximize uv-coverage. However, if uv-coverage is fundamental for the scientific goals of a proposal, PIs should specify this request as a time constraint, and, if necessary, override the OT time estimate with the time needed to achieve such uv-coverage (see Section B.2 for details).

Each SB needs a complete set of calibrations. The calibration times and overheads are based on the number of calibrators of each type, and the default dwell times, duty cycles, and overheads, all of which are frequency and configuration dependent. These times are calculated per SB, and the total calibration time is this value times the number of SB executions needed to reach the required on-source sensitivity. Proposals requesting the suppression of some or all calibrations will be flagged as non-standard and may be deemed technically unfeasible if the request is not properly justified in the proposal (see Section A.9 for details).

The final factor in the time estimate is the time for any additional configurations needed to supplement the configurations that best match the requested range of angular resolutions to also reach the specified LAS (see Table A-1 in Section A.2). The LAS is compared to the “Maximum Recoverable Scale” (MRS) of the configurations that best match the requested range of angular resolutions (MRS are also listed in Table A-1). If the LAS exceeds the MRS of all matching configurations, then additional configurations, if allowed, are added with a time estimated using the multipliers given in Table A-2. If the array combinations are not allowed (Section A.4), the OT will give a validation error. If the LAS can be achieved with one or more of the best-matching configurations, the remaining configurations meeting the angular resolution but not the LAS request will not be considered.

The PI may include additional SGs for array combinations not allowed in a single SG, but each SG must be separately justified and have its own performance specifications (sensitivity, range of angular resolutions, and LAS). Data from each SG will be processed, assessed, and delivered independently.

Stand-alone ACA observations are selected by checking a specific box at the OT interface. When calculating the time required for ACA, the OT uses the TP Array time if this array is required (based on LAS) or otherwise the 7-m Array time; i.e., it is not the sum of the 7-m and TP Array time.

In case of simultaneous observations in the 12-m and 7-m Arrays, the estimated time for the 7-m Array will be adjusted to that of the 12-m Array.

The results of all the time estimates are reported in the OT per SG by clicking “Time Estimate” in the “Desired performance” box. The times for the 12-m Array and ACA and total time are tabulated separately on the proposal coversheet.

Footnotes

 

5.6 Supporting tools and documentation

5.6.1 The Observing Tool documentation

The ALMA OT is the proposal preparation and submission (Phase 1) software application; the OT is also used for observation preparation (Phase 2). The OT documentation suite, which provides all the basic information required to complete the proposal preparation and submission, includes:

• The OT Phase 1 Quickstart Guide: A guide to proposal preparation for the novice ALMA OT user. It provides an overview of the necessary steps to create an ALMA observing proposal.

• The OT Video Tutorials: A visual demonstration of proposal preparation and submission with the OT.

• The OT User Manual: A manual intended for all ALMA users, from novices to experienced users. It provides comprehensive information about how to create valid Phase 1 proposals and Phase 2 programmes for observing astronomical objects. It is also included as part of the “Help” documentation within the OT application itself.

• The OT Reference Manual: A manual providing a concise explanation for all the fields and menu items in the OT. It is also included as part of the “Help” documentation within the OT application itself.

• The OT trouble-shooting page: A list of the OT installation requirements and workarounds for common installation problems.

• The known OT issues page: A list of currently known bugs, their status and possible workarounds. This page may be updated during the proposal submission period and should be checked first if problems are experienced with the OT.

 

5.6.2 Proposal preparation utilities

Two tools are available to help users produce simulated images of ALMA observations of simple or user-provided science targets. A guide for simulating ALMA observations with either tool is available at http://casaguides.nrao.edu/index.php?title=Guide_To_simulating_ALMA_Data.

The first simulation tool is integrated into CASA, the offline data reduction and analysis tool for ALMA data. CASA includes the tasks “simobserve” and “simanalyze”, which generate simulated ALMA data and make images from the simulations. An additional CASA task, “simalma”, simplifies the process of combining data from multiple arrays. These CASA tools require configuration files that specify the outlay of ALMA antennas. Files for representative Cycle 5 configurations are available at the Science Portal (http://almascience.org/documents-and-tools/cycle5/alma-configuration-files). Additional information on CASA, including hardware requirements and download instructions, is available at http://casa.nrao.edu.

The second simulation tool is the ALMA Observation Support Tool (OST). The OST uses a simplified web interface to help users generate ALMA simulations. Users submit jobs to the OST and are notified by email when the simulations are completed. The OST documentation is available at http://almaost.jb.man.ac.uk/help.

Splatalogue is a database containing frequencies of atomic and molecular transitions emitting in the radio through submillimetre wavelength range. This database is #FlytheW used by the ALMA OT for spectral line selection. More information is available in the Splatalogue QuickStart Guide on the Science Portal.

The atmospheric transmission at the ALMA site can be investigated with the Atmosphere Model tool, which allows the user to model the atmospheric transmission as a function of frequency and amount of PWV. The output is a plot of the transmission fraction as a function of frequency. Up to six different water vapour levels can be selected.

 

5.6.3 The ALMA Regional Centre Guides

The ARC Guides contain user support details specific to each ALMA regional partner. They are:

• The East-Asian ARC Guide

• The European ARC Guide

• The North American ARC Guide

5.6.4 Supplemental documentation

The following documents supplement this Proposers Guide for the preparation of Cycle 5 proposals, for either the novice or advanced users. All documents can be accessed via the ALMA Science Portal (http://almascience.org/documents-and-tools).

The Proposing Guidance link from the science portal offers users succinct summaries of the successive steps involved in the preparation and submission of an ALMA observing proposal. It is designed to help users to find the relevant documents and sources of additional information in each step easily.

Observing with ALMA: A Primer is a brief introduction to ALMA observing, to submillimetre terminology, and to interferometric techniques, that should prove useful for investigators who are new to radio astronomy. Several example science projects illustrating the Cycle 5 capabilities are also provided.

The ALMA Users’ Policies document contains a complete description of the applicable users’ policies. The long-term core policies for usage of ALMA and of ALMA data by the user community are presented.

The ALMA Cycle 5 Technical Handbook describes the more technical details of ALMA during Cycle 5, including but not limited to receiver characteristics, array configurations, available observing modes and correlator setups, and the basis of the OT time estimates.

The ALMA Memo Series and ALMA Technical Notes Series include technical reports on various aspects of ALMA project development and construction and from the extension and optimization of capabilities.

 

5.7 The ALMA Helpdesk

The ALMA Helpdesk is accessed from the ALMA Science Portal or directly at http://help.almascience.org. Submitted tickets are directed to one of the ARCs, where support staff are available to answer any question related to ALMA, including but not limited to ALMA policies, capabilities, documentation, proposal preparation, the OT, Splatalogue, and CASA. Users may also request information on workshops, tutorials, or about visiting an ARC or ARC node for assistance with data reduction and analysis. Users must be registered at the ALMA Science Portal to submit a Helpdesk ticket. Replies to an already existing ticket can be sent by the user by logging into the SP or via email (for details on this new feature, see https://help.almascience.org/index.php?/Knowledgebase/Article/View/377/). ALMA staff aim to answer Helpdesk tickets within two working days.

The “Knowledgebase” of the Helpdesk is a database of answered questions or articles on all aspects of ALMA. Users can search the Knowledgebase to find answers to common queries without submitting a Helpdesk ticket. Knowledgebase articles that match their query are automatically suggested to users as they type.

 

6 Proposal preparation and submission

 

6.1 Proposal format

An ALMA proposal consists of basic proposal information that is entered directly into the ALMA OT, a Science Justification uploaded to the OT as a PDF file, and one or more Science Goals.

The OT is a Java-based application that resides and runs on the user’s computer and is used for proposal preparation and submission (“Phase 1”) and, if the proposal is awarded time, for the detailed planning of the observations (“Phase 2”).

Science Goals contain the technical details of the proposed observations and must include a Technical Justification. The OT is designed to facilitate proposal preparation and includes a number of tools and checks to ensure submitted proposals conform to the Cycle 5 capabilities.

After entering the basic proposal information and completing the Science Goals in the OT, the PI can generate the PDF of the complete proposal, including Science Justification, Science Goals and Technical Justification that will be distributed to the ALMA Proposal Review Committee for evaluation.

The following sections contain guidelines for preparing the Science and Technical Justification parts of a proposal. The setup of Science Goals is only briefly explained and users are referred to the extensive suite of OT documentation for details (Section 5.6.1). ALMA novices are encouraged to start with the OT Quickstart Guide and the video tutorials.

 

6.2 Preparing the scientific justification

ALMA Cycle 5 proposals must include a single PDF document that includes a science case written in English. The document may optionally include figures, tables and references. The maximum permitted file size is 20 MB.

6.2.1 Page limits

The total length of the PDF document is limited to 4 pages for Regular, ToO, Solar and mm-VLBI Proposals and to 6 pages for Large Programmes (A4 or US Letter format), with a font size no smaller than 12 points. The recommended breakdown is 2 pages for the science case and 2 pages for figures, tables, and references, but proposers are free to adjust these numbers within the overall page limit. Large Programmes are allotted 2 additional pages, which can be used to further present the scientific justification and describe the scheduling feasibility, data products, and management plan. It is strongly suggested that Large Programmes devote at least one page to describe the data products and management plan.

Figures and tables may be interleaved with the science case so that they appear close to the location where they are referenced in the text. Although the Technical Justification for each Science Goal is entered in the OT, any figure required for it needs to be placed in the Science Justification PDF document. Users are encouraged to use the LaTeX template developed by ALMA for preparation of their proposals (available at http://almascience.org/proposing/proposal-template).

Proposals must be self-contained. Reference can be made to published papers (including astro-ph preprints) as per standard practice in the scientific literature. Consultation of those references should not, however, be required for understanding the proposal.

6.2.2 Science case

Each proposal must describe the astronomical importance of the proposed project and include a clear statement of its immediate observing goals. Additionally, it should explain how the expected intensity of the target source(s) was estimated and justify the Signal-to-Noise (S/N) ratio and the angular resolution range required to achieve the scientific objectives of the project as well as, when appropriate, the size of the target sample. Further details may be provided in the Technical Justification (Section 6.3.2).

Proposers can simulate ALMA observations using different array components and configurations (see Section 5.6.2). Simulations are not required. However, if they are discussed in a proposal to justify any technical aspects of an observation, their results (i.e., images and simulation details) should be included in the science case and referenced in the relevant Technical Justification. Proposers should keep in mind that the fields of expertise of individual members of the ARPs span a wide range of scientific areas. Therefore, proposals should be written for an expert, but also be broad-based to satisfy a wider astronomy audience.

6.2.3 Figures, tables, and references

Figures, tables, and references that support the science case and the Technical Justification may be included. Figure captions, tables and references may use 10-point font and, together with the science case, they must fit within the overall page length and 20 MB size limit of the PDF proposal.

 

6.3 Preparing the Science Goals

6.3.1 Technical setup

The Science Goals (SGs) contain the complete observational setups: spatial coordinates and imaging characteristics, frequency band, spectral windows and spectral resolutions, sensitivity requirements and integration time for one or more science targets.

The OT Quickstart Guide and the OT User Manual provide extensive details and guidance to prepare the Science Goals and Scheduling Blocks. Experienced users who wish to understand how ALMA observations are set up are referred to Chapter 8 of the Technical Handbook.

6.3.2 Technical Justification

All proposals must contain a Technical Justification (TJ), which is entered directly into the OT in the TJ node of each SG. Any figures associated with the TJ must be included in the Science Justification PDF file and clearly referenced in the TJ. Except for the figures, the TJ must be self-contained, and there should be no expectation or requirement that the technical assessor reads the scientific justification for details. Note that while the requested sensitivity or S/N, range of angular resolutions, source size, and source sample size should be justified in the Scientific Justification (Section 6.2.2), the means by which such values will be achieved with the proposed technical setup must be included in the TJ (see Appendix B). An incomplete Technical Justification may lead to the rejection of the proposal on technical grounds.

Each SG has its own Technical Justification since the technical setup of the observations will often vary substantially from one SG to the next. If a Technical Justification is applicable to more than one SG, the TJ node can be easily copied and pasted between SGs. The TJ node contains three main sections – sensitivity, imaging, and correlator configuration - corresponding to the main aspects that need to be addressed to assess the technical feasibility of any proposal. Each section includes at least one free-format text box that must be filled (50 characters minimum), as well as a number of parameters computed from the user input captured in that Science Goal. This information is designed to help with the writing of the Technical Justification, and will also highlight potentially problematic setups (blue text) if applicable. Please see the relevant sections in the OT Reference Manual (accessible by clicking the “?” symbols within the OT) for details. If the OT detects any technical choices that require an extra justification, appropriately labelled text boxes will appear in an additional "Choices to be justified" section.

Given that the information and the text boxes displayed in the TJ node are dependent on information provided elsewhere in the SG (including the Expected Source Properties entered in the Field Setup node), the rest of the Science Goal should be set up before filling in the Technical Justification. Specific guidelines on filling out the Technical Justification are given in Appendix B. Please also see the ALMA OT video tutorial 4: “The technical justification”.

If a proposal does not conform to the advertised capabilities, it can be declared technically unfeasible either during the proposal review process or during Phase 2. The final decision will be made by the ALMA Director based on the advice from a standing committee consisting of senior staff at the JAO.

 

6.4 Proposal validation, submission and withdrawal

 Once the proposal is validated within the OT, it can be submitted to the ALMA Archive. Validation of Large Programmes could take up to 5 minutes (or longer!) if the programme contains very complicated setups or a large number (hundreds) of sources. PIs of such programmes should submit their proposals well before the deadline. A Cycle 5 proposal can be resubmitted as many times as needed by the PI before the proposal deadline, in which case the previous version is overwritten (Section 6.4.1). Submitted proposals cannot be modified after the deadline. For DDT Proposals the first submission is final.

Submission of Regular, ToO, Large and mm-VLBI Proposals will be available starting 15:00 UT on 21 March 2017 and will be accepted through the proposal deadline of 15:00 UT on 20 April 2017. No proposal submission or resubmission will be accepted after the deadline.

PIs, co-Is and co-PIs can retrieve proposals from the Archive both before and after the deadline.

If successfully submitted, a proposal receives a unique code adhering to a standard format, as follows: YYYY.C.NNNNN.X. Here, “YYYY” denotes the year when the CfP for a given cycle is issued, “C” is the cycle ID⁶, “NNNNN” is a five-digit running number and “X” denotes the proposal type (“S” for Regular Proposals, “T” for ToO, “V” for VLBI, and “L” for Large). For example, the code 2015.1.00156.S indicates a Regular Proposal, which is the 156th ALMA proposal submitted for the cycle announced in 2015. PIs who successfully submit their proposal will receive a confirmation e-mail from ALMA that includes the assigned code.

Cycle 5 DDT Proposals may be submitted anytime throughout the cycle. Like all other proposals, they must include a detailed science case and Technical Justification.

A Helpdesk ticket should be submitted if the PI needs to withdraw a proposal after a code has been assigned.

Footnotes:

6.4.1 Proposal updates

To update a previously submitted Cycle 5 proposal, users should either download the submitted proposal from the Archive and modify that copy or modify the saved, post-submission copy, for resubmission to ensure that the same submission code is used. Attempts to update a previously submitted proposal using the local copy without a code should be avoided, as this will result in a new (duplicate) submission that will be assigned a new code.

 Users wishing to re-use a proposal from the current submission period as a template for another proposal should save the original one to disk before it has been submitted. Otherwise, the second proposal will contain the original proposal’s code and will overwrite it when submitted.

 

6.5 Proposal evaluation and selection

6.5.1 Peer review

ALMA programmes in Cycle 5 will be selected through competitive peer review. The reviewers consist of scientists selected from the international astronomical community with (sub)millimetre and topical expertise as well as a broader range of backgrounds including theory, multi-wavelength observations, numerical simulations, and/or instrumentation. The reviewers are assigned to individual ALMA Review Panels (ARPs) that are specialized in a scientific category. The ALMA Proposal Review Committee (APRC) consists of the chairs of each ARP and a Chair, who is selected from the international community by the ALMA Director.

The JAO assigns each submitted proposal to a panel based primarily on the science category selected by the Principal Investigator on the proposal coversheet, but with care taken to avoid conflicts of interest with the ARP members.

The categories of review panels in Cycle 5 are:

1. Cosmology and the high redshift universe

2. Galaxies and galactic nuclei

3. Interstellar medium, star formation and astrochemistry

4. Circumstellar disks, exoplanets and the Solar system

5. Stellar evolution and the Sun

Cycle 5 proposers must further specify the area of investigation to which their project pertains by selecting in the OT at least one and at most two keywords from the list in Appendix D.

The output from each ARP consists of:

1. a ranked list of Regular, mm-VLBI and ToO Proposals based on the review criteria indicated in Section 6.5.2.

2. individual consensus reports that summarize the strengths and weaknesses of each proposal.

3. a recommendation on which Large Programmes should be forwarded to the APRC for further review.

The ranked lists from the individual ARPs are merged to produce a ranked, ordered list of proposals that is forwarded to the APRC for examination and discussion. The APRC will also review Large Programmes selected by the ARPs and will recommend which ones to schedule after taking into consideration the balance of time, science areas, overlap with on-going programmes, and technical and scheduling feasibility.

The APRC Chair will forward the ranked list of proposals and the recommended Large Programmes to the ALMA Director.

 

6.5.2 Evaluation criteria

The primary criteria to rank all proposals are the overall scientific merit of the proposed investigation and its potential contribution to the advancement of scientific knowledge. In particular, a Large Programme is expected to address strategic scientific issues.

Other factors considered to build the observing queue are listed in Section 6.5.3. For Large Programmes, given the significant investment of ALMA resources, the APRC rank will already take these and other additional factors into account as follows:

1. Technical feasibility

   1. As for all other types of proposal, a Large Programme should fully justify the requested sensitivity, the correlator setup, and the imaging requirements. The observations should be consistent with observatory best practices unless justified in the proposal.

2. Scheduling feasibility

   1. A Large Programme should be designed such that the observations can likely be completed within Cycle 5 given the antenna configuration schedule and weather constraints (see Sections 4.3 and 5.3).

3. Data products

   1. A Large Programme should describe the data products that will be produced to achieve their science goals. The programme teams will be expected to deliver these data products to the ALMA Regional Centres (ARCs) so that they can be made available to the community at large.

4. Management plan

   1. A Large Programme should present a management plan that describes a schedule of work, a description of the roles of the proposal team, and a plan to disseminate the results.

6.5.3 Proposal selection

The JAO will take the recommendations of the APRC and form an observing queue based primarily on the scientific ranking from the APRC, but taking also into account the scheduling constraints dictated by the configuration schedule and weather, the share of observing time for each region and the time available for non-standard modes.

Both ALMA and the corresponding VLBI network review and rank the VLBI Proposals independently, and both must accept a given proposal for the observations to be scheduled. The ALMA VLBI Coordinating Committee (AVCC) oversees the merging of the ALMA and VLBI network reviews.

Accepted proposals will be assigned letter grades of A, B, or C and will move forward to Phase 2 preparations (Section 7.1). Grade A proposals have the highest priority, followed by Grade B and then Grade C (see Section 5.3 for all scheduling considerations). Only Grade A are eligible to be rolled over to Cycle 6, if necessary.

Up to 33% of the nominal time specified in Section 5.1 will be assigned to Grade A proposals and 67% to Grade B proposals. The total time assigned to Grade A and B proposals will correspond to the nominal number of hours indicated in Section 5.1.

Grade C will be assigned to non-grade A and B proposals up to an additional 50% of the nominal available time, to ensure that an adequate number of projects are available for all configurations and LST in case the actual observing efficiency or weather conditions differ from expectations.

All remaining proposals will not have Phase 2 SBs generated or be considered for scheduling.

Grade assignments are subject to the following restrictions:

1. VLBI Proposals are not eligible for receiving a Grade A or Grade C.

2. In order for LPs to be accepted, they have to have received a Grade A.

3. Once the Grade A+B time cap for either the 12-m Array (4000 hr) or the ACA time (3000 hr) is reached, no more proposals requesting both 12-m Array and ACA time may receive a Grade A or B.

The shares of the observing time among the regions are:

1. 33.75% for the European Organization for Astronomical Research in the Southern Hemisphere (ESO)

2. 33.75% for the National Science Foundation of the United States (NSF)

3. 22.5% for the National Institutes of Natural Sciences of Japan (NINS)

4. 10% for the Chilean community, which is administrated jointly by the Comisión Nacional de Investigación Científica y Tecnológica (CONICYT) and the Universidad de Chile.

All regions contribute toward “Open Skies” to enable all eligible Principal Investigators to apply for ALMA time.

 

6.6 Proposal confidentiality

For proposals assigned Grade A or B, the project code, the proposal title and abstract, the name and region of the PI, as well as the names of the co-Is (and Co-PIs, in the case of Large Programmes or VLBI Proposals) will be made public soon after PIs are informed of the outcome of the proposal review process. For proposals assigned Grade C, the corresponding information will be made public as soon as its first data are archived.

Proposal metadata (for example the source positions, observation frequencies, and integration times) for Grade A, B and C proposals will be made public as soon as the first data are archived. The metadata for unaccepted proposals or unobserved proposals will remain confidential.

The scientific and technical justifications of all submitted proposals remain confidential, except for proposals for 1 mm VLBI, which will be forwarded to NRAO for review by the Event Horizon Telescope Consortium VLBI network.

 

6.7 PI notification

After the outcome of the proposal review process is approved by the ALMA Director’s Council, the results will be communicated to the PIs of submitted proposals. The notifications will include the assigned grade and a consensus report from the ALMA review panels that summarizes the strengths and weaknesses of the proposal.

 

7 Post-proposal activities

7.1 Observations preparation and submission: Phase 2

Once a project has been approved for scheduling, the project passes into Phase 2. PIs of approved projects are responsible for checking and approving the Phase 2 material (see ALMA Users’ Policies for further details). Any changes resulting from the proposal review process or necessitated by technical considerations will be implemented by the ALMA staff and reviewed by the PI for approval before the SBs are submitted to the scheduling queue. The PI may request the help of an ALMA Contact Scientist (CS) at the associated ARC or ARC node by replying to the Helpdesk ticket that will be opened on their behalf.

Necessary minor changes to the project may also be implemented at this stage as long as they do not impact the science scope or increase the total execution time. Any change that is more significant must be requested through the Helpdesk (see below).

Once PI has prepared and approved the Phase 2 material, ALMA staff will make sure the Phase 2 SBs will run at the telescope and, in case of problems will contact the CS and the PI. Otherwise, the project is approved and admitted to the ALMA observing queue to await execution at the telescope. PIs may track the status of their SBs through the Snooping Project Interface (SnooPI), accessible from the ALMA Science Portal.

For successful Solar observations that were submitted using a dummy ephemeris file (Section A.11), the ALMA Observatory will coordinate with PIs to get an updated target ephemeris at least 24 hours in advance of the proposed observation.

7.2 Changes to submitted programmes

Changes to a submitted proposal will not be permitted prior to the completion of the review process. Therefore, PIs should carefully check source coordinates, frequency and angular resolution settings and calibration needs before submitting their proposal and use Helpdesk if they need support.

Proposals assigned a grade of A, B, or C may request changes to their projects using the ALMA Change Request policies and procedures described in the Users’ Policies. Minor changes can usually be made during the Phase 2 process by the PI (see Phase 2 QuickStart Guide).

Major changes are allowed only if additional information that may seriously affect the scientific case of the project has become available since the time of submission, when there is a demonstrable mistake, or when there is the potential for interesting scientific optimization.

Change requests are made through the ALMA Helpdesk. The request must include a clear description of the proposed change along with a clear, substantive justification for the change. Major change requests are treated case-by-case and evaluated taking into account the increase in science scope, change of observing time, change from a standard to a non-standard mode, and other factors. Change requests leading to duplications against current or past ALMA proposals will not be approved.

7.3 Data processing and data delivery

 

ALMA staff will conduct quality assurance on ALMA data and will provide processed data products through the respective regional ARC archives. QA2 is performed on the data that result from all executions of an SB (called an ObsUnitSet or OUS). Data that meet the PI-specified goals within cycle-specific tolerances are marked “QA2 Pass” and are made available to the PI. Once the products have been identified as suitable for delivery, the PI is notified that the data are available for download through the ALMA archive. PIs are requested to check the delivered data as soon as practical.

For a more complete description of the Quality Assurance process, see Section 6.3 of the ALMA Users’ Policies Document and Chapter 11 of the Technical Handbook.

If the delivered data have problems other than those caused by a mistake of the PI, PIs need to submit a QA3 request to the Helpdesk as soon as possible, since this will have implications for the re-observation of problematic data and its proprietary period. By default, data obtained as part of an ALMA science programme are subject to a proprietary period of 12 months (except DDT programmes, which have a 6-month proprietary period), starting for each data package when the ARC sends the notification to the PI that the data are available (see Sections 8.4.3 and 8.4.4 of the ALMA Users’ Policies document).

7.4 Opportunities for public promotion of ALMA

If the PI believes their results are newsworthy or of interest to a broader community, the PI should contact the ALMA Education and Public Outreach (EPO) team to develop materials for presentation to the media and the public (e.g. press releases), including support in the preparation of visuals if relevant. EPO may ask for cooperation on the scientific content and for the PI to be available for possible interviews. The e-mail address for the ALMA EPO team is alma-iepot@alma.cl.

 

Appendix A: ALMA Cycle 5 Capabilities

This appendix describes the characteristics and capabilities of the ALMA Observatory that are offered for the Cycle 5 observing season. All submitted proposals must be compliant with these capabilities or they will be judged as infeasible. Where possible, the ALMA Observing Tool has validation checks to warn or prevent entering un-allowed values.

A.1 Number of antennas

In Cycle 5 at least forty-three 12 m antennas in the main array (hereafter the 12-m Array) will be offered. The ACA will have available at least ten 7 m antennas (hereafter the 7-m Array) for short baselines and three 12 m antennas (hereafter the Total Power or TP Array) for making single-dish maps. The ACA will be offered both to complement observations with the 12-m Array as well as a stand-alone capability. The stand-alone ACA is offered either for observations only with the 7-m Array or with the 7-m Array and TP Array combined, but not with the TP Array alone. The use of the TP Array is limited to spectral line observations (not continuum) in Bands 3, 4, 5, 6, 7 and 8. Bands 9 and 10 are not available for any TP observations.

The number of antennas available may sometimes be less than the numbers given above due to unforeseen problems with the equipment, or during array reconfigurations. ALMA support staff will endeavour to schedule observations that will not be seriously affected by having a slightly smaller number of antennas. The integration times or uv-coverage might also be increased to compensate whenever this is practical.

A.2 Array configurations

As detailed in Section 5.5, a science goal is defined in terms of a desired range of angular resolutions⁷ and the Largest Angular Structure (LAS) to be imaged. ALMA will meet these requirements by taking observations in one or more array configurations, which are characterized in terms of their Angular Resolution (AR) and Maximum Recoverable Scale (MRS, the largest smooth angular structure than can be imaged without too much degradation – see Chapter 7 of the Technical Handbook for details). The properties of these configurations, and the allowed combinations, therefore define the imaging capabilities of ALMA.

In Cycle 5 the antennas in the 12-m Array will be staged into configurations that transition from the most compact (with maximum baselines of ~160 m) up to the most extended configuration (maximum baselines
of ~16 km). Ten 12-m Array configurations have been defined to represent the possible distribution of 43 antennas over this range of maximum baselines. These are denoted as C43-x, with x=1 for the most compact configuration and x=10 for the most extended. One 7-m Array configuration has been defined to represent the possible distribution of the ten 7 m dishes. The imaging capabilities of these configurations are given in Table A-1.

Footnotes:

 

A.3 Total Power Array

The TP Array is used to recover extended emission when mapping angular scales up to the size of the requested map areas. For Cycle 5, TP Array observations are included only if the LAS cannot be achieved with the 7-m Array, and the TP Array can only be used for spectral line observations (not continuum) in Bands 3–8. No Band 9 or Band 10 TP Array observations are offered for this cycle. This means that angular scales greater than the 7-m Array MRS listed in Table A-1 cannot be recovered for any observations in Bands 9 and 10, or for continuum observations in any band.

 

A.4 Allowed array combinations and time multipliers

For Cycle 5, only certain array combinations are allowed to meet the specifications of a given science goal. A SG can use no more than two 12-m Array configurations, and 7-m Array observations are only allowed in conjunction with 12-m Array observations if one of the three most compact 12-m Array configurations is required. TP Array observations are allowed only if 7-m Array observations are also obtained (and subject to the restrictions in the preceding section). The allowed combinations are indicated in Table A-2 (with empty cells indicating combinations that are not allowed), and built into the OT validation.

For the resulting data to have good imaging properties, the different arrays must be observed in the correct proportion, depending on the number of overlapping baselines (see Chapter 7 of the Technical Handbook for details). These are expressed in terms of multiplicative factors with respect to the time required in the most extended configuration (which in turn is set by the user requested sensitivity and resolution). The time multipliers adopted for Cycle 5 are given in Table A-2, and are reported in the OT.

Table A-2: Allowed Array Combinations and Time Multipliers

Most Extended configuration	Allowed Compact configuration pairings	Extended 12-m Array Multiplier	Multiplier if compact 12-m Array needed	Multiplier if 7-m Array needed	Multiplier if TP Array needed and allowed
7-m Array	TP			1	1.7
C43-1	7-m Array & TP	1		5	8.5
C43-2	7-m Array & TP	1		5	8.5
C43-3	7-m Array & TP	1		5	8.5
C43-4	C43-1 & 7-m Array & TP	1	0.4	5	8.5
C43-5	C43-2 & 7-m Array & TP	1	0.5	4.6	7.8
C43-6	C43-3 & 7-m Array & TP	1	0.4	2.3	3.9
C43-7	C43-4	1	0.4
C43-8	C43-5	1	0.5
C43-9	C43-6	1	0.5
C43-10	-

Notes for Table A-2:

1. See Chapter 7 of the Technical Handbook for relevant equations and detailed considerations.

2. Whether a more compact array configuration is needed is based on the user specified LAS compared to the MRS values corresponding to the more extended configuration, as listed in Table A-1. If the LAS is greater than the MRS of the extended configuration, a more compact configuration is needed. Conversely, if a more compact array configuration is not allowed (e.g. for 12-m Array configurations more extended than C43-6), the LAS is not obtainable and will result in a validation error in the OT.

If more than one configuration is needed to satisfy the AR and LAS constraints of a given SG, during Phase 2 (Sect. 7.1), separate Scheduling Blocks (SBs) will be prepared for each required configuration. These will be observed independently, and the data from the different SBs will be calibrated and imaged separately.

 

A.5 Receivers

Bands 3, 4, 5, 6, 7, 8, 9 and 10 will be available on all antennas. However, observations with Bands 8, 9 and 10 will only be offered for configurations with baselines up to ~ 3.6 km, Band 7 up to ~ 8.5 km, and Bands 3, 4, 5 and 6 up to ~ 16 km (see Section A.2). Note that in Cycle 5 Band 5 observations cannot be carried out in the longest baselines due to the unavailability of the Band 5 receivers before March 2018.

There are two types of receivers: dual-sideband (2SB), where the upper and lower sidebands are separated in the receiver and then processed separately, and double-sideband (DSB), where the sidebands are super-imposed coming out of the receiver but may be separated in later processing. All bands receive dual linear polarizations (X and Y).

Table A-3 summarises the properties of the receiver bands offered in Cycle 5. Details can be found in Chapter 4 of the Technical Handbook.

Table A-3: Properties of ALMA Cycle 5 Receiver Bands

Band	Frequency range1 (GHz)	Wavelength range (mm)	IF range (GHz)	Type
3	84 – 116	3.6 – 2.6	4 – 8	2SB
4	125 – 163	2.4 – 1.8	4 – 8	2SB
5	163 – 211	1.8 – 1.4	4 – 8	2SB
6	211 – 275	1.4 – 1.1	5 – 10	2SB
7	275 – 373	1.1 – 0.8	4 – 8	2SB
8	385 – 500	0.78 – 0.60	4 – 8	2SB
9	602 – 720	0.50 – 0.42	4 – 12	DSB
10	787 – 950	0.38 – 0.32	4 – 12	DSB

Notes for Table A-3:

1. These are the nominal frequency ranges for continuum observations. Observations of spectral lines that are within about 0.2 GHz of a band edge are not possible (at present) in Frequency Division Mode (FDM, see Section A.6.1), because of the responses of the spectral edge filters implemented in the correlator. IF is the intermediate frequency.

Although up to three receiver bands will be available at any time, the capability to rapidly switch between them within the same Science Goal (except for the purposes of data calibration) is not offered in Cycle 5.

Water Vapour Radiometer (WVR) measurements to correct for fluctuations in atmospheric water vapour will be available for all 12 m antennas. No WVRs are installed in the ACA 7 m antennas and no WVR corrections will be applied to 7-m Array observations.

 Band 9 and 10 considerations

For Bands 9 and 10 observations, additional uncertainties will affect the data. Since the sidebands can be separated reliably only in interferometric observations, single-dish Bands 9 and 10 observations with the TP Array will not be offered in Cycle 5. Also, owing to the complexity of the atmospheric absorption in Bands 9 and 10, calibration will be compromised (this also applies to Band 8 and the high frequency end of Band 7). Bands 9 and 10 ACA 7-m Array observations are more compromised than the corresponding 12-m Array observations, since the rapid atmospheric phase correction cannot be applied, and the smaller collecting area will limit the network of usable calibrators; in particular bright calibrators will be sparse at these high frequencies. All these factors, together with the limited uv-coverage, will affect imaging at Bands 9 and 10 during Cycle 5 and will in particular limit the achievable dynamic range with the ACA 7-m Array. Imaging dynamic ranges up to 50 are typical for these bands (see Section A.9.1 for more details).

No mosaics will be offered for Band 10 observations.

 

A.6 Spectral capabilities

A.6.1. Spectral windows, bandwidths and resolutions

The ALMA IF system provides up to four basebands (per parallel polarization) that can be independently placed within the two receiver sidebands. For 2SB receivers (Bands 3–8 – see Table A-3), the number of basebands that can be placed within a sideband is 0, 1, 2, 3, or 4. A user cannot select 3 basebands in one sideband and 1 in the other, but 3 and 0 are fine. For DSB receivers (Bands 9 and 10), any number of basebands (up to 4) is acceptable.

The 12-m Array uses the 64-input Correlator, while the 7-m and TP arrays use the 16-input ACA Correlator. Both correlators offer the same spectral setups. The 64-input Correlator operates in two main modes: Time Division Mode (TDM) and Frequency Division Mode (FDM). TDM provides modest spectral resolution and produces a relatively compact data set. It is used for continuum observations or for spectral line observations that do not require high spectral resolution. FDM provides high spectral resolution and produces much larger data sets. A total of six correlator setups with different bandwidths and spectral resolutions are available (see Table A-4).

Table A-4: Properties of ALMA Cycle 5 Correlator Modes, dual-polarization operation ^1,2

Bandwidth (MHz)	Channel spacing(3) (MHz)	Spectral resolution (MHz)	Number of channels	Correlator mode(4)
1875	15.6	31.2	120	TDM
1875	0.488	0.976	3840	FDM
938	0.244	0.488	3840	FDM
469	0.122	0.244	3840	FDM
234	0.061	0.122	3840	FDM
117	0.0305	0.061	3840	FDM
58.6	0.0153	0.0305	3840	FDM

Notes for Table A-4:

1. These are the values for each spectral window and for each polarization, using the full correlator resources and no on-line spectral binning.

2. Single-polarization modes are also available, giving twice the number of channels per spw, and half the channel spacing of the above table.

3. The “Channel Spacing” is the separation between data points in the output spectrum. The spectral resolution – i.e., the FWHM of the spectral response function – is larger than this by a factor that depends on the “window function” that is applied to the data to control the ringing in the spectrum. For the default function – the “Hanning” window – this factor is 2. See the Technical Handbook for full details.

4. Only for the 64-input Correlator

For each baseband, the correlator resources can be divided across a set of “spectral windows” (spw) that can be used simultaneously and positioned independently. For Cycle 5, up to four spectral windows per baseband are allowed. The correlator can be set to provide between 120 and 3840 channels within each spw, and the fraction of correlator resources that are assigned to each spw sets the number of channels and the bandwidth available within it. The sum of the fractional correlator resources spread across all spectral windows must be less than or equal to one (3840 channels in total).

In Cycle 5, the default correlator setup for FDM modes averages every two channels. This has the advantage of halving the data rate to produce more manageable data cubes, while reducing the spectral resolution by only 15%. However, an additional consideration when selecting the spectral averaging is that data taken over different time periods (e.g., different configurations or multiple observations within the same configuration) are not guaranteed to be precisely aligned in frequency. Therefore, the spectra will need to be interpolated onto a common frequency grid in CASA. If the expected line width is poorly sampled at the resolution of the spectrometer, no channel averaging (i.e. a spectral averaging value of 1) is recommended in order to improve the accuracy of the interpolation (see Chapter 5 of the Technical Handbook for more information). In Cycle 5, the maximum data rate is 66 MB/s. For any spectral setup requiring an average data rate of more than 40 MB/s PIs will be contacted during Phase 2 to discuss the possibility to reduce the data rate.

 

Different correlator modes can be specified for each baseband, but all spws within a given baseband must use the same correlator mode. For example, a high-resolution FDM mode can be used for spectral line observations in one baseband (with up to 4 independently placed FDM spectral windows), while the other three basebands can be used for continuum observations using the low-resolution TDM mode. And while each spw within a baseband must use the same correlator mode, they can each be assigned a different fraction of the correlator resources and each use a different spectral averaging factor, providing a broad range of simultaneously observed spectral resolutions and bandwidths. Spectral windows can overlap in frequency, although the total continuum bandwidth for calculating the sensitivity is set by the total non-overlapped bandwidth.

A.6.2. Science Goals with more than one tuning

Users can include up to five tunings per group of sources within 10 degrees in a single Science Goal. This enables spectral scans or observations of targets with different radial velocities within the same SB.

The current calibration scheme for ALMA is to make each SB self-contained in terms of calibration. Therefore, multi-tuning SGs result in bandpass, amplitude, and gain calibrators being observed for each tuning in the SB. For SBs that can be completed in a single execution, this is quite efficient. However, for SBs that require multiple executions, the available time for science targets in each execution is reduced, and the resulting SBs can be quite inefficient. Separating each tuning into its own Science Goal can lead to more efficient SBs and lower overall time estimates.

Spectral scan mode

A special case of the multiple tuning science goal is the “Spectral scan” mode. This is useful for proposers who wish to carry out spectral surveys or redshift searches. The OT will automatically set up a set of contiguous spectral windows to cover a specified frequency range. The following restrictions apply:

1. Angular resolution and LAS are computed for the Representative Frequency of each SG;

2. No more than 5 frequency tunings per target are used, all in the same band;

3. Only one pointing per target is used (no mosaics or offsets allowed);

4. Only 12-m Array observations can be requested (the ACA is not offered for this mode);

5. Full polarization cannot be selected.

Spectral scans are categorized as a non-standard mode, limiting the total time available for such observations.

A.7 Polarization

For Cycle 5, in addition to the dual polarization (XX, YY) and single polarization modes (XX), observations to measure the full intrinsic polarization (XX, XY, YX and YY) of sources will also be offered for 12-m Array TDM and FDM observations in Bands 3, 4, 5, 6 and 7. Only linear polarization is guaranteed to meet the ALMA specification and only within one third of the primary beam. While PIs will receive data that will allow them to generate circular polarization data, the quality and/or accuracy of that data at this time is not assured, and such data should not be used for scientific purposes.

When a Dual Polarization setup is used, separate spectra are obtained for the cross-correlated parallel hands (XX and YY). These will give two largely independent estimates of the source spectrum that can be combined to improve sensitivity.

In Single Polarization mode, only a single input polarization (XX) is recorded. For a given resolution, this provides √2 worse sensitivity than the Dual Polarization case, but one can use either a factor two more bandwidth for the same spectral resolution (unless the maximum bandwidth was already being used) or a factor of two better spectral resolution for the same bandwidth.

Full Polarization measurements are non-standard, limiting the total time available for such observations. Sources must have a user-specified largest angular structure that is less than one-third of the 12-m Array primary beam at the frequency of the planned observations. The expected minimum detectable degree of polarization is 0.1%(1%) for compact sources and 0.3%(3%) for extended sources for TDM (FDM) observations, respectively. Full polarization is not offered for spectral scans or mosaics. The frequency settings for continuum polarization measurements can be specified by the user, but the OT supplies default setups as detailed in Table A.5. For FDM mode polarization observations any frequency setting within Bands 3, 4, 5, 6 and 7 is allowed, and the spectral setup has to be the same for the polarization calibrator and the science target.

It should be noted that Full polarization observations require about 3 hours of parallactic angle coverage for proper calibration. Science Goals with properties that lead to a total observing time estimate that is less than 3 hours will have the time estimate set to 3 hours to ensure sufficient parallactic angle coverage.

Table A-5: Default frequencies for Continuum Polarization Observations¹

Band	spw1 (GHz)	spw2 (GHz)	LO1 (GHz)	spw3 (GHz)	spw4 (GHz)
3	90.5	92.5	97.5	102.5	104.5
4	127.0	129.0	134.0	139.0	141.0
5	196.0	198.0	203.0	208.0	210.0
6	224.0	226.0	233.0	240.0	242.0
7	336.5	338.5	343.5	348.5	350.5

Notes for Table A.5:

1. Fixed central frequencies for four TDM spectral windows, each of width 1.875 GHz, and the corresponding LO1 setting.

2. Frequencies were chosen to optimize spectral performance, and they are centred in known low noise and low instrumental polarization tunings of the receivers.

A.8 Source restrictions

Source positions are designated by: 1) fixed RA and DEC; 2) RA and DEC at epoch 2000.0 with a linear proper motion; or 3) An ephemeris that is specified that gives the RA and DEC as a function of time.  All positions should be in ICRS (J2000).

At low elevations, it is possible for foreground array elements to block or “shadow” the signal received by background antennas, compromising the sensitivity and imaging characteristics of an observation (see Section 7.3 of the Technical Handbook for details). Therefore, observations of high declination targets should be avoided. For the 12-m Array, this shadowing becomes significant (> 5%) in the most compact configuration for sources with declination lower than −65° or higher than +20°. The adopted upper declination limit for ALMA is ~+47° (corresponding to a maximum elevation of 20 degrees at the ALMA site) and the OT gives a warning for objects transiting between 20 and 30 degrees elevation (corresponding to ~+37-47° declination).

A.8.1. Source Science Goal restrictions

A single Science Goal (SG) is constrained to include one set of observational parameters that apply to all sources included in that goal. This includes a single angular resolution, sensitivity, Largest Angular Structure (LAS), and receiver band. There is no restriction on the number of Science Goals per proposal.

For sources distributed widely in the sky the SG will be split by the OT into different “clusters”, each grouping all sources within 10 degrees. While there is no restriction on the total number of sources in a SG, for each grouping within the SG, the total number of pointings must be less than or equal to 150. Pointings with the ACA, if used in concert with 12-m Array observations, do not count against this 150-pointing limit.

The sources in a SG are further subjected to the following restrictions:

1. All the sources in a SG must be defined by the same field setup – either all as rectangular fields, or all as individual positions

2. Sources must use the same spectral setup (relative placement and properties of spectral windows)

3. For a given group of sources with positions within 10 degrees in the sky the total number of separate tunings cannot exceed 5.

A.8.2. Rectangular Field

A rectangular field (also referred to as a mosaic) is specified by a field centre, the length, width and orientation of the field, and a single spacing between the pointing centres. Observations are conducted using the “mosaic” observing mode. This repeatedly cycles through all the pointings in the mosaic so that the imaging characteristics across the map are similar.

The OT will set up a uniform mosaic pattern based on a user-specified pointing separation, and will calculate the time to reach the required sensitivity considering any overlap. Non-Nyquist spatial samplings are allowed but must be justified in the technical justification. Individual mosaics will not be combined during post-processing.

If ACA observations are requested as part of a mosaic, then a corresponding 7-m Array mosaic will also be observed. If these include TP observations, the mosaic area(s) will be covered by the TP Array using on-the-fly mapping.

Multiple sources may be included inside a SG, each of which can have a differently sized rectangular field. The collection of mosaics is subject to the source SG restrictions given above.

A.8.3. Individual Pointings

For each field source one or more pointings can be defined at a position of the PI's choosing and all must overlap i.e. they must form a single mosaic without gaps. These are often referred to as "custom mosaics" and are subject to the source SG restrictions given above.

 The interferometric data will be combined in post-processing to produce a single image. If ACA observations are requested as part of a 12-m Array Science Goal, then the corresponding 7-m Array observations will be obtained using a Nyquist-sampled mosaic pattern that covers the 12-m Array pointings. If these include TP observations, the mosaic area(s) will be covered by the TP Array using on-the-fly mapping.

 

A.9 Calibration

The ALMA Observatory has adopted a set of strategies to achieve good calibration of the data (see Chapter 10 of the Technical Handbook). Requests for changes in these strategies will only be granted in exceptional circumstances and must be fully justified. These changes will make the proposal non-standard (see Section 5.2). The default option is automatic calibrator selection by the system at observing time, but some flexibility exists in choosing the actual calibrator sources in the OT. If users opt for selecting their own calibrators, justification will be needed. This may result in decreased observing efficiency and/or calibration accuracy.

A.9.1. Imaging dynamic range

The standard ALMA data reduction with nominal phase stability should be sufficient to produce images with dynamic ranges (peak continuum flux to map rms) up to ~100 for the ACA and the 12-m Array compact configurations. For configurations more extended than 2 km and at frequency Bands 8, 9 and 10 the imaging dynamic range may be closer to 50.

Images of bright sources may be dynamic range limited rather than sensitivity limited. Their image quality may be improved by using self-calibration. For more information please see the Knowledgebase article “What is meant by imaging dynamic range?”.

A.9.2. Flux accuracy

Absolute amplitude calibration will be based on observations of objects of the known flux density of eight Solar system objects and a set of 30 quasars whose flux density are monitored every 15 days. It is expected that the accuracy of the absolute amplitude calibration relative to these objects will be better than 5% for Bands 3, 4 and 5; 10% for Bands 6, 7 and 8; and 20% for Bands 9 and 10. The decrease in accuracy at the higher frequencies is caused by variable atmospheric opacity, pointing errors and coherence loss due to phase fluctuations.

A.9.3. Bandpass accuracy

The amplitude and phase shape of the spectral response for each antenna in the array is measured during an observation by observing a strong quasar for the time needed to reach the desired spectral sensitivity for the relevant spectral resolution. The accuracy of this shape particularly affects projects that intend to observe spectral features that cover a significant fraction of a spw, and/or study faint spectral features in the presence of strong continuum. Spectral dynamic range (i.e. the desired signal-to-noise ratio per spectral resolution element) of 1000 has been demonstrated for Bands 3, 4, and 6, and a spectral dynamic range of 400, 250, 170, and 150 has been demonstrated for Bands 7, 8, 9, and 10, respectively. Cycle 5 proposals that request higher accuracies may be rejected on technical grounds. For Band 5, a spectral dynamic range limit of 500 may be assumed, but users should note that this has not yet been verified.

A.9.4. Total Power calibration

The intensity calibration for single-dish observations with the TP Array is made by using the Amplitude Calibration Device (ACD), which results in an intensity scale in terms of the corrected Rayleigh-Jeans antenna temperature T_A^* (K). To combine the TP data with the interferometric data the intensity scale is converted from K to Jy. The conversion factor is a function of the observed frequency, half-power beam width, and aperture efficiency of the TP Array antennas. The latter two are derived from regular single-dish calibration observations. The overall accuracy for the total power calibration is about 5% at Bands 3, 4, 5, 6 and 7, increasing to 15% at Band 8.

A.9.5. Astrometry

The absolute positional registration of an ALMA image on the sky depends on the angular resolution and the quality of the phase calibration. For the standard calibration with average phase conditions, the typical image registration accuracy is ~(angular resolution)/20.0 but with a minimum of 0.003", without special calibrations. This assumes that the SNR of the target image is at least 20:1 to reach this accuracy. For projects for which measuring the position of an object or its motion over a period of time is a main goal, recommendations for Cycle 5 are:

1. Choose a calibrator with a VLBI position as close to the target as possible, using spw and polarization averaging for weaker calibrators.

2. Confirm the observations contain a secondary calibrator of known position (and justify it in the Technical Justification), so its measured position after normal calibration is an indication of the astrometric accuracy of the observations.

3. Choose the observing frequency and configuration to maximize the astrometric precision of the target, based on its angular size and spectral properties.

4. If the desired astrometric precision is less than about 0.003" rms, then multiple calibrators should be observed. Further details and guidelines are given in Chapter 10 of the Technical Handbook. Proposers are also encouraged to discuss the experiment with their local ARC.

 

A.10 Time-constrained observations

Observations of monitoring and time-constrained projects will be offered in Cycle 5 with a few restrictions:

• Observations to be performed with two 12-m Array configurations to satisfy the PI requests of AR and LAS within a SG are not allowed to have time constraints.

• Stand-alone ACA proposals requesting only observations on the 7-m Array will be allowed to have time constraints.

• Observations with one 12-m Array configuration and the 7-m Array are allowed to have time constraints only if simultaneous observations with the two arrays have been requested.

• Simultaneous observations in the 12-m and 7-m Arrays can be requested only for those configurations allowed by the OT.

• In Cycle 5, no restrictions will be imposed on the size of the time window specified by PIs for time-critical observations. The scheduling feasibility of any proposal will depend on the total number of constraints that are imposed and on whether the time window takes place during other activities on the array such as engineering or computing time. Whether such observations are technically feasible will be decided on a case-by-case basis. In particular observations with strict timing constraints but many possible time windows may be feasible.

• Programmes that require more than two hours of continuous observations to monitor a source cannot be guaranteed due to variable weather conditions and system interruptions. Proposers may request monitoring observations longer than two hours, but if the observations fail after two hours, the observations will not be repeated. Monitoring observations will be interrupted by regular calibrations.

 

A.11 Solar observations

Proposals will be accepted for ALMA interferometric and total power observations of the Sun in Cycle 5 with the following capabilities and restrictions:

• Solar observations will be conducted only during the periods when the 12-m Array is in one of the three most compact configurations (maximum baselines less than 500 m; see configuration schedule in Section 5.3.4).

• The interferometric component of Solar observations will be conducted using a special combined array comprising both 12 m and 7 m antennas (to ensure sufficient short-spacing information is observed), and will be processed with the 64-input Correlator (Section 5.1 of the Technical Handbook). Observations with only the 12-m Array or only the 7-m Array are not offered.

• To minimize shadowing of 7 m antennas, observations will be carried out between 10:00 and 17:00 CLT (13:00 UT and 20:00 UT).

• PIs will designate a desired range of angular resolutions. This is restricted to the range provided by one of the three most compact 12 m configurations (see Section A.2).

• The Total Power component of Solar observations consists of fast-scanning mapping observations of the full Sun to recover the largest angular scales for interferometric observations. Proposals requesting only total-power single-dish observations will not be accepted.

• The TP observations will be taken contemporaneously with the interferometric observation. These observations will not be executed when the Sun is at elevations above 70⁰ because the required fast-scan azimuth slew speeds are too high. The time cadence of full-sun images obtained from total power observations is about 7 minutes for Band 3 and 10 minutes for Band 6.

• Proposers will specify their Solar target by providing an ephemeris file. This can be a dummy ephemeris for the purposes of a proposal (one is available from the OT “template library”). The ALMA Observatory will coordinate with successful PIs to get an updated target ephemeris at least 24 hours in advance of the proposed observation.

• Only proposals for continuum observations in Bands 3 and 6 will be accepted. For the interferometric observations these will be obtained using the low spectral resolution (TDM) mode (see Section A.6.1). The individual integration times for this mode are fixed to 1 second, and the frequencies are fixed to four 1875 MHz-wide spectral windows centred on the frequencies shown in Table A-6 below. The high spectral resolution (FDM) observing mode is not offered for Solar observations.

• The observing frequencies of the total power observations are as shown in Table A-6, but the total power data only include one channel per spw; a correlator will not be used for total power observations in Cycle 5 and so autocorrelation measurements will not be available.

Table A-6: Observing frequencies for Cycle 5 Solar observations

Band	spw1 (GHz)	spw2 (GHz)	LO1 (GHz)	spw3 (GHz)	spw4 (GHz)
3	93.0	95.0	100.0	105.0	107.0
6	230.0	232.0	239.0	246.0	248.0

 

• Simultaneous observations with Bands 3 and 6 are not offered: each science goal can only include one band.

• Observations may be performed using dual linear polarization (XX, YY) or single polarization (XX) correlations; full polarization measurements are not currently offered for Solar observations.

• Because the WVR receivers are saturated when the antennas point at the Sun, the on-line WVR phase correction will not be applied and the off-line WVR correction for on-source (Solar) data is not possible.

• Absolute calibration of single-dish brightness temperatures is currently no better than ~10% but is more realistically ~15%. While efforts are on-going to improve Solar calibration, Cycle 5 science goals that require absolute temperatures more accurate than this, and in particular comparisons of absolute temperatures between Bands 3 and 6, will be difficult to carry out successfully.

 

A.12 VLBI observations

Proposals will be accepted for ALMA VLBI (phased array) observations, with the following capabilities and restrictions:

• VLBI observations will be conducted using a “campaign mode”, whereby specific dates are reserved for the execution of VLBI programmes so that VLBI experts are available to help with programme execution. Observing windows will be identified during the periods when the 12-m Array is in one of the three most compact configurations (maximum baselines less than 500 m; see configuration schedule in Section 5.3.4). The actual campaign dates will be set after the proposal review process.

• Due to the need to phase up on the target source, only targets with correlated flux densities > 0.5 Jy on intra-ALMA baselines out to 1 km may be proposed for observation for both Bands 3 and 6.

• Only proposals for continuum observations in Bands 3 and 6 will be accepted. These will be obtained in full polarization using the high spectral resolution (FDM) mode (see Section A.6.1) and the 64-input Correlator. Observing frequencies are fixed to four 1875 MHz-wide spectral windows centered on the frequencies shown in Table A-7 below.

Table A-7: Observing Frequencies for Cycle 5 VLBI Observations

Band	spw1 (GHz)	spw2 (GHz)	LO1 (GHz)	spw3 (GHz)	spw4 (GHz)
3	86.268	88.268	93.268	98.268	100.268
6	213.1	215.1	222.1	227.1	229.1

• The proposers are required to enter a VLBI total time requested. Note that this time is equivalent to the overall time requested which must include overheads. For ALMA + GMVA or EHTC the expected overheads, including ALMA calibrations, are a factor of four (25% duty cycle) of the expected time on source.

• A VLBI session will not exceed one week. Therefore, if multi-epoch observations are requested, they must fit within one week and the total time must be the aggregate time of all observations.

• A minimum of three observing hours is required to make a clean linear to circular transformation of the data.

For 3 mm VLBI, a proposal must have been submitted to the GMVA network by their 1 February 2017 deadline (see http://www3.mpifr-bonn.mpg.de/div/vlbi/globalmm/). The same scientific justification must be used for the ALMA 3 mm VLBI proposal. A sensitivity calculator is available at: http://www3.mpifr-bonn.mpg.de/cgi-bin/mobs.cgi or http://www.evlbi.org/cgi-bin/EVNcalc.

For 1 mm VLBI, the ALMA Observatory will further send the submitted 1 mm VLBI proposals to the EHTC network. Thus, proposers will only submit one proposal to the ALMA Observatory.

 

The Technical Justification must be entered directly into the OT for each science goal. Below are guidelines on issues to consider in the different sections. Sections B.5 and B.6 point to specific items that need justification for Solar and VLBI observations, respectively. In general, PIs should address all the parameters requested in the OT.

 

B.1 Sensitivity

At the top of the sensitivity section, the OT will display the sensitivity and S/N achieved for different bandwidths (bandwidth requested for sensitivity, aggregate bandwidth, a third of the line width) as appropriate for the spectral setup and the Expected Source Properties defined. While the justification for the requested sensitivity or S/N should be included in the Scientific Justification (Section 6.2.2), the TJ must explain which sensitivity or S/N are expected for all the parts of the spectrum that are of interest, e.g. for a spectral setup targeting a weak and a strong spectral line as well as the continuum, and the means by which the proposed technical setup will achieve those requests.

Keep in mind that the fluxes in the Expected Source Properties should have been entered per synthesized beam, i.e. you may have to correct any available flux measurements for the fact that your source is spatially resolved by ALMA and the flux is distributed over several synthesized beams (see Knowledgebase articles “How can I estimate the Peak Flux Density per synthesised beam using flux measurements in Jy or K from other observatories?” (see the video https://www.youtube.com/watch?v=zrsD622iR_g&feature=youtube) and “How do I convert flux measurements given in Jy km/s or K km/s into the peak flux density required by the OT?” for more details on using fluxes/brightness temperatures from other facilities). Users should be aware that the sensitivity requested may not be achievable in practice if the observations are dynamic range limited; e.g. when the field of view contains another, very bright, source or the spectrum has very bright lines. S/N values smaller than three trigger a blue informative message and need to be fully justified; they may lead to a rejection of the proposal on technical grounds if no adequate explanation is given. For setups including spectral lines, another value to double-check is the ratio of the line width (entered in the Expected Source Properties) over the bandwidth used for sensitivity (from the Control & Performance editor), which is conveniently displayed by the OT. It is important to understand that the sensitivity requested will be achieved over a frequency bin corresponding to this bandwidth, not necessarily over every spectral resolution element. For spectral line measurements this value should normally be larger than 3 (or even higher if you want to measure the shape of the line profile). An informative message will appear if this is not the case, and you should address this issue in the justification text (e.g. if the sensitivity requirement is driven by the continuum it may be acceptable to have a very low ratio).

The final parameter to be checked for observations measuring both line and continuum emission is the spectral dynamic range, defined as the continuum peak flux divided by the line RMS. Limits on the spectral dynamic ranges offered in Cycle 5 for the different ALMA bands are given in Appendix A (Section A.9.3); an informative message will appear if these are exceeded and the proposal may be rejected on technical grounds. The spectral dynamic range is important especially when trying to detect a weak line on top of a strong continuum, and high spectral dynamic ranges may require a better bandpass accuracy than possible with a standard calibration. If a high spectral dynamic range is required, extra bandpass calibrations may need to be obtained selecting “User-defined calibration”.

 

B.2 Imaging

When planning your ALMA observations, in addition to the sensitivity goals, the complexity of the emission in the science target field should also be considered. An interferometer's ability to reconstruct complex emission is directly related to the uv-coverage of the data. This section is used to justify the requested angular resolution (AR) and LAS, which for convenience are reported back by the OT. The AR and LAS needed to image complex emission should be carefully justified (if necessary, including simulations), especially if multiple antenna configurations are required. The number of required antenna configurations is listed in the observing time estimate of the project time summary in the OT.

The ''snapshot'' (i.e. short observation) uv-coverage of the smaller ALMA configurations (C43-1 to C43-3) is excellent, it is still reasonably good for C43-4 to C43-6, but for the longer baseline configurations (C43-7 to C43-10) the uv-coverage is quite sparse even with 50 antennas. As such, more observing time must be spent to “fill in” as much as possible the missing uv-coverage. Thus, high fidelity imaging of complex and/or high dynamic range emission may require a longer observing time than implied by sensitivity requirements alone, and this is especially true for the longest baseline configurations. In Cycle 5, consecutive executions of a given SB (if needed) will be favoured during scheduling in order to maximize uv-coverage. Nonetheless, if more extensive uv-coverage is required to satisfy the imaging requirements, the OT's sensitivity-based time estimate can be overridden (see below). PIs are strongly encouraged to use the ALMA simulator tools to assess the potential need for extra uv-coverage.

For single or non-overlapping pointings the source should fit within the inner one third of the primary beam (field of view), or the PI should discuss the effects of the sensitivity loss towards the beam edges.

PIs should also pay attention to the expected image dynamic range (see Section A.9.1) if attempting to detect a weak signal that falls in the same pointing as a much brighter source. The OT cannot identify such cases automatically since it has no knowledge of the flux structure of the field to be observed. See the Knowledgebase article “What is meant by imaging dynamic range?” for details.

 

B.3 Correlator configuration

For spectral line observations, the OT reports the number of (Hanning smoothed) spectral resolution elements per line width, taking into account any spectral averaging, and the width of the representative spectral window. PIs have to make sure to select the correct representative spectral window. If the spectral resolution is larger than one third of the line width from the Expected Source Properties, an informative message will appear, and if not suitably justified this will lead to the rejection of the proposal on technical grounds. Note that the spectral resolution is not necessarily the same as the bandwidth for sensitivity!

The requested correlator setup and the placement of spectral windows should be carefully justified in the free-format text box. In the case of multiple spectral lines and/or narrow spectral windows in particular, PIs should double-check that the line profiles are fully covered by the selected spectral windows.

PIs should also check whether any of the spectral windows are severely impacted by atmospheric absorption, which can affect Bands 5 and 7-10 especially. If necessary, the representative frequency should be modified to be at the most restrictive part of the atmosphere where a line needs to be detected, which will impact the time estimate. Any continuum windows should be moved to avoid areas of bad transmission.

For the double sideband receivers (Bands 9 and 10), the atmospheric transmission in the mirrored spectral window impacts the sensitivity achieved in the spectral window and therefore the time estimate. PIs may wish to modify the spectral setup accordingly. It is advisable to add continuum spectral windows in any unused basebands, in particular for high frequency SGs.

 

B.4 Choices to be justified

The OT will automatically catch a number of user choices that must be explicitly justified in a text box. These choices are:

• Override of OT's sensitivity-based time estimate: Proposers may wish to override the OT's time estimate to monitor a source over a certain time range or to build up the uv-coverage for imaging a complex source. When using this option, proposers should keep in mind that programmes that require more than two hours of continuous observations cannot be guaranteed due to variable weather conditions and system interruptions (Section A.10). The time entered refers to the 12-m Array time, includes all calibrations, and must be fully justified. Note that the OT assigns the PWV based on the representative frequency of the requested observations and the declination of the source; it is not possible to request specific weather conditions for the observations.

• Time-constrained observations: the OT allows you to specify two types of time-constrained observing: single visit and multiple visits. In the first case, one or more time windows are specified, but the observations will only be carried out once during any of these time windows. In the second case, the Science Goal is observed in each of the time windows specified. The technical feasibility of time-constrained observations will be decided on a case-by-case basis.

• User-defined calibration: the default system-defined calibration option ensures that the proper calibrations for the flux scale, bandpass, and relative antenna gains are obtained. Observations making use of the full polarization capabilities of ALMA will also include the necessary calibrations by default. User-defined calibrations should be necessary only in rare cases, e.g. if a very high spectral dynamic range is required, it may be necessary to perform additional calibrations and/or use specific sources. Such requests must be explained and justified in detail. Programmes that cannot be calibrated or that increase significantly the complexity of data reduction will not be allowed and flagged as technically unfeasible and rejected.

• Low maximum elevation: sources that transit at a low elevation are difficult to schedule for observation since they suffer from high atmospheric attenuation and require low PWV, especially at high frequencies (see Section A.8). A detailed explanation should be provided as to why these sources need to be observed rather than sources at higher elevation.

• Single polarization: this should only be used when the highest spectral resolution is required, as the sensitivity achieved is lower than when using the default dual polarization. PIs should carefully justify why the high spectral resolution requested is required.

• Non-Nyquist sampling for rectangular mosaics (Imaging section): given the drop in sensitivity towards the primary beam edges, Nyquist sampling is required to yield mosaics with a uniform sensitivity coverage. However, when the area to be covered is very large and large-scale structures are not being observed it may be acceptable to use a sparser sampling.

In addition to the issues mentioned above, PIs should note that the following requests/mistakes will lead to proposal rejection on technical grounds:

• Underestimation of the required observing time by more than a factor of 2 due to mistakes in the input parameters

• Technical Justifications based on data unavailable at the time of writing the proposal

• Omission of ALMA simulations that are integral to the justification of the observing requirements (see Section 6.2.2).

• Target of Opportunity (ToO) Proposals that do not give full details on the number of triggers needed to reach the science goals of the proposal, what the trigger will be, and the necessary reaction time for scheduling the observation after it is triggered.

 

B.5 Solar observations

The sensitivity calculator is not adequate for Solar observations because the antenna temperature greatly exceeds the system temperature and, moreover, depends on the Solar target (e.g., quiet Sun, active region, Solar limb). Therefore, Solar proposers are asked to enter the total time and justify this request to the extent that depends on technical imaging considerations, not on scientific factors. For example, for a mosaic of a target in a given frequency band, PIs should indicate how many repetitions of the sampling pattern are needed and why. For this calculation PIs should take into account that ALMA observations are comprised of one or more executions of a SB. The total execution time of an SB cannot exceed 2 hours, which will include the time overheads for bandpass and flux calibration. These calibration overheads amount to about 25 mins.

 

B.6 VLBI observations

The VLBI technical justification should be tuned to the overall science goals taking into account the phased ALMA array. Due to the need to phase up on the target source, only targets with correlated flux densities >0.5 Jy on intra-ALMA baselines out to 1 km may be proposed for observation for both Bands 3 and 6. For 3 mm VLBI Proposals, the technical justification that was added to the GMVA proposal can be used for the ALMA observations. The following on-line material is currently available to help justify the requested observing time:

• At 3 mm: the sensitivity calculator at http://www.evlbi.org/cgi-bin/EVNcalc and the 3 mm VLBI page at http://www3.mpifr-bonn.mpg.de/div/vlbi/globalmm/

• At 1 mm: see the 1 mm VLBI page at http://www.eventhorizontelescope.html and links to the Call for Proposals, proposal preparation and technical parameters for details.

 

ACA	Atacama Compact Array
ACD	Amplitude Calibration Device
ALMA	Atacama Large Millimeter/Submillimeter Array
AOS	Array Operations Site
APEX	ALMA Pathfinder EXperiment
ARC	ALMA Regional Center (or Centre, for EU)
ARP	ALMA Review Panel
APRC	ALMA Proposal Review Committee
AR	Angular Resolution
ASC	ALMA Sensitivity Calculator
ASIAA	Academia Sinica Institute of Astronomy and Astrophysics
AUI	Associated Universities, Inc.
CASA	Common Astronomy Software Applications
Co-I	Co-investigator
Co-PI	Co-Principal Investigator
CONICYT	Comisión Nacional de Investigación Científica y Tecnológica
CS	Contact Scientist
DDT	Director Discretionary Time
EA ARC	East Asian ALMA Regional Center
EHTC	Event Horizon Telescope Consortium
EPO	Education and Public Outreach
ESO	European Southern Observatory
EU ARC	European ALMA Regional Centre
FDM	Frequency Division Mode
FOV	Field Of View
GMVA	Global Millimeter VLBI Array
IF	Intermediate Frequency
KASI	Korea Astronomy and Space Science Institute
JAO	Joint ALMA Observatory
LAS	Largest Angular Structure
LST	Local Sidereal Time
MRS	Maximum Recoverable Scale
NA ARC	North American ALMA Regional Center
NAASC	North American ALMA Science Center
NAOJ	National Astronomical Observatory of Japan
NINS	National Institutes of Natural Sciences
NRAO	National Radio Astronomy Observatory
NRC	National Research Council of Canada
NSC	National Science Council of Taiwan
NSF	National Science Foundation
OSF	Operation Support Facility
OST	Observation Support Tool
OT	Observing Tool
OUS	ObsUnitSet
PDF	Portable Document Format
PI	Principal Investigator
PWV	Precipitable Water Vapour
QA2	Quality Assurance Level 2
SB	Scheduling Block
SCO	Santiago Central Office
SG	Science Goal
SnooPI	Snooping Project Interface
SP	Science Portal
Spw	Spectral window
TDM	Time Division Mode
TJ	Technical Justification
ToO	Target of Opportunity
TP	Total Power
VLBI	Very Long Baseline Interferometry
WVR	Water Vapour Radiometer

 

 

 

The list below presents for each science category the keywords that can be used in the OT to further specify the scientific area of the proposal. Proposers must select at least one and at most two keywords.

 

Category 1 – Cosmology and the high redshift universe

1. Lyman Alpha Emitters/Blobs (LAE/LAB)

2. Lyman Break Galaxies (LBG)

3. Starburst galaxies

4. Sub-mm Galaxies (SMG)

5. High-z Active Galactic Nuclei (AGN)

6. Gravitational lenses

7. Damped Lyman Alpha (DLA) systems

8. Cosmic Microwave Background (CMB)/Sunyaev-Zel'dovich Effect (SZE)

9. Galaxy structure & evolution

10. Gamma Ray Bursts (GRB)

11. Galaxy Clusters

 

Category 2 – Galaxies and galactic nuclei

1. Starbursts, star formation

2. Active Galactic Nuclei (AGN)/Quasars (QSO)

3. Spiral galaxies

4. Merging and interacting galaxies

5. Surveys of galaxies

6. Outflows, jets, feedback

7. Early-type galaxies

8. Galaxy groups and clusters

9. Galaxy chemistry

10. Galactic Centres/nuclei

11. Dwarf/metal-poor galaxies

12. Luminous and Ultra-Luminous Infra-Red Galaxies (LIRG & ULIRG)

13. Giant Molecular Clouds (GMC) properties

 

Category 3 – ISM, star formation and astrochemistry

1. Outflows, jets and ionized winds

2. High-mass star formation

3. Intermediate-mass star formation

4. Low-mass star formation

5. Pre-stellar cores, Infra-Red Dark Clouds (IRDC)

6. Astrochemistry

7. Inter-Stellar Medium (ISM)/Molecular clouds

8. Photon-Dominated Regions (PDR)/X-Ray Dominated Regions (XDR)

9. HII regions

10. Magellanic Clouds

 

Category 4 – Circumstellar disks, exoplanets and the solar system

1. Debris disks

2. Disks around low-mass stars

3. Disks around high-mass stars

4. Exoplanets

5. Solar system: Comets

6. Solar system: Planetary atmospheres

7. Solar system: Planetary surfaces

8. Solar system: Trans-Neptunian Objects (TNOs)

9. Solar system: Asteroids

 

Category 5 – Stellar evolution and the Sun

1. The Sun

2. Main sequence stars

3. Asymptotic Giant Branch (AGB) stars

4. Post-AGB stars

5. Hypergiants

6. Evolved stars: Shaping/physical structure

7. Evolved stars: Chemistry

8. Cataclysmic stars

9. Luminous Blue Variables (LBV)

10. White dwarfs

11. Brown dwarfs

12. Supernovae (SN) ejecta

13. Pulsars and neutron stars

14. Black holes

15. Transients