Reference Documents and Web Links
General link to FUSE Guest Investigator Web page at NASA/GSFC is http://fusewww.gsfc.nasa.gov/fuse. From there you can get to the following resources:
General link to FUSE Science Center Web page at JHU is http://fuse.pha.jhu.edu. From there you can get to the following resources:
The submission of Phase 1 proposals for Cycle 2 Guest Investigator (GI) observations with FUSE is the first step in the process that will ultimately lead successful proposers to actual data from the FUSE satellite. GIs will go through a two-phase proposal process. The purpose of Phase 1 is primarily scientific justification and feasibility analysis, ending with the selection of certain proposals by NASA, based on the advice provided by a scientific peer review. The purpose of Phase 2, in which only successful Phase 1 proposers participate, is to provide FUSE mission planners with sufficient information to properly schedule and carry out specified observations.
This document provides all of the supporting
information and documentation necessary to help potential GIs
fill out and submit the Phase 1 template files for the first cycle.
Section 2 provides a brief overview of the Phase 1 proposal process
and describes some general issues about which you should be aware.
Section 3 provides a field-by-field description of the Phase 1 form,
including any syntax issues, and discusses acceptable values or choices
for each parameter.
Section 4 contains a filled-out example form for reference.
The NRA discusses the submission process for Phase 1 proposals.
2. FUSE Phase 1 Overview
The Phase 1 template file is an ASCII LaTeX file containing a set of keywords, similar in many respects to what HST proposers have been using for a number of years. Entries for some keywords will be "required," while entries for others will be "optional," depending on the situation. Electronic submission of the LaTex template file is required of all proposers, since this file will be parsed into a database to support the technical evaluation of proposals. In addition, proposers must submit 12 paper copies of the formatted proposal, which can be most conveniently done using the LaTex formatting software with the "phase1.sty" style file provided by the FUSE project and available by way of the instructions given in the NRA. (Proposers without access to electronic mail should consult the NRA for further information.) Since the forms are in ASCII format, users can edit the files using whatever text editor they wish, and the formatted proposal can also be generated with other software, provided the format given in the NRA section C.2 is followed.
The form contains general "coverpage" fields requesting support and
contact information, followed by text blocks describing the scientific
justification, feasibility and safety analysis, and other descriptive
information about the proposed observations. These sections are followed by a
Target/Observation specification listing, consisting of a set of keywords
that are repeated for each proposed target. These fields provide
both "object" and "exposure" information for each target, i.e., there
are NOT separate target lists and exposure lists.
The information requested will permit
planning personnel to assess the feasibility and safety of the
requested exposures for reporting to the scientific review panels.
(On-line tools are provided to allow users to estimate count rates
and expected signal to noise ratios, and the use of these tools is
strongly encouraged.) Any situations not handled
gracefully by the keywords can be further described in text blocks
that are part of the Phase 1 submission. Very little instrument-specific
information is requested from the proposer in Phase 1.
Instrument Safety Concerns
The Phase 1 submission includes flux and desired signal-to-noise information for each target. This information will be used to determine whether the proposed observations are feasible and consistent with the expected capabilities of the instrument. In addition, FUSE has brightness and exposure limits for both continuum and emission-line sources. (See the FUSE Observer's Guide.) Expected source fluxes extrapolated from longer wavelengths, especially with uncertain extinction characteristics, can be significantly in error. Thus, the FUSE operations team will be cautious with any objects that are within a factor of ten of the stated brightness limits. While the flux and reference wavelength information you provide in Phase 1 should in general be at a wavelength of interest to your science, this may not be representative of the overall source brightness. It is thus extremely important that you discuss in the text the extent to which the peak source fluxes may be higher than that specified on the target listing, and whether substantial uncertainties exist in the flux estimates you use. In summary, the "Feasibility and Safety" text section is important!
Emission-line objects are a special case, because they do not cause
TOTAL flux or count-rate problems but can still be a safety hazard for the FUSE
detectors. While we can flag certain target
classes for special inspection (such as symbiotic stars), YOU know your
targets better than we do. We request for emission-line objects that
you specify the flux-related keywords (including line width) for the
brightest emission line expected, whether or not it is the line
of specific interest to your scientific program. FUSE mission planners can
then assess the situation directly. Again, this is most important for bright
objects that approach the stated brightness limits within a factor of ten.
You should describe carefully any uncertainties in this situation in the
proposal text. For instance, if the intrinsic line widths of your source are
unknown, and this introduces significant uncertainty into the safety
calculation, thit should be stated explicitly.
Special Requirements
Special requirements, or SRs, are less complicated and less extensive than those needed for HST, but serve much the same function: they flag the system to some relatively infrequent but supported mode or situation that requires special attention. The Phase 1 form contains a text block for a general description of your observations and justification of any SRs your program requires. The SRs described below are then entered into the target listing where needed on specific targets. In some instances, more than one SR may apply; all appropriate SRs should be supplied in the target list, separated by commas. NONE of these SRs should be specified frivolously, since they may seriously constrain the schedulability of an observation.
Special Requirements (SRs) for Cycle 1:
Default Aperture and Aperture Selection
After launch, it was determined that the LWRS (30x30 arcsec) apertures would be considered the default observing apertures. This was because thermal effects, both on an orbital time frame and as the pointing is changed between targets, causes the channel alignments to vary. The motions are such that, with care in planning the observations, most point source observations can obtain 4-channels of data when using LWRS. It was also determined that, for point sources (and especially point sources observed in time-tag mode), the spectral resolution is only affected in a minor way, especially on the longer wavelength (LiF) channels. (Some degradation occurs on the SiC channel data or for histogram mode data--see the FUSE Observer's Guide for more information.)
Observations with the MDRS (4x20 arcsec) or HIRS (1.25x20 arcsec) apertures are possible in certain situations. If the wavelength range of primary interest is longward of about 1000 Angstroms (Å), observations are possible because the LiF channel alignments are relatively well behaved. For MDRS, users may want to modify time requests based on the lower total effective area without the SiC channels. (For HIRS, users should only assume the LiF1 channel and calculate necessary observing times accordingly.)
If full wavelength coverage is required with the MDRS apertures, the observation will be considerably more difficult and inefficient operationally. At the time of this writing, the FUSE team is developing procedures for achieving this capability, but only for objects with sufficient FUV flux to allow Peak-up acquisitions (see below). These observing procedures, which may involve multiple Peak-up acquisitions per orbit for realigning channels, may decrease observing efficiency for such observations by a factor of two. Hence, it is extremely important that users requesting MDRS specify whether SiC channel coverage is REQUIRED or simply DESIRABLE for their science. This will allow the operational impact of your request to be assessed properly.
Users requesting use of MDRS or HIRS should discuss explicitly why these apertures
are required, and must also discuss the role of short wavelength (i.e., SiC channel)
data in the pursuit of their scientific objectives. This can be done either in the
scientific justification text or in the feasibility text section, at the user's discretion.
Target Acquisitions and Offset Targets
One positive operational effect of observing primarily with the LWRS apertures is that in many cases the acquisition procedures are simple. Assuming accurate coordinates in the HST guide star reference frame, we select guide stars around each object position and then place the desried coordinate position in the LWRS apertures. (This is called a "guide star acq.")
Guide star acqs may or may not be sufficient to place your target into MDRS, but even if it does, the channel alignment issue still needs to be addressed. Hebce, for successful MDRS observations, the target FUV fluxes must be sufficient for a so-called "Peak-up acq." In this case, the target is placed in/near the MDRS apertures and stepped in X coordinate (across the apertures). The onboard instrument computer processes these data and aligns the channels where fluxes are maximized. This procedure works well for the initial alignment, but best alignment only lasts from 8 - 12 minutes, especially for the SiC channels, before channel misalignments occur. Peak-up acqs in the HIRS apertures work as well, but the thermal drifts affect alignments on an even shorter time scale. (This is why we urge users to assume only the LiF1 channel when using HIRS.)
Objects requiring MDRS that are too faint or extended in the UV to acquire with a
peak-up may need one of several alternate acquisition scenarios
necessitating use of an offset star or nearby offset field. Since the need for
this should be infrequent, we refer users to the
FUSE Observer's Guide for details and restrictions on offset stars.
While offset stars are not requested explicitly in the Phase 1 form,
you should discuss the need for and availability of appropriate offset stars in
the "Description of Observations" text block. Any such offset stars needed will
have to be specified explicitly in Phase 2 for successful proposers.
Calculating Signal-to-Noise Ratios
A "lesson learned" from on-orbit operations to date is that the combining of data from the different channels is a complex operation, especially if one is concerned with maintaining the highest resolution and/or handling statistical errors correctly. In many cases, users may want to consider not only the total effective number of counts from all four channels, but also the signal-to-noise they will achieve from an individual channel of the spectrograph.
The on-line tools (e.g. the Exposure Time Calculator and the Count Rate Tool)
for Cycle 2 have been updated to provide (or allow specification of) signal-to-noise
for individual channels as well as the total. It is important that users
describe their S/N calculations and assumptions in the feasibility text section.
Also, a new keyword has been defined starting in Cycle 2 for the user to specify
the channel assumed (or TOTAL) for the signal-to-noise calculation on each target.
Coordinated Observations and Beta Angle Considerations
For any number of scientific reasons, coordinating FUSE observations with other space-based or ground-based facilities may be desirable. However, operational constraints discovered during Cycle 1 make coordinated observations very difficult, and often extremely inefficient, to schedule. Even modest coordination (at the several week level) can become a significant driver to overall scheduling of a given time period.
Briefly, we have found that, in order to maintain optical alignment of the channels, we should restrict the beta angle (beta is the angle from the anti-sun point) to approximately the 30 - 85 degree range. Outside of this range, channel misalignments become not only larger, but more unpredictable. Furthermore, even within the new operational range, channel motions can be significant and can take a number of orbits to thermalize, or relax into their calculated relative positions. To first order, the larger the beta angle change between targets, the longer the thermal relaxation timescale and the greater the possibility of actually losing one or more channels in the subsequent observations. Because of this, FUSE mission planning tries to manage beta angle changes between targets as much as possible.
It should thus be obvious why coordinated observations, or any other time-critical or time-specific observation, becomes a driver for scheduling: Any observation that says "we need to be in a certain place in the sky NOW" drives targets both before and after the desired target to also be in that part of the sky. (Or alternatively, it drives us to perform a special realignment just for the coordinated observation, which takes about half a day and considerable human and other resources.)
Recognizing the potential importance of coordinated observations, the FUSE project
will support a limited number of such requests on a best effort basis. For Cycle 2
GI programs, this will be limited to 12 observations, or roughly once per month
on average. Hence, ths is a very limited resource, and the desire for coordinated
observations should be discussed in detail in the "Additional Information" text block.
Requests for coordinated observations in Phase 2 that were
not discussed and justified in the Phase 1 submission will have lower
priority for implementation than requests that were accepted as
part of the Phase 1 process.
3. FUSE Phase 1 Proposal Keyword Definitions
In this section, we step through the Phase 1 form and describe the expected or allowed entries for each of the keywords and note what should be addressed in each text section. Please note that you can bury comments anywhere within the form by preceding them with a "%" sign. However, any such comments you add are for your own use; they will not be processed or read by FUSE mission planners. Only material in the standard text blocks will be processed. For keywords with curly brackets information should be inserted between the curly brackets. Text blocks are simply inserted below the appropriate keyword entry. An example form showing the proper syntax is provided in section 4, and many helpful guidelines are also included directly in the Phase 1 template file.
1. Proposal Title
\title{} (Required)
The program's title should be as short and descriptive as
possible and should be no more than about 100 characters.
(The requirement is "no more than two lines on the formatted output.")
2. Principal Investigator Contact Information
Please supply the requested contact information for the PI.
All fields should be supplied for the PI, who is assumed to be
the primary point of contact for any questions about the program.
\pititle{} [e.g. Dr., Mr., Ms., Prof., etc. ] (All required)
\pifirstname{} [e.g. John, or John G. to include middle initial]
\pilastname{}
\piaffiliation{} [e.g. Department of Astronomy, etc.]
\institution{} [e.g. your university or institute name]
\address{} [e.g. 123 East St., Baltimore, MD 21218]
\country{} [e.g. USA, UK, CAN, FRA, etc.]
\phone{}
\fax{}
\email{} [e.g. [email protected]]
3. Scientific Category
\scientificcategory{} (Required)
Select a primary scientific category for your proposal, from the following list.
This category will be used in scientific peer review panel selection.
4. Observation Summary Information
\totalobstime{} (Required, in ksec)
\totalobjects{} (Required)
After specifying your observing program, you should fill in this summary
information. The \totalobstime is the total requested observation time
in kiloseconds for all targets in the program. Any observations with
\integrationtime values less than 4000 seconds in your target listing
should be accounted as 2 ksec toward this total. Likewise, any SAFTSNP
exposures, which are likely to be very short, are accounted as 4 ksec
toward this total. This is done to account (approximately) for the large
overhead expected for objects with short exposure times. See the FUSE
Observer's Guide for more information.
The \totalobjects keyword indicates the number of independent positions on the sky you wish to observe. (Multiple positions in extended sources should be counted as separate targets, but moving targets should be counted as one target.)
5. Abstract (Required, text block)
Enter a brief description up to about 200 words between the
\begin{abstract} and \end{abstract} keywords summarizing
your program's goals. (The real
restriction here is that the abstract should fit on the front page of the
proposal when formatted.) The abstracts for all successful proposals will
be made available on-line.
6. Co-I Information (Required for all Co-investigators)
Format is similar to the PI entries, but less extensive information
is requested.
\coititle{} (Required for any Co-Is; duplicate and repeat as needed
\coifirstname{} for each Co-I.)
\coilastname{}
\institution{}
\country{}
\phone{}
\email{}
7. Scientific Justification (Required, text block)
Enter text after the \justification keyword.
Describe the scientific justification for the proposed program, stating clearly
its goals and significance to astronomy. You should include a brief discussion
of scientific background, previous work, and why FUSE data are needed to address
your goals. The Scientific Justification
is limited to three pages including
figures, tables, and/or references. Other text blocks are provided below for
further descriptive material about the program.
8. Feasibility and Safety (Required, text block)
Enter text after the \feasibility keyword.
Discuss in detail the signal-to-noise and resolution requirements for
your proposed observations and whether your estimates apply to the total
data set or an individual channel. Describe the quality of your flux estimates
or extrapolations into the FUSE range. Describe explicitly any targets
or situations that may create concerns for instrument safety. Finally,
describe your method of estimating the necessary exposure times for your
targets. You are STRONGLY ENCOURAGED to use the on-line exposure time
calculator and/or spectral simulators in making these estimates. Up to
one page single spaced can be used for this section.
9. Description of Observations (Optional, text block)
Enter text after the \describeobservations keyword.
Up to one page of additional description is permitted here to address
any "strategy issues" on how the observations should be performed.
Examples include:
10. Additional Information (Optional, text block)
Enter text after the \additionalinfo keyword.
Up to one page of text can be supplied here to describe anything else
about your proposed program that is relevant or that the review panel should know.
(Note that this section is NOT intended to serve as additional space for Scientific
Justification.) Examples that might be discussed include:
In addition, proposer's may wish to discuss the desire for certain "extended" capabilities of the satellite that may become available. These include such things as:
11. Investigator Information (Optional)
Provide a short biographical sketch for the PI after the \vita keyword,
including recent publications relevant to this proposal. Relevant information
about CoIs may also be included here at the proposer's discretion,
but the total length of this section must not exceed one page when formatted.
12. Target List and Observation Summary (Required)
Repeat keywords as necessary for each target to be observed. In the formatted
proposal, this information will come out in tabular format on a separate
page or pages at the end of the proposal.
\objectname{} (Required)
Object naming conventions and syntax will generally follow those
developed for use in HST proposals. Please refer to Appendix A below
for FUSE target naming conventions. (Note: if other names are used in the
proposal text, provide cross references in "Additional Information"
section above.)
\ra{} (Required)
\dec{}
Coordinates in standard astronomical format (HH:MM:SS.SS and
[+/-]DD:MM:SS.S), referenced to the J2000 equinox, are required. In
general, the most accurate coordinates available should be provided
whenever possible, but accuracy to at least 5 arcsec is required for
target duplication checks. For moving targets or TOOs of unknown position,
provide "all nines" for these fields (e.g. 99:99:99.99, -99:99:99.9, etc.).
\vmag{} (Required for continuum sources)
Johnson V magnitude or equivalent.
\spectype{} (Required)
Provide MK spectral type and luminosity class for all stellar objects.
Multiple entries are allowed for unresolved binaries, but no spaces are
permitted. Hence, O7Ve+WN6 is allowed, but B3 III is not.
For other types of sources, choose the best abbreviation from the following
list of object types: QSO, AGN, GAL (galaxy), SOL (solar system object), CV
(cataclysmic variable), PN (planetary nebula), SNR (supernova remnant),
CSPN (central star of planetary nebula), PSR (pulsar), REF (reflection nebula),
CLU (cluster of galaxies), or OTR (other).
\colorexcess{} (Optional)
Measured E(B-V), if available.
The next set of keywords define the flux and source type information necessary for checking observation safety and feasibility and verifying the proposer's expectations.
\sourcetype{} (Required) PC, PE, EC, EE
A two-letter mnemonic is entered, indicating first whether the
source is point-like (P) or extended (E), and secondly whether it is
primarily a continuum (C) or emission-line (E) source. For FUSE, any source
below 2 arcsec is effectively point-like. In cases with
both continuum and emission lines, the user should choose the one more
important to the scientific program. This flag affects the detailed meaning
of some of the entries given below (for instance, the units of "flux")
and should be consistent with the other data entered.
Also for combination sources, FUSE mission planners needs to know of any special situations that might cause safety concerns. For instance, if you were interested in the continuum level of a symbiotic star, but strong emission lines are also expected, you would specify "PC" here, and give the appropriate fluxes, etc., below. However, the feasibility text block above should discuss the expected peak line intensities and verify that they are below stated safety limits for the detector. (See the FUSE Observer's Guide for information about brightness limits.)
\lambdaref{} (Required)
A reference wavelength in Angstroms (Å) should be entered. This should
be a wavelength within the FUSE range (i.e. 905 - 1187 Å). This is the
wavelength for which the flux below pertains and for which the S/N has
been calculated. As such, it should be a wavelength of interest to your
scientific program. (For emission line sources, this should be the brightest
line expected in the spectral range, usually O VI 1032.)
\fluxlambdaref{} (Required)
The user should enter a "flux" value, in n.nnE-nn format (where each "n" is
a single-digit integer), corresponding to the above reference wavelength.
The expected units are ergs/cm^2-s-Å for continuum sources, and integrated flux
(ergs/cm^2-s) for emission line sources. For extended sources, the flux should
be the total flux expected through the selected aperture. Refer to the FUSE
Observer's Guide for important information on brightness limits for continuum
and emission line sources.
\fluxaccuracy{} (Required) HIGH, MED, LOW
This keyword is used to indicate the accuracy level of the flux information
provided above. (This is important for both safety and onboard memory
usage estimation.) As a guideline, HIGH should indicate an actual observed value
in the FUSE range (say 1200 Å or below, from HUT, ORFEUS, or HST)
or a small extrapolation from <=1300 Å MED should indicate situations
where extrapolation from longer UV wavelengths was required, or where
some model-dependent or reddening uncertainty is involved; and LOW
corresponds to more uncertain estimates (e.g., a larger extrapolation from, say,
optical wavelengths or where the reddening curve or E(B-V) applied is uncertain).
\elinefwhm{} (Required for \sourcetype = PE and EE)
FWHM of line in decimal Å should be entered.
Only needed if source type involves emission lines.
\sblambdaref{} (Required for \sourcetype = EC and EE)
Expected surface brightness (flux units from above per square arcsec) in n.nnE-nn
format; only needed if source type involves an extended source.
\resolutionelement{} (Required)
This field should indicate the size of the resolution element over
which the quoted signal-to-noise ratio below has been calculated,
in Å. This may be larger than the actual expected resolution of 0.033
Å, depending on the needs of your program. (Note: FUSE data will
always be obtained at the highest possible resolution; any binning is
left to the user.)
\signoisechan{} (Required)
This keyword is new as of Cycle 2, and specifies whether the listed signal-to-noise
applies to a particular channel or is for the total effective area at the specified
wavelength. The user can choose these options in the Exposure Time Calculator.
Valid entries are SIC1, SIC2, LIF1, LIF2, or TOTAL.
\signoise{} (Required)
This should be the expected signal-to-noise per specified resolution
element at the reference wavelength. Only requests for values of 30 or smaller
per default (0.033 Å) resolution element can be supported for Cycle 2
requests, although techniques for improving this are being studied.
Whether your S/N entries pertain to an individual channel or the entire data set
should be addressed directly in the "Feasibility" text block.
\aperture{} (Required)
Enter a four-character mnemonic for the FUSE aperture to be used
for the observation. The options are:
\specialreq{} (Optional, as needed)
Supported special requirements for Cycle 1 are TOO, MOVE,
ROLL, MON, SNAP, SAFTSNP, and EPHEM. (Meanings are described above in section
2.) If more than one SR is needed on a target, uncomment multiple SRs
in the template file listing.
\numvisits{} (Required)
For programs desiring MON (or EPHEM, if more than one phase is desired)
observations, more than one visit to
the same target will be explicitly required for the science, and this
keyword should be set appropriately to indicate the number of independent
observations that will be required. This value times the
"\integrationtime" value provides the total time needed for the target.
Most of the time, this keyword will default to "1", even for targets
requesting long exposure times. (The proposer is NOT expected to figure
out how requested times will get broken into "visits" in the sense
that it is done with HST; this will be handled internally to the FUSE
planning system.)
\integrationtime{} (Required)
Enter the total integration time desired for the observation, in units of
seconds. This does not include acquisition, but is the actual
desired integration time on target, and should correspond to the observing time
needed to produce the quoted S/N ratio above. If the MON special
requirement is set above, this should be the length of an individual
monitoring observation, with this value times the number of visits
giving the total time for the target. For SNAP observations, this
is the length of the short "test" exposure; a separate target entry should
be provided for the proposed "science" observation. For SAFTSNPs,
enter 4000 seconds (for accounting purposes only).
% FUSE Phase 1 observing proposal LaTex template (version 2.0)
% For Cycle 2
\documentstyle[phase1,12pt]{article}
\begin{document}
% 1. Proposal Title
\title{FUSE Observations the Universe}
% 2. Principal Investigator information
% Please supply the requested contact information for the PI
\pititle{Prof.}
\pifirstname{H. Warren}
\pilastname{Moos}
\piaffiliation{Dept. of Physics and Astronomy}
\institution{Johns Hopkins University}
\address{3400 N. Charles St, Baltimore, MD 21218-2686}
\country{USA}
\phone{410-516-1234}
\fax{410-516-4321}
\email{[email protected]}
%
% 3. Scientific Category
\scientificcategory{INTERSTELLAR MEDIUM AND GALACTIC STRUCTURE}
% 4. Observation Summary Information
\totalobstime{50}
\totalobjects{2}
% 5. Abstract
\begin{abstract}
Blah, blah, blah. Text should be all ASCII characters, but may include
LaTex formatting commands as desired.
\end{abstract}
% 6. Co-Investigator list
\begin{investigators}
\coititle{Dr.}
\coifirstname{George S.}
\coilastname{Sonneborn}
\institution{NASA/Goddard Space Flight Center}
\country{USA}
\phone{301-456-7890}
\email{[email protected]}
\coititle{Prof.}
\coifirstname{Possible}
\coilastname{Collaborator}
\institution{Observatoire de Paris}
\country{FRANCE}
\phone{33-1-44-12-34-56}
\email{[email protected]}
\coititle{Ms.}
\coifirstname{Graduate}
\coilastname{Student}
\institution{Dominion Astrophysical Observatory}
\country{CANADA}
\phone{250-123-4567}
\email{[email protected]}
\end{investigators}
% 7. Scientific Justification.
\justification % <=3 pages, including figures, tables and refs.
Blah, blah, blah.
% 8. Feasibility and Safety.
\feasibility % <=1 page
Blah, blah, blah.
% 9. Description of Observations.
\describeobservations % <=1 page
Blah, blah, blah.
% 10. Additional Information.
\additionalinfo % <=1 page
Blah, blah, blah.
% 11. Investigator Information.
\vita % <= 1 page
%----------------------------------------------------------------------
% 12. Target List and Observation Summary
%----------------------------------------------------------------------
\begin{observations}
% Repeat this set of keywords for every target (two targets shown).
% Target 1: Example of a stellar source with MON spec. req.
\objectname{HD123456} % see Appendix A of Phase 1 instructions for conventions
\ra{12:12:12.12} % HH:MM:SS.SS (J2000 equinox)
\dec{-45:45:45.4} % DD:MM:SS.S (J2000 equinox)
\vmag{12.1} % Johnson V magnitude
\spectype{O3III} % Enter a spectral/object type.
\colorexcess{0.05} % Measured E(B-V)
\sourcetype{PC} % Point Continuum
\lambdaref{1000} % Reference wavelength in Angstroms
\fluxlambdaref{1.25E-12} % Flux value at wavelength \lambdaref
\fluxaccuracy{HIGH} % HIGH
%\elinefwhm{} % FWHM of line in Angstroms for emission line objects
%\sblambdaref{} % Surface brightness at wavelength \lambdaref
% NOTE: Unused keywords can be left in the file!
\resolutionelement{0.10} % Size of resolution element in Angstroms
\signoisechan{TOTAL} % SIC1, SIC2, LIF1, LIF2, or TOTAL.
\signoise{25} % Expected S/N per resolution element
\aperture{LWRS} % LWRS 30"x30")
\specialreq{MON} % Monitoring observations
\numvisits{4} % Number of visits required for each object
\integrationtime{10000} % Desired integration time, in seconds (per visit).
% Target 2: Extended Emission Line Source
% with ROLL spec. req.
\objectname{NGC6543} % see Appendix A of Phase 1 instructions for conventions
\ra{10:10:10.10} % HH:MM:SS.SS (J2000 equinox)
\dec{+35:35:35.3} % DD:MM:SS.S (J2000 equinox)
\vmag{} % Johnson V magnitude
\spectype{PN} % Enter a spectral/object type.
\colorexcess{0.1} % Measured E(B-V)
\sourcetype{EE} % Extended Emission-line
\lambdaref{1032.} % Reference wavelength in Angstroms
\fluxlambdaref{8.25E-12} % Flux value at wavelength \lambdaref
\fluxaccuracy{MED} % MED
\elinefwhm{0.34} % Angstroms; note: 100 km/s FWHM.}
\sblambdaref{3.30E-13} % per sq. arcsec; assumes "filled" HIRS slit.
\resolutionelement{0.10} % Size of resolution element in Angstroms
\signoisechan{TOTAL} % SIC1, SIC2, LIF1, LIF2, or TOTAL.
\signoise{15} % Expected S/N per resolution element
\aperture{MDRS} % MDRS (4"x20")
\specialreq{ROLL} % A specific roll angle is desired
\numvisits{1} % Number of visits required for each object (nominally
\integrationtime{10000} % Desired integration time, in seconds (per visit).
%
\end{observations}
\end{document}
Note: Additional Examples will be made available on the FUSE JHU Science Center Web page, URL http://fuse.pha.jhu.edu.
The following is a modified version of the target naming conventions used by the Space Telescope Science Institute for HST proposals. FUSE will use the procedures outlined below to standardize target names in FUSE proposals and in the FUSE archive. Prospective proposers and archival researchers will use these names to determine whether FUSE has observed a particular object. Your adherance to these rules will assist in making the archive more useful for everyone. We thank you in advance for your efforts in this regard.
The following conventions must be followed in naming targets:
Only one formal designation should be provided for each target. This should be a "catalog name" (for example, HD124897), with the preferred catalog designations being given below. The "catalog name" is entered in the FUSE forms for the \objectname{} keyword in Phase 1, and the object_name keyword in Phase 2. "Common names" (e.g., ALPHA-BOO, ARCTURUS) can be included in proposal forms as buried comments, but will not be processed or used by the FUSE proposal or archive system.
If a target is not contained in these catalogs, other catalog designations may be used (e.g., 4U X-ray catalog designation, Villanova white-dwarf catalog number, etc.). The use of positional catalogs (SAO, Boss, GC, AGK3, FK4, etc.) is discouraged.
For uncatalogued targets, see "Uncatalogued Targets."
(a) Stars
1. Henry Draper Catalog number (e.g., HD140283). HDE numbers are discouraged, except in the Magellanic Clouds.
2. Durchmusterung number (BD, CD, or CPD). In the southern hemisphere, adopt the convention of using CD north of -52 degrees and CPD south of there (e.g., BD+30D3639, CD-42D14462, CPD-65D7691).
3. General Catalog of Variable Stars designation, if one exists (e.g., RR-LYR, SS-CYG).
4. AFGL
5. IRC
6. IRAS
(b) Star Clusters and Nebulae
1. New General Catalog (NGC) number (e.g., NGC6397, NGC7027).
2. Index Catalog (IC) number (e.g., IC418).
3. For planetary nebulae for which you do not have an NGC or IC designation, the Perek-Kohoutek designation (e.g., PK208+33D1) may be used.
4. For H II regions for which you do not have an NGC or IC designation, the Sharpless catalog number (e.g., S106) may be used.
5. For IR nebulae, AFGL.
(c) Galaxies and Clusters of Galaxies
1. NGC number (e.g., NGC4536).
2. IRAS
3. IC number (e.g., IC724).
4. Uppsala Catalog number (e.g., UGC11810).
5. For clusters of galaxies, the Abell catalog number (e.g., ABELL2029).
(d) Quasars and Active Galaxies
1. The name defined in compilation by Veron-Cetty and Veron (ESO Report No. 7, 1989) must be used (e.g., 3C273).
1. Isolated objects must be designated by a code name (the allowed codes are STAR, NEB, GAL, STAR-CLUS, GAL-CLUS, QSO, SKY, FIELD, and OBJ), followed by a hyphen and the object's J2000 equatorial coordinates, if possible, rounded to seconds of time and seconds of arc (e.g., for a star at J2000 coordinates RA = 1H 34M 28S, DEC = -15D 31' 38", the designation would be STAR-013428-153138).
2. Uncataloged objects within star clusters, nebulae, or galaxies must be designated by the name of the parent body followed by a hyphen and the rounded J2000 coordinates, if possible, of the object (e.g., for a target within NGC 224 with J2000 coordinates RA = 0H 40M 12S, DEC = +40D 58' 48", the designation would be NGC224-004012+405848).
3. Positions within nebulae or galaxies may also be designated by the name of the parent object followed by a hyphen and a qualifier. The qualifier should be brief, but informative (e.g., the jet in NGC 4486 could be designated NGC4486-JET). Other examples are: NGC5139-ROA24, LMC-R136A, ABELL30-CENTRAL-STAR, NGC205-NUC.
As with other targets, Solar System target names within a proposal must be unique. FUSE does not have the resolution or pointing capability of HST, so the possibilities for Solar System observations are not as complex. In any case, the use of standardized names is encouraged.
The common name of the object, together with appropriate qualifiers or identifiers appended, should be sufficient for the purpose of specifying FUSE targets in Phase 1. As with other targets, no blanks are permitted in Solar System target names. A hyphen should replace blanks that would normally be used to separate fields (e.g., IO-TORUS, COMET-HYAKUTAKE-1996B2, JUPITER-NPOLE, etc.). As with other targets, a 30 character limit is imposed, and no punctuation other than hyphens and + or - are permitted.
Target names should be constructed so that they represent good mnemonics for the observing program. For example, if the program consisted of three separate observations of Mars to search for longitudinal variability, then three appropriate target names might be: MARS-LONG1, MARS-LONG2, and MARS-LONG3.