Web Links and Reference Material
The FUSE Guest Investigator Web page is http://fusegi.pha.jhu.edu, where the following are available:
The FUSE Science Center web page, http://fuse.pha.jhu.edu contains links to important reference documents and on-line tools.
Main Updates and Changes for Cycle 7
Guest Investigators (GIs) interested in obtaining FUSE data during Cycle 7 must complete and submit the Phase 1 proposal form. The main contents of a Phase 1 proposal are the scientific justification for the observations as well as their feasibility. These proposals will be peer reviewed by a committee of scientists. Based on the recommendations of the committee, NASA will select a certain number of programs for implementation. GIs whose programs have been selected will be required to submit a Phase 2 form where more detailed information will be required.
Prior to submitting a Phase 1 form, GIs are requested to fill out a cover page as required by NASA. This can be done on-line at the NASA Peer Review Services NSPIRES,/b> web site. On completing the information for this page, the proposer must pass it on to an Authorizing Official ("Grants Manager") at the PIs institution, who will then submit the cover page to NASA. At this time, the proposal will be assigned an identifier which constitutes a required keyword, \nasapropno{}, in the Phase 1 proposal. PIs at US institutions should not submit a Notice of Intent to Propose.
The web-generated Proposal Cover Page is now for US institutions only. For non-US institutions, the web-generated Notice of Intent to propose (NOI), accessible at the same web location( NASA Peer Review Services) fulfills the function of the cover page (allowing NASA and the FUSE project to track the proposals). More information about using the NSPIRES system for FUSE Cycle 7 proposals is available on the FUSE GI web site (http://fusegi.pha.jhu.edu).
This document contains the information necessary to complete a Phase 1 file for FUSE Cycle 7. Section 2 starts with an overview of the Phase 1 proposal process and goes on to describe general issues that proposers need to be aware of. Section 3 contains a description of the Phase 1 form, with detailed instructions on how to fill in each field. Section 4 contains a completed form for reference. The submission process for Phase 1 proposals is described in the NRA.
The sky availability for Cycle 7 is limited to absolute
declinations above 50 degrees, as the new attitude control software is still
being developed. The FUSE project expects to be able to expand the sky
availability beyond this range again in the future. For lower declinations,
the target database from earlier proposal cycles already provides a well-
populated source list for when this capability is achieved. Given that high
declination targets are usually observed in the Continuous Viewing Zone (CVZ),
the observing efficiency for such targets is potentially high and a well
populated target pool is required. This is the primary goal of the Cycle 7
selections.
2. FUSE Phase 1 Overview
The Phase 1 template file is an ASCII LaTeX file containing a set of keywords. Entries for some keywords are required, while entries for others are optional. Electronic submission of the completed LaTeX template file is required of all proposers -- this file will be parsed and a database populated in order to support technical evaluation of the proposal. The proposers must also submit 12 paper copies of the formatted proposal. This can be done conveniently using LaTeX along with the style file fuse7.sty provided by the FUSE project. (Instructions for retrieval of Phase 1 related material are given in the NRA.) Proposers without access to electronic mail should consult the NRA for further information. The users can choose to edit the Phase 1 forms using any text editor and use other software to generate the formatted proposal provided the format given in section 2 of the NRA is followed.
The Phase 1 form starts with several "front page" fields requesting
contact information and summary details about the proposal. This is
followed by text blocks for scientific justification, feasibility and
safety analysis, and additional information. Next target and
observation specific information is requested. The information is
necessary for the planning personnel to perform a technical review of
the proposal. The review includes an assessment of feasibility of the
proposed observations and also addresses issues regarding instrument
safety. GIs can use the on-line tools provided by the FUSE project to
estimate count rates and expected signal to noise ratios. 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 will include flux estimates for each target, as well as the signal to noise desired for each observation. The information provided will be used to determine whether the proposed observations are consistent with the capabilities of the instrument. FUSE has brightness and exposure limits for both continuum and emission line sources (see the FUSE Observer's Guide). Source fluxes extrapolated from longer wavelengths or based on models can be significantly in error, especially since the interstellar extinction at FUV wavelengths is often uncertain. The FUSE operations team will be cautious when dealing with any objects that are within a factor of 10 of the brightness limit and may require that a safety snap be performed (see next section on Special Requirements).
The flux provided in the Phase 1 form would in general be at a reference wavelength that is of importance to the science. However, it may not be representative of the source brightness at other wavelengths in the FUSE bandpass. Therefore, it is extremely important that the peak fluxes expected from the proposed targets, and the uncertainties in the flux estimates be discussed in detail in the "Feasibility and Safety" text section.
Emission line objects are a special case, since they seldom cause
TOTAL flux or count rate problems but can still be a safety
hazard for the FUSE detectors. The FUSE brightness limit applies
at each wavelength - and a strong emission line from a source
may violate that limit. It is requested
that properties of the brightest emission line expected be used to
populate the flux-related keywords (e.g.~surface brightness, line width).
This should be done even if the brightest line is not the one of specific
interest in the proposed scientific program. This is especially true
for targets that are within a factor of 10 of the brightness limit.
FUSE planners will assess the safety concerns based on the information
provided. Therefore, methods of estimating the line flux and any
uncertainties should be carefully described in the text. For example,
if the line widths of the source are not well known and could introduce
a brightness violation it should be stated explicitly in the proposal.
Legacy Programs
The "Legacy" program category, introduced in Cycle 5, will not be available in Cycle 7.
Survey and Supplementary Programs
The program category, "Survey and Supplementary", was introduced in Cycle 4 and continues to be offered in Cycle 7. This category allows GIs to submit proposals with scientific emphases somewhat different from that in "Standard" proposals. At the same time, these proposals help in maintaining scheduling flexibility without loss of observing efficiency.
"Survey and Supplementary" programs are for projects involving the survey of a class of objects or alternatively for providing supplementary data of scientific importance on some set of targets. In either case, the GI lists a number of proposed targets (there is no restriction on the number, and may be as low as one) and if the proposal is accepted, these targets are put into the database of objects to be scheduled for observation. However, the scheduling priority is lower for these objects than for "Standard" targets and any given object will be observed only if it suits the scheduling plan. The decision whether to observe a target or not is driven solely by the requirements of FUSE mission planning. "Survey and Supplementary" targets must also be constrained to absolute Declination above 50 degrees. Accepted targets for these programs that are not observed during Cycle 7 will as a rule not be carried over to subsequent cycles.
"Survey and Supplementary" programs have some advantages. If a
prospective GI is interested in a class of objects (say, Algol binaries)
and would like to obtain FUV spectra of as many as possible, that
person could propose a list of targets. If the proposal is accepted,
some fraction of the objects on the list will be observed. The
scientific justification for such a proposal would not be focused on
one or a few objects but rather on why FUSE observations of Algol
binaries are important. The object class need not be the link among
the targets proposed. The link may be, for instance, the properties of
the sight-lines proposed. Although it is expected that data will be
obtained for most accepted "Survey and Supplementary" programs, the
drawback is that a specific object may not be observed. Also, there is
no minimum executed observation time guaranteed for an accepted
survey program.
Special Requirements
Special Requirements (SRs) flag the system to some supported modes of observation that are used relatively infrequent, or to situations which require special attention on the part of the planners. (Although less extensive that those needed for the Hubble Space Telescope, they serve the same function.) There is a text block in the Phase 1 form for describing the proposed observations. Justification for any desired SRs must be included in this section. The SRs also need to be entered, where needed, at the appropriate places in the target lists. If more than one SR applies, all should be supplied with individual entries separated by commas. Observations with SRs often constrain the scheduling and are sometimes lower observation efficiency (since they require special handling) so SRs should be requested only when the need is there. For cycle 7, most of the earlier available SRs will not be allowed.
Special Requirements allowed for Cycle 7:
Default Aperture and Aperture Selection
Due to intermittant problems with Fine Error Sensor A (FES-A), initially encountered in the spring of 2005, the default Guide Camera as of July 2005 is FES-B. As FES-B is associated with the Focal Plane Assembly (FPA) for LiF2, the most reliable (and well centered) data will now occur in LiF2(A & B), rather than LiF1. Because of differences in the focus of FES-A and FES-B, the LiF2 FPA has been moved to a position which is slighty off the FUV focus. This means that the FUV spot at the location of the LiF 2 FPA is not at a minimum and so for the smaller apertures (MDRS and HIRS) the throughput is somewhat smaller for LiF2 than for LiF1. The spectrograph focus has not been affected and so the spectral resolution of FUSE data remains basically unchanged (see the FUSE Observer's Guide, v7.0 for details).
During the science verification period soon after launch, it was seen that thermal effects caused channel alignment to vary on orbital time scales as well as during slews between targets. With careful planning the alignment can be maintained sufficiently well that point sources are within the LWRS aperture in all 4 channels. Furthermore, it was found that the spectral resolution achieved for point sources (especially if observed in time-tag mode) was about the same for LWRS and MDRS observations. This is particularly true for the LiF data. The spectral resolution in the SiC channels, and for histogram data is slightly lower for LWRS observations (see the FUSE Observer's Guide for more information). As a result of these findings, it was determined that the LWRS (30x30 arcsec) would be the default observing aperture.
Data aquired in the fourth and fifth years of operation indicated that the cumulative effect of all observations performed since the beginning of the mission had at that time measurably depleted the available charge on the FUSE detectors at certain wavelengths at the location corresponding to the LWRS aperture. In order to preserve sensitivity for faint targets (which do not allow FUV PEAK-UPs), the default aperture for bright target (HIST) observations were, as of June 2004, changed to the MDRS aperture. Due to alignment shifts, an observation in the MDRS aperture generally requires approximately twice the exposure time as indicated by the Exposure Time Calculator. (For observations requiring ONLY LiF2 data, this doubling is not needed, or valid) Proposers should take this into account when estimating exposure times for cycle 7. The use of the LWRS aperture for HIST observations, will be permitted only for strongly justified scientific reasons, such as high precision spectrophotometry or the requirement of SiC channel wavelength coverage.
Observations with the MDRS (4x20 arcsec) or HIRS (1.25x20 arcsec) apertures are preferable in certain situations. If the wavelength range of interest is longward of about 1000 Å, observations using the smaller apertures are possible. This is because the LiF alignments are relatively well behaved. GIs may want to modify the requested integration time based on lower total effective area available. The LiF 2 channel is linked to the Fine Error Sensor that is used to guide and therefore always maintains alignment. For observations where the HIRS aperture is requested, only LiF 2 coverage is guaranteed.
Full wavelength coverage using the MDRS apertures is possible for objects with sufficient FUV flux to allow peak-up acquisitions (see next section). The procedure for observing may require multiple peak-ups per orbit for re-aligning the channels. This will have an impact on operational efficiency and may be difficult to schedule. Hence GIs requesting MDRS aperture observations must specify whether SiC (i.e., short wavelength) coverage is essential, desirable, or not necessary for the science proposed. This will allow the operational impact of the request to be assessed properly. Note that requiring SiC data puts additional planning constraints on the observation. If these cannot be met at an otherwise opportune time, the observation will be delayed.
The need for MDRS or HIRS apertures (or LWRS for HIST observations) must be
explicitly discussed in the
Phase 1 proposal. The short wavelength requirement for MDRS observations
must likewise be included. The discussion can be in either the scientific
justification section or the feasibility section, at the GIs discretion.
Target Acquisitions and Offset Targets
When observing with the LWRS apertures, acquistion procedures are usually simple. Guide stars are selected around the target position. The coordinates are assumed to be accurate in the HST Guide Star reference frame, and the target is placed in the LWRS apertures. (This procedure is called "guide star acquisition".)
Guide star acquistion may be sufficient to place a target in the MDRS apertures, but even then the issue of channel alignment needs to be addressed. If the target is bright enough in the FUV, "peak-up acquistion" can be performed. The target is placed near the MDRS apertures which are then stepped along the X co-ordinate (i.e., across the aperture width). The onboard instrument computer processes the data and aligns the channels based on the position where fluxes are maximized. This procedure works well for initial alignment but lasts only about 10 minutes, particularly for the SiC channels (note that LiF 2 will stay aligned). Therefore multiple peak-ups during an observation may be necessary. Peak-up acquisition can be used for the HIRS apertures as well, but the time scale for misalignment to occur is much shorter. Hence, only LiF 2 data is guaranteed for observations requesting HIRS.
Extended targets (using any of the apertures), and MDRS observations of
targets that are too faint in the FUV to acquire with peak-ups will
need alternative acquistion procedures. These usually entail the use
of an offset star or an offset field. Such observations are not very
frequent, so we refer GIs to the FUSE Observer's Guide for details
about offset star acquistion. Note that offset stars are not requested
as separate targets in Phase 1. However, the need and availability of
appropriate offset stars should be discussed in the "Description of
Observations" text block. Offset stars will have to be specified
explicitly in the Phase 2 submission.
Signal-to-Noise Ratios in Individual Channels
Combining data from
the different channels usually results in lowering
the spectral
resolution. Also, handling the statistical errors in such
a data combination correctly is
complicated. Therefore, in many cases GIs may want to consider the
signal to noise that will be obtained from an individual channel of the
spectrograph. The on-line tools (e.g. the Exposure Time Calculator and
the Count Rate Tool) were updated prior to Cycle 3 to allow the
calculation of signal-to-noise for individual channels as well as for
the sum of all channels. A new keyword was also introduced into the
Phase 1 form that let the proposer specify the channel assumed for the
S/N calculation. These updates will hold through Cycle 7. It is
important that proposers describe their S/N calculations and
assumptions in the feasibility text section. The use of the on-line
tools is strongly encouraged.
Observations of Faint targets, NIGHT Observations
Observations of faint
(<3e-15 ergs cm-2 s-1 Å-1)
sources, particularly through the LWRS apertures may be compromised by
terrestrial airglow emission. The airglow problem can be significantly
reduced by analyzing data taken only during the night-time portion of
the observation. FUSE cannot be easily re-targeted within orbits, so
scheduling "night-only" observations is extremely inefficient and is
NOT supported. If an observation requires night-time data, then the
proposer should request a total observation time that is long
enough to obtain the desired night exposure. Experience has shown that
for a typical observation, the total exposure time is about 1.6 times
the night exposure time. If an observation requires 10,000 seconds of
exposure time at night, the proposer should request 1.6*10,000 = 16,000
seconds for the observation.
Beta Angle Considerations
Shortly after launch it was discovered that the co-alignment of the four optical channels was sensitive to the thermal environment and history of the spacecraft. The main parameter controlling this environment is the beta angle, defined as the angle between the anti-Sun direction and the telescope boresight. In order to keep the four optical channels co-aligned, the FUSE project has carefully managed the target scheduling to, as far as possible, keep beta angle changes between consecutive targets at a minimum. While the nominal beta angle restriction is 15 to 105 degrees, in practice the FUSE project has, for this reason, strived to keep it in the range 30 to 90 degrees
While the restrictions in beta angle are still in effect, the main planning
constraints for the current spacecraft configuration consist of the requirement
for instantaneous torque-authority (i.e. the need for sufficient control torque
to counter-balance the external disturbances on the spacecraft) and the
requirement to keep the remaining reaction wheel from spinning up to saturation
speeds. These two requirements limit both the short-time sky availability and
the duration and cadence of allowable pointings. These requirements may not
always be compatible with the desire to limit the change in beta angle between
consecutive targets.
Coordinated Observations
For any number of scientific reasons coordinating FUSE observations with other space-based or ground-based facilities may be desirable. Operational constraints, however, make coordinated observations very difficult and often extremely inefficient to schedule. Even modest coordination (at the several week level) can have a significant effect on overall scheduling over some longer time period.
The FUSE project recognizes the scientific importance of co-ordinated
observations and will support a very limited number of such requests on
a best effort basis. Under the present attitude control scheme it is unlikely that a "simultaneity" better than several weeks can be achived. The need
for co-ordinated observations should be discussed in detail in the
"Additional Information" text block in the Phase 1 form. While
co-ordinated observations may be requested at the
Phase 2 stage,
acceptance for such requests will be contingent on the explicit
approval of the FUSE project scientist.
3. FUSE Phase 1 Proposal Keyword Definitions
In this section we step through the Phase 1 form and describe the keyword entries and the text block requirements. Note that comments in the template are preceded with a "%" sign (LaTeX syntax). Proposers can add comments to the form for their own convenience, but these will not be processed by the Phase 1 ingestion software nor will they be read by FUSE personnel.
Keyword values are generally inserted between the curly brackets. In some cases a list of options is given in the form of comments. Then, one of the entries in the list must be un-commented by deleting the "%" sign. Text for the text blocks should be inserted below the appropriate keyword. An example form showing the syntax for keyword values is given in Section 4. Helpful guidelines are included in the Phase 1 template file. Please use the most recent template and style files -- these can be downloaded from the FUSE website.
1. Proposal Title
\title{} % (Required)
The program title should be as short and descriptive as
possible and should be no longer than two lines in
the formatted output. (This limits the title to about
100 characters.)
2. NASA Proposal Number
\nasapropno{} % (Required)
This keyword allows cross-referencing between NASA Peer Review Service
proposal numbers and those used by the FUSE project. Enter the identifier
assigned to the "Cover Page" submitted to NASA NSPIRES proposal processing web
site
(or the NOI for non-US proposers). For example, for a US PI the identifier
is of the form 05-FUSE05-123, whle for non-US PIs it will be of the
form N5-FUSE05-123.
3. Principal Investigator Contact Information (All Fields Required)
\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, SWE, IND, etc.]
\phone{}
\fax{}
\email{} [e.g. you@somewhere.anywhere.edu]
All requested contact information should be supplied
for the principal investigator (PI). The PI is the
primary contact for questions about the program.
4. Scientific Category (Required)
%\scientificcategory{COOL STARS AND PROTOPLANETARY SYSTEMS}
%\scientificcategory{WHITE DWARFS AND CATACLYSMIC VARIABLES}
%\scientificcategory{HOT STARS AND MASSIVE BINARIES}
%\scientificcategory{STELLAR EJECTA AND GASEOUS NEBULAE}
%\scientificcategory{INTERSTELLAR MEDIUM AND GALACTIC STRUCTURE}
%\scientificcategory{GALAXIES AGN AND QUASARS}
%\scientificcategory{INTERGALACTIC MATERIAL}
Select a primary scientific category for your proposal by uncommenting
the appropriate line from the list.
5. Observing Program Category (Required)
%\programcategory{STANDARD}
%\programcategory{SURVEY}
A proposal must be designated as "Standard" or "Survey" by uncommenting one of the lines. The "Standard" category consists of normal programs where all targets shoud be observed. The "Survey" designation is short for the "Survey and Supplementary" category, which allows GIs to propose observations of a class, or list of objects with the understanding that a specific target may or may not be observed in the course of Cycle 7. For Cycle 7 both "Standard" and "Survey" targets are restricted to absolute Decilinations of more than 50 degrees.
6. Observation Summary Information
\totalobstime{} % (Required, in ksec)
\totalobjects{} % (Required)
The \totalobstime keyword value should be the total requested
observation time in kiloseconds for all targets in the program. To
calculate this, any observations with \integrationtime less
than 4000 seconds should be accounted as 4 kiloseconds. Any SAFTSNP
exposures, which are likely to be very short should be accounted as
2000 seconds. This is done because of the relatively large overhead
needed for observations with short exposure times. See the FUSE
Observer's Guide for more information.
The \totalobjects keyword value is the number of independent positions on the sky that are proposed. Different positions on extended sources should be counted as separate targets.
7. Abstract (Required, text block)
\begin{abstract}
\end{abstract}
Enter a brief description of the proposal between the
\begin{abstract} and \end{abstract} commands. The
goals of the program should be summarized. The abstract should fit on
the front page of the formatted proposal and is therefore restricted to
200 words. The abstracts for all successful proposals will be made
available on-line. In this and other text blocks do not use colons
(":"). This causes problems with the proposal ingestion software.
(However, keyword values such as the RA and DEC require colons.)
8. Co-I Information (Required for all Co-investigators)
\begin{investigators}
% List each Co-Investigator (CoI) by replicating the following seven
% items for each CoI. If you have no CoIs, leave these lines unchanged.
\coititle{}
\coifirstname{}
\coilastname{}
\institution{}
\country{}
\phone{}
\email{}
\end{investigators}
The format is similar to the entries for the PI, but less
information is requested.
9. Scientific Justification (Required, text block)
% Enter text after the \justification keyword. % <=3 pages, including figures, tables and refs. \justificationDescribe the scientific justification for the proposed program, stating clearly its goals and significance to astronomy. Brief discussions of the scientific background and previous work done on the subject should be included. The scientific reasons why FUSE data are needed should be discussed. The Scientific Justification (including figures, table and references) is limited to three pages. Other text blocks are provided for further descriptive material about the program.
10. Feasibility and Safety (Required, text block)
% Enter text after the \feasibility keyword. % <=2 page \feasibilityA detailed description of the signal-to-noise and spectral resolution requirements for the proposed observations should be included. (It should be explicitly mentioned whether the estimates apply to data from individual channels or the total.) The method and quality of the target flux estimates must be described, particularly if there are any concerns for instrument safety (typically targets that are close to or may possibly violate the bright limit). Describe the method used to estimate exposure times. the use of the on-line exposure time calculator is strongly encouraged. Up to two pages can be used for this section.
11. Description of Observations (Optional, text block)
% Enter text after the \describeobservations keyword. % <=1 page \describeobservationsAdditional information about observation strategy can be included in this optional text block. Examples include:
12. Additional Information (Optional, text block)
% Enter text after the \additionalinfo keyword. % <=1 page \additionalinfoUp to one page of text can be included here to describe anything about the proposed program that the review panel may find useful. This section is not for adding to the scientific justification. Examples of what may be included here are:
13. Previous FUSE Observing Programs (Optional, text block)
% Enter text after the \previousfuseprograms keyword. % <= 1 page \previousfuseprogramsSummarize the status of any FUSE programs the PI has from earlier cycles. Previous programs that the Co-Is have may be included but would be less important. The section has a limit of one page (including figures).
14. Investigator Information (Optional)
% <= 1 page \vitaA short biographical sketch of the PI may be presented here. Publications relevant to the proposal may be included. Such 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.
15. Target List and Observation Summary (Required)
\begin{observations}
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 follow those developed for use in
HST proposals. Please refer to Appendix A below for FUSE target naming
conventions. If other names are used in the proposal text, provide
cross references in the "Additional Information" text block.
\ra{} % (Required)
\dec{} % (Required)
Coordinates in standard astronomical format (HH:MM:SS.SS and
[+/-]DD:MM:SS.S), referenced to the J2000 equinox, are required.
The most accurate coordinates available should be provided.
Accuracy to at least 5 arcsec is required for
target duplication checks.
\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), 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 telescope safety, feasibility and verifying the expected signal-to-noise.
% Source type: (uncomment only one) (Required)
%\sourcetype{PC} % Point Continuum
%\sourcetype{PE} % Point Emission-line
%\sourcetype{EC} % Extended Continuum
%\sourcetype{EE} % Extended Emission-line
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
smaller than 2 arcsec is 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 interpretation of some of
the entries given below (for instance, the units of "flux") and should
be consistent with the other data entered.
FUSE mission planners need to know of any special situations that might be safety concerns. For instance, if the continuum level of a symbiotic star was of primary scientific importance then the source type would be "PC" and the subsequent entries would follow appropriate to this designation. However, the peak line intensities of expected emission lines should be discussed in the "Feasiblity" text block so it can be verified that fluxes are below the detector bright limits.
\lambdaref{} % (Required)
The reference wavelength in Angstroms (Å) should be entered. This should
be a wavelength within the FUSE range (i.e. 905 - 1187 Å).
The flux and S/N entered should pertain to this wavelength.
As such it should be a wavelength that is of interest to the
proposed scientific program. For emission line sources the wavelength
of the strongest expected line from the source should be chosen.
\fluxlambdaref{} % (Required)
The user should enter the flux at the reference wavelength. The flux
should be written as n.nnE-nn format (where each "n" is a single-digit
integer - please, no TeX formatting commands!). The value should be
the flux at the telescope. That is, it should be corrected for
interstellar extinction. The units are
ergs/(cm2 s Å)
for continuum sources, and ergs/(cm2 s)
(integrated line flux) 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.
% Flux estimate accuracy: (uncomment one) (Required)
%\fluxaccuracy{HIGH} % HIGH
%\fluxaccuracy{MED} % MED
%\fluxaccuracy{LOW} % LOW
This keyword is used to indicate the accuracy level of the flux information
provided above. It 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 IUE, 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 extinction uncertainty is involved; LOW
indicates uncertain estimates either because the extrapolation is from
much longer wavelengths, or the source flux is not well understood in the
FUV, etc.
% Info for emission line or extended objects.
% Uncomment next 2 keywords if they apply:
%\elinefwhm{} %(Required for \sourcetype = PE and EE)
%\sblambdaref{} %(Required for \sourcetype = EC and EE)
The \elinefwhm{} keyword entry is required only for emission
line sources. Enter the FWHM of the line in decimal Å. The
\sblambdaref{} keyword entry is required only for extended
sources. Enter the expected surface brightness at the reference
wavelength in flux units per square arcsecond. The format is n.nnE-nn
(no TeX formats allowed).
\resolutionelement{} % (Required)
This field is the resolution element, in Å, for which the quoted
signal-to-noise ratio has been calculated.
The smallest meaningful resolution element value allowed is 0.05 Å,
which
is the measured instrumental resolution.
Larger values can be entered, depending on the scientific goals
of the proposal. The data will always be obtained at highest possible
resolution and any binning will be left to the user.
\signoisechan{} % (Required)
The signal-to-noise can be calculated for individual channels or for
the total of all channels available at a given wavelength. The entry
to this keyword specifies the channel for which the S/N is listed.
Valid entries: SIC1, SIC2, LIF1, LIF2, or TOTAL.
\signoise{} % (Required)
The expected signal-to-noise per resolution element at the reference
wavelength for the channel (or TOTAL) specified should be entered
here. The maximum S/N per default (0.05 Å) resolution element
is 30. Higher S/N values can be obtained using the special FSPLIT
procedure (see Section 2).
% (Required)
% LWRS (30"x30") (Default)
\aperture{LWRS}
% MDRS (4"x20")
%\aperture{MDRS}
% HIRS (1.25"x20")
%\aperture{HIRS}
LWRS is the default channel for low count rate targets, while MDRS is the
default for high countrate (HIST) targets. Comment out LWRS and uncomment
one of the
other channels to change the aperture requested. Any request
for MDRS
or HIRS should be justified in the "Description of Observations" text
block, except for bright targets where a request for LWRS must be explicitly
justified.
% Special requirements: (uncomment all keywords that apply)
% (Optional, as needed)
%\specialreq{TOO}
%\specialreq{FPSPLIT}
%\specialreq{SNAP}
%\specialreq{SAFTSNP}
Special requirements that will be supported for Cycle 7 are TOO, FSPLIT, SNAP and SAFTSNP. These are described
in Section 2, above. Uncomment all SRs that are needed for a target.
\integrationtime{} % (Required)
The on-source integration time requested for an observation should be
entered here, in units of seconds. For SNAP observations, this is the length of the shorter test exposure; a separate target entry should be provided for the
proposed science observation. For SAFTSNPs, enter 2000 seconds (for
accounting purposes only).
The template included below has many of the comment lines deleted, and is meant only to give the proposer an idea about the layout of the form. The proposer should download and use the Phase 1 form available at the FUSE website. It contains detailed comments and additional instructions.
% FUSE Phase 1 observing proposal LaTeX template (version 7.0)
% For Cycle 7
%
\documentclass[12pt]{article}
\usepackage{fuse7}
\begin{document}
% 1. Proposal Title
\title{Observations of a Twinkling Star} % (Required)
% 2. NASA Proposal Number
\nasapropno{05-FUSE05-234} % (Required)
% 3. Principal Investigator Contact Information. (All Fields Required)
\pititle{Mr.}
\pifirstname{Johns}
\pilastname{Hopkins}
\piaffiliation{Board of Directors}
\institution{Baltimore and Ohio Railroad}
\address{111, Railway St., Baltimore, MD 21000}
\country{USA}
\phone{410-111-1111}
\fax{410-222-2222}
\email{jh@bando.rail.com}
% 4. Scientific Category (Required)
%\scientificcategory{COOL STARS AND PROTOPLANETARY SYSTEMS}
%\scientificcategory{WHITE DWARFS AND CATACLYSMIC VARIABLES}
\scientificcategory{HOT STARS AND MASSIVE BINARIES}
%\scientificcategory{STELLAR EJECTA AND GASEOUS NEBULAE}
%\scientificcategory{INTERSTELLAR MEDIUM AND GALACTIC STRUCTURE}
%\scientificcategory{GALAXIES AGN AND QUASARS}
%\scientificcategory{INTERGALACTIC MATERIAL}
% 5. Observing Program Category (Required)
\programcategory{STANDARD}
%\programcategory{SURVEY}
% 6. Observation Summary Information
% Total observing time, in Kiloseconds
\totalobstime{40} % (Required)
% Total number of objects
\totalobjects{1} % (Required)
% 7. Abstract (Required, text block)
\begin{abstract}
Enter abstract text here.
In this and other text blocks do not use colons
(":"). This causes problems with the proposal
ingestion software. (However, keyword values such
as the RA and DEC require colons.)
\end{abstract}
% 8. Co-Investigator Information (Required for all Co-investigators)
\begin{investigators}
\coititle{Dr.}
\coifirstname{Henry}
\coilastname{Rowland}
\institution{Johns Hopkins University}
\country{USA}
\phone{410-516-0000}
\email{rowland@pha.jhu.edu}
\end{investigators}
% 9. Scientific Justification. (Required, text block)
% <=3 pages, including figures, tables and refs.
\justification
Enter justification here. Figures may be included.
%Include Figure
\begin{figure}[h]
\plotone{image.eps}
\caption{image worth a thousand words}
\end{figure}
% 10. Feasibility and Safety. (Required, text block)
% <=2 page
\feasibility
Enter text here.
% 11. Description of Observations. (Optional, text block)
% <=1 page
\describeobservations
Enter text here.
% 12. Additional Information. (Optional, text block)
% <=1 page
\additionalinfo
Enter text here.
% 13. Previous FUSE Observing Programs. (Optional, text block)
% <= 1 page
\previousfuseprograms
Enter text here.
% 14. Investigator Information. (Optional, text block)
% <= 1 page
\vita
Founded university.
%----------------------------------------------------------------------
% 15. Target List and Observation Summary
%----------------------------------------------------------------------
\begin{observations}
% see Appendix A of Phase 1 instructions for conventions
% NOTE THAT THERE MUST NOT BE ANY SPACES IN THE TARGET NAMES.
\objectname{HD4515} % (Required)
% Should be in the form HH:MM:SS.SS (J2000 equinox)
\ra{45:45:45.45} % (Required)
% Should be in the form DD:MM:SS.S (J2000 equinox)
\dec{15:15:15.3} % (Required)
% Visual magnitude, Johnson V magnitude preferred
\vmag{12.1} % (Required)
% Enter a spectral type. For stars, provide the MK spectral type
% and luminosity class (no spaces! example: O7Ve).
% For non-stars use one of the following:
% QSO, AGN, GAL, SOL, CV, PN, SNR, CSPN, PSR, REF, CLU, OTR.
% (CLU=cluster of galaxies; OTR=other)
\spectype{B0V} % (Required)
% Measured E(B-V)
\colorexcess{0.03} % (Optional)
% Source type: (uncomment only one) (Required)
\sourcetype{PC} % Point Continuum
%\sourcetype{PE} % Point Emission-line
%\sourcetype{EC} % Extended Continuum
%\sourcetype{EE} % Extended Emission-line
% Reference wavelength in Angstroms
\lambdaref{1030} % (Required)
% Estimated, observed, flux value at wavelength \lambdaref. in erg/cm2/s/A
% Example: \fluxlambdaref{1.5e-12}
% NO TeX formatting allowed in this keyword.
\fluxlambdaref{1.2e-12} % (Required)
% Flux estimate accuracy: (uncomment one) (Required)
%\fluxaccuracy{HIGH} % HIGH
\fluxaccuracy{MED} % MED
%\fluxaccuracy{LOW} % LOW
% Info for emission line or extended objects.
% Uncomment next 2 keywords if they apply:
% FWHM of line in Angstroms for emission line objects
%\elinefwhm{} %(Required for \sourcetype = PE and EE)
% Surface brightness at wavelength \lambdaref in erg/cm^2/s/A/arcsec^2.
% (Required for \sourcetype = EC and EE)
% Example: \sblambdaref{1.2e-15}
% NO TeX formatting allowed in this keyword.
%\sblambdaref{} %(Required for \sourcetype = EC and EE)
% Size of resolution element in Angstroms
\resolutionelement{0.1} % (Required)
% Channel used to calculate the S/N: SIC1, SIC2, LIF1, LIF2, or TOTAL
\signoisechan{LIF2} % (Required)
% Expected S/N per resolution element
\signoise{20} % (Required)
% Aperture: (LWRS is default, change by commenting out LWRS and
% un-commenting other. Only one must be un-commented)
% (Required)
% LWRS (30"x30") (Default)
%\aperture{LWRS}
% MDRS (4"x20")
\aperture{MDRS}
% HIRS (1.25"x20")
%\aperture{HIRS}
% Special requirements: (uncomment all keywords that apply)
% See phase 1 proposal instructions for details
% (Optional, as needed)
% Target of opportunity
%\specialreq{TOO}
% FPSPLIT observing procedure required (high S/N observation)
%\specialreq{FPSPLIT}
% Short exposure (snapshot) before follow up
%\specialreq{SNAP}
% To highlight potential bright object violations
%\specialreq{SAFTSNP}
% Desired integration time, in seconds (per visit). For SAFTSNPs, enter
% 2000 sec here. For short science observations enter time needed to
% achieve listed S/N. See Phase 1 Proposal Instructions for more info.
\integrationtime{10000} % (Required)
%---------------------------------------------------------------------
% Repeat the above information as needed for each target/observation.
\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.