The display of the RPS form will be much
faster if you have only
1 target expanded at a time.
Use the arrows next to the
Target Number to expand/collapse
the target.

Target Form: 1
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 2
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 3
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 4
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 5
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 6
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 7
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 8
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 9
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 10
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 11
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 12
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.

Target Form: 13
Do you want to delete this target?
Target Number
Please use IAU-sanctioned names and verify before submission
with Target/Coordinate Check button at the top of this page.
Enter coordinates in J2000:
Grids:
Any observation intended to be part of a grid must have other similar
pointings within 1 degree to qualify for a reduced slew tax. To be clear,
in the final grid, no pointing may be farther than 1 degree from its
nearest neighbor. Individual pointings within a grid 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 average R.A. and Dec of the grid pointings in the
R.A. and Dec fields above, and then also specifying the 3 general grid
parameters below. Proposer MUST provide a detailed description of the
grid positions on the sky in the science justification (preferably a
figure).
|
|
|
|
(ksec)
If this is a multi-cycle target, please enter:
CCDs On:
Y (Required), N (turn off) or Off# (Optional with Turn-off order)
For example, Off1 should be the first optional CCD, meaning that it should
be the
first optional CCD to be turned off.
Most science programs should specify a total of 4 or fewer required CCDs .
All science programs that request a total of 5 or 6 CCDs must
specify Optional CCDs.
If the science requires 5 or 6 CCDs, proposers should state this in the Remarks field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are using ACIS-I with no grating:
Please ensure that your target falls within the chosen subarray (e.g. use
ObsVis)
Window Order |
Chip ID |
Sampling Frequency Accept 1:n events (0=none,1=all, etc.) |
Starting Column (1-1023) |
Column Width (1-1024) |
Starting Row (1-1023) |
Row Height (1-1024) |
Lower Energy Threshold (keV) |
Energy Range (keV) |
1 | |
|
|
|
|
|
|
|
2 | |
|
|
|
|
|
|
|
3 | |
|
|
|
|
|
|
|
* Starting Row and Row Height only apply to 2-dimensional windows (i.e., TE-mode) |
Additional spatial windows : If you need to specify more windows, define them in the space below, one per line, with the following comma-delimited values: 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 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
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 format for entering dates is dd-mon-yyyy hh:mm
Roll Constraints
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.
Phase Constraints:
Do you have a preference regarding the
distribution of observing time within the specified phase range?
If yes, describe the preference in the
additional constraints or preferences remarks field
and indicate Preferred in the associated menu.
Monitor Observations:
A maximum of 20 monitor observations are allowed. Additional entries
will be displayed when the
Exposure Time for entry 5,10,
and/or 15 is entered and the user
Verifies the form.
All required 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.
Do you want more than one observation of this target?
Grouping Targets: If this target needs to be observed within a relative time range with other targets in this proposal, select 'Y' for
Group Observation? and enter
a unique
Group Identification to be used for all targets in the group.
Enter the maximum time interval that you wish all targets to be observed.
This is often used for rasters or grids to facilitate alignment of roll angles.
Note: This will be counted as a constraint. It is normally not necessary unless T>20ksec.
Uninterrupted or Contiguous Observation Required?
Note: Ground-based observations other than the NRAO are only available as a Preferred constraint.
TOO Details
Is this the trigger target for a TOO?
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?
Note: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.
Exact TOO trigger criteria (400 characters)
Alternate Targets
If you are specifying alternate targets in this proposal for a group of TOOs,
please identify a group name and then specify the number of targets
you are requesting for this group. For example, if you
want to observe 1 of 3 TOOs in this proposal, 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
for the initial target and then the exposure time, minimum and maximum time
intervals, and target number for each followup
in the Followup Summary form below. We strongly recommend
you refer to the detailed
instructions. Followups WILL count as constraints at the Chandra Peer review.
TOO followup instructions (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.