When and How to Use Chandra PRoVis

POG Threads (Cycle 11)

1. Introduction
2. Roll Constraint
- Example 1
- Example 2
3. Window Constraint
4. Uninterrupted Observation
5. Triggering a TOO
History
Images

1. Introduction

PRoVis is a web-based application that allows viewing and interactive manipulation of Roll, Pitch and Visibility Plots. The plot uses a recent projected Chandra ephemeris. Since Chandra's orbit does not change much from year-to-year, plots are also closely applicable for any mission year.

The plots are generated directly into the browser, unless postscript is requested, for which the browser needs to have an external viewer configured to retrieve and view postscript. The PRoVis GUI consists of 4 elements: buttons frame, target parameters frame, plot options frame and actual plot frame. To use: enter the J2000 sky coordinates of the source of interest in the boxes on the left in the target parameters frame, then press enter or click on the "Generate Plot" button at the top of the page. Alternatively, type in a target name in the "Target Name" input box on the left, then either press return, which will resolve the name to sky coordinates, or click on "Generate Plot" which will resolve the name to coordinates and generate the plot in one step.

Please note: PRoVis works best with Mozilla Firefox (v1.5.0.5 or newer), SeaMonkey (v1.1.8 or newer), Safari (v3.1.2 or newer), and Internet Explorer (v6 and newer) browsers.

Proposers should use PRoVis to investigate the effects of their constraints on pitch when their observations require one or more of the following:

Roll Constraints
Window Constraints
Phase Dependent Observations
Coordination with Another Observatory
Uninterrupted Observations
Grid Observations (in which the pieces must line up)
Long (>100 ks) observations
Triggering a Target of Opportunity (TOO)

Please read about pitch angle restrictions in Section 3.3.3 of the Proposers' Observatory Guide (POG).

This thread demonstrates how proposers should use PRoVis in several different types of scenarios.

2. Roll Constraint

If an observation has a roll constraint (e.g. a gratings observation that requires two nearby sources to be spatially resolved, with distinct spectra), the observer should use PRoVis to check that this roll constraint does not force the target to be at bad pitch.

Example 1

An observer wishes to use ACIS-S to image a pair of O4 stars that constitute a visual binary in M17. In order to obtain spatially resolved, simultaneous X-ray grating spectra of the two O4 stars, the Chandra spacecraft must be within a narrow range of roll values. PRoVis can be used to see whether these roll constraints force the target to be at bad pitch, so that the observer will know if the plan is feasible, or whether the constraints must be relaxed.

The plot will look like this .

The roll constraint for this observation is 135 degrees, with a 15 degree tolerance. Looking at the above PRoVis plot for the Cycle 11 time frame, we can see that a restriction between 120 and 150 degrees requires the observation to be done between June 12 and June 19, 2010. By tracing the mouse cursor along the roll curve to a roll of 120 degrees, we see that roll is nominal on June 12, when the target pitch is 165 degrees. This can also be seen directly from the Plot Data by clicking the View Plot Data button in PRoVis. Table 3.1 of the POG shows the target pitch as very near to the 170 degree cutoff for observations. In addition, observations at a pitch of 165 degrees are limited by EPHIN temperature restrictions, which may be undesirable for this 150-ks proposal, depending on the science goals. To see what the maximum continuous exposure time is for a given pitch angle, consult the MaxExpo chart. This chart indicates that, at 165 degrees of pitch, the maximum exposure is 20 ks, and as the pitch increases to 170 degrees, the maximum exposure time drops rapidly to 0.

In such cases, working closely with Mission Planning to relax some constraints can often result in obtaining the best data possible. For instance, relaxing the roll constraint slightly in the above situation may allow the observation to be scheduled with fewer interruptions.

Example 2

A proposer wishes to observe the Vela Pulsar Wind Nebula (PWN) with ACIS-S while ensuring that the "trailed image" does not contaminate the regions of interest within the target. Such an observation requires avoiding roll angles of 40-80 degrees and 220-260 degrees. The resulting roll constraint (150 degrees with a 70 degree tolerance) is pretty workable. However, if the observers want to study temporal variations in the structure, such as taking eight 40-ks observations with one-week intervals (a Monitoring observation), this presents further scheduling restrictions: the proposer must make sure that there are significantly large chunks of time in which the target is at suitable pitch and roll for the monitoring observation to take place.

The plot (for coordinates 08 35 20.70 -45 10 35.70) will look like this .

By studying the above PRoVis plot and taking into account the MaxExpo chart (to see which pitch ranges will allow for maximum exposures of 40 ks or more), we can see that roll and pitch restrictions would allow for this monitoring observation to be feasible from July to September of 2010, when the roll fluctuates roughly between 190 and 115 and the pitch varies from 65, down to 60, and back up to 65.

3. Window Constraint

A window-constrained observation must take place within a specific time window, due to some time-critical aspect of the target. Read about other types of time constraints at Section 3.4.2 of the POG. Any proposer placing a window constraint on his or her observation must use PRoVis to check that this constraint does not force the target to be at bad pitch.

An example of a window-constrained observation is the coordination of Chandra time with another space mission, e.g. NASA's Deep Impact mission in July of 2005. The Deep Impact investigators wished to use Chandra's ACIS-S for spectroscopic imaging of comet 9P/Tempel 1 before, during, and after a 370-kg impactor collided with the comet.

Entering the coordinates of 9P/Tempel 1 in July 2005 (13 40 45.38 -10 11 40.59) should produce a plot like this (using 2010 as the year, since the plots change little from year-to-year).

From the plot, we see that the pitch is approximately 103 degrees, which, because of EPHIN temperature limitations (see Section 3.3.3 of the POG), imposes restrictions on the maximum exposures. Referring to the MaxExpo chart, we see that in July (the red dotted line), a solar pitch angle of 104 (for the July 4 impact event date) makes observations up to approximately 25ks possible.

By breaking the proposal into 35 observations of 7-10 ks each, between June 30 and July 24, this proposal was made feasible, even though the pitch was not ideal.

4. Uninterrupted Observation

If a proposal's science is dependent upon the exposure being uninterrupted, this places constraints on when and how Mission Planning can schedule the observation. Thus, the proposer should use PRoVis to determine how feasible it is to obtain the uninterrupted observation.

For example, to constrain both thermal and nonthermal coronal properties of a pole-on binary system, proposers wanted to simultaneously image the binary with Chandra, the VLA, and the VLBA. In addition, they required that the two 40-ks observations with Chandra (80 ks total) were each uninterrupted. Since this is not only an uninterrupted proposal, but also a joint proposal, there are two types of constraints to check.

Pitches that cause EPHIN temperature restrictions will probably not be able to accommodate two 40-ks uninterrupted observations; the MaxExpo chart shows how quickly the maximum exposure time drops below 40 ks when a target isn't at good pitch. The PRoVis Plot shows that the target resides at good pitch for a nice chunk of time from March 10 to April 8. This should make two 40-ks Chandra observations feasible, but whether the target can be observed at the VLA and VLBA in that window is another question for the proposer to address. For joint observations with ground-based optical telescopes, the Chandra observation is further constrained by whether the target is visible from the ground at a given time of year. Note that Chandra coordination with ground-based observatories other than NRAO is only available as a preference and will be carried out on a best-effort basis.

5. Triggering a TOO

Before triggering a Target of Opportunity (TOO), an observer must use PRoVis to check that the target is not at bad pitch. Since TOO's must be observed within either 0-4, 4-12, 12-30, or >30 days, there is an effective time constraint whenever a TOO is triggered. It is especially important to check that the TOO is feasible when the observation includes an additional constraint, e.g. the exposure must be uninterrupted.

For example, an observer may trigger a TOO when a nova, in outburst, is observed to turn into a luminous supersoft X-ray source with Swift. In addition, part of the science is dependent on obtaining an uninterrupted observation.

When we enter the coordinates of the nova, PRoVis produces this plot .

The proposer triggered this particular observation on December 16. We can see from the plot that the target was at good pitch roughly between November 30 and December 21. After December 21, EPHIN restrictions apply, which could prevent an uninterrupted observation, depending on the length. Refer to MaxExpo to find the maximum uninterrupted exposure time for a given pitch angle.

History

05 Jan 2009

Updated for Cycle 11