Chandra X-Ray Observatory (CXC)

Specific Help for Chandra Remote Proposal Submission

RPS provides a facility for filling the Chandra Observation Request forms. Electronic submission of forms and scientific justification is required.

Short descriptions of each form and field are below. This file is ordered by form (Cover, General, Target, Constraint). Form names are prefixed with * and field names are prefixed with **. Fields in this file are listed in the same order as found on the hardcopy forms, WWW forms, and the E-Mail talker forms.


* COVER PAGE

Your personal details (name, address, telephone number, etc.) and the proposal name and number of targets.

** Does this replace a previously submitted proposal for the current cycle?

Logical value indicating whether this proposal is a resubmission of a proposal previously submitted for the current Call For Proposals. The default is 'N'. Please only set this value to 'Y' if this proposal is being used to replace a proposal that was previously submitted for the CURRENT cycle.

On submission, a new number will be assigned to this proposal which should appear in your browser. You should then resubmit (upload) your replacement science justification using the new number, along with the separate, single page PDF file detailing Previous Chandra PI Programs (required if relevant) and PI CV (optional).

If you are replacing ONLY your science justification, then you can simply use the Upload Science Justification feature again without changing the proposal number. The latest justification (and if appropriate, Previous Chandra Programs and CV) PDF file(s) will supersede the previous file(s).

** If known, please enter the previous proposal number

If this proposal is a resubmission of a previous proposal, please enter the previously assigned proposal number. This will result in that previous proposal's removal. If unknown, please leave blank but contact us using the CXC Helpdesk or email cxchelp@head.cfa.harvard.edu.

** Principal Investigator Title

This item and the next 3 are combined on the hardcopy form to identify the Principal Investigator(PI).
PI title (Dr, Ms, Mr, etc.). This does NOT refer to one's job description (e.g., "Postdoc" or "Assistant Professor").
Maximum of 20 characters.

** First Name

PI first name.
Maximum of 20 characters. Required.

** Middle Name or Initial

Another name or initials of PI.
Maximum of 20 characters.

** Last Name

PI last name.
Maximum of 25 characters. Required.

** E-mail Address

PI E-mail address. An E-mail receipt will be sent to this address within 24 hours of the electronic submission of your proposal. Please make sure this is entered correctly.
Maximum of 50 characters. Required.

** Primary Institute

This is the primary PI Institute. To be eligible for funding (for either the PI or co-Is), a U.S. Institution MUST specified on the RPS form, and must be the primary institution of the investigator seeking funds.

Select an institute from the pull down menu, which should then appear in the Institute field. If not, use your internet browser's Edit, Copy and Paste functions to place your selection from the Institute list in the RPS window. If your institution is not on this list, just type the Institute in this field. A warning will be displayed when the RPS form is verified or submitted. This warning does NOT affect the submission of your proposal.
Maximum of 100 characters. Required.

** Address/Street

The first line of the Institute address, i.e., Street, any number within it, etc.
Maximum of 30 characters.

** Department

Department of PI at the Institute.
Maximum of 100 characters.

** Mail Stop

PI's mail stop at the Institute, if any.
Maximum of 30 characters.

** City/Town

Institute's Town or City.
Maximum of 30 characters.

** State/Province

The name of the state or province of the Institute.
Maximum of 30 characters.

** Zip/Postal Code

The Institute's post code, ZIP code or equivalent.
Maximum of 10 characters.

** Country

The default is USA.

Below is the list of accepted country designations:

Argentina Armenia Australia Austria
Belgium Brazil Bulgaria Canada
Chile China Czech Republic Denmark
Egypt Estonia Finland France
Germany Greece Hungary Iceland
India Indonesia Iran Ireland
Israel Italy Japan Korea
Latvia Lithuania Mexico Netherlands
Nigeria Norway New Zealand Peru
Poland Portugal Romania Russia
Slovakia South Africa Spain Sweden
Switzerland Taiwan Turkey UAE
UK Ukraine USA Venezuela

If your country is not on this list, please contact CXC HelpDesk
Maximum of 30 characters. Required.

** Telephone

PI telephone number, plus any extension.
Maximum of 30 characters. Required.

** Fax

PI Fax number, if available.
Maximum of 30 characters.

** Subject Category

The type of objects(s) to be viewed in the Proposal. Enter one of the following categories:
Solar System
Stars and WD
WD Binaries and CV
BH and NS Binaries
SN, SNR and Isolated NS
Normal Galaxies: Diffuse Emission
Normal Galaxies: X-ray Populations
Active Galaxies and Quasars 
Clusters of Galaxies
Extragalactic Diffuse Emission and Surveys
Galactic Diffuse Emission and Surveys
Required.

** Science Keywords

Please select three or more descriptive keywords pertaining to this proposal and/or to your science goals. Be inclusive; your selections may be used for preliminary matching of proposals to reviewers, and also for archive searches. Many of these keywords are in common with HST.

To select multiple items, click on each item while holding the Ctrl key. Browsers and keyboards may vary so try the Shift or Alt or Command keys if the Ctrl key does not work. For email users, the keywords must be separated by a semicolon (;).
Maximum of 255 characters. Required.

** Proposal Type

Choice
Description
GO General Observer
LP Large Project (> 300ks including slew tax)
TOO Target of Opportunity
TOO/LP TOO and Large Project
ARCHIVE Archive Request
THEORY Theory Request
GTO Guaranteed Time Observer
GTO/LP Guaranteed Time Observer, Large Project
GTO/TOO    Guaranteed Time Observer, TOO
CAL Calibration (Chandra personnel only)

RPS is used by all Chandra groups as the input to the observation database, so the Proposal Type is important. General Observers (GOs) should choose one of the GO, TOO, LP(GO and Large Project), TOO/LP(TOO and Large Project),Theory or Archive types as appropriate.

The CXC expects to award ~4 Msec of observing time to Large Projects as described in the Call for Proposal (CfP).

The Proposal Type of CAL is only to be used by CXC. No proposal from non-CXC personnel can be accepted that requests a Calibration observation. The Proposal Type of GTO is only to be used by members of a GTO team when submitting proposals using the time allocated to the GTO team.

Required.

** If archive/theory request, enter proposed budget

If this is an archive or theory request, please enter the total amount of the proposed budget. Units = $1000 (U.S. dollars).
Valid range is 1.0 to 1000.0 .

** Is this a multi-cycle observing proposal?

When scientifically well-justified, Chandra observing time for a target may be proposed to span up to 3 cycles. Only targets proposed in the current cycle may have observations extending into future cycles. Please refer to the information on Multi-Cycle Observing Proposals in the Chandra Call for Proposals and/or on the Proposer page: http://cxc.harvard.edu/proposer.

Multi-cycle proposals must request time for the current Cycle. TOO triggers cannot be proposed here for future cycles, though TOO followups may extend into future cycles. Up to 10% (5%) of the requested joint time may be allocated to Cycles 18 (19) if scientifically justified and subject to the continued availability of that joint time. Archive/Theory proposals cannot be multi-cycle. However, archival proposals can be linked with a multi-cycle observing proposal.

If multi-cycle observations are requested for a given target, the proposer must specify the observing constraints that require the observations to extend into future cycles. Multi-cycle observations may not be requested as a preference. Constraints must be well-justified scientifically. The PI must estimate based on these constraints the amount of time required in Cycle 18 and 19 for each such target, assuming the earliest feasible start date for the first target observations.

For accounting purposes, the cycles are defined below:

Cycle 17 from 01-Jan-2016 00:00 through 31-Dec-2016 23:59
Cycle 18 from 01-Jan-2017 00:00 through 31-Dec-2017 23:59
Cycle 19 from 01-Jan-2018 00:00 through 31-Dec-2018 23:59
The total observing time indicated for each of cycle 17, 18, and 19 will be tallied by RPS from the individual Target Pages and indicated on the RPS CoverPage. Total time requested for any proposal will be directly forwarded to the peer review, and (at least 90%) completed if the program is approved in its entirety. The estimates of the allotment of exposure time between this and future cycles are for accounting purposes only and will be specified in the ObsCat accordingly. Note that, as for all observations, scheduling considerations may result in actual observation dates outside of the cycle date ranges specified above.

The proprietary period for data from multi-cycle targets begins when 90% of the data for any given target (as allocated to each cycle) has been made available to the observer.

Required. Default is No.

** Is this proposal linked to another in this cycle ?

Logical value indicating that this proposal is linked to another proposal submitted for the current Call for Proposals. Two proposals in the same cycle which represent separate pieces of the same science project will be reviewed by the same panel if linked (e.g. archive/observing proposals to complete a sample).

** If known, please enter the proposal number of the linked proposal

If this proposal is linked with another proposal, please enter the proposal number assigned to the linked proposal. If unknown, leave blank.

** Proprietary Rights

The default is the standard 12 months for proprietary data rights. 'No proprietary rights' means that the data flows directly into the archive. Valid options are:
Standard (12 months) (default)
9 months
6 months
4 months
3 months
2 months
1 month
No proprietary rights
Required.

** Joint Proposals

Optional. The Joint Proposal section should ONLY be filled out if this is a joint proposal which also requests time on one or more of the facilities listed below. Please refer to the information on Joint Proposals in the Chandra Call for Proposals and/or on the Proposer page: http://cxc.harvard.edu/proposer. If proposing joint time for future cycles, include the total joint observing time request across all cycles here. The specific joint observatory requests by cycle must be described in the Remarks fields of the Target pages.

A small amount of observing time has been reserved in the programs of HST, NRAO, Spitzer, XMM, and Chandra to be awarded by the review panels of the other observatories Users may apply to HST, NRAO, Spitzer, or XMM and be awarded Chandra time and vice versa.

Those proposing for Chandra time in response to this call may also apply for time from the following facilities:

ObservatoryJoint Time Available
HST Maximum of 100 orbits available.
XMMMaximum of 400ks available.
SpitzerMaximum of 60 hours available, with no more than 20 to any single proposal.
SwiftMaximum of 300ks available.
NuSTARMaximum of 500ks available.
NOAOUp to 5% of the time on ach telescope available for the Joint opportunity. Details of telescope/instrument combinations available at a given time are provided on the web at: http://www.noao.edu/gateway/nasa/.
NRAO3% of the NRAO telescopes (max 5% in any one configuration): NRAO/VLA, NRAO/VLBA, and NRAO/GBT .

No Joint time will be allocated by the Chandra peer review without allocation of Chandra time except in the case of winning Archive proposals that request NOAO night(s).

Up to 10% and 5% of the available joint time in Cycles 18 and 19 respectively may be allocated to multi-cycle observing proposals if scientifically justified and subject to the continued availability of that time. If proposing joint time for future cycles, include the total joint observing time request across all cycles.

Note: If close coordination between space-based observatories is required, you should set the Must this observation be coordinated with that of another space-based observatory? option to Y, whether or not your current proposal requests joint time awarded through Chandra.

** Has this proposal already been allocated Chandra time by the HST, NRAO, Spitzer or XMM review panels?

Please use this field if this proposal has already been allocated Chandra time after review by HST, NRAO, Spitzer or XMM review panels. Please select the Observatory that awarded the Chandra time. You don't need to fill in any of the other Joint parameters if this proposal is simply a submission for Chandra time already awarded by another observatory. Valid observatories are HST, NRAO, Spitzer or XMM .

** For HST, proposed orbits

Enter the proposed number of orbits for HST. The maximum number to be allocated by the Chandra peer review is 100 orbits. This field is not required for proposals already approved by HST.
Required for all joint HST proposals reviewed by Chandra.

** For HST, desired instruments

Enter one or more HST instruments. After the successful SM4 repair mission in 2009, the HST instrument complement is WFC3, COS, STIS, ACS, NICMOS and FGS. Proposers should carefully consult the status of HST observing capabilities at http://www.stsci.edu/hst.

This field is not required for proposals already approved by HST.

Required for all joint HST proposals reviewed by Chandra.

** For XMM, enter the proposed exposure time(ksec)

Enter the proposed exposure time in kiloseconds for XMM. The maximum time allocated by the Chandra peer review is 400 ksec. This field is not required for proposals already approved by XMM.
Required for all joint XMM proposals reviewed by Chandra.

** For Spitzer, proposed hours

Enter the proposed hours for the Spitzer Space Telescope. The maximum time allocated by the Chandra peer review is 60 hours, with no more than 20 to any single proposal.
Required for all joint Spitzer proposals reviewed by Chandra.

** For Swift, enter the proposed exposure time(ksec)

Enter the proposed exposure time in kiloseconds for Swift. The maximum time allocated by the Chandra peer review is 300 ksec. Check the Swift webpage http://heasarc.gsfc.nasa.gov/docs/swift/swiftsc.html for details.
Required for all joint Swift proposals reviewed by Chandra.

** For NuSTAR, enter the proposed exposure time(ksec)

Enter the proposed exposure time in kiloseconds for NuSTAR. The maximum time allocated by the Chandra peer review is 500 ksec. Check the NuSTAR webpage http://heasarc.gsfc.nasa.gov/docs/nustar/nustar_prop.html .
Required for all joint NuSTAR proposals reviewed by Chandra.

** For NOAO, enter the proposed number of nights

Enter the proposed number of nights on available telescopes at NOAO. For hours of Gemini queue time, you may enter fractional nights, assuming 10 hours per night.
Required for all joint NOAO proposals reviewed by Chandra.

** For NOAO, enter the requested telescope/instrument combinations

Details of telescope/instrument combinations available at a given time are provided on the web at: http://www.noao.edu/gateway/nasa/.
Required for all joint NOAO proposals reviewed by Chandra.

** For NRAO, enter the proposed hours

Enter the proposed total number of hours for all NRAO telescopes/configurations/wavelengths.
Required for all joint NRAO proposals reviewed by Chandra.

** For NRAO, enter the requested telescopes

For NRAO, enter the requested telescope(s) from the pulldown list. Choices are GBT, VLA, VLBA. Multiple selections are allowed. To select multiple items, click on each item while holding the Ctrl key. Browsers and keyboards may vary so try the Shift or Alt or Command keys if the Ctrl key does not work. For email users, multiple telescopes must be separated by a comma(,).

Detailed technical information concerning the NRAO telescopes can be found at : http://science.nrao.edu/facilities. Include in your scientific justification a full and comprehensive scientific and technical justification for the requested NRAO configuration(s) and observing time.

** Proposal Title

The title of the proposal.
Maximum of 120 characters. Required.

** Abstract

The abstract. Maximum of 800 characters. Abstracts exceeding this limit will be truncated. Required.

NOTE: LaTeX Special Characters The RPS processor prepends all LaTeX special characters, such as $ % # \ with a backslash (\) when generating the LaTeX file. When this file is run through the LaTeX processor, the special characters will be printed as they were entered. If these special characters are intended as LaTeX markups (i.e., a math environment delimited by dollar signs in the abstract field), the prepended backslashes must be removed by editing the LaTeX file before the file is LaTeX'd. Making changes elsewhere in the form will create a discrepancy between the electronically submitted proposal and the LaTeX form.


* GENERAL FORM

For details of any collaborators, etc. Up to 15 Co-Investigators are allowed. All investigators listed on the RPS form will receive an email after the submission deadline containing basic information such as proposal number, PI, co-investigators, proposal title, and abstract.

If the number of co-investigators is greater than 15, please set the Are there additional Co-Is listed in the science justification? field to 'Y' and include the additional names, addresses, etc. in the Scientific Justification. Additional Co-I lists which are too long to fit into the science justification may be included within the (1) page allowed for previous Chandra projects.

Please select the institute from the Institute List provided in RPS. All fields are optional apart from the printed form requiring the name of an administrator at your institution. For Cost Proposals, the printed form must be signed by both the proposer and an administrator of her/his institution. If you are using the Web, a wide browser window will avoid form entry fields wrapping to new lines.

** Co-Investigator First Name

First Name for each Co-Investigator. Maximum of 20 characters.

** Co-Investigator Last Name

Last Name for each Co-Investigator. Maximum of 25 characters.

** Co-Investigator E-Mail Address

E-Mail address for each Co-Investigator . Maximum of 50 characters.

** Co-Investigator Institute

For a Co-I to be eligible for funding, their U.S. Institution must specified on the RPS form, and must be the primary institution of the investigator seeking funds.

Institute for each Co-Investigator. Maximum of 100 characters.

** Co-Investigator Country

For non-US Co-Investigators, please read Appendix C of the CfP. Below is the list of accepted country abbreviations:

Argentina Armenia Australia Austria
Belgium Brazil Bulgaria Canada
Chile China Czech Republic Denmark
Egypt Estonia Finland France
Germany Greece Hungary Iceland
India Indonesia Iran Ireland
Israel Italy Japan Korea
Latvia Lithuania Mexico Netherlands
Nigeria Norway New Zealand Peru
Poland Portugal Romania Russia
Slovakia South Africa Spain Sweden
Switzerland Taiwan Turkey UAE
UK Ukraine USA Venezuela

If the country is not on this list, please contact CXC Help Desk
Maximum of 30 characters.

** Are there additional Co-Is listed in the science justification?

Logical value indicating that there are more than 15 Co-Is for this proposal. Additional Co-Is should be listed in the Science Justification for this proposal. Additional Co-I lists which are too long to fit into the science justification may be included within the (1) page allowed for previous Chandra projects.

** Is the first Co-I doing observing, rather than the PI?

Logical value indicating if the first Co-I listed is also the person who will primarily carry out the observations. This should be used for PIs who may be difficult to reach and for situations when a graduate student or postdoc is to be considered the "real" PI. The default is 'N'.

** Observing Investigator: Telephone

If the Co-I is doing the observing, enter the telephone number of the Observing Investigator. Maximum of 24 characters.

** Were you PI on any previously approved Chandra programs?

Logical value indicating the PI has had a Chandra proposal(s) approved in a previous cycle(s).
The PI must provide a list of selected previous Chandra Observing, Archival Research, Theory/Modeling, or GTO programs for which they were PI along with a brief status of the program(s) and resulting publications (1 page maximum). A webtool for searching the CXC approved proposal database by PI Name, Chandra cycle, proposal number, etc. is available at http://cxc.harvard.edu/soft/propsearch/prop_search.html.
Omit this page if there are no such programs.

To find Chandra-related papers of yours that are already recognized as such, you can search ADS using http://adsabs.harvard.edu/abstract_service.html as follows:

  1. Type your name in the "Authors" box near the top
  2. Scroll down under FILTERS
  3. Optionally, under "Select References From:" click "All refereed articles"
  4. Under "Select References In:" click "All of the following groups"
  5. Check the "Chandra" box, and then
  6. Scroll until you find and push the Send Query button.

If there are Chandra-related publications of yours not retrieved in this fashion, please email the information to arcops@head.cfa.harvard.edu

We encourage all users to provide material within their publications to facilitate this tracking. Details are described at http://cxc.harvard.edu/cdo/scipubs.html.

**If PI is not based in USA and proposal has USA Co-Is, which Co-I will be the Cost PI?

This field is only needed if the P.I. of the proposal is not based in the USA but one or more of the Co-Investigators are based in the USA. Please identify which USA Co-I will be the Cost PI by entering the Co-Investigator entry number in this field.

* TARGET FORM

The details that need to be filled in for each different target.

** Do you want to delete this target?

The default is 'N'(No). The default should be changed only if a particular target is to be removed. A target is deleted by setting this parameter to 'Y'(Yes) and clicking on the "Delete Target" button at the top or bottom of the RPS form. Please note that when a target is deleted, the remaining targets will need to be re-numbered accordingly so that there is no missing number.

** Target Number

The number of the target. Since the number is used to show the Peer Review the observing priority of one target relative to another, you may wish to change these around. However, the final proposal must contain a sequence of target numbers from 1 to the total number of primary targets. Valid range is 1 - 999. Required.

** Target Name

Targets are searched in the database by common name which should be used as the name (NGC 4051). In the absence of a common name, please use IAU-sanctioned names. *Append* any additional target info (e.g., NGC 4051 field 2).

The Target Name/Coord button at the top of the RPS form provides the results of the SIMBAD/NED coordinate check for the target names you entered, if available.
Maximum of 30 characters. Required for all except Solar System Object

** Solar System Object

The name of the Solar System Object to be observed, from the following choices: None, Asteroid, Comet, Earth, Jupiter, Mars, Moon, Neptune, Pluto, Saturn, Uranus or Venus.

The default is 'None'. Observations of moving solar system objects are made with a sequence of pointed observations, with the object moving through the field of view during each dwell period. The sequence of pointings will be derived from the object ephemeris to ensure that the object remains within 5' of the Chandra line-of-sight. Most solar system objects move slowly enough so that a single pointing will suffice. Should your observation be selected then the CXC will work with you to produce an observation that both meets your scientific objectives and optimizes the use of Chandra.

** Is target position known and fixed?

Logical value indicating target position is known for this target. Modify value to 'N' if target position is unknown for this TOO or Solar System Object.

** R.A.

The Right Ascension of the source in mandatory J2000 coordinate system at the current epoch. Offsets from this position may be specified using the Y/Z Detector Offset field. The standard format is HH MM SS.S - hours, minutes, seconds, separated by spaces. Alternatively, it may be entered as degrees (DDD.DDDDDD), in which case it will be converted to sexagesimal during verification. The seconds may be entered as a real value with tenths (i.e., SS.S).
Required, except for Solar System Objects and TOO's of unknown position.

** Dec.

The declination of the source in mandatory J2000 coordinate system at the current epoch. Offsets from this position may be specified using the Y/Z Detector Offset field. The standard format is +/-DD MM SS.S - sign, degrees, arcminutes, arcseconds, separated by spaces. Alternatively, it may be entered as degrees (+/-DD.DDDDD), in which case it will be converted to sexagesimal during verification. If no sign is given it will be assumed to be positive.
Required, except for Solar System Objects and TOO's of unknown position.

** Is the observation (part of) a grid?

Logical value indicating whether this target is part of a grid of pointings. The default is 'N'. The observer is advised that there will be a reduction in the slew tax charged for a series of contiguous or nearly contiguous pointings each separated by no more than a degree from its nearest neighbor (a grid), provided that there is no instrument set-up or observing mode change. Proposer MUST provide a detailed description of the grid positions (preferably a figure) in the science justification. Please refer to the CfP http://cxc.harvard.edu/proposer/CfP/ for details.

Grids may be entered as separate targets. Alternately, for a large number of pointings with identical observing parameters, you may specify all pointings by entering the grid center (the average coordinates of all grid pointings) in the R.A. and Dec fields above, and then also specifying the 3 general grid parameters below. This shortens and simplifies the proposal, but still allows target duplication checks and proper accounting of time and targets at peer review. Approved programs will be required to provide exact pointings within the grid to the CXC.

** Unique Grid name

A unique grid name allows the pointings in a grid to be more easily associated, scheduled, or searched as an ensemble in the CXC database. Required for all pointings intended to be part of a grid. Maximum of 30 characters.

** Number of grid pointings

The total number of grid pointings. Input of this datum indicates that the proposer wishes to use the parameterized generation of grid pointings for proposal purposes, rather than individual target pages. Default is blank. If grid parameters are used, the minimum value is 2.

** Distance from center to farthest grid pointing (degrees)

Distance in degrees between the center (average) grid coordinates entered in the R.A. and Dec fields above, and the intended pointing that is farthest from that center. Maximum value is numerically equal to the number of pointings.

** Offset Pointing (Y/Z Detector Target Offset )

The user may wish to offset-point the observatory pointing for a number of reasons, e.g., to reduce the effects of ACIS pile-up or to avoid HRC pore limits by blurring the image. Offset pointing is discussed in section 3.2 of the Proposer's Observatory Guide(POG) .

In general however, most observers/proposers should leave BLANK all detector offsets in RPS if they wish their target to be close to the optical axis (best focus position). For either ACIS-I or ACIS-S, the unadjusted aimpoint (target position) falls 10 - 20 arcsec from the optical axis. To reduce this difference, a default offset is added to every ACIS observation if both the ACIS Y- and Z- detector offsets are left blank in RPS.

A positive Z offset moves the target from ACIS-I towards ACIS-S. A positive Y offset moves the target from chip S3 towards chip S2. (see POG Figure 3.1). Note the 180 degree difference between the Y/Z coordinates and the Delta-Y/Delta-Z coordinates. Section 6.10 of the POG discusses the previous ACIS aimpoints and offsets in detail.

Note that the RA and Dec of the optical axis will depend upon the spacecraft roll angle at the time of the observation. If the observer wants the optical axis at a particular RA and Dec with a YZ target offset, then the observer must specify a roll constraint.

All units are arcmins. The overall valid range is -50.0 to +50.0 for (y,z) offsets. Thus it is possible to specify an offset so large that the target is not imaged anywhere on the detector, so exercise caution. Furthermore, if the target is offset by more than 15 arcmins, then ghost images (see POG Chapter 4) from the target may be visible.

Finally, offsets are implemented in software by redefining the pointing position. This means that roll constraints apply at the new position.

Y Pointing Offset:
Sense: negative Y offset moves the target away from the aimpoint in the direction of S4 on ACIS-S (ie. further onto the S3 chip)

Z Pointing Offset:
Sense: positive Z offset moves the target towards the readouts in ACIS-S (i.e. away from ACIS-I)

Recommendations: The default values (used if the field is left blank) are instrument dependent. Units are arcmin.

Default offsets for both ACIS-I and ACIS-S imaging, effective 15 Oct 2013, are

           Y      Z
---------------------
 ACIS-S  +0.00  -0.30
 ACIS-I  -0.30  -0.30
Any numeric value entered in the box will override the default values.

Proposers/observers who require specific offsets from the default aimpoint should enter into RPS Y,Z offsets in arcmin relative to the new aimpoint . This is most likely to affect gratings observers who wish to optimize the position of chip gaps along the spectrum of their source.

Further details are available in the POG at http://cxc.harvard.edu/proposer/POG/html/.

WARNING: It is quite possible to specify an offset so large that the target is not imaged anywhere on the detector, so exercise caution. To make sure your target is placed as desired, we recommend use of the Observation Visualizer(ObsVis) available in the latest CIAO downloadable package at http://cxc.harvard.edu/ciao/download. Note that RPS software forbids entry of offsets larger than 10/30/20/50arcmin for ACIS-I/ACIS-S/HRC-I/HRC-S.

** SIM Translation Offset

Offset from nominal translation position. This is a motion of the SIM and thus the aimpoint away from the default position on the detector along the z-axis (which is along the axis from ACIS-S to ACIS-I).

Warning: The standard sub-arrays DO NOT take into account these recommended offsets. Thus if you wish to use a sub-array in conjunction with one of these offsets, you will need to specify it explicitly as a custom sub-array. For recommended values please see the web pages: http://cxc.harvard.edu/cal/Letg/ACIS_params for recommended offsets for LETG/ACIS-S gratings observations and http://space.mit.edu/ASC/calib/hetgsubarray.html for the HETG.

Units are in millimeters.

Sense: a negative motion moves the aimpoint (and the target) towards the 
       readouts on ACIS-S (ie. away from ACIS-I)

Units: mm (scale 2.93mm/arcmin)

Default Values:

Configuration  Mode  SIM z(mm)  SIM z (arcmins)  SIM z (motor steps)*
----------------------------------------------------------------------------
HETG+ACIS-S     TE   -3         -1.02389         -1193
HETG+ACIS-S     CC   -4         -1.36519         -1591
LETG+ACIS-S     TE   -8         -2.73038         -3182
LETG+ACIS-S     CC   -8         -2.73038         -3182

Valid values by detector are:

Detector   Minimum   Maximum
-----------------------------
HRC-S     -12.5439   61.3518
HRC-I     -61.3518   126.621
ACIS-S    -190.500   22.5685
ACIS-I    -22.5685   27.4739

** Do you want optical monitor data for your target?

Logical value indicating whether optical data from the aspect camera is requested for this observation. The default is 'N'.

The proposer should be aware that the aspect camera is NOT optimized for optical monitoring. Please see the Proposer's Observatory Guide for the limitations on the photometry and the expected signal-to-noise ratios (chapter on Aspect system ).

The use of one of the guide-star channels as an optical monitor will be subject to peer review. The degradation of the aspect solution may lower the usefulness of the archive of the field. This will be weighed with the scientific value of the optical data.

** V Magnitude of Target

Specify the V magnitude of the target if the use of the optical monitor is desired. Valid range is -15.0 - 20.0. Required if optical monitor flag is set to "Y"

** Total Observing Time

The total exposure time in kiloseconds for requested observation(s) of this target. For monitoring observations or grids, this is the sum of all pointings. For example, for two observations of 40 kiloseconds each, specify 80 kiloseconds as the Total Observing Time and 2 for the Number of Observations in the 'Constraints' section.

Individual exposures may need to be segmented. If an observation that is uninterrupted (or at worst contiguous across orbits) is required, proposers must set the Uninterrupted constraint flag.

Observations >180 ksec will have to be interrupted due to the satellite orbit. If the Uninterrupted Observation Required flag is checked, the pieces will be observed as contiguously as possible, and certainly in adjacent spacecraft orbits.

Valid range for an observing proposal is 1 - 10000 kiloseconds.

** Multi-Cycle Targets: Projected Observing Time for Future Cycles

If multi-cycle observations are requested for a given target, the proposer must specify the observing constraints that require the observations to extend into future cycles. Multi-cycle observations may not be requested as a preference. Constraints must be well-justified scientifically. The PI must estimate based on these constraints the amount of time required in Cycle 18 and 19 for each such target, assuming the earliest feasible start date for the first target observations. For accounting purposes, the cycles are defined below:
Cycle 17 from 01-Jan-2016 00:00 through 31-Dec-2016 23:59
Cycle 18 from 01-Jan-2017 00:00 through 31-Dec-2017 23:59
Cycle 19 from 01-Jan-2018 00:00 through 31-Dec-2018 23:59
The proprietary period for data from multi-cycle targets begins when 90% of the data for any given target (as allocated to each cycle) has been made available to the observer.

** Detector

Specifies which detector will be on the optical axis during the observation. The choices are: ACIS-S, ACIS-I, HRC-S or HRC-I. See the HRC and ACIS chapters of the Proposer's Observatory Guide for the aim point locations.

The target coordinates, including any specified offsets, will be placed at the aim point of the selected detector. Note a user should use the offset parameters (above) to move the target away from the nominal aim point should this be desired.

Nominal aim points:
    ACIS-I:  aim point on chip I3
    ACIS-S:  aim point on chip S3, +.1667 arcmin Y offset
    HRC-I :  Detector center
    HRC-S :  1.3 arcmin from detector center to minimize effect of MCP
             boundaries

** Grating

Specifies which grating to use. Grating options are NONE, HETG, and LETG. The default is NONE which specifies no grating (direct imaging). You should use ACIS-S with the HETG and HRC-S with the LETG, unless you make a case otherwise in your proposal.

** Source Count Rate

The Source Count Rate box must be filled in by all users. For detectors without gratings, this count rate is the source count rate in counts per second. For ACIS-S+grating or HRC-S+grating, this count rate is the zero-order count rate in counts per second. All count rates are to be specified as observed (not pile-up corrected).

For variable sources, supply the maximum expected count rate. This will allow for consistency checking of requested observation mode(s). The PIMMS tool can be used to calculate count rate.
Required.

** 1st Order Count Rate

The 1st order count rate entry should be filled in ONLY for those GOs who choose to use ACIS-S+grating or HRC-S+grating. The units are counts per second. All count rates are to be specified as observed (not pile-up corrected). Required for all observations that use gratings.

** Total Field Count Rate

This item requests the count rate across the field of the detector. This rate should include the total background (see the Proposer's Observatory Guide instrument chapters) as well as nearby sources. Units are counts per second. All count rates are to be specified as observed (not pile-up corrected).

** Is target an extended source ?

Select Y if most of the source count rate above comes from extended emission. The default is `N'.

** HRC Parameters

** HRC Timing Mode

Observers who wish to perform timing studies with the HRC should select this mode. This timing mode for HRC consists of using the HRC-S detector in what is called the Imaging Mode. In this mode, only the center segment of the HRC-S is active. The overall detector background is currently about 50 counts/sec (this is because of the overall background reduction associated with high solar activity reducing the Cosmic Ray flux). Sources with rates up to the telemetry limit (184 counts/sec) can be observed with no lost events and fully correct times. It is not advisable to look at very bright sources that actually come within about 10-15% of the telemetry limit to avoid the occasional statistical fluctuations that might cause the loss of some events. It is also not advisable to look at very strong point sources due to count rate limitations on the HRC (for HRC-S this is about 20-30 counts/sec).

* ACIS Parameters

This section contains the details for any observation which proposes to use the ACIS. ACIS has a large number of possible observing modes. The GO is urged to become familiar with each mode prior to specifying the details of the proposed observation.

* ACIS Required Parameters :

For faint sources (~< 0.01 cps), these are the only parameters that must be set.

** Exposure Mode

The exposure mode for ACIS for which two choices are possible: Timed Exposure (TE) or Continuous Clocking (CC). The default is TE. The CC mode may be used for bright, isolated sources to mitigate pileup. Please refer to the Proposer's Observatory Guide for more information.
WARNING! CC MODE WILL NOT RESULT IN AN IMAGE.

**Event Telemetry Format

Event Telemetry Format controls the packing of the data into the telemetry stream. This is similar to Bit Mode for ASCA. The default value is F(Faint).
Choice Format Exposure Mode Description




FFaintTE,CCreturns (x, y) position of event, energy, time-stamp + values of pixels in the 3x3 region surrounding event
VFVery FaintTEsame as above, except surrounding region is 5x5 pixels in size
GGradedTE,CCreturns (x, y) position of event, energy, time-stamp + Grade of pixels in 3x3 region

** CCDs On

                   I0  I1
                   I2  I3
            S0  S1 S2  S3  S4  S5

The ACIS CCD chip layout is as pictured. ACIS can read out a maximum of 6 chips. Each required chip should be set to 'Y', up to a maximum of 5.

If a chip is desirable, but the primary science could still be accomplished without it, please identify that chip as optional so that the CXC can optimize scheduling given thermal operating constraints. This is accomplished by specifying Off# (instead of 'Y' or 'N'), where # represents the turn-off order of the optional chips selected, i.e., if thermal constraints dictate that one of your selected optional chips be turned off, that will be Off1. If two must be turned off, then both Off1 and Off2 will be turned off.

The CXC recommends that you specify no more than 4 required CCDs ("Y" = required) if your science objectives can be met with 4 or fewer CCDs. If 4 CCDs are specified as required, the GO may specify 1 or 2 optional CCDs to bring the total of required plus optional CCDs to 5 or 6 CCDs, but the GO should be aware that optional CCDs may be turned off once the thermal environment is known at the time the short term schedule is generated. GOs may still request 5 CCDs as required, but they should only do so if their science objectives require 5 CCDs. GOs may still request a total of 6 CCDs, but only 5 CCDs may be required and one CCD must be optional. If the science requires 6 CCDs, proposers should state this in the Remarks field. Chips set to 'N' will not be used for the given observation.

Values are:
In summary,
  min 1, max 5 chips may be required (selected as 'Y')
  min 0, max 5 chips may be optional  (selected as 'Off#')
  max 6 chips total may be turned on (Y + Off#)
  min 4, max 9 chips may be turned off  (selected as 'N')
A description of optional chips, including motivations and some recommended chip sets can be found in the ACIS chapter of the POG.

**I have reviewed the selection of ACIS chips and identified any chips whose operation is optional

Logical value indicating that you have reviewed your ACIS chip selection. This field is required if 5 or more chips have been selected and no optional chips have been identified.

**What is the maximum number of counts you expect in any of the spectra you will analyze from this observation?

Total maximum expected number of counts for any spectrum to be scientifically analyzed from this observation. Default is blank. Input is required for any ACIS-I non-grating observation. Valid range is 1 - 100000.

**Do you expect to analyze more than 2 resolved spectral lines in that spectrum?

Logical value indicating whether or not more than 2 resolved spectral lines are expected in the brightest spectrum to be analyzed from this observation. Default is blank. 'Y' or 'N' is required for any ACIS-I non-grating observation. Both the two questions above are asked to trigger assessment of the sensitivity of ACIS-I imaging observations to gain calibration. Science from high S/N ACIS-I imaging spectroscopy (no gratings) with rich spectra may be affected by thermally-induced gain drifts. As spacecraft/environment/analysis evolves, CXC may determine that appropriate scheduling (treated as a preference, not as a constraint) can minimize such thermal impacts.

*ACIS Optional Custom Parameters:

The custom parameters are available so users can mitigate the effects of pileup and avoid exceeding the telemetry saturation limit.

Parameters that affect PILEUP :

** Use most efficient frame exposure time?

Logical value indicating use of the most efficient values for the CCD Frame exposure time. If you do not wish to use the default most efficient values, please enter the exposure time in the CCD Frame exposure time field. 'Y' is required for CC exposure mode. The default is 'Y'.

** CCD Frame Exposure Time

The CCD frame exposure time is the fundamental unit for ACIS . It ranges from 0.0 to 10.0 seconds in 0.1 second increments. The default frame time is 3.2 seconds.

Responding with a `Y' to the question `Use most efficient frame exposure time?' allows the ACIS team to adjust the CCD frame time as necessary. The user may override that freedom by specifying a CCD frame time. Note that an entire CCD takes 3 seconds to read, so a 0.2 second frame time has a small observing efficiency which the proposer must justify. A shorter frame time can aid in mitigating pileup by a factor of up to 8. A shorter frame time is most easily achieved by the use of a Subarray.
Valid values: 0.0 to 10.0 seconds in 0.1 second increments depending on the number of active CCD's. The minimum times depend on the number of CCDs as follows:

1 or 2 CCDs	- 0.1 second
3 or 4 CCDs	- 0.2 seconds
5 or 6 CCDs	- 0.3 seconds

** Subarray Type

Choices are: None, 1/2, 1/4, 1/8 and Custom

A subarray is a reduced region of all of the active(turned on) CCDs that will be read. A reduced region may also help to reduce the effects of pulse pile-up. The first box indicates whether the proposer intends to use the subarray capability.
Valid only for TE exposure mode. The default is 'None'.

PLEASE ENSURE THAT YOUR TARGET FALLS WITHIN THE CHOSEN SUBARRAY (e.g., use the Observation Visualizer(ObsVis) available in the latest CIAO downloadable package at http://cxc.harvard.edu/ciao/download)

Note that the minimum Frame Time depends on the size and location of the subarray. Read the ACIS chapter of the Proposer's Observatory Guide(POG) for more information.

The standard subarrays can be selected to avoid pileup approximately by the factor of the subarray size. The standard subarrays for ACIS-I use the values as listed in the table. For ACIS-S, the starting rows differ because of the different position of the aimpoint relative to the readout node. The ACIS chapter of the POG Guide contains a schematic of the locations of the default Subarrays.

                     ACIS-I                       ACIS-S 
   Standard Size    Start Row     No. of Rows    Start Row  
   -------------------------------------------------------
       1/2            513            512           257 
       1/4            769            256           385 
       1/8            897            128           449 

** Subarray: Start Row

The starting row that will be read for processing custom subarrays.
Valid range is 1 - 925.

** Subarray: No. Rows

The number of rows that will be read for processing custom subarrays. A minimum of 128 rows is required if multiple ACIS chips are selected. A minimum of 100 rows is required is a single ACIS chip is selected..
Valid range is 100 - 1024.

** Alternating Exposure Readout: Use Alternating Exposure Readout

Logical value indicating use of alternating exposure readout.
Valid only for TE exposure mode. The default is 'N'.

Alternating Exposure Readout observation sets the number of SECONDARY exposures that will follow each primary exposure. If n = 0, only primary exposures are used. A deadtime will result from the short exposure since the electronics still require 3.2 sec to process the full frame. Therefore, to minimize the deadtime, the number of short exposures should be kept to a minimum. The fraction of time during which data are taken is the ratio of the selected frame time to the sum of this and the nominal frametime: e.g. for a new frametime of n (<3.2) secs, the fraction of time during which data are taken is n/(3.2+n). Note the minimum on the primary exposure is 0.2 sec. Times longer than 3.2 seconds are discouraged until operational experience exists.

An example is useful. Suppose you want to sample the image in a repeated cycle of 4 exposures with a primary exposure time of 0.3 sec. If all 6 CCDs are active the secondary exposure time will be 3.2 sec. The resulting sequence of exposures will be 0.3 sec, 3.2 sec, 3.2 sec, 3.2 sec, 0.3 sec, 3.2 sec,. etc. until the total requested observing time is used.

** Alternating Exposure Readout: Number of Secondary Exposures

The number of secondary exposures that will follow each primary exposure. If n = 0, only primary exposures are used. Read the ACIS chapter of the Proposer's Observatory Guide for an estimate of the efficiency.
Valid range is 0 - 15.

** Alternating Exposure Readout: Exposure Time for Primary Cycle

The primary exposure time in tenths of seconds. The recommended time for a non-zero number of secondary exposures is 0.3.
Valid times:        n=0 :  T-p = 3.2 sec
             non-zero n :  T-p = 0.2 - 10.0 sec

Parameters that affect TELEMETRY :

Before event candidates are written to telemetry, they are subjected to three sets of filters, each of which can cause them to be rejected. The filters can reject events by their grade code*, by their energy, and by their spatial location on the CCD array. The order in which these filters are applied is unimportant.

* At the present time, the proposer cannot change the set of grade codes to be rejected by the on-board grade filter; they were chosen to exclude only those event candidates that are almost certainly not caused by target X-rays. This is discussed in the Non-X-ray Background section of the Chandra Proposer's Guide.)


** Energy Filter: Use Energy Filter

All event candidates from all CCDs are filtered by energy before they are packed into the telemetry stream. This does not affect pulse pileup: it only reduces the telemetry. When this field contains 'N', the filter rejects only those events with energies below 0.24 keV for ACIS-S and below .36 keV for ACIS-I. The filter also rejects those events with energies above (the lower threshold + 13 keV).

When the field contains 'Y', the proposer gets to specify more restrictive values of Lower Energy Threshold and Energy Filter Range. (Note: additional energy filtering may be applied to events that fall within particular spatial windows, as described below. Such events will be rejected if they fail either filter.)

** Energy Filter: Lower Energy Threshold

Event candidates will be rejected if their energy lies below this value.
Units are keV; the valid range is 0.24 - 15.0 keV.
For ACIS-S the minimum threshold is 0.24 keV
For ACIS-I the minimum threshold is 0.36 keV
ACIS is insensitive to X-rays below these energies.

** Energy Filter: Energy Filter Range

Event candidates will be rejected if their energy lies above (Lower Energy Threshold + Energy Filter Range).
Units are keV; the valid range is 0.1 - 15.0 keV.
The effective area of the Chandra mirrors above 10 keV is essentially zero, but X-ray pileup can result in event candidates with energies above 10 keV.

** Use Spatial Windows?

By setting this field to 'Y', the user can specify one or more spatial window filters -- rectangular regions on specific chips -- within which event candidates can be rejected according to their energy or to their frequency of occurrence. The use of spatial windows does not affect the way the CCD is read out, so there will be no impact on event pile-up. Spatial windows will reduce the telemetry volume by removing event candidates.

As many as six spatial windows may be specified for each chip. If windows overlap, the order in which they are defined in the RPS form is important: for each event candidate centered at (CHIPX=x, CHIPY=y), the on-board software examines all spatial windows defined for that chip, in the order specified in the RPS form, lowest index first, and decides whether to reject the event based on the parameters in the first window that contains that (x,y). If the event lies outside all windows, it will not be rejected by the window filter.

If more than 3 spatial windows are desired, use the Additional Spatial Windows text field to define their parameters.

BE SURE TO CHECK THAT YOUR TARGET FALLS WITHIN THE CHOSEN WINDOWS (Hint: use ObsVis, the Observation Visualizer, distributed with the CIAO package from "http://cxc.harvard.edu/ciao/download/".

Example:

Three rectangular areas are defined on the S3 chip: window #1 accepts all events that fall within its bounds with energies from 0.1 to 10.0 keV; window #2 accepts one out of two events within its bounds, provided they are not within the overlap with window #1 and provided they are in the energy range 0.3 to 10.0 keV; the third window covers the entire CCD and rejects all events that are not within the areas covered by the other windows.

Window
Order
Chip
ID
Sampling
Frequency
Starting
Column
Column
Width
Starting
Row
Row
Height
Lower Energy
Threshold
Energy
Range
1 S3 1 200 500 400 500 0.1 9.9
2 S3 2 500 400 200 400 0.3 9.7
3 S3 0 1 1024 1 1024

1024










Window 1







Window 2


Window 3



S3
CHIPY
0

0          CHIPX 1024

** Spatial Window: Order

The index of this spatial window: if a chip's spatial windows overlap, the window with the lowest index determines how events falling within the overlap region are to be filtered. Valid values are: 1-36.

** Spatial Window: Chip

The ACIS chip on which this spatial window is defined.
Valid values are: I0,I1,I2,I3,S0,S1,S2,S3,S4,S5.
This parameter is required for all spatial windows.

** Spatial Window: Sample Rate

It determines what fraction of the events are to be accepted* by the spatial window filter, i.e.,

0 All of the events falling within the window are rejected.
1 All of the events falling within the window are accepted, provided they meet the energy threshold and range criteria*.
n Every nth event falling within the window is accepted, provided it meets the energy threshold and range criteria*; the remainder are rejected.

*  acceptance by the spatial window filter is no guarantee that the event will be output to the telemetry stream -- it may be rejected by the grade filter or the overall energy filter.

This parameter is required for all spatial windows.
Valid values are 0-255.

Examples:

  1. Accept every third event in a 100-row band centered near the suggested aimpoint of the S3 chip (CHIPX=215, CHIPY=497), discarding all other S3 events.

    Window
    Order
    Chip
    ID
    Sampling
    Frequency
    Starting
    Column
    Column
    Width
    Starting
    Row
    Row
    Height
    Lower Energy
    Threshold
    Energy
    Range
    1 S3 3 1 1024 447 100

    2 S3 0 1 1024 1 1024

    Note that this operation required two windows for the S3 chip: the first to accept one-in-every-three events falling within the band, the second to reject all events outside the band. Since neither "Lower Energy Threshold" nor "Energy Range" was defined for either window, they default to 0.08 keV and 13.0 keV, respectively, unless 'Y' was selected for Energy Filter: Use Energy Filter, in which case, the Energy Filter: Lower Energy Threshold and Energy Filter: Energy Filter Range values will be used.

  2. Accept every fifth event with energy less than 10keV falling within a 100-by-100 pixel square centered on the zeroth order aimpoint in a grating observation; retain all events falling outside that area.

    Window
    Order
    Chip
    ID
    Sampling
    Frequency
    Starting
    Column
    Column
    Width
    Starting
    Row
    Row
    Height
    Lower Energy
    Threshold
    Energy
    Range
    1 S3 5 226 100 447 100 0.1 9.9

    Note that this operation required only one S3 window since the filter will not reject any event falling outside the defined window area(s).

** Spatial Window: Start Column

The first column of the rectangular area that is to be filtered.
This parameter is required for all spatial windows.
The valid range is 1 - 1023.

** Spatial Window: Width of Window

The number of columns in the rectangular area that is to be filtered.
This parameter is required for all spatial windows.
The valid range is 1 - 1024.

** Spatial Window: Start Row

The first row of the rectangular area that is to be filtered.
This parameter is required for all spatial windows in TE mode. In CC-mode, it will be ignored.
The valid range is 1 - 1023.

** Spatial Window: Height of Window

The number of rows in the rectangular area that is to be filtered.
This parameter is required for all spatial windows in TE mode. In CC-mode, it will be ignored.
The valid range is 1 - 1024.

** Spatial Window: Lower Energy Threshold

Discard all events within this window whose energies are less than this value. The units are keV.
The valid range of this parameter is 0.08 - 15.0 keV.
If omitted, the value will depend on the choice of Use Energy Filter in the preceding section. If 'Y', its Energy Filter: Lower Energy Threshold value will be used for the window; otherwise, the window's Lower Energy Threshold value will default to 0.08 keV.

** Spatial Window: Energy Range

The range of event energies to be accepted, i.e., events with energies above (Lower Energy Threshold + Energy Range) will be rejected. The units are keV.
The valid range of this parameter is 0.1 - 15.0 keV.
If omitted, the value will depend on the choice of Use Energy Filter in the preceding section. If 'Y', its Energy Filter: Energy Filter Range value will be used for the window; otherwise, the window's Energy Range value will default to 13.0 keV. Note that the effective area of the mirrors above 10 keV is essentially zero, but pileup can cause multiple photons of lower energy to register as single events with energies above 10 keV.

** Additional Spatial Window definitions

Additional spatial window filters may be defined in this text box, one per line, using the same (comma-delimited) fields as in the table structure, viz., window order (4-36), chip ID (I0-S5), sampling frequency (0-255), starting column and width, starting row and height, lower energy threshold (0.08-15.0 keV), and energy range (0.1-15.0 keV). If your proposal is approved, the CXC will enter this additional data in the Observation Catalog. Up to 6 windows may be specified for each chip, for a total of no more than 36 spatial windows.
This field is limited to a maximum of 800 characters, including commas and line feeds.


* CONSTRAINTS

This section contains the details for any time critical observation. The constraints may be required (Y) or preferred (P).

If any constraint is required, the observation is considered time constrained and will be subject to the limits set for the number of approved constrained observations during the Chandra Peer Review.

If the constraints are only preferred, the flag should be set to 'P'. The CXC will interact with the PI/observer to see if the 'Preferred' requests can be met, but they are NOT GUARANTEED.

The types of constraint are:

Window:		        In a fixed time-window
Roll:                   Roll constrained 
Phase dependent:	Samples at a given phase
Monitoring: 		Repeated observations of a single target at specified intervals.
TOO Followups: 		Repeated observations of a TOO target at specified intervals.
Grouping: 		Single or multiple targets observed in any order and encompassed by a single time interval.
Uninterrupted:          Absolutely no interruptions
Coordinated Obs.:       Coordination with other observatories/telescopes
Remarks:                Constraints are defined in the remarks because it is not possible to define them using the existing fields.
'Monitoring', 'Grouping' and 'TOO Followup' observations are mutually exclusive.

Note:If any constraint is set to Y (i.e., required), the observation is time constrained and therefore subject to the limits set for the number of approved constrained observations during the Chandra Peer Review. BEFORE SUBMISSION, please click the Constraints/SlewTax button to estimate the constraint difficulty level of each target and the total slew tax for your proposal.

You may want to use the PRoVis tool to investigate Chandra spacecraft roll, pitch and visibility for your target as a function of date. Chandra Mission Planning schedules all observations, but information from PRoVis can be especially useful for proposers whose observations require constraints.

** Window Constraints

These parameters indicate the earliest observation start time and the latest observation end time. USE THE LARGEST VIABLE WINDOW. Do not enter window constraints merely to indicate periods of sunblock, as these are accounted for by Chandra Mission Planning.

The start and end times must be given in UT . Up to 4 window constraints may be entered per observation. See the Call for Proposals document for the anticipated dates covered by this cycle. The window start/stop format is dd-mon-yyyy hh:mm where :

    dd = day of month
   mon = 3 character abbreviation of month. Valid Values:
         Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov,Dec
  yyyy = full year (ie: 2002)
    hh = hours (valid values 0-23)
    mm = minutes (valid values 0-59)

** Window Constraint?

Logical value indicating a window constraint exists for this observation.
Options are: Y (Yes, required), P (Preferred), N (No). The default is 'N'.

** Window Constraint: Start

The time in UT specifying the earliest observation start time. Format is dd-mon-yyyy hh:mm.
Required if Window Constraint? is 'Y' or 'P'.

** Window Constraint: Stop

The time in UT specifying the latest observation end time. Format is dd-mon-yyyy hh:mm.
Required if Window Constraint? is 'Y' or 'P'.

** Roll Constraints

The spacecraft roll is the angle between celestial north and the spacecraft -Z (minus Z) axis projected on the sky, as measured from N through W. The roll angle is constrained as a function of time for thermal control and because power must be supplied by the solar cells. For any given time and target, there is a nominal roll angle for which the solar power arrays are aimed directly at the sun. The nominal roll for a target may be displayed using PRoVis, the Chandra Pitch-Roll-Visibility tool, available on the web at http://cxc.harvard.edu/soft/provis/. The Observation Visualizer (ObsVis) further allows display of the Chandra instrument field-of-view on the sky, and is available in the latest CIAO downloadable package at http://cxc.harvard.edu/ciao/download.

A roll constraint translates directly into a constraint on the day and time when an observation may be carried out. It should only be specified for cases in which a specific attitude is required to meet scientific objectives. The PRoVis tool interactively plots roll angle as a function of time for a given target.

A maximum of 4 roll constraints may be entered.

** Roll Constraint?

Value indicating a roll constraint exists for this observation.
Options are: Y (Yes, required), P (Preferred), N (No). The default is 'N'.

** Roll Angle and Roll Tolerance

The spacecraft roll angle and roll tolerance(defined as the half-range and assumed symmetric) for the observation. Valid range is 0.0 - 360.
Required if Roll Constraint? is 'Y' or 'P'.

** Is 180 Rotation OK?

Logical value indicating whether a 180 degree rotation of the roll angle is acceptable. The default is 'N'.

** Phase Dependent Observation

Value indicating that the observation is to be spread over a number of intervals with a fixed interval between them and a given reference date. The Epoch is the reference date given in MJD and the Period is the interval in days. The Minimum and Maximum Phase are the minimum and maximum orbital phase.
Options are: Y (Yes, required), P (Preferred), N (No). The default is 'N'.

** Phase Dependent: Epoch (MJD)

For Phase Dependent observations, the reference date (MJD). The observations will be made at an integral number of Periods from this date. The reference date must be within 5 years of the current date.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Phase Dependent: Period (days)

The period in days between phase dependant observations.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Phase Dependent: Minimum Phase

Minimum orbital phase to be observed. Values must be between 0 and 1.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Phase Dependent: Minimum Phase Error

The error on the minimum orbital phase. This parameter sets how precisely the phase range will be covered. Values must be between 0 and 0.5.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Phase Dependent: Maximum Phase

Maximum orbital phase to be observed. Values must be between 0 and 1.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Phase Dependent: Maximum Phase Error

The error on the maximum orbital phase. This parameter sets how precisely the phase range will be covered. Values must be between 0 and 0.5.
Required if Phase Dependent Observation? is 'Y' or 'P'.

** Monitoring Observation

A monitoring program is defined as more than 1 observation of the same source. Specify the desired number of observations below up to a maximum of 20. Please specify the exposure time and the minimum/maximum interval in days for which each observation should be spaced from its preceding observation. All monitor observations but the first will count as constrained at the Chandra Peer review. If there are any separate constraints on the first, it will also count as constrained.

If different instrument parameters are required for the monitoring series, please specify the additional instrument configurations in the 'Remarks' field.

** Exposure Time allocated for monitor

Exposure time in kiloseconds allocated for each monitor observation. The total of the exposure times must equal the time specified in the Total Observing Time field.

** Minimum days since preceding observation

Minimum interval between preceding monitoring observation in days. Valid range is 0.0 - 364.0 days except for multi-cycle proposals.
Required for all monitor observations.

** Maximum days since preceding observation

Maximum interval between preceding monitoring observation in days. Valid range is 0.0 - 364.0 days except for multi-cycle proposals.
Required for all monitor observations.

** Group Observation

Logical value indicating whether the observation needs to be observed within a relative time range with other targets in this proposal. The default is 'N'.

** Group Identification

Enter the group identification (e.g. short name selected by the observer) to be used to identify which targets in this proposal need to be grouped within a relative time range. Maximum of 10 characters.
Required if Group Observation? is 'Y'.

** Interval for Grouping Observations

Relative Time Interval for grouping observations. Valid range is 0.0 - 364.0 days.
Required if Group Observation? is 'Y'.

** Uninterrupted or Contiguous Observation Required

Value indicating that the science can only be optimized if the observation is interrupted as little as possible. Use sparingly, as this WILL BE COUNTED AS A CONSTRAINT. This flag should, in general, NOT be used unless the requested Observing Time is >20 ksec. The typical operating mode for Chandra generally results in the allocated observing time being assigned to a single pointing.

Options are: Y (Yes, required), P (Preferred), N (No). The default is 'N'.

'Y' indicates that the science goals can only be achieved if the observation is not interrupted. Use 'Y' sparingly, as this WILL BE COUNTED AS A CONSTRAINT.

Use 'P' if the science goals do not require - but will clearly be optimized by - minimized interruptions. As a preference, this will be implemented to the extent allowed by all other demands on the scheduling process.

Note that for short observations, normal Chandra scheduling results in the allocated observing time being assigned to a single pointing, but there is no guarantee of this for any exposure time above about 20 ksec.

Observations >180 ksec will have to be interrupted due to the satellite orbit. If the uninterrupted flag is checked, the observations are constrained such that the pieces will be observed as contiguously as possible, and certainly in adjacent spacecraft orbits.

** Must this observation be coordinated with that of another observatory?

Value indicating that the Chandra observations are to be coordinated with another observatory. Ground-based observatories other than the NRAO are not available as a required constraint (Preference only).
No default value. If set to Yes, required, the observation WILL BE COUNTED AS A CONSTRAINT and is subject to the limits set for the number of approved constrained observations during the Chandra Peer Review.

Options:

N (No constraint) No coordination needed
Y (Yes, required) Coordination required
P (Preferred) Coordination helpful but not required

** Maximum Time Interval Encompassing Coordinated Observations

Relative Time Interval for coordinated observations. Valid range is 0.0 - 364.0 days. Required if Coordinated Observation? is 'Yes, Required' or Preferred. This is the maximum scientifically-permitted interval encompassing the Chandra observation and those of the coordinating observatory(ies). If the intervals differ for different coordinating observatories, provide details in the Remarks field and check "Are there additional constraints or preferences in the remarks?"

** Observatories

If 'Y' or 'P' is selected in the 'Must this observation be coordinated with that of another observatory? ' field, specify the other space-based observatories, NRAO or Ground. Except for NRAO, ground-based observations are not available as a required constraint (Preference only). Joint proposals should be specified using the joint proposal fields on the Cover Page of the RPS form.

Choices are: HST, XMM, Spitzer, Swift, NuSTAR, NRAO, Ground.
Maximum of 60 characters.

** Are there additional constraints or preferences in the remarks?

Value indicating there are additional observational constraints or preferences described in the Remarks field. No default value. If set to Y, the observation is subject to the limits set for the number of approved constrained observations during the Chandra Peer Review. Required instrument configurations are not considered to be observing constraints.

Options are: Y (Yes, required), P (Preferred), N (No).

** Remarks

Enter any additional target remarks in this field. Remember that constraints should be entered into the appropriate Constraint fields on this form. Only those constraints that cannot be specified using the existing constraint fields should be entered in this 'Remarks' field.
Maximum of 600 characters.

* TOO Details

This section contains the additional details for Targets of Opportunity (TOO).

If this is the trigger target for a TOO, please specify the exact CXC response window, probability, trigger criteria and any followups. These fields should NOT be specified if this target is a TOO followup, even if the followup specifies a different instrument configuration than the trigger target. The response to a TOO will be classified according to the minimum time delay between trigger and observation. The faster the Chandra response, the more difficult and the more limited the number of TOOs allowed. TOO Followups will be counted as a CONSTRAINT at the Chandra Peer Review.

** Is this the trigger target for a TOO?

If this target is the trigger target (first observation) for a TOO, please set the value to Yes. If this target defines a different instrument configuration for a TOO followup observation, please set the value to No.

** If this TOO is a resubmission of a proposal approved in the previous Cycle, should this TOO be canceled if the previous Cycle TOO is triggered?

Logical value indicating whether this TOO request should be canceled if a previously approved TOO is triggered. Default is No.

** Exact CXC start/stop response window

Start time is the minimum time after the official request to trigger the Chandra TOO observation that the exposure should begin. This value will be used to determine the correct Peer Review category for TOO constraints. Peer review Categories are: 0-5, 5-15, 15-30, >=30.
Peer Review Category Response Window CXC Start (t)
Very Fast0-50 < t < 5
Fast 5-155 <= t < 15
Medium 15-3015 <= t < 30
Slow >=30t >=30

Stop time is the maximum time after that trigger for the exposure to begin and still be scientifically useful.

Units are days.
Required for all trigger targets for TOOs.

** Probability of TOO occurring

Enter the probability of the TOO occurring during the proposed Chandra cycle. The default is 1.0. Valid values are 0.1 - 1.0.

** Exact TOO Trigger Criteria

Specify the trigger criteria for the TOO, e.g. information that will establish the trigger,such as how bright the source should be, in which instrument or telescope, minimum time above threshold brightness, etc..
Maximum of 400 characters. Required for all trigger targets for TOOs.

**Alternate Target Group Name

If this target has alternates or is an alternate please specify the name for this group of alternate targets.
Maximum of 20 characters.

**Number of targets requested for this alternate group

If you've specified an alternate group name, enter how many targets you are requesting for this group. For example, if you want to observe 1 of 3 TOOs in this group, then the 3 TOO's should all specify the same group name (i.e.: alt1) and the number of targets requested would be '1'. The alternate targets can then be added using the Add Target button. You must specify the identical group name for all the alternate targets.

** Followup Observations

If followup TOO observations are being proposed, please enter the exposure time, minimum and maximum time interval between the preceding TOO observation,and target number which identifies the instrument configuration for each followup in the Followup Summary table. All followups must be specified in the Followup Summary table, but the table should NOT include the trigger observation. Target Number MUST be specified for every followup. Followups WILL count as constraints at the Chandra Peer review.

Note that the Trigger target should be labeled as such (Is this the trigger target for a TOO? set to 'Y') and that the exposure time for the trigger target should be the full observing time for the trigger and all followup observations.

If a different instrument configuration or offset is required for a followup, you must enter that observation as a new target with all observational parameters specified, setting the Total Observing Time to 0 and Is this the trigger target for a TOO? to 'N'(No). For non-trigger target forms, all other fields in the TOO Details section must be blank. Be sure to enter the correct target number for each followup observation in the Followup Summary table of the trigger observation. Target Number MUST be specified for every followup.

For a detailed example of how to use the RPS TOO Followup forms, see http://cxc.harvard.edu/proposer/threads/TOO.

All followup observations whose ideal spacing is best determined from measurements by Chandra or other observatories near the time of the trigger will be classified as TOOs in the appropriate time delay category. Followup observations which translate into potential fast TOOs and are not fully specified and accounted for in the target forms will not be accepted.

** If followups, time allocated for initial TOO

Enter the amount of the total observation time that should be used for the initial TOO observation. The remaining time will be used for the followup observations.
Required if the number of followup observations is greater than 0.

** Followups: Exposure Time

Enter the requested duration for this TOO followup observation in kiloseconds.
Required for TOO followup observations.

** Followups: Minimum days since preceding TOO

Enter the minimum time interval in days between this observation and the preceding observation.
Required for TOO followup observations.

** Followups: Maximum days since preceding TOO

Enter the maximum time interval in days between this observation and the preceding observation.
Required for TOO followup observations.

** Followups: Target Number

Please enter the target number in this proposal which defines the instrument configuration for this followup target.
Required for TOO followup observations.

** TOO followup instructions

Specify additional TOO followup instructions only if the 'Number of followup observations' is greater than 0.
Maximum of 1500 characters.

**TOO Coordinated Observations:

Indicate all of the coordinated observations (simultaneous or contemporaneous) associated with this TOO in the appropriate box for coordination with other observatories. This includes observations already approved under other programs, even if time is not requested as part of this proposal. Coordinated observations included only in proposal text will not be recognized or accepted. For non-Chandra observations approved after your Chandra proposal has been accepted, you may request coordination if and when you trigger your TOO. Any such request for additional coordination or observing constraints must be made to the Director and approved by the Chandra Director's Office. For a constraint approved in this way, the CXC will try to accommodate on a best efforts basis.


RPS was written at the HEASARC and modifications to support Chandra were made at the CXC.

10.3.2 Wednesday, November 26, 2014
The Chandra X-Ray Center (CXC) is operated for NASA by the Smithsonian Astrophysical Observatory. 60 Garden Street, Cambridge, MA 02138 USA.   Email: cxcweb@head.cfa.harvard.edu Smithsonian Institution, Copyright © 1998-2014. All rights reserved.