BASIC INSTRUCTIONS

Utilizing ARK, the Astrophysics Research Knowledgebase, a service of NASA's High Energy Astrophysics Science Archive Research Center, RPS provides a facility for filling out the NICER proposal forms, as part of the ROSES NRA. Electronic submission of the proposal forms is required. The anonymized scientific/technical justification must be submitted electronically, uploaded as a PDF file after the initial submission of the electronic proposal forms. A one-page "team expertise and resources" (not anonymized) PDF also will need to be uploaded. Please note that each of these PDFs cannot exceed 10 MB in size and each have specified page limits. The page limit for the anonymized scientific/technical justification PDF is 5 pages (4 pages for text/figures + 1 page for references) for NICER-only proposals and 6 pages for joint program(s) proposals (4 pages for the NICER justification text/figures + 1 page for the joint program(s) justification + 1 page for references).

Note: NICER proposals must follow the Guidelines for Anonymous Proposals for dual-anonymous peer review. (Note that, for NICER proposals, the page limit for the team expertise document is one page, i.e. further constrained compared to the "no more than three pages" from the general guidelines document.) Proposers should fill in all required information on the forms, as detailed below. All fields (except those fields that specifically request names or institutions) should not contain personally identifying information. If a field does, NASA will need to redact it from the information provided to reviewers. With especially egregious cases (too many violations to readily redact, for example), NASA reserves the right to return your proposal without review. Your abstract, the contents of all other RPS form fields (except those fields specifically for names or institutions), and your justification PDF should not include language that identifies the names of investigators or their institutions.

In order to access the NICER RPS web form, you must first create an ARK account and/or join the NICER group.

If you already have an ARK account, login first and select "Join Group" from the menu next to "NICER RPS (NICER)" and then click on the Submit Changes button.

If you do not already have an ARK account, enter your e-mail address in the input field provided and click on the checkbox next to "NICER RPS (NICER)" and then click on the Join ARK button. Check your e-mail and follow the registration URL found therein. Fill out the ARK registration form and submit.

Next, proceed to the NICER RPS web form and fill out the form as directed below. Targets can be added at the end of the form or by clicking the Add Targets button at the top or bottom of the page. The Add Targets button can be used to add blank targets or to upload a plain text file containing a list of target names and/or positions. Please note that this latter method will only fill in the fields for the target name and pointing position; you will still need to enter other information (observation time, expected rates, constraints, etc.) for each target using the web interface. Alternatively, after adding some targets, you can use the Save button to download a plain text representation of the RPS form, which you can edit in your favorite text editor and then Reload into ARK. Note that the file format used by the Reload mechanism is the same as the format of the files generated by the Save button.

After you have filled out the form, click the Verify button to make sure you have entered the form information correctly. If the form does not validate, ARK/RPS will identify the reason(s) why it did not, which you will need to correct. Once the form verifies successfully, a Submit button will appear, allowing you to submit the proposal to RPS. Note that you must Verify successfully before the Submit button will be revealed and you must use the Submit to submit your proposal.

The PostScript, PDF, and LaTeX buttons can be used to generate formatted versions of the proposal forms. We recommend that PIs keep formatted copies of the forms for their personal records, but it is not a required part of the proposal submission process.

After clicking on the Submit button, go to your Recent Activity page. Summary information for the proposal that you just submitted should be listed here, indicating that you have successfully submitted your NICER proposal forms to ARK/RPS. You may now upload your scientific/technical justification (anonymized) and your team expertise and resources (not anonymized) documents in PDF format. From the Recent Activity page, click on the Files button next to the proposal you submitted, and then click on the Upload button and follow the instructions on that page. After you have successfully uploaded both of those files required for your proposal, you will have completed your RPS electronic submission.

Note: After submission and before the proposal deadline, you may still Modify or Discard your proposal using the appropriate buttons on the Recent Activity page. The Files button also enables you to Download, Discard, or Replace any file that you previously uploaded.

Additional information on how to use RPS and the answers to some frequently asked questions can be found on the RPS Quick Help page.

Short descriptions of the forms and fields are below. The fields are listed in the same order as found on the web page. The labels for the fields in the web form will link to the appropriate field description below.

FORM/FIELD-SPECIFIC INSTRUCTIONS

Cover Page

This section contains fields for the proposal title, the type of proposal, the proposal abstract, and information about the Principal Investigator of the proposal, such as name, institution, address, telephone number, etc.

Proposal Title

The title of the proposal. Up to 120 characters are allowed. Required.

Abstract

800 characters maximum. Abstracts exceeding this limit will cause an error and must be shortened. Please do not use special characters or LaTeX markup in the abstract. In accordance with the Guidelines for Anonymous Proposals for dual-anonymous peer review, the abstract should not include language that identifies the names of investigators or their institutions. Required.

Joint Proposal?

It is possible to propose for joint NICER-NuSTAR and/or joint NICER-Swift and/or joint NICER-TESS and/or joint NICER-NRAO facility observations in the NICER Guest Observer cycle.

Select the NRAO checkbox if observations with one of the participating NRAO facilities (the Jansky Very Large Array, the Very Long Baseline Array, and or the Robert C. Byrd Green Bank Telescope) are requested. If specified, please add at least one target form in order to specify the particulars of the NRAO observation(s). Note that the joint proposal program can award up to 5% (around 200-300 hours) on NRAO facilities for any single proposal.

Select the NuSTAR checkbox if NuSTAR observation time is desired for any of the proposed targets. If NuSTAR is checked, then you must specify the preferred NuSTAR exposure times and other relevant observation parameters for each target in the proposal in the individual target form(s). Enter a zero (0) for the exposure time for any target for which NuSTAR observations are NOT requested. The total amount of NuSTAR observing time available in the entire NICER-NuSTAR joint program is 400 ks.

Select the Swift checkbox if Swift observation time is desired for any of the proposed targets. If Swift is checked, then you must specify the preferred Swift exposure times and other relevant observation parameters for each target in the proposal in the individual target form(s). Enter a zero (0) for the exposure time for any target for which Swift observations are NOT requested. The total amount of Swift observing time available in the entire NICER-Swift joint program is 200 ks.

Select the TESS checkbox if TESS observations are desired for any of the proposed targets. If TESS is checked, then you must specify the TESS sector number and may optionally request a 20-second cadence slot for each target in the proposal you wish TESS to observe in the individual target form(s). Enter a zero (0) for the sector number for any target for which TESS observations are NOT requested. There are up to 300 2-minute cadence target slots and only 50 20-second cadence observations available in the entire NICER-TESS joint program.

Multi-Cycle Proposal?

Check the Yes checkbox if any of the NICER observations extend beyond the end of the cycle currently being proposed. Multi-cycle proposals cannot extend beyond the end of the next proposal cycle (i.e., the cycle after the one currently being proposed). Requests for observations extending beyond the end of the current cycle must be scientifically justified. Such multi-cycle requests are not available within the joint NICER and NuSTAR/Swift/TESS programs.

Principal Investigator Title

Your title (Dr., Ms., Mr., Prof.). The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

First Name

Your first name. Up to 30 characters are allowed. Required. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Middle Name or Initial

If you like, you may add your middle name or initial(s). Optional. Up to 30 characters are allowed. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Last Name

Your last name (surname). Up to 30 characters are allowed. Required. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Department

The name of your department at your institution. Up to 60 characters are allowed. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Institution

Your institutional affiliation. Required. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Address 1

The first line of your institution's address, e.g., the street name, any number within it, etc. Up to 60 characters. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Address 2

The second line of your institution's address, if needed. Up to 60 characters. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

City/Town

Your city or town. Up to 32 characters. Required. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

State/Province

The name of the state/province/prefecture in which your institution is located. Up to 30 characters. Required. For states in the U.S., please use USPS-standard, two-letter abbreviations. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Zip/Postal Code

The postal code, ZIP code, or the equivalent of your institution. Up to 10 characters. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Country

The name of the country in which your institution is located. Required. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission. If your country is not listed, please contact the RPS Help Desk. Note: Proposals from PIs affiliated with People's Republic of China (PRC) organizations and bilateral collaborations between scientists affiliated with institutions from the USA and the PRC are not eligible for NASA support under United States Federal law. Multilateral collaborations that involve scientists from institutions in the USA, the PRC, and other countries are allowed, however. Refer to the PRC FAQ for ROSES for details.

Telephone Number

Your telephone number, plus any extension. Please include the international prefix, if appropriate. Up to 24 characters allowed. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

Fax Number

Your fax number, if available. 24 characters allowed. The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

E-mail Address

Your e-mail address. Up to 60 characters. Required. If the e-mail receipt option is checked in your ARK user profile, an e-mail receipt will be sent to this address within 24 hours of the electronic submission of your proposal (usually much sooner). The value for this field comes from your ARK user profile. If it is incorrect, update your ARK user profile prior to proposal submission.

General Form

This section contains fields for details about your collaborators, if any, and additional contact information. Up to 30 Co-Investigators can be specified here. However, only the first 15 will be displayed in the PDF, PostScript, and LaTeX output options. If you have more than 30 Co-Investigators, additional Co-Investigators can be specified in the team expertise PDF that you will need to upload after successful submission of your proposal forms. The team expertise PDF should always include your complete list of Co-Investigators regardless of how many you have. Do not list any Co-Investigators in any comment fields of the forms, please.

Co-Investigator First Name

The first name of each Co-Investigator. Up to 20 characters.

Co-Investigator Last Name

The last name of each Co-Investigator. Up to 20 characters.

Co-Investigator Institution

The institution for each Co-Investigator. Up to 60 characters. Please refer to the List of Institutions Recognized by RPS and use the official name of the institution wherever possible. Note: If your Co-I's institution is not among those listed, please contact the RPS Help Desk and request that it be added to the list. Such requests are typically answered within 24 hours, excluding weekends and U.S. Federal holidays.

Co-Investigator Country

The country for each Co-Investigator. If a country is not listed, please contact us at the RPS Help Desk and request that it be added to the list. Note: Bilateral collaborations between scientists affiliated with institutions from the USA and the People's Republic of China (PRC) are not eligible for NASA support under United States Federal law. Multilateral collaborations that involve scientists from institutions in the USA, the PRC, and other countries are allowed, however. Refer to the PRC FAQ for ROSES for details.

Co-Investigator E-mail Address

The e-mail address for each Co-Investigator. Up to 60 characters.

Contact First Co-Investigator Listed Above?

This checkbox is used to indicate whether or not the first Co-Investigator listed is also a contact person in cases where the Principal Investigator cannot be reached. The default is to contact only the Principal Investigator.

Telephone Number of First Co-Investigator

Telephone number of the Co-Investigator that should be contacted. Up to 24 characters. Be sure to include the international code if outside the United States. Only enter a value for this field if you specify that the first Co-Investigator should be contacted.

Data to be used by a student as part of a thesis project?

Select the Yes checkbox if the data from this proposal is part of a student's thesis.

Exclusive Use Requested?

Indicate whether or not exclusive use of the data is requested. The default is no. By default NICER data are archived and publicly released within two weeks of acquisition. NICER proposers can request an exclusive use period of up to 6 months if scientifically warranted. Proposers will need to justify the need for exclusive use in the Exclusive Use Justification box, and should also describe the need for exclusive use in the scientific justification of the proposal.

Exclusive Use Duration

Specify the duration of the desired exclusivity period between 1 month and 6 months, inclusively. Required for exclusive use requests.

Exclusive Use Justification

Give reasoning and/or specifics for the exclusivity requirement. Up to 400 characters. Required for exclusive use requests.

Maximum Number of Triggers Requested for Target(s) of Opportunity

Only fill in this field if this is a Target(s) of Opportunity (ToO) proposal. A ToO proposal may request that all listed targets which satisfy the triggering criteria be observed; in this case, the maximum number of triggers is equal to the number of targets. Alternatively, a ToO proposal may request that only the first (or first several) targets to satisfy the triggering criteria be observed. In this case, the number of times this proposal can be triggered (a number less than the number of targets) should be entered here. For example, a ToO proposal may list 10 possible trigger targets, but only requires 3 triggers to accomplish the proposed science. In this case the maximum number of triggers would be 3. The proposal text must include a justification for the number of triggers, if greater than 1.

Maximum Total Time Requested for Target(s) of Opportunity

Only fill in this field if this proposal requests Target(s) of Opportunity (ToO) observations. If it does, then you must specify the maximum time requested in kiloseconds. The value should be a sum of the Total Observation Time values for either a subset of your targets or all of your targets, depending on the number of ToOs you want to trigger. The value must be between 1 and 1,000 kiloseconds.

Example #1: Suppose you have three Targets of Opportunity of 25 ksec each (i.e., you have completed three target forms), but you only need two of them to be observed, you should specify 50 ksec for this field.

Example #2: If you have four Targets of Opportunity of 30 ksec each (i.e., you have completed four target forms) and you want all four of them to be observed, then you should specify 120 ksec for this field.

Example #3: If you have three Targets of Opportunity with requested exposure times of 25, 30, and 50 ksec, respectively, and you only want to trigger one of the three ToOs to be observed, then you should specify 50 ksec (since 50 ksec is the largest time request) for this field.

Example #4: If you have three Targets of Opportunity with requested exposure times of 25, 30, and 50 ksec, respectively, and you only want to trigger two of the three ToOs to be observed, then you should specify 80 ksec (30 ksec + 50 ksec, i.e., the sum of the two largest time requests) for this field.

Target Form(s)

This section contains all of the details regarding how each different target should be observed.

Target Name

The commonly accepted name for the object. Up to 20 characters. For known targets, please use names (e.g., NGC 2237 or Eta Car) which are recognized by standard astronomical object databases such as SIMBAD or NED. Required.

Target Category

Specify one of the following categories that best describes this target. Required.

    Magnetars and Rotation-Powered Pulsars
    X-Ray Binaries
    White Dwarfs and Cataclysmic Variables
    Non-Compact Stellar Objects
    Supernova Remnants/Other Extended Galactic Sources
    Normal Galaxies
    Active Galaxies and Quasars
    Galaxy Clusters and Extragalactic Extended Objects
    Gravitational-Wave Sources
    Solar System Objects
    Other

R.A.

The J2000 right ascension of the source. The value can be entered in either sexagesimal format (HH MM SS.SS — hours, minutes, seconds, separated by spaces) or decimal degrees format (DDD.DDDDD). If you enter the value in sexagesimal format, it will be converted to decimal degrees format when you submit. Required.

Note: If you are proposing to observe a target whose position is unknown at the time of proposal submission (e.g., a moving object), please specify "0.0" for both the R.A. and Dec. fields.

Note: Proposers of accepted moving targets will need to provide the NICER target planning team with J2000 R.A. and Dec. coordinates as a function of time.

Dec.

The J2000 declination of the source. The value can be entered in either sexagesimal format (±DD MM SS.S — an optional sign, either + or -, followed by the degrees, minutes, and seconds, separated by spaces) or decimal degrees format (±DD.DDDDD). If you enter the value in sexagesimal format, it will be converted to decimal degrees format when you submit. If you do not specify the sign, it is assumed to be positive. Required.

Note: If you are proposing to observe a target whose position is unknown at the time of proposal submission (e.g., a moving object), please specify "0.0" for both the R.A. and Dec. fields.

Note:Proposers of accepted moving targets will need to provide the NICER target planning team with J2000 R.A. and Dec. coordinates as a function of time.

Moving Target?

If the target's position is expected to move by more than 2 arcminutes over the course of the proposal cycle, click this checkbox. The default is no. Proposers of accepted moving targets will need to provide the NICER target planning team with J2000 R.A. and Dec. coordinates, as seen from the International Space Station, as a function of time.

Total Observation Time

The total requested exposure time (i.e., total amount of good on-source data, after standard screening) in kiloseconds for this target. The value must be between 1 and 1,000 kiloseconds. For non-ToO proposals, note that the sum total amount of time that can be requested for all targets in the whole proposal is 1,000 kiloseconds. For ToO proposals, the sum total time for all targets can exceed 1,000 kiloseconds (because the requested number of ToO triggers can be less than the number of targets), but Maximum Total Time Requested for Target(s) of Opportunity value cannot exceed 1,000 kiloseconds. Required.

Expected Count Rate Above Background

Give the expected total band (0.3-10 keV) count rate of the source in counts/second for all 52 active Focal Plane Modules (FPMs) with no deadtime. Proposers may use WebPIMMS to estimate NICER count rates, or WebSpec or XSPEC for more detailed simulations. Proposers should note that deadtime is important for very bright sources (a flux of 3 Crab, corresponding to about 60,000 NICER counts/s for 52 FPMs). Deadtime can be reduced by reading out a subset of the focal plane modules. Proposers who wish to observe very bright sources should consult with the NICER team on the observing strategy. Required.

Extended Source?

If the target is not a point source, mark this checkbox.

Source Extent

Specify the diameter (in arcminutes) of the circle that completely encloses the region of interest and is centered on the target's position. This is to assure that all of your targets will remain in the observing field in case the field center needs to be shifted. Round to the nearest hundredth of an arcminute, with a minimum of 0.01 arcminutes.

Background Restriction?

Specify whether the observation should occur during times of low particle background (which mostly affects the high-energy band above 2 keV) and/or optical loading (which mostly affects the low-energy band below 1 keV). Required.

Since there is a limited amount of low-background time available, observations which require restricted background are considered to be time-constrained. Required.

     No
     Minimize Optical Loading - Observe only during orbit night or large Sun angles
     Minimize Particle Background - Observe outside SAA and far from Polar Horns
     Minimize Optical Loading and Particle Background

Note: Background restrictions reduce the NICER visibility to the target by restricting either the observable part of the year (Optical Loading) or the observable part of each orbit (Particle Background). A request to satisfy both of these constraints will severely restrict the time available during the cycle when a given target may be observed. For ToO proposals it may not be possible to adhere to requested background restrictions, depending on when the ToO is triggered.

Background Restriction Remarks

Describe the purpose of the background restriction. Include any details necessary to properly implement the constraint. Required if any Background Restriction other than No is selected for the previous field.

Uninterrupted Observation?

Indicate whether or not an uninterrupted observation of the target is required. The default is no. Note that NICER has complicated visibility constraints due to occultation with external structures on the ISS, and, in general, the longest available uninterrupted observing interval is 2 ksec or less for most targets.

Uninterrupted Observation Justification

Give reasoning and/or specifics for the uninterrupted observation(s). Up to 200 characters. Required for uninterrupted observation(s).

Compact Observation?

Check Yes if the observation is one in which any part of the desired exposure needs to be acquired in a limited time window. A monitoring program may be made up of one or more compact observations. The default is no.

Typically, a target will be visible to NICER for about 10 ks in any given day. However, target visibility varies over time due to sun avoidance and obstruction with the ISS solar panels or other structures.

Compact Observation Description

Describe the specific details of the time window in which the observations are to be carried out. Up to 300 characters. Required if "Compact Observation" is Yes.

Number of Visits

Enter the desired number of visits for the target. A visit is the number of intervals into which the Total Observation Time will be evenly divided. If exposure times vary for some visits, multiple target forms will be needed for each distinct exposure time. The number of visits must be between 1 (the default) and 99. If more than 99 visits are desired, the proposer should submit additional target forms for this target. Required.

Monitoring Program?

Answering Yes indicates that the total observation time needs to be spread over more than one visit at pre-determined intervals, usually to examine target variability over some user-defined time interval. Use the Phase Dependent Observations or Specific Time Range categories in this form if the observation should be done in specific orbital or rotational phase intervals or on a range of specific dates/times, respectively, during the proposal cycle.

Monitoring Specifics

Describe the specifics of the monitoring program, such as the minimum and maximum range for the start of the monitoring in MJD, the time interval between consecutive observations, etc. For complicated observing strategies (e.g., logarithmic spacing) be explicit in the required spacing. Up to 400 characters. Required for monitoring programs.

Coordinated Observation?

Indicate whether or not the observation is linked with observations by another observatory/mission. The default is No.

     No
     Yes
     Preferred But Not Essential

Coordinating Observatory

Indicate the other ground-based, airborne, and/or space-based observatories with which the observation(s) should be coordinated. Required for coordinated observations.

Coordinated Observation Description

Give specific details regarding the coordination of the observation(s). Details should include relative frequency, timing, duration etc. between NICER and the other observatory or observatories. The need for strict simultaneity should be strongly justified. Up to 400 characters. Required for coordinated observations.

Phase Dependent Observations?

Answering Yes indicates that the observation needs to occur at one or more specified phase intervals of the orbital period, spin period, or other periodic phenomena. The "Epoch" is the reference date given in MJD and the "Period" is the period in days. The "Minimum Phase" and "Maximum Phase" are the minimum and maximum phases desired for observation of this target, i.e. the observation will be done at phase φ between φ_min ≤ φ ≤ φ_max, where φ_min is the minimum phase and φ_max the maximum phase. If approved, the PI will be expected to provide the NICER Science Team with time windows that meet the required phase constraints.

Phase dependent observations are considered to be time-constrained.

Phase Dependent Epoch

For phase dependent observations, this is the reference date in Modified Julian Date (MJD) number format. The observations will be made at an integral number of "Period" values from this date. Required for phase-dependent observations.

Phase Dependent Period

The orbital period of the source in days. Required for phase-dependent observations.

Minimum Phase

Minimum or starting orbital phase to be observed. Values must be between 0 and 1. Required for phase-dependent observations.

Maximum Phase

Maximum or ending orbital phase to be observed. Values must be between 0 and 1. Required for phase-dependent observations.

Phase Dependent Remarks

Provide any details related to the phase-dependent observations. Up to 400 characters. Required for phase-dependent observations.

Specific Time Range?

Answering Yes indicates that the observation should be made within a specific time range. This may be used, for example, if the observation needs to be coordinated with observation of this target by another observatory.

Please note that the amount of available time for which a target is visible to NICER in a specific time interval may be limited by obstruction with the ISS solar panels or other structures; because of uncertainties in the flight orientation of the ISS with time, it is not always possible to predict the target visibility more than a few weeks in advance. Please contact the NICER Help Desk if you have concerns about the visibility of your target.

The start of a specific time range request must be within the cycle being proposed, but the range may extend to include time in the following cycle.

Specifying a time range means that the observations are considered to be time-constrained.

Specific Time Range Start

The start date/time of the observation, in MJD. The observation should start no earlier than this time.

Specific Time Range End

The end date/time of the observation, in MJD. The observation should end no later than this time.

Specific Time Range Remarks

Provide any comments related to the need for observation within the specified time range. Up to 400 characters. Required for observations for which a specific time range is indicated.

Target of Opportunity?

Indicate whether or not this object is a Target of Opportunity (ToO). A Target of Opportunity includes any proposal to observe a source under conditions that cannot be scheduled in advance (e.g., when non-periodic phenomena such as outbursts, state changes, novae, etc., occur). Target of Opportunity proposals may not span multiple cycles. ToOs and non-ToOs cannot be in the same proposal.

Trigger Criteria

Specify how the NICER observation will be triggered. For coordinated ToO observations, the triggering for NICER and the other observatories should be given here. 400 characters maximum. This field is required for ToOs.

Trigger Probability

Give an estimate of the probability of triggering this Target of Opportunity during this Cycle. The probability should be given as a decimal number between 0.01 and 1.00. This field is required for ToOs.

Trigger Urgency

Characterize the urgency of the NICER response to the trigger:

     Highest: NICER observations should begin within 4 hours of the trigger
     High:    NICER observations should begin within 24 hours of the trigger
     Medium:  NICER observations should begin within days to a week of the trigger
     Low:     NICER observations should begin within weeks to months of the trigger

Note that NICER's response to a ToO depends on visibility constraints. This field is required for ToOs.

Other Remarks

Any other relevant comments you wish to make regarding the target or how it is to be observed. Up to 500 characters. Optional.

NRAO Observation Parameters

If you are requesting an observation at an NRAO facility through the NICER-NRAO joint proposal program, you must request a positive number of hours at least one NRAO facility. Note that the joint proposal program can award a total (maximum) of 5% of time (about 200-300 hours depending on the telescope) on NRAO facilities. The array, wavelength, or receiver should be specified through the pull-down menus, if possible. Additional information, such as the justification for the number of hours requested, must be provided in the scientific justification. These fields are only visible if the NRAO Joint Proposal checkbox is selected.

VLA Hours

Specify the total number of hours requested on the Karl G. Jansky Very Large Array. Required for NICER-NRAO joint proposals requesting VLA time. Specify values in 0.1-hour increments up to a maximum of 200.0 hours. Leave this field blank if you are not requesting VLA time.

VLA Array

Optional (but encouraged) for NICER-NRAO joint proposals requesting VLA time. If possible, indicate the VLA array from the following possible choices:

     VLA-A
     VLA-BnA
     VLA-B
     VLA-CnB
     VLA-C
     VLA-DnC
     VLA-D
     VLA-Any

VLA Wavelength

Optional (but encouraged) for NICER-NRAO joint proposals requesting VLA time. If possible, indicate the VLA wavelength from the following possible choices:

VLBA Hours

Specify the total number of hours requested on the Very Large Baseline Array. Required for NICER-NRAO joint proposals requesting VLBA time. Specify values in 0.1-hour increments up to a maximum of 200.0 hours. Leave this field blank if you are not requesting VLBA time.

VLBA Wavelength

Optional (but encouraged) for NICER-NRAO joint proposals requesting VLBA time. If possible, indicate the VLBA wavelength from the following possible choices:

GBT Hours

Specify the total number of hours requested on the Robert C. Byrd Green Bank Telescope. Required for NICER-NRAO joint proposals requesting GBT time. Specify values in 0.1-hour increments up to a maximum of 200.0 hours. Leave this field blank if you are not requesting GBT time.

GBT Receiver

Optional (but encouraged) for NICER-NRAO joint proposals requesting GBT time. Indicate the GBT receiver to be used from the following possible choices:

     290-920 MHz (PF1)
     910-1230 MHz (PF2)
     1.15-1.73 GHz (L)
     1.73-2.60 GHz (S)
     3.8-6.1 GHz (C)
     8.0-12.0 GHz (X)
     12.0-15.4 GHz (Ku)
     18.0-26.5 GHz (K)
     26.0-36.0 GHz (Ka)
     38.2-49.8 GHz (Q)

NuSTAR Observation Parameters

If you are requesting NuSTAR observing time through the NICER-NuSTAR joint proposal program, you must fill in the fields below. These fields are only visible if the NuSTAR Joint Proposal checkbox is selected. Proposers should also fill out the Coordinated Observation? section with information about the coordination between NICER and NuSTAR, if desired.

NuSTAR Total Observation Time

Specify the total NuSTAR exposure time in kiloseconds requested for this target. Requested exposure times may be either zero (if you do not need a particular target to be observed by NuSTAR) or ≥ 20 kiloseconds and ≤ 400 kiloseconds. This field should only be visible if you have specified that you are applying to the NICER-NuSTAR joint program. This field is required for NuSTAR joint observations.

NuSTAR Expected Count Rate Above Background

Give the expected total band (3-79 keV) NuSTAR count rate of the source in counts/second for both modules in a 50% PSF extraction with no deadtime. Proposers may use WebPIMMS to estimate. Proposers who use XSPEC/WebSpec instead should remember to account for both telescopes/modules (FPMA and FPMB). The minimum acceptable net count rate is 0.001 counts/sec, and the maximum is 10000 counts/sec. Targets with estimated count rates outside this range should input the appropriate limit and note the actual estimated rate in the NuSTAR Other Remarks field. Required.

NuSTAR Tiling Observations?

If you wish to tile observations with NuSTAR, select Yes.

NuSTAR Tiling Pattern

Specify the pattern used to tile multiple NuSTAR observations together, if tiling observations are desired. The standard tiling pattern for NuSTAR survey observations is a half-shift, i.e. the 12-arcminute field of view is shifted by 6 arcminutes between positions. Required for tiling observations.

NuSTAR Tiling Remarks

Explain how the tiling should be done and/or why it is needed. Up to 200 characters. Required for tiling observations.

NuSTAR Stray Light Issue?

Specify the estimated impact of stray light for the NuSTAR observation. If the field is visible and a non-zero NuSTAR observation time has been specified, this field is required. The following are the choices:

     No
     Potential Stray Light Issue

Extremely bright X-ray sources (>100 mCrab in the 3-79 keV band) within 1 to 5 degrees of a target can cause issues with elevated backgrounds due to stray light. An estimate of the stray light contamination for any target can be obtained using the NuSTAR Target Constraint Visibility Tool available on the NuSTAR SOC website. If a constraint check indicates a "Potential stray light issue," then proposers may also submit a request for a feasibility analysis to nustar-help@srl.caltech.edu at least 48 hours prior to the proposal deadline.

NuSTAR Stray Light Description

Describe the nature of the stray light issue. If a constraint check indicates a "potential stray light issue," then proposers may also submit a request for a feasibility analysis to nustar-help@srl.caltech.edu at least 48 hours prior to the proposal deadline. Information from that feasibility analysis can be included in this field. Required if Potential Stray Light Issue is selected for the previous field.

NuSTAR Position Angle Dependent?

Specifying this option indicates that the NuSTAR observation is dependent on the position angle (PA) of the NuSTAR field of view. The position angle is defined as the angle East of North of the direction of the +DET1Y focal plane axis. At PA = 0 degrees the +DET1X axis points East and the position of the optical axis of the telescopes is approximately 1 arcminute NE of the center of the field of view. See the NuSTAR FAQ for details.

NuSTAR Minimum PA

Specify the minimum NuSTAR position angle (PA) in degrees, if applicable. The proposer is responsible for verifying that the scientifically desirable PA is achievable within the operational constraints. Required for a PA-dependent observation.

NuSTAR Maximum PA

Specify the maximum NuSTAR position angle (PA) in degrees, if applicable. The proposer is responsible for verifying that the scientifically desirable PA is achievable within the operational constraints. Required for a PA-dependent observation.

NuSTAR Monitoring Program?

Indicate whether the observation is to be made in more than one exposure (considered a "visit") at pre-determined intervals but with no fixed starting time. Use the NuSTAR Phase Dependent Observations? and/or NuSTAR Specific Time Range? fields in this form if the starting time needs to be made during a specific phase or date/time interval during the proposal cycle. The time interval between successive visits must be ≥ 14 hours. If the time interval between two successive visits is ≤ 1 week, then the observations should also be designated as a NuSTAR Specific Time Range observation and a description provided in the NuSTAR Specific Time Range Remarks field.

NuSTAR Monitoring Criteria

Describe the specifics of the monitoring program, such as how far apart in time the object should be observed and the number of times. Up to 400 characters. Required for all monitoring programs.

NuSTAR Phase Dependent Observations?

Indicate that the observation is to be spread over a number of intervals with a fixed interval between them and a given reference date. The "Epoch" is the reference date given in MJD and the "Period" is the orbital period of the source in days. The "Minimum Phase" and "Maximum Phase" are the minimum and maximum orbital phases.

NuSTAR Phase Dependent Remarks

Provide any details related to the phase-dependent observation. Up to 400 characters. Required for phase-dependent observations.

NuSTAR Specific Time Range?

If observation of the target should be done at a specific date/time (other than phase-dependent), select Yes.

NuSTAR Specific Time Range Remarks

Describe the time constraints of the observation. Up to 400 characters. Required for time constrained observations.

NuSTAR Uninterrupted Observation?

Indicate whether or not an uninterrupted observation of the target with NuSTAR is required. The default is no.

NuSTAR Uninterrupted Observation Justification

Give reasoning and/or specifics for the uninterrupted observation(s). Up to 200 characters. Required for uninterrupted observation(s).

NuSTAR Other Remarks

Any other relevant comments you wish to make regarding the NuSTAR observation of the NICER target. Up to 500 characters. Optional.

Swift Observation Parameters

If you are requesting an observation through the NICER-Swift joint joint proposal program, you must fill in the total amount of time requested for the Swift observation(s) in kiloseconds. Additional information, such as the exposure time per visit and the cadence of the Swift observations should be provided in the Observation Remarks box. The justification for the amount of time requested must be provided in the scientific justification. Proposers should also fill out the Coordinated Observation? section with information about the coordination between NICER and Swift, if desired.

Swift Time

Specify the total number of kiloseconds requested to observe this target by Swift. Requested exposure times may be either zero (if you do not need a particular target to be observed by Swift) or between 1 and 200 kiloseconds, which is the total time allotment of the NICER-Swift joint program. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If the field is visible, it is required. If you enter zero, then you do not need to enter any other fields in the Gehrels Swift Observation Parameters section.

Swift Number of Observations

Enter the desired number of observations of the target, where an observation must be between 1 and 40 kiloseconds. For monitoring observations this will give the number of parts into which the Total Observation Time will be evenly divided, unless the Observation Remarks field below indicates otherwise. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If the field is visible and the Swift Time field for this target is non-zero, it is required.

Swift Instrument Most Critical to Science Goals

Select the Swift instrument from the list provided which is most critical to achieving your science goals. If the field is visible and the Swift Time field for this target is non-zero, it is required.

Swift Estimated XRT Count Rate

Estimate the Swift XRT count rate in counts/sec typical of the source. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If the field is visible and the Swift Time field for this target is non-zero, it is required.

Swift XRT Mode

Select the Swift XRT mode from the list provided. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If the field is visible and the Swift Time field for this target is non-zero, it is required.

Photon Counting (PC) Mode: PC mode generates images with 2.5-s time resolution and is best suited to count rates below 0.5 cps. PC mode can be used for higher count rates, but the data will be piled up and will require special processing by the user. Choose PC mode if your science goal is to determine a good X-ray position. A two-dimensional image is generated. This mode allows the user to derive spectra at the CCD resolution.
Windowed Timing (WT) Mode: WT mode produces 1-D images with about 2-ms time resolution and is best suited to count rates over 1 cps. WT mode has higher background than PC mode. Choose WT mode if your science goal requires high-resolution timing. This mode allows the user to derive spectra at the CCD resolution.
Automatic (AUTO) Mode: Auto mode allows the instrument to choose the mode automatically, based on the count rate. Sometimes subject to "mode switching", which can result in a loss of useful data. Choose this mode when the X-ray count rate is unknown; the instrument will then select the mode automatically. Useful data results, unless the target is affected by scattered light from the bright earth.

Swift UVOT Filter Mode

Select the Swift UVOT filter mode from the list provided. In order to preserve UVOT filter wheel rotations, any filter mode other than "Filter of the Day" needs a strong justification. If you select "Custom," then you must specify the mode in the Swift Observation Remarks field. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If the field is visible and the Swift Time field for this target is non-zero, it is required.

Swift Observation Remarks

Summarize any Swift observation details that may be relevant, such as Swift ToO trigger criteria and probability, monitoring criteria, and any scheduling constraints, if known. This field should only be visible if you have specified you are applying to the NICER-Swift joint program. If that is the case and the Swift Time field for this target is non-zero, it is required. Up to 1000 characters.

TESS Observation Parameters

If you are requesting TESS observing time through the NICER-TESS joint proposal program, you must fill in the fields below. These fields are only visible if the TESS Joint Proposal checkbox is selected. Proposers should also fill out the Coordinated Observation? section with information about the coordination between TESS and NICER, if desired.

TESS Sector Number for NICER Target

Enter the TESS sector number for the NICER target as determined by the Web TESS Viewing Tool or the list of observing times of TESS sectors on the TESS MIT website. Observation of this TESS sector must occur during the NICER proposal cycle's observation interval in order to be considered a joint observation. For example, NICER Cycle 7 observations take place between March 1, 2025, and February 28, 2026 (for a one-year NICER proposal). Thus the allowed TESS sector numbers for the NICER Cycle 7 interval are 90 through ????.

If you are proposing for the NICER-TESS joint program and either do not desire to have a specific NICER target observed by TESS or TESS cannot observe the target during NICER's observation interval for this proposal cycle, then leave this field blank. Otherwise, you must specify the TESS sector number for any NICER target that you want TESS to observe.

TESS 20-Second Cadence Slot?

Indicate "Yes" if 20-second cadence postage stamp data is requested for this target. Otherwise, only 2-minute cadence data will be provided. Only 50 20-second cadence slots are available in the entire NICER-TESS joint program.

TESS Observation Remarks

Any comments you wish to make regarding the TESS observation of the NICER target can be provided in this field. The justification for the TESS observation, however, must be provided in the scientific justification. Up to 1000 characters. Optional.

Last Modified: Thursday, 25-Jul-2024 16:31:15 EST

For assistance please contact the ARK Help Desk

HEASARC Staff Scientist Position - Applications are now being accepted for a Staff Scientist with significant experience and interest in the technical aspects of astrophysics research, to work in the High Energy Astrophysics Science Archive Research Center (HEASARC) at NASA Goddard Space Flight Center (GSFC) in Greenbelt, MD. Refer to the AAS Job register for full details.

Search: