Directions for Phase 2 Submission
GALEX GI Program, Cycle 2, Starting 1 October 2005
PIs of accepted proposals (not archival proposals) should have received a template for submitting Phase 2 information. Many of the fields have been prefilled for you from your Phase 1 information (for reminders on the fields, see information shown below). Note that disallowed targets (listed in "Additional Comments" section of the peer reveiw report) have not been removed. This will be the PI's responsibility. Please read carefully the steps shown below.
Please edit the template we sent you in August (NOT your original copy) to revise your target information as noted below.
SAMPLE XML template files for Phase 2 may be found at http://galexgi.gsfc.nasa.gov/Cycle2/Phase2/index.html
After you update the template, you should check it using the validation tool, also at http://galexgi.gsfc.nasa.gov/Cycle2/Phase2/index.html and make any corrections needed.
Submit the final, completed Phase 2 template by emailing it to
finalsubmission@galexgi.gsfc.nasa.gov
Please note the following while revising your Phase 2 template.
0. It is the PROPOSER'S responsibility to verify the observation information. Please pay particular attention to the target information. It is the PROPOSER'S responsibility to specify observations that are safe for the instrument. Observations will not be repeated for errors that are the proposer's.
1. Targets will only be accepted after 1) a successful Phase 2 submission and 2) a safety check by the SODA (Science Operations and Data Analysis team at Caltech. Unsafe fields may be rejected by the SODA team without further work on their part. Please check your targets against the brightness checker and Zodi background checker at http://galexgi.gsfc.nasa.gov/tools/index.html. If you have questions or need help, send email to galexhelp@galexgi.gsfc.nasa.gov
Note: (8/24/05) If you have brightness limit concerns, here is the latest information. FUV limits remain the same. Observations are being performed that will determine what the NUV bright source limit will be. When preparing your xml file, submit as much information as possible (the science target position is critical, possibly a small table of brightest stars in field) and mission planning will work through GALEX GI Helpdesk Team to get your targets through Phase 2. Please read the BRIGHTWAIVER information below as well.
2. If targets were disallowed as described in the "Additional Comments" section of the peer review report, proposers should remove them from the target list. Please do not renumber your targets after removing disallowed targets.
3. Proposers may not add targets/observations in Phase 2 which were not originally proposed in Phase 1, other than grism pre-images as directed in the review recommendations.
---------------------------------------------------------------
Information about the Phase 2 template fields
PROPOSAL AND GI IDENTIFICATION: Identifying information (<nasapropno>,
<title>, <PI> and associated contact information, <programcategory>) will be autopopulated from the Phase 1 submission and should be left alone unless corrections are needed for the contact information. The <contact> block has been autopopulated with the GI's information; it should be changed if someone besides the PI will be the individual responsible for planning the observations.
TOTAL OBSERVING TIME: Replace this with the observing time allocated in the award letter from NASA (and in the email note sent in early August about time allocation).
OBSERVATIONS: Please check carefully and update as necessary. These are organized one observation at a time. An imaging observation and a grism observation of the same target are two different observations and each needs an independent entry. Repeated observations of the same target are two different observations and each needs an independent entry. Multi-orbit integrations of the same target count as a single observation; this includes grism observations at different orientations on the sky.
Comments about individual tags:
TARGNO: Do not change. If you are adding new observations (e.g. grism pre-images) enter "NEW". Phase 2 checking / submission software will assign <targno> for new targets.
PRIORITY: Rank each target's priority to your program. 1/3 of your targets should be priority 1 (high), 1/3 priority 2 (med) and 1/3 priority 3 (low). If you only have one target, make it priority 1. This parameter is added to mitigate the effects of, for example, possible unexpectedly low GALEX observing efficiency. It does not have anything to do with the likely observing order of your targets. Note that the priority tags are initially empty; you must fill them in. If you don't set your priorities, or do not divide your priorities evenly between 1,2,3, we will assign them all to priority 3.
OBJECT NAME: Please use IAU conventions for target names, in the <objectname> field. (Information on IAU conventions at:
http://galexgi.gsfc.nasa.gov/Cycle2/Phase2/index.html )
RA/DEC: All coordinates are in J2000. Using other epochs will result in observing the wrong place in the sky. RA can be specified as <hrs> or <deg>, either decimal or sexagesimal (separated by :'s). You can also specify RA as <hrs> or <deg> plus <min> and <sec>. The following examples are all acceptable:
<ra> <hrs> 12:34:56 </hrs> </ra>
<dec><deg> -33.43536 </deg> </dec>
<ra> <deg> 12.4567 </deg> </ra>
<dec><deg> -00:01:02 </deg> </ra>
<ra> <deg> 47 </deg><min> 19 </min><sec> 19.9 </sec></ra>
<dec> <deg> -33 </deg><min> 25 </min> <sec> 23.4</sec></dec>
POSITIONS: Note that you must include at least two positions:
-- <pointing> for the field center (i.e. the center of the FOV), and
-- <sciencetarget> for the position of target of scientific interest
We have assumed (incorrectly, in many cases) that the RA and DEC submitted in Phase 1 is appropriate for both <pointing> and <sciencetarget> positions. If you have more than one science target in a field, add additional <sciencetarget> fields with the appropriate contents. In cases where the field center requires shifting to avoid bright stars or to reduce glint from nearby bright stars, you can find tips for workarounds at
http://galexgi.gsfc.nasa.gov/tools/chkbstar_whatif.html
You can explore possible moves of the field center using the GALEX PI team's GMOSAIC tool at http://galexgi.gsfc.nasa.gov/tools/index.html
You should verify that <pointing> passes the brightness checker, at
http://galexgi.gsfc.nasa.gov/tools/index.html .
SCIENCE TARGET SIZE: You will need to add a size (~diameter) in arcminutes, for each target of scientific interest in the field. For point sources, set <sciencetargetsize> to 0.01. Note that this field is not pre-populated, but the submission checker requires it to be filled.
SPECTRUM / BRIGHTNESS: Following the position and size parameters is a block of science target parameters that are not expected to change from the Phase 1 submission. These include:
<spectype> </spectype>
<colorexcess> </colorexcess>
<sourcetype> </sourcetype>
<lambdaref> </lambdaref>
<fluxlambdaref> </fluxlambdaref>
<fluxacc> </fluxacc>
<signoise> </signoise>
INSTRUMENT SETUP: These are from Phase 1, and normally will not change
<aperture> </aperture> GRISM or IMAGE
<mode> </mode> ONE or MULTI (presently ONE is only option)
<numsteps> </numsteps>
Additional information is requested for some instrument setups:
GRISM PREIMAGE: If your observation uses the aperture <GRISM>, you will be asked to provide the name of the pre-image field (the <grismpre> field appears after the special requirements). If you will use a GALEX PI team observation for a pre-image, please give the full GALEX team target name. If you will be using a different observation in your own program, use the same name you used for that observation.
If you are using an image from another GI program, please use the name provided in the referee report.
e.g.
<grismpre> GALEX PI team target MIS3DFSGP_38185_0401 </grismpre>
or
<grismpre> Target 4 (NGC 4523) of this proposal </grismpre>
or
<grismpre> Target 64 in GI program 47; GI_047_64 (NGC4244) </grismpre>
A list of PI team and GI planned targets is at http://galexgi.gsfc.nasa.gov/targets/planned/index.html
MULTIPLE POINTINGS IN ONE ORBIT: For (possibly future) cases where the <mode> parameter is MULTI (several contiguous pointings during one eclipse), you would need to verify the number of steps <numsteps> and provide additional target entries for each <pointing>. Presently, however, <mode>ONE</mode> is the only option.
INTEGRATION TIME: The total time you want to spend in this mode, in seconds. Note that GALEX scheduling is generally by orbit ("eclipse"). Orbits should not be assumed to be longer than 1500 seconds for the purpose of planning observations. Shorter observations can be accommodated, particularly for SNAP observations; longer ones may be rounded to the nearest integral orbit by mission planners.
<obtime> </obtime> in seconds
Note: Spectroscopy proposers should revisit the GALEX Exposure Time Simulator using a pessimism factor of .33 (http://galexgi.gsfc.nasa.gov/tools/ExpTimeCalc.html)
SPECIAL OBSERVATIONAL REQUIREMENTS:
Special requirements should have been specified in Phase 1, and may not be imposed in Phase 2. Each of the special requirements require further information for Phase 2.
GRAN (Specific GRism ANgle)
In the parameter <granexplain>, please give the required angle(s) of the dispersed spectrum (East of North, e.g. straight NS is 0 deg, straight EW is 90, etc.) and acceptable tolerances (not finer than 5 degrees), and a short explanation.
e.g.
<granexplain> GRISM should be oriented with dispersion at roughly 50
degrees E of North, with a tolerance of 30 degrees. The program is
to obtain a spectrum of an extended filament that runs along a line
140 degrees on the sky. </granexplain>
FUVONLY: For FUV-only targets, in the parameter <fuvexplain>, please give short explanation of what NUV-bright object(s) (fluxes and field locations) drive the requirement for FUV-only observations.
e.g.
<fuvexplain> The cluster contains two stars that are expected to
exceed the NUV count limit by a factor of 10, but are safely
within the FUV limit. The stars are located 20, 35 and -52, -61
arcmin from the field center, and moving the field center away from
them means that half of the cluster (main science target) is moved
out of the field of view. In a few cases, specified in the peer
review letters, the FUV requirement should be deleted.
TIMECRITICAL: For Ephemeris targets, in the parameter <timecriticalexplain>, please give a clear description of the nature and origin of the restrictions on observation times, as well as the resulting time precision required. <timecriticalexplain> The timing of the obeservation during the year does not matter. However, once the first observation has been made, the second needs to be planned for 24 hours later, the third for 48 hours later, and the fourth for 96 hours later. Observations should not be more that 2 hours different from the stated interval.
</timecriticalexplain>
LOWZODI: If you specifically mentioned low-zodi observations in your proposal,
and if they are absolutely required for your science goals, you may have the EPHEM special requirement for those targets. In this case, you must also write a short justification for this need in <lowzodiexplain>. You should be aware that using this requirement reduces the likelihood that your target will be observable by GALEX.
TOO (target of opportunity)
TOO: For Targets of Opportunity, in the parameter<tooexplain> , please give detailed information of how the TOO program will be triggered where such targets will likely appear on the sky, and what will be needed from the SODA team.
e.g.
<tooexplain> Proposed TOO's will be asteroids brighter than
Mv=12, and will generally lie near the ecliptic in the hemisphere
away from the Sun. GI will notify SODA team of discovery of such
objects. </tooexplain>
Agreement on the appropriate triggering event, and subsequent
action, may need some iteration with the SODA team. TOO proposers
will be asked to work with the SODA team to develop a "skeleton"
observation plan.
MOVE (Moving target)
MOVE: For Moving targets, in the parameter <moveexplain>, please give a clear description of the target's expected motion on the sky as a function of time, and other relevant information related to that motion.
e.g.
<moveexplain> The comet is expected to move across the sky at a
rate of 0.5 degrees/hour. We will observe in AIS mode,
obtaining 30 images per orbit (<numsteps>=30), which will remove
the need to reconstruct the comet image from time-tagged data.
</moveexplain>
BRIGHTWAIVER: If your field exceeds ANY brightness limit you must enter YES in this tag and the rationale in the <brightwaiverexplain> tag. If you do not require a waiver (i.e. you have checked, and your field is safe, enter NO. Please check your targets against the brightness checker and Zodi background checker at
http://galexgi.gsfc.nasa.gov/tools/index.html
and read about workarounds at
http://galexgi.gsfc.nasa.gov/tools/chkbstar_whatif.html
You can use the GALEX PI team's GMOSAIC tool to explore possible moves of the field center. (http://galexgi.gsfc.nasa.gov/tools/index.html).
Note that that this field is NOT pre-filled, but must have some value entered. Targets that do not pass the brightness checker and do not request and justify a brightness waiver may be dumped from the program by the SODA team.
TIME-TAGGED PHOTONS / COMPRESSION: If you requested time-resolved data
in you Phase 1 proposal, please enter YES in <TIME-TAG-PHOTON-LIST> with explanation in <time-tag-photon-list-explain> , and indicate in <compressionratio> whether you want high compression (5millisec precision) or low compression (20 microsec precision). <TIME-TAG-PHOTON-LIST> is set to "NO" by default.
COMMENTS: Use the <comments> field to include other information that the mission planning team will need to schedule and execute your observations correctly. Examples might include coordinating observation with other events, contact information that will change between now and the observations, or data products that you'd like to see but are not now offered (no promises implied).
SOME DETAILS ON USING THE XML TEMPLATE
1. The template is an XML file. You do not need to be familiar with XML to update the template, but a short explanation follows:
a- Information is enclosed by tags, which are marked with angle brackets (< >).
b- Each opening tag e.g. <RA> must have a corresponding closing tag </RA>.
c- The tags are case sensitive, so <RA> and </Ra> are a mismatched pair.
d- The tags must strictly nest within each other.
e- The content of each item is contained between the opening and closing tags.
E.g. <deg> 01:23:45 </deg>.
f- You may use as much or as little white space (spaces, tabs, carriage
returns) as you please. We have inserted a fair amount to try to make
the file easier to read.
2. Please use only plain ASCII text. Do not use any LaTeX formatting or macros, or any other formatting. It may do bad things to your observing instructions which neither you nor we will recognize, and waste valuable observing time
3. Please use < to indicate a less-than symbol '<', to avoid confusing the XML parser, or write out the words "less than" in text fields. All other symbols (including '>') are OK.. Please use Å to indicate the Angstrom symbol.
4. The Phase 2 template can be edited with any text editor program.
VALIDATION OF YOUR XML FILE
We will provide a style-sheet that will check your submission for basic validity (e.g. things we expect to be numbers are numbers, all required fields are filled in, etc). For those of you not familiar with SMX and XSLT style-sheets, we will also provide a way to validate your Phase 2 template before final submission via our website at http://galexgi.gsfc.nasa.gov/Cycle2/Phase2.
If you have any questions, please send email to galexhelp@galexgi gsfc.nasa.gov.
Please do NOT contact us individually, as several of us will be on vacation during parts of August.
Responsible NASA Official: Susan G. Neff
Curators: Joan E. Hollis and Joel D. Offenberg