Uploading Cycle 3 .xml Files into AKBAR/RPS Header Body-ED
NASA GSFC: GALEX
Galaxy Evolution Explorer
 

Site Home Page

Helpdesk

Targets

Tools

Data

Instrument & Calibration

Science

Documents

Cycle 6 Information

GALEX at Caltech

 

For Cycle 5, we will use GALEX proposal submission via ARK/RPS (Remote Proposal System) used by the HEASARC (result of reorganization at NASA / GSFC). Please send email to us at the helpdesk if you have questions or run into difficulties (unless they are clearly questions specific to RPS/AKBAR, in which case they should go to the ARK/RPS helpdesk).

ARK/RPS is very straightforward - you enter your proposal and target information (web-based form), verify it, submit it, and then upload your science justification as a .pdf file. However, if you submitted a proposal in Cycle 3 that you wish to resubmit, particularly if you have a large number of observations, you may wish to upload your Cycle 3.xml target file, rather than re-entering the observation information. You will still need to request and set up an ARK/RPS account, and join the GALEX RPS group. Then, from the GALEX ARK/RPS page, click on "Submit New Proposal". Once it brings up a blank form, click on the "Reload" button, and upload your .xml file.

 

The upload is pretty good, but it is not perfect - mostly because we made some changes to the information needed. There are a few areas that will need adjusting:

1) Co-Investigator information.

Names: in our previous .xml file, we did not separate Co-I's first and last names. ARK/RPS makes its best guess, but sometimes it gets the split wrong.

Institution: If you did not use the same form/spelling institution name that ARK/RPS keeps, then ARK/RPS does not recognize the institution and leaves the field blank - you can select most institutions from the drop-down menu (or request to be added).

E-mail address - we are now required to collect e-mail contact info for all proposers, including co-I's, so you'll need to fill this in.

2) Observation time (integration time) - Check to be sure that the time requested is correct, in kilosec (not seconds), for each observation.

3) Grism pre-images. We now need to collect coordinates and exposure times for grism zero-order images (pre-images).We have not collected this information previously, so you'll need to type it into the ARK/RPS form. (Note that archival pre-images must be within 15' of the proposed grism observation, and they must have integration times at least 5% of the requested grism integration time; if not then you'll need to add a new pre-image observation to your program. Also, please note that AIS images cannot be used as pre-images - the GALEX data pipeline cannot use them.)

4) Archival data - you'll now need to enter the exposure time for archival observations. This was optional in the past.

5) Constraints. We now ask you to explicitly denote any constraint(s) your observation has, explain it briefly here, and more fully in the feasibility section of the proposal. Time constrained observations of any sort (orbital phase, coordination with other observations, specific timing etc.) should be noted here if you don't want your proposal to be disallowed.

 

 

 


Responsible NASA Official: Susan G. Neff
Curator:
Dot Appleman

NASA Privacy, Security, Notices