RADMON threshold crossing and Rad-zone preparation

Meeting time:
  Tuesday, 26 August 2003, 3:00pm EDT
Telecon #:
  405-244-5060, 1165#

Next meeting:
  Tuesday, 02 September 2003, 3:00pm EDT

===========================================================================

Agenda:
1) Review data from recent rad-zones and set pad-time for SEP08103 week
2) RADMON patch schedule
3) Pad-time plans - CRM derived pad-time usage
4) Progress on action items


1) Review data from recent rad-zones and set pad-time for SEP08103 week
- SEP0803 week is days 251 to 258
- No change in EPHIN P4 or E1300 on ingress or egress from their
recent behavior
- solar-wind speed prediction is for starting at~600km/s and gradually
declining
- Expect RADMON patch to be on-board so plan to rever to the prior
scheme of pads. Known added observing time viewed as winning over
possible loss of observing from not making the uplink and getting a
RADMON trigger.

The group recommends the following for pad times:
 10ks before the minimum of EE1RADZ or 6hours from perigee on entry
 10ks after XE1RADZ on exit


2) RADMON patch schedule
- Plan to uplink and test patch during a comm starting at
2003:245:22:10UT (evening Tues Sep 2). 
- SEP0103 loads being built with SCS-107 enable assuming this comm
- CAP to do test is ready and expect to do CAP-review on Thursday


3) Pad-time plans - CRM derived pad-time usage
- Need to check CRM pad time against the recent rad-zone entry
history. We don't want to find out the the proposed pad-times would
lead to RADMON triggers
- HRC team needs to assess impact of proposed CRM pad-time on
MCPs. Plan to examine EPHIN rates during the added intervals and use
previously determined scaling relations to predict HRC
performance. 
- Analysis of HRC MCP rates versus CRM/ACE-P3 indicates that ~35% of
the time is affected by variable backgrounds at CRM fluxes near the
GLBs proposed for determining the pad times. Not all the time
recovered may be good for science goals. Preferentially scheduling
grating observations around rad-zone entry/exit may reduce background
problems. 

4) Progress on action items
AI-9) R. Cameron - Investigate what inputs to the AE8 model are needed
to make far-future predictions of the AE8 rad-zone 
- Rob has an initial version of code to do this. Need to verify
against historical record

AI-10) E. Martin - Take an initial look at possible software mods to
RADMON to achieve "double layer" protection (i.e. double set of
thresholds, selectable by command or second instantiation of the
RADMON process).
- No new progress

AI-13) K. Gage - get long-range (to 2015?) AE8 entry/exit predicts from
OFLS
- Using a year 2005 OFLS generated ephem (from STK state-vector)
managed to get file with no un-matched events. Will try to do same
with 12 years.

AI-23) M. Juda - coordinate patch request for changing from 3 samples to
10 samples
- The patch was approved for uplink at the Aug 21 FD/Level-II
Board. Action will be closed by uplink and test of patch.

AI-25) M. Juda - generate added fluence data for the "Unsafe ACIS" study
- Distributed results on 8/20, see:
  http://hea-www.harvard.edu/~juda/memos/radmon/missed_safing_fluence.html


New Actions
-----------
J. DePasquale - provide pad-times we would have used in the past
J. DePasquale - perform CRM pad-time comparison to recent data
M. Juda - coordiante HRC team on determining the impact on the HRC to
using the CRM derived pad-times