From: ymei Date: Fri, 23 Apr 1999 16:10:54 -0700 (PDT) To: wire Subject: SO's response to DA's anomaly report SO's RESPONSE to DA's ANOMALY REPORT 3/5/99 to 4/15/99 by Yi Mei ****************************************************** ANOMALY REPORT ON "REAL" DATA FROM 3/5/99 TILL 4/15/99 by Olga Pevunova (WIRE mission) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Data gaps are mostly associated with limited room on disks in DPS. SO: N/A. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2. Long non-Dither Time: 04a0acb2(2sec) 04a0ad91(3sec) 04a0b0b1(3sec) 04a0b1b1(3sec) 04a114d0(3sec) 04a11011 04a10971 04a108f2 04a10991 04a10d71 04a10d91 04a110f2(1sec) 04a114d0 04a118f2(1sec) 04a11c11 04a11cf2(2sec) 04a11db2(1sec) 052120b1 0521ac31(3) 06108d91(3sec) 06109050(3sec) 0610a812(1sec) and many more... SO: Dave Shupe will solve this. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3. Bad predicted dither via dither table &Unsettled during frame 04a11c11(2) 04a11811(2) 04a11011(2) SO: There are several kinds of bad predected dither (dpd) problems. (1) 04a12811, 04a12c11, and 04a13812 have the same problem as above. All of those observations have some unsettled frames. Don't the why dpd. More obs: 04a23111, 04a23551, 05713517, 061099b2. (2) 04a21851, 04a219b2, 04a21db1,04a22151,04a22430,04a22930, 0510b171, 0510b411, 0510b4b1, 05110510, 05218530, 05713c90 0571a470, 05e18550, 0610a450, 06111891, 06111970. ACS data are missing. (3) 05211d70, 05719d91, 05e11d51, 05e19d71, 05e1b517, 06109d71, 0610b117, 0610b517, 0610b917, 06111d91, 06511d31, Tdx=Tdy=0 because timeline report missed the observations. Fan fixed the code. Now is okay. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4.No Stim Flashes: 04a11471-only 3 frames,first. 05218c71 - 8frames 05210c91-5 frames segm. 0610bc90-9 frames segm. SO: There are more observations missing stim flash. 05e1a450, 05110c91, 0571a470, 06510010... Most of the above stim flash missings are caused by data gap, either big gaps like hours or days, or small gap for only few obs, Some data gaps are very short, shorter than a segment. But if both the stim flash and the first frame of the next observation are missing, it is clear that data gap is still the reason. There is only one case that the stim flash is missing but the no missing frames in the next segment. We can not figure out any other reason then data gas to cause this. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 5. Delivery 1129 (obsid 04a1b991-04a23911) is weird(Ingest had problems) SO: N/A. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 6. About 6 unsettled frames in the beginning of the segm from time period: 3/17/99 22:57 --> 3/18/99 02:02 SO: Dave Shupe modified RTS for those survey_a and survey_e. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7. For slc_irregular segments in 057 day too many frames were produced purposely, what cause many different error messages in the Tom's table, like: bfseq bfrt bsfn(0) bsf bsfcoa(2). SO: Now RTS is modified. Less frames come in and the problem is gone. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 8. Bad RA and DEC error message (bradec) should be ignored in most cases, because in LMC segments or where were used biggest dither step(~15') difference between commanded RA&DEC and taken easily can be 1 degree. SO: There are several kinds of reasons for this bad RA and Dec. (1) Some _a and _e observations have strips. DA software still report as bad Ra and Dec. (2) If no CMDRA and CMDDEC (DA's bug, fixed), bradec will be reported. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 9. Bad spin(bspin) is not a problem, it generates this warning if spin is not equal 1 or 3 seconds, but for IRS segm or gyrcal spin time can be anything from 2 to 16 sec. SO: N/A. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 10. Some segments have one or two frames without ACS data , no STP: which cause many warnings in the table, like: bfseq lda(2) bcdi(1) bpd(2) {} bacs(1) 05218530(frame#2) 0610a450(last frame) 06111891(10th frame) 06111970(7th frame) 06512431(last frame) SO: N/A. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 11. Negative "dither" time & 2 stim flashes: 05218c31-looks like last frame was repeated(stim) twice. SO: Dave Shupe will explane this. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 12. Unsettled during taking data in: 061095d1(1first frame) 061099b2(one frame, before stim) SO: N/A. Russ and Joe's ACS data analysis? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13. when number of frames > 50, ignore warnings about not having stim flash and anything what goes with it, like:bsfn(0) bsf bsfcoa(2) because Tom's table oriented on less than 50 frames in normal segm. SO: RTS is modified. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 14. Large dither time: 06111c12 06512417-really weard looking tlm: large Dither time or No dither time with NO DITHER ANGLE 065124b7 - the same story... 065124d7 -"- 06512817 -"- all slc_irregular in delivery 1408 are like that... SO: Dave Shupe. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 15. Short dither time&Dither amplitude < 1 without changing Dither Index 04a0b112 04a0b4f2 061125b2 all AI 16x1 j segments SO: Dave Shupe. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 16. During segment went to ZSP mode: 05823530(after 5first frames) probably for "parking for weekend"(4/2/99 21:18) SO: N/A. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 17. During segment TSA mode is reached (added by Yi). SO: Moon got into FOV of star tracker during moon_test or other similar observations. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Yi Mei