General link to the FUSE Public Web page is http://fuse.pha.jhu.edu. From there you can get to the following resources (some at the top level, some under the "Observing with FUSE" heading):
The submission of PI Team Science Proposals for Cycle 1 will provide the first functional test of the Phase 2 proposal submission system that will be used for both the PI team and successful Guest Investigators (GIs). You may recall that GIs will go through a two-phase proposal process, with the purpose of Phase 1 being primarily science justification and proposal selection. The purpose of Phase 2, in which both the PI Team and GIs participate, is to provide FUSE mission planners with sufficient information to properly schedule and carry out required observations of selected astronomical targets. The forms to support the Phase 2 submission are identical for the PI team and GIs; the only difference is that GIs will be provided with "templates" that are partially filled-out (using the Phase 1 information), while the PI team will probably have to fill out Phase 2 template forms from scratch. The PI team will also be expected to provide an abstract and text blocks describing flux estimates, program feasibility, and any special requirements of each program, as described in more detail below.
The purpose of this document is to provide all of the supporting information and documentation necessary to help PI team members fill out the Phase 2 template files for the first cycle. Successful GIs will follow this same procedure at a later date. Section 2 provides a brief overview of the current procedures for FUSE Mission Planning. Section 3 describes some general considerations about the Phase 2 process. Section 4 provides a field-by-field description of the Phase 2 forms, including syntax issues, and discusses allowed values or choices for each parameter. Appendix A contains filled-out example forms for reference.
2. FUSE Mission Planning Overview
The FUSE Mission Planning system is being designed to handle many aspects of scheduling in an automated fashion. However, in an attempt to simplify the process, we have decided to handle certain aspects of planning in a less automated manner, in particular, those situations that we anticipate will be needed infrequently. We have designed the forms and keywords to handle the "normal" situations in an efficient manner, but request text inputs to describe any off-nominal or uncertain situations or special needs. FUSE mission planners will handle these situations on a case-by-case basis, thus limiting the number of options that need to be supported by the automated software (and incidentally, making life easier for the user community by keeping the forms as simple as possible).
The PI team member in charge of each program will receive an electronic mail message containing a Phase 2 template file. This will be an ASCII file containing a set of keywords. Entries for some keywords will be "required," while entries for others will be "optional," depending on the situation. Since the forms will be in ASCII format, users can edit the files using whatever text editor they are familiar with. While other options, such as a web-based form with a graphical user interface, are being discussed for possible future implementation, we do not plan to support this for the first cycle submission.
The forms contain some general fields requesting contact information, followed by a set of keywords that are repeated for each object. These fields provide both "object" and "observation" level information for each target, but there are NOT separate `target list' and `exposure logsheet' sections in Phase 2 as with HST proposals (for instance). In addition, information is requested that will permit planning personnel to validate the feasibility and safety of the requested exposures. We also require the user to submit a total expected count rate from each object, based on a simulated spectrum or exposure time calculation using the on-line tools provided for this purpose. A reasonably accurate count rate is important for verifying the safety of the instrument, as well as managing detector lifetime and onboard memory usage relative to downlink opportunities. Any situations not handled gracefully by the keywords can be described further in text blocks that accompany the Phase 2 submission. It is important to realize that these text blocks will not just be stuffed in a file somewhere; mission planners will actually read this information and use it to help plan your program.
Another important point is that very little instrument-specific information is requested from the user. Other than the desired spectrograph aperture and the option to suggest instrument mode (time-tag or histogram), nothing else is requested. Rather, we expect to be able to specify other instrument-related parameters based on the information provided by users in conjunction with the current knowledge of the instrument performance at a time much closer to the observation. Again, options are available in text blocks for users to provide any additional supporting information they think will aid in planning the observations properly.
After filling out the forms and supporting information, the Phase 2 file will be submitted electronically. A "parser" program will check all keyword entries for proper syntax, and either a) bounce the submission back to the submitter (if there are problems), or b) ingest the data into the Mission Planning Database (MPDB). Additional parameters needed for planning will be calculated from the basic data provided by the user, guide star selection routines will be run, and input files will be created to support timeline scheduling.
The primary FUSE scheduling tool is called "Spike." Spike first performs Long Range Planning, placing targets into weekly bins based on target visibility and other selectable suitability functions. Spike then supports Short Term Scheduling of the targets in each bin, actually timelining detailed activities (slews, acquisitions, observations, etc.) on an orbit-by-orbit basis. The results of Short Term Scheduling are periodically formatted and delivered to the Mission Operations Team as "Mission Planning Schedules" for pass planning and implementation on the spacecraft. An iterative procedure is used to keep Long Range and Short Term Schedules in sync, and a feedback loop from FUSE Science Data Processing will provide information on the status of all observations actually carried out with the spacecraft.
Time Allocations and Priority Assignments
3. Phase 2 Proposal General Considerations
Each program receives a total on-target time allotment in ksec (recommended by the TAC for GI programs and assigned by the FUSE PI for PI team programs). This will either be filled in for you in the template file, or provided to you separately. For French PI programs, time is officially assigned in "orbits", which is the official "currency" for tracking their programs. However, for uniformity an approximate "time allotment" will also be carried for the French programs.
PI program target lists are built for an assumed two-year period. However, we will be planning initially for the first year of operations. Hence, we need a mechanism for tracking what you really anticipate observing in the first year. This will be accomplished using the following target priority scheme: Use priority 1 and 2 to indicate those targets you are most interested in for Cycle 1. The times requested for priority 1 and priority 2 objects should utilize roughly half of your total program allotment. The remainder of the targets, comprising the other half of your program time, should be listed as priority 3 for Cycle 1. Priority 3 targets will be in the database and available for scheduling, providing both scientific and scheduling flexibility and contingency. However, priority 1 and priority 2 targets will be preferentially scheduled during the first year. The total requested observing time for all objects in the program should add up to your program's allocation.
Instrument Safety Concerns
The Phase 2 submission includes flux and signal-to-noise information for each target as well as an estimated total count rate. This information will be used by FUSE mission planners to verify that the user's expectations are reasonable and consistent with the expected capabilities of the instrument. However, we must ALL remain aware of brightness and safety-related issues as well. FUSE has brightness and exposure limits for both continuum and emission-line sources. (See FUSE Observer's Guide.) Because of uncertainties in the flux levels of many targets in the FUSE range, extrapolated fluxes, especially with uncertain extinction curves or from far outside the FUSE wavelength range can be substantially in error. Thus, we must be cautious with any objects that are even within a factor of ten of the stated bright limits.
It is extremely important that you provide accurate information on source fluxes and an estimate of the TOTAL expected count rate for each of your targets, especially for reasonably bright targets. This should be done using one of the FUSE simulators or the exposure time calculator on the FUSE Web page. It will give you (and us!) an idea of the expected target brightness, and will also be important in setting the instrument mode, the acquisition mode, and in estimating the memory usage required to support each observation.
Emission-line objects are a special case because they do not cause TOTAL flux or count-rate problems, but rather cause potentially dangerous levels over localized regions on the detector. 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 science program. FUSE mission planners can then assess the situation directly. Again, this is most important for bright objects that approach the stated bright limits within a factor of ten.
At some level, we hope YOU will be our first line of defense against any overly-bright objects. Use the text blocks to describe any uncertainties for targets in your program. Specify keywords correctly, and work hard to provide the best flux and count rate estimates possible. Specify the SAFTSNP special requirement when necessary (see below). After review of your program, FUSE Mission Planning reserves the right to invoke SAFTSNP on any targets for which conditions are potentially dangerous to the instrument.
Instrument Mode Selections
The two operating modes of the detector are time-tag mode (TTAG; also called "address-stream mode") and histogram mode (HIST; also called "spectral imaging mode"). See the FUSE Observer's Guide for more details. FUSE mission planning will normally select the instrument mode based on the expected count rate from each target and other considerations (e.g. on-board memory usage, required resolution, etc.). Up to a count rate of about 1200 cts/s TTAG mode will normally be used, and for higher rates, HIST mode will be the normal mode. There is some gray area in this decision, however. For instance a 1500-3000 ct/s object can (in principle) be observed in TTAG if scheduled when appropriate downlink is available, but it will require careful coordination and planning. Furthermore, THIS CAPABILITY IS A RESOURCE, and as such may affect the schedulability of your observations. In this gray area, the user is allowed to suggest one or the other of these instrument modes if it is important to the science requirements of the program.
Spectral Resolution Considerations
Maintaining high spectral resolution would be one reason for requesting TTAG mode even on a moderately bright object. The "default" mode for HIST exposures will be set to keep the data sets at a manageable size, at the expense of some spectral resolution. While numbers on the flight detectors are not finalized at this writing, a default 1x4 binning on HIST exposures might lower the peak resolution from 30,000 to 28,500 and requiring the memory usage for each HIST exposure to be <=7 MB. Getting and maintaining high spectral resolution in HIST mode will possibly require decreasing the default binning used on HIST exposures, or require more HIST exposures per viewing period to reduce Doppler smearing (due to the spacecraft's motion). Both of these have a large impact on memory usage and available downlink capability; in certain cases it may be beneficial to observe in TTAG mode to maintain the highest spectral resolution.
If HIST mode is chosen, you should realize that SOME amount of Doppler smearing is unavoidable unless the target is very near the orbit pole. We intend to keep these effects to a minimum (<3 km/s smearing) by scheduling multiple HIST exposures per viewing period when necessary. Please note that the requested observing time for HIST observations should still be the "total" requested observing time on the target, NOT the expected length of individual HIST exposures. Mission planning will assess and implement observing at the exposure level.
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 planning system to some relatively infrequent but supported mode or situation that requires special attention by planners. Invoking SRs often constrains the time at which the observations can be scheduled. As such, these should only be specified when required by the science. In some instances, more than one SR may apply; all appropriate SRs should be listed, separated by commas.
Information on SRs is requested at an `object' and `observation' level in the Phase 2 submission. A separate general text block is also encouraged to discuss any such requirements of the program. NONE of these SRs should be specified frivolously, since they may seriously constrain when a given object or observation can be scheduled.
Object-specific Special Requirements (SRs) are defined with the following options on the `object_spec_req' keyword: TOO, MOVE, NIGHT, HIRES. Very briefly, the meaning of each of these is:
Observation-specific SRs are defined with the following options on the `obs_spec_req' keyword: SNAP, SAFTSNP, ROLL, MON, EPHEM, SPATIAL, CONTIG, FESIMG. Very briefly, the meaning of each of these is:
Target Acquisitions and Offset Targets
Since FUSE contains four mirrors and four separate focal plane assemblies (FPAs), target acquisitions provide a real challenge, especially since they must happen autonomously. Depending on the aperture you select, and also depending on how stable the relative positioning of the separate FPAs is on-orbit, we expect to acquire most targets using a procedure called a peak-up. For this procedure, a stellar source is stepped over a range perpendicular to the apertures and the onboard computer analyzes the counts as a function of position for all four channels. It then calculates the FPA motions necessary to align the channels and center the target in each of the four apertures.
For this procedure to work, we must determine dwell time for the peak-up steps, which will depend on the expected source flux as a function of wavelength as well as on the approximate effective sensitivity of the four FUSE channels. We need to receive enough source counts in each channel to ensure a good centroid measurement. To assist with this calculation, we require specification of three continuum points (at 950, 1050, and 1150 Å) as part of the Phase 2 inputs for each stellar continuum source that requires a peak-up acquisition. The three requested wavelengths should not be taken explicitly: we are looking for "effective" continuum fluxes near these wavelengths. (So for instance, if your source has a strong Lyman-delta line near 950 Å, we don't want the flux in the core of the line, but rather a representative continuum level.) For sources not previously observed in the FUV, you should use the on-line FUSE Spectral Simulator or the FUSE Blackbody Calculator to provide this information. For bright sources, this also provides information required to verify safety of the instrument.
Objects that are too faint or extended in the UV to acquire with a peak-up will require one of several alternate acquisition scenarios necessitating use of an offset star. For extended sources, the offset star can probably be any star brighter than V=13.5 that can be seen in the FES, and whose position you can determine accurately with respect to the target. (Implicit here is the assumption that no "FPA alignment" is needed.) The FES will centroid the star and then move the telescope to point at the target position via blind offset. Such a star should be selected from within the FES field of view of the target if possible (say <15 arcmin as a working number).
For point sources fainter than about 2E-14 ergs/cm^2-s-Å on average over the FUSE range, especially if being placed in the 1.25" slit, you should consider specifying an offset star with sufficient FUV flux to permit a peak-up and focal plane alignment if necessary, prior to blind offsetting. (This is less crucial for the larger apertures.) It may not be possible to find an appropriate source within the FES FOV of your target, but it is desirable to stay within 30 arcmin if possible, although up to a degree can probably be tolerated. An offset target is then connected to a particular target with the `off_object_num' keyword in the observation listing. If no UV-bright offset star is available within a degree, you should consider using a larger slit.
Offset targets can be named normally (see Appendix C), but should end with "-OFF" and be given a priority of "4" to identify them as targets for which no FUV science exposure will be requested.
You should also highlight any KNOWN situations where your target is in a confused field or may otherwise be a difficult acquisition for FUSE. It is in your best interest to make us aware of these cases so we can plan your observations accordingly.
Coordinates and Proper Motion Corrections
It is the user's responsibility to provide target coordinates in Phase 2 corrected from the epoch of whatever plate material or catalog they are using to J2000. It is also the user's responsibility to check their objects for significant proper motion, and if necessary correct the coordinate to the J2000 equinox (i.e. roughly the mid-point of the expected FUSE mission). Since peak-up acquisitions should be robust for coordinate differences of 2-3 arcsec, only proper motion corrections larger than this normally need to be incorporated. Objects with significant PM corrections should be brought to the attention of mission planners in the "support_info_text" section described below and by setting the "high_prop_motion" flag to "Y" after correcting the supplied coordinate. (This flag is simply to permit mission planning personnel to easily identify those targets with proper motion corrections, which may be of importance during field verification and guide star work.)
4. FUSE Phase 2 Proposal Keyword Definitions
In this section, we step through the Phase 2 form and describe the expected or allowed entries for each of the keywords or text sections. Please note that you can bury comments anywhere within the form by preceding them with a "#" sign. However, any such comments will be for your use only; these comments will not be processed by the FUSE planning software or read by FUSE mission planners. (Only the standard text blocks will be read.) Example forms showing proper syntax are provided in Appendix A.
prog_id: (Required) title: (Required) t_alloc_total: (in ksec, Required) t_alloc_orb: (in orbits, Required for French Programs)This information will be filled in or provided to you. Program IDs are assigned to "accepted" proposals by the proposal system. Since PI team programs are "accepted" by default, the program IDs will be provided to you. This ID permits tracking of targets and program status throughout the planning and implementation phases. The program's title should be as short and descriptive as possible, and will be used in tracking and report generation. `t_alloc_total' is the total on-target time for the program in ksec, while for French PI programs, the t_alloc_orb keyword is provided and is the official "allotment." (Note: French "orbit" allotments include acquisitions.)
pi_title: (All required) pi_first_name: pi_last_name: pi_affiliation: pi_institution: pi_address: pi_country: pi_phone: pi_fax: pi_email:PI contact information. These entries provide contact information for the person tasked with being "in charge" of each FUSE science program. This person is assumed to be the primary point of contact for any questions about the program, UNLESS the "Lead Investigator" fields below are filled out.
li_title: (All optional, unless there is a lead investigator.) li_first_name: li_last_name: li_affiliation: li_institution: li_address: li_country: li_phone: li_fax: li_email:Lead Investigator information. Only fill in these fields if someone other than the listed program PI will be the primary point of contact for technical questions about the proposal.
coi_title: (Required for any Co-Is; duplicate and repeat as needed coi_first_name:: for each Co-I.) coi_last_name: coi_institution: coi_country: coi_phone: coi_email:Co-I information. For PI team proposals, list each person who has participated in the appropriate working group or who has expressed interest in or has helped define the program. (Note: less information is requested for Co-Is.)
abstract_text: (Required)Enter a 200-word (or less) abstract for the program. This abstract should provide a descriptive overview, and will be made available on-line at some point.
feasibility_text: (Required)The Science team signed-on at the Jan. 1997 meeting to provide a description of program feasibility with each Phase 2 program. This should include discussion of the quality of the flux estimates, and the method used to calculate count rates, signal-to-noise, and program feasibility. Use of the FUSE simulators and/or the on-line Exposure Time Calculator are STRONGLY encouraged. FUSE mission planners will perform a feasibility analysis of all PI team programs using this information and the data provided for each object below.
spec_req_text: (Optional, as needed)Information on "special requirements" is requested on an `object' and `observation' level below. A text block is encouraged here to discuss in general terms any such requirements of the program. Again, NONE of these should be specified frivolously, since they may seriously constrain when a given object or observation can be scheduled. Refer to section 3 above for a discussion of these SRs.
support_info_text: (Optional, as needed)Brief, text block. The user should describe any special considerations or strategy issues here, or desires to use possible "extended" capabilities of the satellite, should they become available. These may include such things as:
Object-specific Information: (repeat keywords as needed, for each object; unused "optional" keywords can be dropped or left blank.)
object_number: (Required)This should be a two-digit integer with or without leading zeroes (e.g. 1, 01, etc.) that is unique for each target in your program, including any offset stars. If your program requires more than 99 objects, you're special. Contact FUSE mission planners.
object_name: (Required)Object naming conventions and syntax should basically follow those developed at STScI for use in HST proposals. Details are provided in Appendix C, "FUSE Target Naming Conventions for Cycle 1."
Offset targets, if needed, should be identified by "Object_name"-OFF, where "Object_name" refers to the primary object (or a primary object) of interest. Offset targets should only be needed in specialized cases, where the primary target is too faint or extended for a direct "peak-up" acquisition. Offset targets should themselves be reasonably bright FUV sources, to permit a peak-up and/or channel alignment to be performed, if needed. (May not be necessary for some extended sources.) Acquisition of the primary target will then be done by blind offset to the target position. Hence, offset stars should be as close as possible to the primary target, and hopefully within an FES FOV of the target (roughly 15 arcmin). Other than flux information and an accurate position RELATIVE TO your primary source position, no other data are required for offset stars.
object_class: (Required)We will use a slightly modified version of the two-digit numerical IUE Object classification scheme, given in Appendix B. This code number provides a rough idea of object type to mission planners, and will "follow" the observation into the archive for future reference.
object_spec_req: (Optional)Specify any object-specific special requirements (SRs) that apply: MOVE, TOO, NIGHT, HIRES. (Meanings are described in section 3.)
ra_j2000: (Required, unless target is a moving target or dec_j2000: TOO of unknown position.)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. However, if the target is bright enough at UV wavelengths to permit a PEAK-UP acquisition to work, coordinates accurate to about 2-3 arcsec or better will be sufficient. In particular, if your target is bright enough to be listed in the HST Guide Star Catalog, this coordinate is preferable since it will already be in the proper frame of reference for use by FUSE.
The next set of keywords define the user-supplied flux and source type information necessary for checking observation safety and feasibility and verifying the user's expectations.
source_type: (Required) PC, PE, EC, EEA 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. In cases with both continuum and emission lines, the user should choose the one more important to the science 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 Planning needs to know of any special situations that might cause a safety or count rate 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 bright limits.)
lambda_ref: (Required)A reference wavelength in Angstroms should be entered. This should be a wavelength <=1190 Å (i.e. within the FUSE range). This is the wavelength for which the flux below pertains and for which the S/N has been calculated. As such, it should generally be a wavelength of interest to your science program. (However, see comments in section 3 for emission line sources.)
flux_lambda_ref: (Required)The user should enter a "flux" value, in n.nnE-nn format (n=0-9) 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. Refer to the FUSE Observer's Guide for important information on bright limits for continuum and emission line sources.
eline_fwhm: (Required for source_type = PE and EE)Only needed if source type involves emission lines. Approximate FWHM of line in Angstroms should be entered.
sb_lambda_ref: (Required for EC and EE)Expected surface brightness (flux per square arcsec) in n.nnE-nn format; only needed if source type involves an extended source. This number should be the above expected flux divided by the number of square arcsec of emission expected through the chosen aperture.
flux_950: (Required for continuum sources) flux_1050: flux_1150:These keywords list representative continuum fluxes expected at three reference wavelengths in the FUSE range, to be used both for safety checking and calculation of `peak-up' acquisition times. (See discussion in section 3 for more detailed information.) The values entered should be in exponential format (n.nnE-nn) in units of ergs/cm**2-s-Å.
flux_accuracy: (Required) HIGH, MED, LOWThis keyword is used to indicate the accuracy level of the flux information provided above. (This is important for safety checks, acquisition time calculations, and estimating spacecraft memory usage.) As a general guideline, HIGH should indicate an actual observed value in the FUSE range (say 1190 Å or below, from HUT, ORFEUS, or HST) or a small extrapolation from <1300 Å ; MED should indicate situations where extrapolation from longer FUV 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 used is uncertain).
v_mag: (Optional, but strongly encouraged)Johnson V magnitude. This is for general information, and flagging potential FES-related issues. This information will be carried into the archive with the data.
v_range: (Optional)Used only for indicating the extent to which the object may be variable in the visual band, and for flagging potential FES issues. When entered, this should be a V magnitude range, separated by a hyphen and without spaces (e.g., 10.1-14.5).
resolution_element: (Required)This field should indicate the size of the resolution element over which the quoted signal-to-noise ratio below has been calculated.
expected_ct_rate: (Required, and very important)For each object, the user should provide an estimate of the expected total source count rate (cts/sec), preferably based on a FUSE simulation or Exposure Time Calculator output. This is needed as accurately as possible, and will ultimately drive the selected observing mode (TTAG or HIST) and onboard memory requirements of the observation.
sig_noise: (Required)This should be the expected signal-to-noise per specified resolution element at the reference wavelength.
spectral_type: (Optional) Provide MK spectral type and luminosity
class for all stellar classes.
color_excess: (Optional) Measured E(B-V), if available.
red_shift: (Optional) Either standard format, or in km/s; value will
be obvious either way.
The three items above should be provided when available or appropriate.
This information will probably not be used directly for mission planning, but
will be available for reference if needed and will accompany the
observational data into the archive.
high_prop_motion: (Optional)Leave blank or "N" if no correction, or set to "Y" if a proper motion correction has been applied to the submitted coordinate. See notes in section 3 above for more information.
object_prio: (Required)See notes in section 3 (above) on target priorities. Legal values are 1, 2, or 3 (1=high). These priorities are for use within individual programs and are not intended to indicate relative target priorities across different programs. Targets to be used for ancillary purposes (for instance, an OFFSET star, for which an actual FUV observation is not desired) should be specified with priority 4.
The last two object entries deal only with "ephemeris" targets for which the EPHEM SR will be invoked below:
phase_zero: (Optional unless EPHEM.) phase_period: (Optional unless EPHEM.)The phase_zero keyword provides the Julian day of the assumed zero point in the periodic phenomenon of interest. Only the day number ABOVE 2,400,000 SHOULD BE PROVIDED, and no commas should be entered. (For instance, June 1, 1997, was JD2,450,601, and would be specified 50601.) The phase_period keyword should provide the period of the variation in decimal days, to whatever accuracy is required.
Observation-specific information: (repeat keywords as needed, for each observation of each target; unused "optional" keywords can be dropped or left blank.)
observation_num: (Required)An increasing integer, used for specifying separate observations of a target. Ranges from 1-99, and leading zeroes are optional. This should be the FIRST keyword listed for each new observation. If MON, a range is allowed for this field, viz. "1 to 20" (see Appendix A for example). If your program requires more than 99 observations, you're special. Contact FUSE mission planners.
obs_object_num: (Required)This keyword mirrors the `object_number' from the target listing above, and identifies the object for which this observation is being specified.
off_object_num: (Optional)Enter the `object_number' of any specified offset target needed to acquire your science target.
obs_spec_req: (Optional, as needed)Supported observation-specific SRs for Cycle 1 are ROLL, MON, EPHEM, SNAP, SAFTSNP, SPATIAL, CONTIG, and FESIMG. (Meanings are described above in section 3.)
A couple of these SRs will spawn secondary keywords that are required only when the primary keyword is present. These include:
For ROLL SR:
aperture_pa: The desired Position Angle (east from north) for the long dimension of the FUSE apertures. This angle will be assumed to be modulo 180 degrees unless called out otherwise in the SR text block above. pa_tolerance: The allowed half angle or "tolerance" on the above position angle, to permit scheduling flexibility.For MON SR:
MON indicates a target for which a repeated observation (or monitoring program) is desired. In this case, the user must specify a "mon_t_sep" keyword, which is the nominal separation of the observations in decimal days, and a "mon_delta_tsep" keyword (also in days) indicating the amount of leeway allowed in the separation. In this case, the "obs_time_req" keyword (given below) pertains to an individual observation.
mon_t_sep: nominal separation of individual observations, in days. mon_delta_tsep: tolerance permitted on nominal separation, also in days.
For EPHEM SR:
EPHEM indicates a target for which a specific ephemeris constraint applies to the observation (say a binary star or cataclysmic variable phase). Such observations need to be scheduled at certain specific UTs (or at least within some range of UT). The EPHEM special requirement spawns the additional keywords "phase_zero" and "phase_period" (discussed above under object-specific keywords) and:
phase_desired: The midpoint of the desired phase to observe. phase_delta: The allowed delta on the "phase_desired:" parameter.
The phase_desired keyword should be a number between 0.0 and 1.0, and phase_delta will be assumed to indicate a desired plus or minus in phase space. For example, if phase_desired is 0.5 and phase_delta is 0.1, then we will assume you are after an observation covering phase 0.4 - 0.6.
For FESIMG SR:
The user can specify whether a reference FES image should be obtained with the object in the aperture, or with the object bumped out of the aperture (i.e. actually visible in the FES image). The user can also specify a filter if desired. The keywords are:
targ_pos: Legal values are IN or OUT, specifying the target
position relative to the aperture.
fes_filter: Allowed values are ND, COL, NONE, or DEF(ault) (i.e. same
as used for guiding).
(Note: Implementation of FES imaging is still uncertain at this writing. At the very least specifying a filter here will tell us what you desire for the exposure. We may have to default to the same aperture used for guiding, at least initially.)
instrument_mode: (Optional) TTAG, HISTFUSE mission planners will apply rules to decide whether each observation should be performed in TTAG or HIST mode. If it matters to your science, you have the option here of telling us which mode you want or think is appropriate for your observation. Differences will be tracked and resolved as needed.
aperture_req: (Required)Enter the desired FUSE aperture to be used for the observation. The options are:
obs_time_req: (Required)Enter the total integration time desired for the observation, in units of seconds. This does not include acquisition, but is the real desired integration time on target, and should correspond to the observing time needed to produce the quoted S/N ratio above. If the MON keyword is set above, however, this should be the length of an individual monitoring observation.
5. Phase 2 Template File and Strategy
You will be provided with an ASCII file containing a blank Phase 2 template (keywords and comments only). (We may provide allocation and program ID information in the delivered file.) After the generic "proposal information" sections (investigator information, text blocks, etc.) will be a set of keywords that are repeated for each target, and then for each observation the user wishes to specify. Each specified "observation" is tied to an "object" via the `obs_object_num' keyword, as described above. This provides the user with the option to organize the Phase 2 submission in one of two ways:
Appendix A. Example FUSE Phase 2 Template Forms
NOTE: This form shows examples and syntax, but is not meant to represent a completely self-consistent proposal. For visibility, unused keywords are left in place.
#
#
#
# #########################################
# ## ##
# ## FUSE Phase 2 Proposal Example ##
# ## ##
# #########################################
#
#
# Proposal Identification
prog_id: P114
title: FUSE Team Project on Supernova Remnants
t_alloc_total: 25 # Ksec
t_alloc_orb: # Orbits, for French programs only.
# ######################
# ## ##
# ## PI Information ##
# ## ##
# ######################
pi_title: Dr.
pi_first_name: William P.
pi_last_name: Blair
pi_affiliation: Dept. of Physics and Astronomy
pi_institution: Johns Hopkins University
pi_address: 34th and Charles Streets, Baltimore , MD, 21218-2686
pi_country: USA
pi_phone: 410-516-xxxx
pi_fax: 410-516-8260
pi_email: wpb@pha.jhu.edu
# ######################
# ## ##
# ## LI Information ##
# ## ##
# ######################
li_title: Mr.
li_first_name: Carl A.
li_last_name: Johnson
li_affiliation: Space Telescope Science Institute
li_institution: NASA
li_address: 3700 San Martin Drive, Baltimore, MD, 21218
li_country: USA
li_phone: 410-338-2615
li_fax: 410-338-xxxx
li_email: cjohnson@stsci.edu
# ########################
# ## ##
# ## COIs Information ##
# ## ##
# ########################
# COI - 1
coi_title: Dr.
coi_first_name: Kenneth
coi_last_name: Sembach
coi_institution: Johns Hopkins University
coi_country: USA
coi_phone: 410-516-4756
coi_email: sembach@pha.jhu.edu
# COI - 2
coi_title: King
coi_first_name: William
coi_last_name: Lancaster
coi_institution: Tower of London
coi_country: UK
coi_phone: 888-IAM-KING
coi_email: the_king.@london.uk.com
#
# ############################
# ## ##
# ## Proposal Information ##
# ## ##
# ############################
# -------------
# | Abstract |
# -------------
abstract_text:
We will use FUSE to make key observations of several supernova
remnants to further our understanding of the universe at large and
our place in it. Since we are all made of star stuff, these
observations cut right to the heart of the matter of origins. Hence,
NASA-HQ supports this proposal in its entirety.
# ----------------
# | Feasibility |
# ----------------
feasibility_text:
All of these observations are based on previous FUV observations,
so the flux levels are actually known. We have made extensive use
of the various FUSE simulators to prove beyond the shadow of a
doubt that the observations are not only feasible, but should win us
the Nobel prize for Physics in the year 2015.
# ------------------
# | Special Reqs. |
# ------------------
spec_req_text:
Some of the observations require specific aperture orientations to
place the long dimension of the FUSE apertures along particular SN
remnant filaments, within a 10 degree tolerance. A grid of three
aperture positions is planned, which should be closely grouped in time.
FESIMG is specified on the first pointing to provide a reference image
of the star field in the vicinity of the slit for future reference.
Although the SPATIAL requirement is not shown (because it is not a
driver for the program), it is conceivable that some spatial information
may be obtainable at O VI.
# ------------------
# | Support Info. |
# ------------------
support_info_text:
The target positions are faint supernova remnant filaments, which must
be acquired by blind offset from a nearby star (target 2), in order to
position the FUSE aperture correctly. Targets 1-3 form a small
"grid" of aperture positions across the filament of interest. Although
the tolerance on the requested roll angle is 10 degrees for these
observations, once one of the observations is scheduled, the other two
positions should be observed at as close to the same roll angle as
possible.
# ############################
# ## ##
# ## Object 1 Information ##
# ## ##
# ############################
object_number: 1 # 1-99
object_name: CYG-LOOP-P1A # See separate document.
object_class: 75 # See Appendix B.
object_spec_req: # MOVE, TOO, NIGHT, HIRES
ra_j2000: 20:47:32.1 # e.g. 20:31:45.22
dec_j2000: +31:02:01.5 # e.g. +31:02:01.5
source_type: EE # PC, PE, EC, EE
lambda_ref: 1032. # e.g. 1032.
flux_lambda_ref: 1.2E-12 # e.g. 1.2E-12
eline_fwhm: 0.5 # in Angstroms, e.g. 0.5
sb_lambda_ref: 6.0E-14 # "flux" per sq. arcsec.
flux_950: # Equiv. Cont. Flux at 950 A; e.g. 1.2E-12
flux_1050: # Equiv. Cont. Flux at 1050 A
flux_1150: # Equiv. Cont. Flux at 1150 A
flux_accuracy: HIGH # HIGH, MED, LOW.
v_mag: # mag, e.g. 12.5
v_range: # mag range, e.g. 9.9-13.2
resolution_element: 0.1 # in Angstroms, e.g. 0.033.
expected_ct_rate: 55 # cts/s, pref. from ETC or sim.
sig_noise: 20 # per specified res. element.
spectral_type: # No spaces please.
color_excess: 0.08 # mag, e.g. 0.10.
red_shift: # Z format or km/s.
high_prop_motion: N # Y if you applied a PM
# correction to above coordinate.
object_prio: 1 # 1, 2, 3, or 4.
phase_zero: # Only for Ephem. targets.
phase_period: # Only for Ephem. targets.
# ###################################
# ## ##
# ## Obj 1 Obs 1 Information ##
# ## ##
# ###################################
#
#
observation_num: 1 # 1-99, or `1 to N' if MON.
obs_object_num: 1 # From Object listing
off_object_num: # Offset Target Number
instrument_mode: TTAG # HIST, TTAG
aperture_req: HIRS # HIRS, MDRS, LWRS
obs_time_req: 8000 # sec per obs, e.g. 4000
# NOTE: "per obs." for MON.
obs_spec_req: ROLL, FESIMG # ROLL, SNAP, MON, EPHEM,
# SPATIAL, CONTIG, and/or FESIMG.
#If ROLL spec. req.
aperture_pa: 135. # angle in degrees, e.g. 135.0
pa_tolerance: 10. # angle in degrees, e.g. 10.0
# If MON spec. req.
mon_delta_tsep: # days, e.g. 2.50
mon_t_sep: # days, e.g. 21.00
# If EPHEM spec. req.
phase_desired: # e.g. 0.5
phase_delta: # e.g. 0.05
# If FESIMG spec. req.
targ_pos: IN # IN or OUT
fes_filter: NONE # ND, COL, or NONE.
#-----------------------------------------------------------
# Next Object: Example OFFSET star Object listing. (Note: no
# "observation" fields required.)
# ############################
# ## ##
# ## Object 2 Information ##
# ## ##
# ############################
object_number: 2 # 1-99
object_name: CYG-LOOP-P1A-OFF # See separate document.
object_class: 21 # See Appendix B.
object_spec_req: # MOVE, TOO, NIGHT, HIRES
ra_j2000: 20:47:35.2 # e.g. 20:31:45.22
dec_j2000: +31:03:22.1 # e.g. +31:02:01.5
source_type: PC # PC, PE, EC, EE
lambda_ref: 1000. # e.g. 1032.
flux_lambda_ref: 5.5E-12 # e.g. 1.2E-12
eline_fwhm: # in Angstroms, e.g. 0.5
sb_lambda_ref: # "flux" per sq. arcsec.
flux_950: 1.1E-12 # Equiv. Cont. Flux at 950 A; e.g. 1.2E-12
flux_1050: 1.05E-12 # Equiv. Cont. Flux at 1050 A
flux_1150: 1.0E-12 # Equiv. Cont. Flux at 1150 A
flux_accuracy: MED # HIGH, MED, LOW.
v_mag: 12.2 # mag, e.g. 12.5
v_range: # mag range, e.g. 9.9-13.2
resolution_element: # in Angstroms, e.g. 0.033.
expected_ct_rate: # cts/s, pref. from ETC or sim.
sig_noise: # per specified res. element.
spectral_type: B4V # No spaces please.
color_excess: # mag, e.g. 0.10.
red_shift: # Z format or km/s.
high_prop_motion: N # Y if you applied a PM
# correction to above coordinate.
object_prio: 4 # 1, 2, 3, or 4.
phase_zero: # Only for Ephem. targets.
phase_period: # Only for Ephem. targets.
# An object listing this as an offset target would specify
# `off_object_num' as "2" in the observation listing.
#-----------------------------------------------------------
# Next Object: Example Extragalactic Target and MON observation.
# ############################
# ## ##
# ## Object 3 Information ##
# ## ##
# ############################
object_number: 3 # 1-99
object_name: NGC4151 # See separate document.
object_class: 84 # See Appendix B.
object_spec_req: # MOVE, TOO, NIGHT, HIRES
ra_j2000: 14:47:35.2 # e.g. 20:31:45.22
dec_j2000: -21:03:22.1 # e.g. +31:02:01.5
source_type: EC # PC, PE, EC, EE
lambda_ref: 1000. # e.g. 1032.
flux_lambda_ref: 3.0E-12 # e.g. 1.2E-12
eline_fwhm: # in Angstroms, e.g. 0.5
sb_lambda_ref: # "flux" per sq. arcsec.
flux_950: 1.0E-13 # Equiv. Cont. Flux at 950 A; e.g. 1.2E-12
flux_1050: 1.1E-13 # Equiv. Cont. Flux at 1050 A
flux_1150: 1.2E-13 # Equiv. Cont. Flux at 1150 A
flux_accuracy: HIGH # HIGH, MED, LOW.
v_mag: 12.2 # mag, e.g. 12.5
v_range: # mag range, e.g. 9.9-13.2
resolution_element: 0.1 # in Angstroms, e.g. 0.033.
expected_ct_rate: 300 # cts/s, pref. from ETC or sim.
sig_noise: 10.0 # per specified res. element.
spectral_type: # No spaces please.
color_excess: 0.03 # mag, e.g. 0.10.
red_shift: 1100 # Z format or km/s.
high_prop_motion: N # Y if you applied a PM
# correction to above coordinate.
object_prio: 1 # 1, 2, 3, or 4.
phase_zero: # Only for Ephem. targets.
phase_period: # Only for Ephem. targets.
# ###################################
# ## ##
# ## Obj 3 Obs Information ##
# ## ##
# ###################################
#
#
# This sets up 9-2000 sec observations separated by 14 +/- 2 days.
observation_num: 2 TO 10 # 1-99, or `1 TO N' if MON.
obs_object_num: 3 # 1-99
off_object_num: # Offset target number, if needed.
instrument_mode: TTAG # HIST, TTAG
aperture_req: MDRS # HIRS, MDRS, LWRS
obs_time_req: 2000 # sec per obs, e.g. 4000
# NOTE: per obs. for MON.
obs_spec_req: MON # ROLL, SAFTSNP, SNAP, MON, EPHEM,
# SPATIAL, CONTIG, and/or FESIMG.
#If ROLL spec. req.
aperture_pa: # angle in degrees, e.g. 135.0
pa_tolerance: # angle in degrees, e.g. 10.0
# If MON spec. req.
mon_delta_tsep: 14 # days, e.g. 2.50
mon_t_sep: 2 # days, e.g. 21.00
# If EPHEM spec. req.
phase_desired: # e.g. 0.5
phase_delta: # e.g. 0.05
# If FESIMG spec. req.
targ_pos: # IN or OUT
fes_filter: # ND, COL, or NONE.
#-----------------------------------------------------------
# Next Object: Bright, stellar object requiring HIST observation.
# ############################
# ## ##
# ## Object 4 Information ##
# ## ##
# ############################
object_number: 4 # 1-99
object_name: HD13245 # See separate document.
object_class: 23 # See Appendix B.
object_spec_req: HIRES # MOVE, TOO, NIGHT, HIRES
ra_j2000: 06:53:10.2 # e.g. 20:31:45.22
dec_j2000: -02:42:37.6 # e.g. +31:02:01.5
source_type: PC # PC, PE, EC, EE
lambda_ref: 1000. # e.g. 1032.
flux_lambda_ref: 3.0E-11 # e.g. 1.2E-12
eline_fwhm: # in Angstroms, e.g. 0.5
sb_lambda_ref: # "flux" per sq. arcsec.
flux_950: 2.9E-11 # Equiv. Cont. Flux at 950 A; e.g. 1.2E-12
flux_1050: 3.1E-11 # Equiv. Cont. Flux at 1050 A
flux_1150: 3.3E-11 # Equiv. Cont. Flux at 1150 A
flux_accuracy: MED # HIGH, MED, LOW.
v_mag: 8.2 # mag, e.g. 12.5
v_range: # mag range, e.g. 9.9-13.2
resolution_element: 0.033 # in Angstroms, e.g. 0.033.
expected_ct_rate: 2830 # cts/s, pref. from ETC or sim.
sig_noise: 30.0 # per specified res. element.
spectral_type: B0II # No spaces please.
color_excess: 0.13 # mag, e.g. 0.10.
red_shift: # Z format or km/s.
high_prop_motion: N # Y if you applied a PM
# correction to above coordinate.
object_prio: 1 # 1, 2, 3, or 4.
phase_zero: # Only for Ephem. targets.
phase_period: # Only for Ephem. targets.
# ###################################
# ## ##
# ## Obj 4 Obs Information ##
# ## ##
# ###################################
#
#
observation_num: 11 # 1-99, or `1 TO N' if MON.
obs_object_num: 4 # 1-99
off_object_num: # Offset target number, if needed.
instrument_mode: HIST # HIST, TTAG
aperture_req: HIRS # HIRS, MDRS, LWRS
obs_time_req: 4000 # sec per obs, e.g. 4000
# NOTE: per obs. for MON.
obs_spec_req: FESIMG # ROLL, SNAP, MON, EPHEM,
# SPATIAL, CONTIG, and/or FESIMG.
#If ROLL spec. req.
aperture_pa: # angle in degrees, e.g. 135.0
pa_tolerance: # angle in degrees, e.g. 10.0
# If MON spec. req.
mon_delta_tsep: # days, e.g. 2.50
mon_t_sep: # days, e.g. 21.00
# If EPHEM spec. req.
phase_desired: # e.g. 0.5
phase_delta: # e.g. 0.05
# If FESIMG spec. req.
targ_pos: OUT # IN or OUT
fes_filter: COL # ND, COL, or NONE.
#-----------------------------------------------------------
#(End of examples.)
Appendix B: Numerical Object Class Designations
Below are the IUE target class codes with no changes (cf. IUE Observer's Guide, in IUE Newsletter 32, pg. 78, July 1987). Obviously, some of these are not appropriate for FUSE, but many are. Specifying a reasonable code number will make comparisons between the IUE and FUSE archives more straightforward.
00 Sun 50 R, N, or S Type Star 01 Earth 51 Long Period Variables 02 Moon 52 Irregular Variables 03 Planet 53 Regular Variables 04 Planetary Satellite 54 Dwarf Novae 05 Minor Planet 55 Classical Novae 06 Comet 56 Supernovae 07 Sky Background 57 Symbiotic Stars 08 Great Red Spot 58 T Tauri Stars 09 59 X-ray Source 10 WC 60 Shell Star 11 WN 61 Eta Carinae 12 Main Sequence O 62 Pulsar 13 Supergiant O 63 Nova-like 14 Oe 64 Other 15 Of 65 Misidentified Targets 16 O Subdwarf 66 Interacting Binaries 17 WD O 67 18 68 19 Other Strong UV source 69 Herbig-Haro Object 20 B0-B2 IV-V 70 Cent. Star Plan. Neb. 21 B3-B5 IV-V 71 Planetary Nebula 22 B6-B9.5 IV-V 72 H II Region 23 B0-B2 I-III 73 Reflection Nebula 24 B3-B5 I-III 74 Dark Cloud (Absorp. spectrum) 25 B6-B9.5 I-III 75 Supernova Remnant 26 Be 76 Ring Nebula (Shock-ionized) 27 Bp 77 28 B Subdwarf 78 29 WDB 79 30 A0-3 IV-V 80 Spiral Galaxy 31 A4-9 IV-V 81 Elliptical Galaxy 32 A0-3 I-III 82 Irregular Galaxy 33 A4-9 I-III 83 Globular Cluster 34 Ae 84 Seyfert Galaxy 35 Am 85 Quasar 36 Ap 86 Radio Galaxy 37 WDA 87 BL Lac Object 38 Horiz. Branch Stars 88 Emission-line Galaxy (non-Seyfert) 39 Composite Spectra 89 40 F0-2 90 Intergalactic Medium 41 F3-9 91 42 Fp 92 43 Late-type Degenerates 93 44 G IV-V 94 45 G I-III 95 46 K IV-V 96 47 K I-III 97 48 M IV-V 98 49 M I-III 99
Appendix C: FUSE Target Naming Conventions for Cycle 1
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 position al 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 desi gnated 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 par ent 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.