@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ @ @ MTA Monitoring Report 7/07/00 - 7/13/00 @ @ @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Archive of all weekly reports http://asc.harvard.edu/mta/REPORTS/weekly.html Archive of Monthly reports http://asc.harvard.edu/mta/REPORTS/MONTHLY ************ Radiation ************* We violated the Costello Kp 6 limit Mon, 10 Jul 2000 04:06:01 EDT. in response we change the alert thresholds, defining 5.5 as a yellow, or email alert and 6.5 as a red or pager alert. No other action was taken. We violated all non-chandra limits, Costello, Airforce Kp, Orbital fluence, adn 2 hour fluence. During the morning of 13 Jul EDT. Chandra was put into an SI-Safe mode (SCS 107) at 195:1128 and restarted Science operations at 196:0447 ************ CTI trend ************* Although we observed higher CTI on Jul 4 and 6 due to higher focal plane temperature, no significant deviations are observed this reporting period. Software note: We found a cause of difference between MIT and CXC cti errors. The modification will be implemented as soon as possible. *********** ACIS Focal Temperature ******** For this period, the higher temperature observation (-110.5) finished on DOY 188.67, and three peaks are observed. Day (DOY) Temp (C) Width (DAY) 188.82 -110.5 0.29 191.5 -110.3 0.28 193.1 -111.3 0.26 The widths are slightly wider than the previous several periods. It was around 0.24 previously. ************** MTA Problem Tracking ***************** One new msid was tripped: AOMOMMON (pcad): SPACECRAFT MOMENTUM MONITOR FAULT FLAG the following had been seen commonly: AWD3TQI, AWD1TQI, AWD4TQI,AWE2TQI, AWD5TQI, AWD6TQI These limit trips are expected when running SCS #107 while in Normal Pointing Mode (thanks Jeff Shirer) Other warnings were issued for (they were already opened previously): 2LLDIALV, AOPSAMUL, ESAPYI ******** Trending *********** Some of HRMA system temperature gradients show large scattering this period. OBA Cone and TFTE are those show the scattering most. ************* Telemetry *********** Two yellow warnings which we usually do not see reported on 7/13: 1DPICBCU (DPA INPUT CURRENT B): 40.40% yellow; around 0.24 TSCIUSF1 (SC-IUS FITTING-1 TEMP): 46.69% yellow; green to yellow (348.12C) *********** Photon Page ************ BSID DETECTOR GRATING TARGET ANALYSIS - --------------------------------------------------------- 732 ACIS-I NONE SN1005-NE OK 943 ACIS-I NONE MBM 12 OK 933 ACIS-S NONE 1WGA J1340.1+2743 OK 615 ACIS-S NONE VB8 OK 789 AICS-S NONE HCG 92 OK 117 AICS-I NONE 249B OK 945 ACIS-I NONE GALACTIC CENTER ARC OK 666 ACIS-I NONE 1736-297 OK 800 ACIS-S NONE CBSS OK 628 ACIS-S NONE HD 135379 NO ANALYSIS 538 AICS-I NONE A1423 OK 399 ACIS-S NONE NGC 4314 OK 1779 AICS NONE G21.5-0.9 OK 607 HRC-I NONE WR 147 OK ******** Notes from experts *************** Bad Column in ACA CCD Tom Aldcroft It appears that there is a bad column in the ACA CCD. The column number is 454. This is manifested as a single column where the response of the CCD is reduced relative to the average CCD response. I haven't quantified the reduction, but it is enough to cause centroiding errors of up to 2 arcsec. Based on experience with optical telescope CCDs, applying a 'flat-field correction' (i.e. adjusting the response map) will probably NOT fix the problem sufficiently to allow high-accuracy centroiding. I have verified large centroiding errors in images (from different obsids) which range from row = -22 to row = -282. However, there is no problem for two star observations with row < -442. Between this range I found no data. Therefore, I recommend that we declare a new bad region covering the range row = [-1, -441], column = 454. For the ACABPL (bad pixel list) ARD, this should be a new entry with type=OTHER, row0=-441, row1=-1, col0=454, col1=454 ta: type : int : Catagory (DEAD,WARM,HOT,OTHER) : pixel : type :0: 0:0:0 ta: row0 : int : Min. row boundary : pixel : row0 :0: 0:0:0 ta: row1 : int : Max. row boundary : pixel : row1 :0: 0:0:0 ta: col0 : int : Min. col boundary : pixel : col0 :0: 0:0:0 ta: col1 : int : Max. col boundary : pixel : col1 :0: 0:0:0 This should be entered into the OFLS CHARACTERISTCS as well. If I understand the format, we need a new line in theODB_AC_BAD_PIXELS list which reads -441,-1,454,454, I find it pretty curious that there is already an entry for column 454 on the *positive* rows side: ODB_AC_BAD_PIXELS = 12,12,-68,-68, 0,9,449,449, 426,430,-164,-164, 227,230,454,454, -512,511,0,-1, -1,0,-512,511, 376*0,