RADMON threshold crossing and Rad-zone preparation Meeting time: Tuesday, 22 July 2003, 3:00pm EDT Telecon #: 405-244-5060, 1165# Next meeting Tuesday, 29 July 2003, 3:00pm EDT =========================================================================== Agenda: 1) Review data from recent rad-zones and set pad-time for AUG0403 week 2) RADMON patch 3) Progress on action items. 1) Review data from recent rad-zones and set pad-time for AUG0403 week ---------------------------------------------------------------------- - AUG0403 week is days 216-223 - No change in recent threshold-crossing behavior on ingress or egress for P4. There is a suggestion in the E1300 data of fewer threshold crossings at early-times relative to perigee. - solar-wind speed forecast is for the week to start at ~500km/s and gradually drop until day 220, at which point it jumps to ~600-800km/s The group recommends no change to pad times: 11hrs before perigee on entry 10ks after XE1RADZ on exit 2) RADMON patch --------------- - Initial draft of patch request is available at http://hea-www.harvard.edu/~juda/memos/radmon/k-constant_change.txt - In e-mail prior to the meeting Dan Shropshire asked about: a) on-orbit testing (what is the plan) b) ASVT testing c) Why change all channels when we are mostly concerned with P4GM a) During OAC, and again after updating the RADMON process in Dec 1999, we performed an on-orbit test which demonstrated that the RADMON process would trip when each of the monitored channels exceeded its threshold for the required number of samples. This was done by repeated uploads to EPHIN to force it report a specified number of counts on several consecutive frames. We would likely repeat this. Eric pointed out that all RADMON K-constant patches were confirmed by on-orbit test in the past. b) We don't have any real capability in ASVT to test RadMon changes/updates. This is why we've conducted on-orbit tests in all previous cases. c) Setting all KR.Mon_Delay(HI,..,..)=10 is a good idea, since ~10 min is a reasonable above-threshold period in all cases (given that the SIs have said they can tolerate the extra dose). This does increase the risk when the radiation levels are just on the borderline, going above & below threshold, since it will be harder to trip RadMon. However, this is a low risk, since if, e.g., P4GM is hovering at the threshold, it is unlikely that E1300 is doing the same. Because we are monitoring both electron & proton channels, we can still expect to detect significant radiation events with a 10 min criterion vs. a 3 min one. Changing E1300 in addition to P4GM provides additional protection against the electron events. Brief, hard X-ray flares might also generate signifcant signals in the E1300 and P41GM channels which we would not wish trigger RADMON on. 3) Progress on action items --------------------------- AI-6) K. Gage to coordinate end-to-end test of CRM derived pad-times so we can begin to use for rad-zone exit - K. Marsh to generate products AI-9) R. Cameron - Investigate what inputs to the AE8 model are needed to make far-future predictions of the AE8 rad-zone - On hold subject to outcome of AI-13 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 progress AI-13) K. Gage - get long-range (to 2015?) AE8 entry/exit predicts from OFLS - Issue with missing AE8 events was resolved and a second attempt may have been made but Ken has to check AI-19) Bill Blackwell/Joe Minow: examine change in IMP-8 solar wind proton flux with solar cycle phase. - No progess reported AI-23) M. Juda - coordinate patch request for changing from 3 samples to 10 samples - Initial draft of patch request prepared and discussed at this meeting