|Information for Researchers|
3. Cycle 2
This page will cover the following topics:
Cycle 2 observations will take place between January, 2014 and December, 2014. During this period there will be four observing campaigns with a total of approximately 200 hours of science flight time available to the astronomical community, excluding time allocated for the German call and Director's Discretionary Time.
Five instruments, FORCAST, GREAT, FLITECAM, EXES, and HIPO will be available during Cycle 2. The instrument capabilities, the available modes, and the resulting performance specifications of the telescope are described in later sections. Some of the modes offered for FLITECAM, and GREAT and all of the modes available with EXES will be offered as ''Shared Risk'' as they have not yet been commissioned or fully tested.
FIFI-LS will be offered in ''Short Science'' mode. Those who have an interesting science question and would like to collaborate on a joint investigation with the FIFI-LS team are encouraged to apply for this ''Short Science'' time.
Proposals are being solicited for the Cycle 2 SOFIA flights by USRA on behalf of NASA.
The duration of each SOFIA Cycle 2 flight is expected to be between 9 ‒ 10 hours, 8 ‒ 9 hours of which will be available for observing at altitudes of 37,000 ‒ 45,000 feet. There will be only one instrument on board the aircraft for any given flight, with the exception of the FLIPO configuration (FLITECAM + HIPO). The SMO director will determine the total number of flights dedicated to each instrument, after consideration of the number of TAC-approved proposals for each.
Proposals should request observing time in units of hours. Once a proposal has been approved, the first stage is complete and the GI is then expected to carry out the detailed planning of their observations in consultation with a support scientist. This second stage of observation planning is known as Phase II. The GIs will be informed who their SMO support scientists are and how to contact them.
On each SOFIA Cycle 2 flight, there will be one or more seats available for GIs or designated CoIs of the proposals scheduled for that flight. Since there are a limited number of seats available on each flight, the choice of GIs given the opportunity to fly on SOFIA will be made by the SMO director according to a number of considerations, including the duration of science observations for each program on the flight and the proposal rank.
The observations will be carried out either by members of the instrument team along with SOFIA personnel, or solely by SOFIA personnel. The GIs on board SOFIA will participate in the observing, and monitor the data as it is received, but will have limited decision making abilities. For example, the GI will be allowed to make real-time changes to exposure times for different filters or channels. However, changing targets or any modifications that alter the durations of flight-legs will not be allowed.
Those GIs or CoIs chosen to fly aboard SOFIA will be required to complete a flight participation form, a medical release form, and documentation related to badging. In addition, they will be required to participate in an Egress Training course prior to being allowed on board the aircraft. Full details will be provided to GIs of approved proposals during the Phase II process.
Scheduling and flight planning will be handled by the SMO staff and is not the responsibility of the GI. However, an understanding of the flight planning process and the restrictions inherent to airborne astronomy may be useful in preparing a successful proposal.
The most distinctive aspect of SOFIA flight planning is the interdependency of the targets observed in a flight. Because the azimuthal pointing is controlled primarily by the aircraft heading and because, in normal operations, the take-off and landing air fields are the same, efficient flight plans must generally balance East-bound with West-bound flight legs and South-bound with North-bound legs. This also means that for any flight only a limited fraction of the observing can be performed in a given region of the sky. An example of a flight plan flown during Basic Science in May 2011 is shown in Figure 3-1 below. Several more examples of flight plans flown during Basic Science can be found on the Information for Researchers Flight Plans web page.
For the proposer this leads to several considerations:
GIs are encouraged to review the Flight Planning presentation delivered by Dr. Randolf Klein at the SOFIA User's Workshop in November, 2011. The full list of presentations can be found on the SOFIA web site. In addition, a much more detailed discussion of target scheduling and flight planning can be found in the Observation Scheduling and Flight Planning White Paper.
SOFIA has three optical cameras for acquisition, guiding and tracking. The Wide Field Imager (WFI) and Fine Field Imager (FFI) are mounted on the telescope head ring. The upgraded Focal Plane Imager (FPI+) images the focal plane of the telescope via a dichroic and a tertiary mirror. All three imagers use ''High Speed Slow Scan'' CCD cameras.
The WFI has a 6°x6° field of view, and is expected to achieve a centroid precision of ~8'' for stars brighter than R = 9. The field of view of the FFI is 1°x1°. It is expected to achieve a centroid precision of ~1'' for R = 11 or brighter stars. The FPI+ has an 8' diameter and is expected to provide a centroid precision of 0.05'' for R = 16 or brighter stars.
Most observers do not need to select guide stars as they will be chosen by the SMO staff. However proposers should be aware that the guiding cannot be done on IR sources unless they are optically bright.
Once SOFIA achieves its nominal operating capabilities, it will be able to observe solar system targets by (i) guiding on the object itself, (ii) offset guiding from field stars, or (iii) predictive tracking based on accurate ephemerides. However, by the time of Cycle 2 observations, only the first of these techniques will have been tested and implemented.
The SOFIA project will make every attempt to observe Solar System targets in highly ranked proposals. However, proposers should bear in mind that Cycle 2 observations of moving targets are ''Shared Risk''. The observatory is still in development so many of its performance characteristics will not be fully known at the time of the Cycle 2 proposal deadline.
Successful guiding on a moving target requires it to be bright at visible wavelengths, where the guider cameras operate. Our current estimate is that we will be able to guide on solar system targets with R ≤ 10 and that have a non-sidereal angular speed of 1'/s or less. The minimum acceptable solar elongation for a target is limited by the lower elevation limit of the telescope and the rule that no observations can be acquired before sunset or after sunrise. For Cycle 2, the minimum solar elongation is 25 degrees.
Identification of solar system targets will be done manually by the Telescope Operator by inspecting images obtained with the FPI. The ephemerides of the proposed target must be accurate enough to allow for unambiguous identification. While the required accuracy could vary somewhat based on the complexity of the background star field, it should in general be better than about 30\arcsec.
For moving objects with visible magnitude fainter than 10th, it will be possible (on a Shared Risk basis) to utilize the fast diagnostic camera (FDC) as a guider camera. This mode has not yet been tested and requires a custom installation, so only a limited number of such observations will be performed. With this camera sources brighter than 15th magnitude should be usable for guiding. Proposals requesting this configuration should note the Shared Risk involved and make the case for why such observations should be performed during Cycle 2.
In many respects, the design of the SOFIA telescope is similar to that of a typical altitude-azimuth telescope. One such similarity is that as the telescope tracks a target it must rotate in order for the sky to remain at the same orientation on the detectors. The range of free rotation by the telescope is limited, however, to ± ~3°. Hence, the telescope must periodically undergo a ''Line-of-Sight (LOS) rewind'', or de-rotation. The required frequency of LOS rewinds depends on rate of field rotation experienced by the target, which is a complex function of the position of the target in the sky relative to that of the aircraft heading. Since the relative target position is not known
, but is only determined during flight planning, it is not possible to determine precisely the field rotation rate until after the observations have been scheduled. However, one can estimate either the rate of field rotation using Figure 3-2 or the time it takes for a field of view to rotate by six degrees using Figure 3-3.
In order to use the plots effectively, one must first use the SOFIA Target Visibility Tool or similar visibility planning tool to determine the airplane heading ( AH ) and the target elevation ( El ) at the desired date of observation. Since the telescope is situated in the port side (i.e. the left side as seen by a person on board, facing the front of the aircraft), the target azimuth angle ( Az ) is calculated according to, Az = AH - 90° . The zenith angle ( ZA ) is calculated according to, ZA = 90° ‒ El . Once the ZA and Az of the target have been determined for a sample observation date, then the LOS plots provide an estimate of the rotation of field for the target.
For example, according to the SOFIA Target Visibility Tool, during the month of August, the W3 star forming region, is at an elevation that ranges from between about 20° and 60° throughout the evening. The aircraft heading would be ~130°. Hence, ZA = 70° ‒ 30° for an average of ~50° and Az ≅ 40° . On Figure 3-2, these coordinates correspond to a field rotation rate of approximately -25° per hour, or roughly 6 degrees every 15 minutes as indicated on Figure 3-3.
When using Figures 3-2 and 3-3 to estimate the rotation of field, it is important to bear in mind the associated caveats. First, the plots were calculated assuming that the aircraft position was at 37.415°, the latitude of NASA Ames. In practice, the latitude of the aircraft may deviate significantly from this. In addition, in the example, we made the estimates using the average ZA of the target, but in practice, neither the ZA at the time of observation nor the actual observation date will be known until flight planning is complete. This means that one should consider the estimates of the rotation of field as being only approximate. Finally, in flight, the LOS rewinds are performed after a field rotation of ~3° rather than the maximum possible range of 6°, in order to account for slight deviations in the airplane heading.
Special care must be taken when designing spectroscopic observations. GIs should bear in mind that the orientation of the slit on their targets will change with each LOS rewind. For point sources, this should not cause problems, but for extended sources, this means that after each rewind the slit will be sampling a slightly different region of the source. In addition, there is no way to choose the orientation of the slit on the target.
SOFIA operates at altitudes above 99% of the water vapor in the atmosphere. The average atmospheric transmission across the SOFIA bandpasses is about 80% at these altitudes. There are however a number of strong absorption features which, even at these altitudes, make the atmosphere nearly opaque. Broad band filters, such as those on FORCAST, account for the presence of such features. However, when using high-resolution tunable instruments such as GREAT, it is necessary to examine the atmospheric transmission at the wavelengths of interest in detail. This may be done using the web interface to the ATRAN program that was developed and kindly provided to the SOFIA program by Steve Lord. A plot of the atmospheric transmission seen by SOFIA in comparison to that achieved at Mauna Kea is shown in Figure 3-4 below.
In addition to its dependence on wavelength due to the presence of absorption features, the atmospheric transmission varies with latitude and with time of year, primarily due to differences in the amount of water vapor. It also exhibits variations on smaller time scales due to changes in the location of the tropopause. Full discussions of these issues may be found in Haas & Phister 1998 (PASP, 110, 339) and Horn & Becklin 2001 (PASP, 113, 997).
The variations in atmospheric water vapor could have a significant impact on some observations, particularly when using GREAT or grism modes with FLITECAM or FORCAST. For example, GREAT observations of a line situated on the shoulder of an atmospheric water feature could be strongly affected by water vapor variability. SITE allows the user to specify the water vapor overburden and adjusts the time estimates appropriately. A water vapor monitor will be functioning during full operations, but is not expected to be available during Cycle 2.
Calibration observations will be planned by the SMO staff using standard stars, asteroids and planets. It is expected that three or more calibration targets will be observed per flight, each at a different altitude. The time used for calibration observations are part of the general overhead, and will not be charged against any GI program time. The calibration accuracy will depend on the instrument and observation mode, but an accuracy of ≤ 20% is expected to be obtained, even in ''Shared Risk'' modes.
Unless the proposer requires more accurate calibration, there is no need to request time for calibration or to choose calibration targets. If the GI has such requirements for more accurate calibration, they must be justified in the proposal, and the time required for the calibration observations should be included in the total time request.
Page Last Updated: November 6, 2013