Phase II Proposal - Old Format
Target List
A target list must be submitted in ELECTRONIC FORM.
The target list must be in plain ASCII text, and the columns MUST BE
SEPARATED BY TABS. NO spaces are allowed unless in the comment
field (see below) but then mandatorily enclosed within quotes.
Every entry in the target list needs to start with TWO tabs and MUST
contain the following information
in the order given below:
- Blank column
- Object Status:
- A string that is either D (Deferred), H (Hold), or blank (active)
- The PI should submit the targets as either active or on hold
- Program Number:
- In the form UTYY-N-XXX, where
YY is the 2-digit year (e.g. 01 for 2001),
N is the observing period within the year (1-digit integer), and
XXX is the 3-digit program number assigned by the TAC (e.g. 003; this is given
in the message sent to you by the TAC telling you about the fate of your proposal).
- Examples: UT01-1-001, PSU01-1-014, STA01-1-005
- Object Name:
- Remember to avoid spaces, for NGC 3379 use NGC3379 or NGC_3379
- For MOS setups, follow with W or E for West or East track
- Azimuth Restriction:
- For tracks that should only be done at one specific AZ give an E or W
- If no AZ restriction is required leave this field blank
- This is primarily for MOS, moving targets and synoptic targets
- For MOS targets this is required because the tracker rho ring is
limited to 180 degrees of rotation and thus east and west tracks will be
inverted as to PA. For far northern or southern tracks, there exists sufficient
rho angle travel to permit matching the PA in the east-track and west-track visits.
- See the Position Angle Calculator for more detail about PA and AZ restrictions
- Right Ascension:
- 12:05:36.1 (to 0.1 seconds of time)
- Declination:
- +33:29:08.7 (to arcsecond precision)
- Equinox:
- V Magnitude:
- Position Angle:
- Measured in degrees from north through east, including at least one
decimal place
- Use par for parallactic, not zero, as the recommended default PA
- See the Position Angle Calculator for more detail about PA and AZ restrictions
- Priority:
- Your priority will be that given to you by the TAC
- You may distribute your objects over the priorities assigned by the TAC,
or you may "oversubscribe" your top priority
- When your higher priority TAC allocation has been depleted, all
remaining active targets will be reassigned to lower priority
- RA Priority Modifier:
- This is reserved for a quantitative RA algorithm for highlighting
special urgency factors, which a more mechanistic execution of the queue could
well overlook. It helps promote delivery of whole data sets and HET partner equity, and helps prevent missed chances for scarce observing opportunity windows.
- Setup:
Maximum Seeing:
- The maximum acceptable delivered PSF on the sky, in arcsec
- For expected performance, consult our image quality histograms
Sky Brightness:
- Maximum acceptable sky brightness, expressed as a V-band magnitude
- Inclusion of real time V-band sky brightness measurements in the
night report is under development
- Do NOT leave blank
- Consult out HET sky brightness discussion
for details
Sky Transparency:
- Use either P (photometric), S (spectroscopic), or N (not spectroscopic),
do NOT leave blank
- In practice these correspond roughly to P=100-95%, S=95-50% and N=20-50% transmission
- HET closes under high dust, fire-smoke, or fog conditions
- Guider flux, DIMM flux, an IR zenithal cloud sensor, weather satellite
maps, dust gauges, a scanning wide-angle video camera, and
personal gauging are all used continually to monitor the status
- Exposure times are by and large not scaled for sky transparency,
with some allowance possible for significantly opaque yet borderline
productive conditions, provided that the scaling in no way vitiates
the scientific value
- Despite any possible scaling, for an accepted observation only the
exposure time given by the Phase II plan will be charged
Integration Time:
- The total shutter open time per visit, in seconds
- Please keep this number smaller than the
track length
at the target declination, and a good practice is to limit it to
one hour, because of filling factor and scheduling flexibility
- Occasionally the time may be slightly truncated due to end of
track, tight scheduling fits, unforeseen equipment or
weather interference, etc; truly shortchanged integrations will
not be charged
CRsplit:
- Number of sub-exposures in which to split the above integration time
- Subdividing into no longer than 20 min integration splits is important
for checking LRS focus and, at least with narrow slits, centering.
Splits also allow cosmic ray flagging.
- CRsplit of 1 means no subdivision, i.e. a single exposure
- Example: an 1800 exposure time with CRsplit 2 means two 900s exposures
Visits:
- Number of visits to execute
- Prescribed integration time and CRsplit will be used for each visit
Done:
- Initialized to 0
- The resident astronomers will increment as visits are executed
(and decrement for rejections)
- Because of CRsplits the resulting doneness can be non-integral
Moving Target:
- A boolean field Y or N whether the target is a moving target
- Do NOT leave blank
- Multiple sets of moving targets should use a group ID
- Each moving target entry should also include a SYN Date
- If required, a AZ entry can also be specified
SYN Frequency:
- It specifies the visit cadence in days for synoptic targets
- Use string RAND#-# for synoptic targets with repeat visits,
where the # gives a range on the desirable number of days between
visits
- A minimum frequency of 0 means that you do not mind having the target
observed in both East and West tracks.
- RAND1-7 means that the target repeat visits should occur at
a spacing of between 1 and 7 days; be aware that with high priority
and good observing conditions this can produce nearly all 1 day spacing
- Leave blank for non-synoptic targets
SYN Dates:
Group ID:
- For programs that require visits to multiple targets
- For all targets in a group give them a unique identifier, e.g. mygroup1
- Leave blank for ungrouped observations
Standard CALS:
- A boolean string Y or N indicates whether the
standard calibration set is necessary
- Calibration Information explains the
standard and some available nonstandard (special) calibrations
- Special calibrations must be listed in the Phase II submission form,
and may be charged to the PI if they take time away from science
within the night
Flux standard:
- Give the required quality class of flux standard in terms of
the HET scale from 1 to 4 (viz. standards
list)
- OR enter N meaning none is required
Radial Velocity standard:
- Give the required quality class of RV standard in terms of
the HET scale from 1 to 4 (viz. standards
list)
- OR enter N meaning none is required
Telluric standard:
- Give Y or N depending on whether a telluric standard is required (viz. standards list )
Skyflat:
Comments:
- If there are spaces, enclose in double quotes.
- Keep it as brief as possible, starting with anything vital to know about at the
time of execution, e.g. any request ("Take adjacent ThAr") or ID clarification
("Fainter star of close pair") or intention that might be misread from a finding
chart ("Transect BOTH nuclei with the slit").
- For blind offset setups, give the name of the .xy setup file.
- For MOS setups, give the name of the .cfg setup file.
- For MOS setups, also specify whether this is the West or East track.
- Users tend to confuse the intentions of the COMMENT and the Phase II printed
notes. COMMENT is for the most concise, vital, real-time
instructions necessary for the visit; not the lengthy tome that goes in
the Phase II printed notes.
- Format Examples:
COMMENT "Take
adjacent ThAr"
COMMENT template_exposure
We have created a few examples with different
formats to aid you in creating your own Phase II target list.
Last updated: Sun, 08 Jan 2012 03:41:58 -0600 caldwell
|
|
|
