|
Planning Notes - Synoptic And Monitoring Activities
This is the CDS schedule for regular monitoring and calibration activities. The Studies are defined below.
When entering these Studies in mk_plan, please ensure that the following is done:
- the OBJECT field is set to one of QS/AR/CH/LMB (but to SYN for the synoptic meridian scans only)
- the OBJ_ID is loaded with an appropriate specific identifier e.g. if there is an AR number
- the SCI_OBJ field should start with the word SYNOPTIC and continue with any additional
information necessary (For the daily SYNOP the line "Synoptic meridian images" is good.)
See XSTUDY or previous runs using XCAT for details of any Studies.
Please stick to this schedule as much as possible. It is recognised that
these Studies cannot be run in exceptional circumstances such as low-rate
telemetry weeks.
Due to temperature effects, it is preferable, though not essential, for
the pointing to be well onto the Sun for at least half an hour prior to the SYNOP runs.
Title
|
SYNOPTIC SCAN
|
Dates
|
Run ONCE PER DAY as near to 00:00 UT as possible
|
Contact
|
Andrzej Fludra (A.Fludra@rl.ac.uk)
|
Activity
|
N-S scan in several lines running down central meridian.
|
Studies
|
SYNOP_F (Study ID 37, Var 4) [Assumes medium telemetry, i.e. 11.3 kbit/s. If
high rate run SYNOP_HI, Study ID 37, Var. 2 instead].
|
Duration
|
6.5 hours
|
Pointing
|
Encoded in study definition
|
Notes
|
On a day when USUN_4 is
scheduled, run a shorter SYNOP_G5 (ID 219, var.1).
|
TOP OF PAGE
|
|
Title
|
CONTAMINATION CHECK (QCM READING)
|
Dates
|
Run ONCE PER DAY DURING A DSN CONTACT
|
Contact
|
Jeff Payne
|
Activity
|
QCM reading
|
Studies
|
Acronym 'ENG' (and the title 'Run Anytime') in planning tool
|
Duration
|
-
|
Pointing
|
Encoded in study definition
|
Notes
|
- Insert as time-tagged study
- This study will be lost if run outside DSN contact
- !!!!! NEVER run QCM studies as the last study of the day!!! The pointing of the
following study on the next day will be WRONG !!!!!
- When 'ENG' is inserted immediately before a GIS study, it may include the lookup
table loading for that GIS study and the duration of 'ENG' increases by ~30
minutes. Do not be alarmed, this is normal
- ENG should *not* be run directly before engineering studies (such as NIMCP,
GIMCP, FULLCCD).
|
TOP OF PAGE
|
|
Title
|
GIS MCP SENSITIVITY MONITORING
|
Dates
|
Run TWICE PER WEEK on Quiet Sun
|
Contact
|
Lucie Green (lmg@mssl.ucl.ac.uk)
|
Activity
|
Wide/narrow slit comparison for mapping sensitivity degradation of GIS detectors
|
Studies
|
GIMCP_1B (Study ID 1, Variation 2; GSET=87) followed immediately by GIMCP_2 (Study ID 2, Variation 1; GSET=90) at same pointing
|
Duration
|
3.5 min and 20 s, not including table loads.
|
Pointing
|
Quiet Sun
|
Sequence
|
GIMCP_1B (Study ID 1, Variation 2; GSET=87) followed immediately by GIMCP_2 (Study ID 2, Variation 1; GSET=90) at same pointing
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
NIS MCP SENSITIVITY MONITORING
|
Dates
|
Run THREE TIMES PER WEEK on Quiet Sun
|
Contact
|
Bill Thompson - thompson@orpheus.nascom.nasa.gov
|
Activity
|
NIS wide/narrow slit comparison for mapping sensitivity of VDS.
|
Studies
|
NIMCP (Study ID 61, Var. 1)
|
Duration
|
17 min.
|
Pointing
|
Pointing must be completely on the solar disk, in a featureless area of quiet Sun
|
Notes
|
- Try to spread the NIMCPs throughout the week, e.g., run them on Monday,
Wednesday & Friday. The weekend is also possible
- This study should also be run after CDS sees a flare - either inadvertently or by
desire (point to a quiet sun area)
|
TOP OF PAGE
|
|
Title
|
CDS QUIET SUN SPECTRAL ATLAS
|
Dates
|
Run ONCE PER WEEK on Quiet Sun
|
Contact
|
Peter Young (p.r.young@rl.ac.uk) , Lucie Green (lmg@mssl.ucl.ac.uk)
|
Activity
|
NIS and GIS full spectral atlases on a quiet Sun region, for detailed
spectral information and instrument monitoring
|
Studies
|
GISAT/v2 (GSET_ID=82, quiet Sun), NISAT_S/v2
|
Duration
|
2hr 30min (including table load for GIS)
|
Pointing
|
Choose a patch of quiet Sun close to Sun centre. Use ame pointing for
both studies
|
Sequence
|
Run GISAT followed by NISAT_S with exactly the same pointing
|
Notes
|
GISAT must be run first, and *must* be time-tagged
|
TOP OF PAGE
|
|
Title
|
NIS FULL CCD STUDY
|
Dates
|
Run ONCE PER WEEK on Quiet Sun
|
Contact
|
Bill Thompson - thompson@orpheus.nascom.nasa.gov
|
Activity
|
Full NIS CCD read out test activity
|
Studies
|
FULLCCD (Study ID 15, Var. 3)
|
Duration
|
25 min
|
Pointing
|
Quiet Sun
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
FULL SUN SCAN
|
Dates
|
Once every month, on the 2nd Monday of the month.
|
Contact
|
Bill Thompson - William.T.Thompson.1@gsfc.nasa.gov
|
Activity
|
Multi-pointed raster/scan of full solar disc
|
Studies
|
FSUN (Study ID 40, Var. 1)
|
Duration
|
11 hours
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
FULL SPECTRAL FULL SUN SCAN
|
Dates
|
Run at least ONCE PER MONTH, preferably TWICE PER MONTH.
|
Contact
|
Bill Thompson - William.T.Thompson.1@gsfc.nasa.gov
|
Activity
|
Undersampled full Sun scan, returning full NIS spectrum
|
Studies
|
USUN_4 (Study ID 271, Var. 1). This study must be run 03:40 - 23:40 UT
|
Duration
|
20 hours
|
Pointing
|
Pointing is encoded in study definition
|
Notes
|
Run the shorter **SYNOP_G5** before USUN_4
|
TOP OF PAGE
|
|
Title
|
CORONAL HOLE SPECTRAL ATLAS
|
Dates
|
Run ONCE PER MONTH ON OR NEAR THE 20TH, when a coronal hole can be clearly identified
|
Contact
|
Andrzej Fludra (A.Fludra@rl.ac.uk)
|
Activity
|
Regular spectral atlas in a coronal hole region
|
Studies
|
NISAT_S (Study ID 17, Var. 2)
|
Duration
|
58 m
|
Pointing
|
Point at a coronal hole
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
ACTIVE REGION HOLE SPECTRAL ATLAS
|
Dates
|
Run ONCE PER MONTH ON OR NEAR THE 20TH, when an active region can be clearly identified
|
Contact
|
Andrzej Fludra (A.Fludra@rl.ac.uk)
|
Activity
|
Regular sampling of an active region atlas
|
Studies
|
NISAT_S (Study ID 17, Var. 2)
|
Duration
|
58 m
|
Pointing
|
Point at a coronal hole
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
GIS Meridian Study (SPECT_4)
|
Dates
|
Tuesday, 19:15 - 24:00 UT
|
Contact
|
Lucie Green (lmg@mssl.ucl.ac.uk)
|
Activity
|
Run GIS study SPECT_4 (GSET ID: 82, quiet region).
|
Studies
|
SPECT_4 (GSET ID: 82, quiet region)
|
Duration
|
~4.5 hrs (including lookup table upload).
|
Pointing
|
Pointings are already encoded in the study definition (along the central meridian)
|
Notes
|
If the date or time clashes with a JOP or campaign, then the study can
be moved to another date or time during the week
|
TOP OF PAGE
|
|
Title
|
NIS MCP SENSITIVITY SCAN
|
Dates
|
Run once per month, in the first 'FULL' week of the month. ** Notify GSFC operators before running **
|
Contact
|
John Rainnie (J.A.Rainnie@rl.ac.uk)
|
Activity
|
Wide slit exposures taken during slewing of OPS to average intensities in quiet Sun
|
Studies
|
FFCAL_5 (ID 222, var. 1) run in NRT with OPS commanding. Notify the operator
|
Duration
|
1 hour
|
Pointing
|
Choose pointing to avoid active regions (the study makes one leg of an
X across the sun - the operator can choose the direction to be
\ or /. The pointing value refers to the centre of the path)
|
Sequence
|
Sequence
|
Notes
|
- Make sure FFCAL_5 is time-tagged, and the study following it has to be
time-tagged as well
- Notify GSFC operators before running
|
TOP OF PAGE
|
|
Title
|
GIS MCP SENSITIVITY SCAN
|
Dates
|
Run once per month, in the first 'FULL' week of the month. ** Notify GSFC operators before running **
|
Contact
|
Lucie Green, lmg@mssl.ucl.ac.uk
|
Activity
|
Monitor the variation in sensitivity of each GIS detector.
|
Studies
|
GIMCPS1/v1, GSET=82 (quiet Sun), duration: 1hr 21min, + 30min for table load
|
Duration
|
2 hours
|
Pointing
|
A quiet Sun region. Do not use several pointings!
|
Notes
|
- The planner should confirm with the GSFC operators at the beginning
of the planning week a date and time for this study to be run.
The date given in the weekly schedule above is only a suggested date
- The GIMCPS1 study, and the one following it, must be time-tagged
- Only run the study once. Do not perform repeats of the study
|
TOP OF PAGE
|
|
Title
|
GIS GSET MONITORING - QUIET SUN, SLIT 2
|
Dates
|
To be run once per month
|
Contact
|
Paul Kuin (npmk@mssl.ucl.ac.uk), Peter Young (p.r.young@rl.ac.uk)
|
Activity
|
A GSET monitoring programme for the 4"x4" GIS slit
|
Studies
|
GISAT/v2 (Quiet Sun/Zone 4; GSET=82) GISAT/V2 (Quiet Sun/Zone 4; GSET=84)
|
Duration
|
-
|
Pointing
|
A quiet Sun region.
|
Sequence
|
The first GISAT should be time-tagged; each GISAT should be run once each.
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
GIS GSET MONITORING - ACTIVE REGION, SLIT 2
|
Dates
|
To be run once per month
|
Contact
|
Paul Kuin (npmk@mssl.ucl.ac.uk), Peter Young (p.r.young@rl.ac.uk)
|
Activity
|
A GSET monitoring programme for the 4"x4" GIS slit
|
Studies
|
GISAT/v2 (Active Region/Zone 5; GSET=83) GISAT/V2 (Active Region/Zone 5; GSET=85)
|
Duration
|
-
|
Pointing
|
An active region.
|
Sequence
|
The first GISAT should be time-tagged; each GISAT should be run once each.
|
Notes
|
-
|
TOP OF PAGE
|
|
Title
|
INTERCALIBRATION 1
|
Dates
|
To be run once per month
|
Contact
|
CDS Planner (cdsplanner@grace.nascom.nasa.gov),
EIT Planner (eit@grace.nascom.nasa.gov)
|
Activity
|
CDS to run this once a month even if no-one else is
running with us, i.e. for our own calibration and
monitoring work
|
Studies
|
ICAL1_G (Study ID 14, Var. 1, GSET_ID=82, quiet region),
ICAL1_N (Study ID 13, Var. 20 ***PLEASE MAKE SURE IT IS
VARIATION 20! ***), and NISAT_S (50 s exposure)
|
Duration
|
Total duration 2-3 hours.
|
Pointing
|
The EIT default pointing is (0,0). The CDS planner should send
an e-mail to confirm this pointing or change it by the morning
(EST) before the ICAL. The e-mail should go to;
- soc@esa.nascom.nasa.gov
- planner@lasco6.nascom.nasa.gov
- eit@grace.nascom.nasa.gov
|
Sequence
|
Run ICAL1_G (Study ID 14, Var. 1, GSET_ID=82, quiet region),
followed by ICAL1_N (Study ID 13, Var. 20 ***PLEASE MAKE SURE
IT IS VARIATION 20! ***), and repeat this sequence three times
at the same pointing (i.e., keep alternating between GIS and
NIS). Finish with full atlas NISAT_S (50 s exposure)
If running with SUMER,
use the following order instead, ICAL1_G (before SUMER starts,
to ensure GSETS loaded), then starting with SUMER, ICAL1_N four
times, followed by ICAL1_G twice. This is to ensure coincident
timing with similar lines. This assumes that the SUMER running
order is 584, 629, 629, 624, 770, 770 Angstrom
|
Notes
|
DO NOT select campaign #500 for this study
|
TOP OF PAGE
|
|
From the CDS Operations Management Team in the Space Science & Technology Department at
CCLRC Rutherford Appleton Laboratory
Site maintained by
John Rainnie.
Last revised on Wednesday (27/May/2009) at 17:00.
|
|