1. UVIS TEAM MEETING 7/2005 1 Instrument Status On/Off Cycle: 26 Hours On: ~43000 hours –~4500 hours since last shut down (probe relay) HDAC Filament Modulation: –Filament 1: 86.12 hours –Filament 2: 12.22 hours

2. UVIS TEAM MEETING 7/2005 2 FSW Status ISA Z70771 –Fixed by FSW patch in C24 –Fixed by FSW V1.3 starting C31 ISA Z86939 (bad EUV data in S11 icylon) –Probably FSW problem –Affects all icylon in S11 and the first icylon in S12 S12 IEB patched for Enceladus encounter S13 and S14 IEB updated –Identification of the problem EUV.WIN1=14, 48, 1, 560, 1023, 2 16-pixel repeat pattern

3. UVIS TEAM MEETING 7/2005 3 ISA Z86939

4. UVIS TEAM MEETING 7/2005 4 ISA Z86939

5. UVIS TEAM MEETING 7/2005 5 ISA Z86939 (EM test) Compare the EUV and FUV indirection tables –They are identical Test using a Hg lamp (FUV channel) –Could not reproduce

6. UVIS TEAM MEETING 7/2005 6 ISA Z86939 (Hg lamp test) Extracted from 14, 48, 1, 512, 1023, 2 Extracted from 0, 63, 1, 0, 1023, 1 14, 48, 1, 560, 1023, 2

7. UVIS TEAM MEETING 7/2005 7 ISA Z86939 (Hg lamp test) 0, 63, 1, 0, 1023,1 14, 48, 1, 560, 1023, 2 14, 48, 1, 512, 1023, 2

8. UVIS TEAM MEETING 7/2005 8 GSW Issues EUV and HDAC records are coalesced in DAPS (report #38) –Reported at the last team meeting –Has been fixed –But data has not yet been re-ingested into DAPS –Conditions generating the problem: A trigger generates only one source packet onboard the S/C The packet is not full There are no configuration changes in the next trigger –Affects all data set meeting the above conditions prior to Feb 5 2005

9. UVIS TEAM MEETING 7/2005 9 GSW Issues Incompatibility between FSW and GSW (report #40) –Data appears shifted –Happened when (window dimension) modulo (window binning) is not 0 –Fixed and the affected data have been re- ingested –Identification of the problem has been added to IEB check software and subsequence checklist

10. UVIS TEAM MEETING 7/2005 10 Operational Issues HVPS turned off –IEB build with HDAC and HSP HVPS off –Affected All icylon & icymap in S08 (HDAC) Starring part of the AlpVir calibration in S08 (HDAC and HSP) –Identification of the situation has been added to IEB check software and subsequence checklist

11. UVIS TEAM MEETING 7/2005 11 Operational Issues Data is partially zeroed –Not enough time left between end of last integration and next trigger –Affected: UVIS_00CSA_AURORA001_PRIME in S07 –We have developed a program to identify trigger/integration timing issues

12. UVIS TEAM MEETING 7/2005 12 Other Issues High background during dust crossing –Affects all four detectors Data misdirected to row 0 –Seems to affect FUV only

13. UVIS TEAM MEETING 7/2005 13 Dust Crossing in S10 “Hazardous” part of the dust crossing was from 2005-104T22:11 to 2005-104T22:16 (G ring)

14. UVIS TEAM MEETING 7/2005 14 Dust Crossing in S10 FUV profile at 2005-105T00:08:00

15. UVIS TEAM MEETING 7/2005 15 Data Misdirection System Scan 2004/332

16. UVIS TEAM MEETING 7/2005 16 Data Misdirection Seems to be FUV only The same spectral positions are always illuminated Depends on the spatial position of the bright object System Scan 2004/310

17. UVIS TEAM MEETING 7/2005 17 Triggers Generation Process End of SOPU Start SSUP Run PDT on SOPU integrated sequence Merge short form files Generate triggers in sync with S/C movements Merge with IEB expansion (uvis_pef) Generate SSR loading and trigger timing reports Check IEB and reports Manually edit triggers and/or IEB until satisfy Starts about 11 weeks prior to execution, about 3 weeks prior to first delivery

18. UVIS TEAM MEETING 7/2005 18 Triggers Generation Process SSG SCR Manually edit triggers and/or IEB and generate reports until satisfy Check subsequence and IEB using delivery checklist (2 pairs of eyes) Deliver subsequence PSIV2 SCR And SAP Manually edit triggers and/or IEB and generate reports until satisfy Delta check subsequence and IEB using PSIV2 checklist Deliver Subsequence and IEB About one week prior to first delivery and 8 weeks from execution

19. UVIS TEAM MEETING 7/2005 19 Planning/Sequencing Issues At the start of the SOPU we too often find problems with CIMS requests. Some problems are found later on in the process –More difficult to fix then Two Major issues –Riders do not match the primes (start and duration) –Setups are not defined Saturn/Titan –Is it possible to define a set standard setups? –Or give us the rules used to defined the setups? –We seem to be re-inventing the wheel at each sequence

20. UVIS TEAM MEETING 7/2005 20 New Products SSR Loading Prediction –How to best use it? –Shall it be published on the team web site? SCET CIMS Label I... SSR loading +-------------------+------------------------------ E... +--------------------------+ B... Indiv. Curr. CIMS Delta 2005-243T00:51:40.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 5.14 5.14 29.06 23.91 2005-243T02:18:33.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 1.04 6.18 29.06 22.88 2005-243T02:49:40.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 5.14 11.33 29.06 17.73 2005-243T04:16:33.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 1.04 12.36 29.06 16.70 2005-243T04:47:40.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 5.14 17.51 29.06 11.55 2005-243T06:14:33.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 1.04 18.54 29.06 10.52 2005-243T06:45:40.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 5.14 23.69 29.06 5.37 2005-243T08:12:33.00 UVIS_014RI_FMONITOR003_CIRS_T 15... 1.04 24.72 29.06 4.34

21. UVIS TEAM MEETING 7/2005 21 Notes on DAPS IDL routines The accuracy of the SCLK to SCET conversion depends on which version of convert_sclk.pro is used. Currently you should be running version 1.9 The version number is at the top of the file ; ;$Header: /cassini2/uvis_fm/daps_tools/RCS/convert_sclk.pro, v 1.9 2005/07/11 15:28:18 uvis_fm Exp uvis_fm $ ;