From scheduling andPhase 2 generation viewpoints
Yu-Ting Wu (EA ARC)
and Phase 2 Generation Group in EA

What is Phase 2?
• Once a project has been approved for scheduling, it passes to Phase 2.
approved project
PIphase 2CS

P2G group

observing queue
JAOHD• Each approved project will be assigned an ALMA Contact Scientist (CS).
• A project Helpdesk (HD) ticket will be opened on behalf of the PI for
communication with the CS and others.
• ALMA staff will generate the Scheduling Blocks and, in case of problems,
will contact the CS and the PI. If no problems are found, the project will besubmitted to the ALMA observing queue to await execution at thetelescope.

2

Why we care about scheduling and Phase 2 generation?
• Various aspects of a proposed observation such as weather conditions
or requested angular resolution and Largest Angular Structure (LAS)
are important when an observation is scheduled.
• Let's plan observations to maximize project completion to achieve ourscientific goals!

31. Angular resolution• Observations are scheduled based on the angular resolution• For scheduling feasibility and Quality Assurance (QA) purposes, if the PI selects a single
value for the Desired Angular Resolution or a range narrower than 20% around its centervalue, a range of +/-20% around the single or center value specified will be enforced(Section 4.3.2 of the PG).

A1
<0.2xAA

A2<0.2xA4

1. Angular resolution• Observations are scheduled based on the angular resolution• For scheduling feasibility and Quality Assurance (QA) purposes, if the PI selects a single
value for the Desired Angular Resolution or a range narrower than 20% around its centervalue, a range of +/-20% around the single or center value specified will be enforced(Section 4.3.2 of the PG).

A1
<0.2xA

0.2xA
0.8xA

AA2
<0.2xA

0.2xA
1.2xA

5

1. Angular resolution• Observations are scheduled based on the angular resolution• For scheduling feasibility and Quality Assurance (QA) purposes, if the PI selects a single
value for the Desired Angular Resolution or a range narrower than 20% around its centervalue, a range of +/-20% around the single or center value specified will be enforced(Section 4.3.2 of the PG).
• Whenever a range of angular resolution is acceptable for the science goals, PIs areencouraged to enter a range of Desired Angular Resolution broader than 20% around itscenter value.
hieved!!
caebnaclsnce goa
iec
sr
uoyne
A2
hA1
A
do this only w<0.2xA

0.2xA
0.8xA

<0.2xA

0.2xA
1.2xA

6

1. Angular resolution• Whenever a range of angular resolution is acceptable for the science goals,PIs are encouraged to enter a range covering more than one configuration.

hendo this only w

e achieve
bnaclsaogienced!!

your sc7

2. Weather• Section 4.3 of the ALMA Cycle 10 Proposer’s Guide• Band 9 and 10 observations will bescheduled during the LST ranges givenin the fourth column.
• Bands 7 and 8 observations outside ofthose LST ranges are limited
During the cycle…

mentioned in Nagai-san’s talk8

3. Spectral setup• Avoid placing spectral windows (spw) close to the baseband edge
• Any spw located within 30 MHz of the baseband edge could result incompromised flux calibration and might cause problems for finding thetuning solution for Local Oscillator signals as well.

tiomenne’s taegrod in Jlk9

4. Multiple-visit observation• Two possible strategies
Visit 1

Visit 2Visit 3

If…

Visit 1

Visit 2

X

Visit 3

Visit 1

Visit 2

X

Visit 32+/-1 day
5+/-1 day

Visit 1

Visit 2Visit 3If…

X10

4. Multiple-visit observation

Visit 1

Visit 2Visit 3

If…

Visit 1

X

Visit 2Visit 32+/-1 day
5+/-1 day11

5. TP only observation• Section A.3 of the ALMA Cycle 10 Proposer’s Guide• The TP Array cannot be requested in a standalone mode using the OT.
However, if a user has existing 7-m Array data through their own
program or through archival data, but now realizes that TP Array data
are needed to obtain short spacings, they can submit a proposal
requesting both the 7-m Array and TP Array.
• The proposal should indicate that only the TP Array is needed and thatthe 7-m Array should be descoped if the proposal is accepted. This
option is available only if the 7-m Array data have already been obtained.

126. Checking for duplications• Duplicate observations of the similar location on the sky with similar
observing parameters (frequency, angular resolution, coverage, andsensitivity) are not permitted unless scientifically justified (Section 4.4.1)

1.

2. on-going Grade Aor
13

6. Checking for duplications
band 10my sourceband 314

6. Checking for duplications15

6. Checking for duplications• Criteria
ALMA Users’ Policies

16

7. Resubmission of an unfinished proposal• Proposal teams that submit a Cycle 10 proposal to observe some or allthe SGs of an unfinished project will have the relevant SGs identified as a“resubmission”.
• Criteria: Appendix A of the Users’ Policies• Policies (Section 4.4.2 of the ALMA Cycle 10 Proposer’s Guide):

For such resubmissions, the relevant portion of the Cycle 10 proposal will be canceled if
the observations are successfully completed in Cycle 9. Observations started in a previous
cycle and accepted as a resubmission in Cycle 10 will continue to be observed with thesetup of the previous cycle.

178. Change requests (Section 8 of the ALMA Users’ Policies)• Triple-check all setups before the proposal submission deadline!!
• After the PIs have been notified of the results of the proposal review
process, PIs of scheduled proposals may request necessary changes totheir project via the ALMA Helpdesk.
• Major changes (defined in Appendix B of the ALMA Users’ Policies) areallowed only if the change is essential for the science goals of the project.
Any major change request by a PI must be made by submitting a Helpdesk
ticket and will only be implemented after the approval of the changerequest.

18

8. Change requests (Section 8 of the ALMA Users’ Policies)• Major change requests may be motivated by the following considerations• New information received since the original proposal submission• e.g. new observations including interim observational results of aproject, other new information on planned observing targets, orexternally-imposed changes to the scheduling of time-coordinatedobservations at other observatories• Technical considerations for implementation during Phase 2 (that areinitiated by the PI, e.g. to optimize the scientific yield of the observations)• Mistakes made by the PI• Please read Section 8 and Appendix B of the ALMA Users’ Policies carefully
before requesting any changes!
19Pleaseso th keep theat you can affiliation
aget adequ nd email
ate suuppo p to datert from the during the whcorreole c
sp o nycding
ARC le.

20

Please don’t hesitate to contact us through the Helpdesk!
https://help.almascience.org/21